How to override the default dataset name for MSM transaction dumps.

book

Article ID: 49181

calendar_today

Updated On:

Products

CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA Mainframe Software Manager (Chorus Software Manager) CA MICS Resource Management CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD

Issue/Introduction

You can override the default dataset name for these transaction dumps. In your HLQ.SAMPLIB(MSMLIB), this is referenced on the STDENV DD statement in the MSMTC startup procedure, at the end of this member you should see export IBM_JAVA_ZOS_TDUMP.

You change it to:
export IBM_JAVA_ZOS_TDUMP=ALL
and also code:
export JAVA_DUMP_TDUMP_PATTERN="HLQ.DUMP" where HLQ.DUMP is the high level qualifier for the transaction dump dataset.

Environment

Release:
Component: MSM