How to assure that my MVS debugging tool does not limit creating a full SYSMDUMP?
search cancel

How to assure that my MVS debugging tool does not limit creating a full SYSMDUMP?

book

Article ID: 11151

calendar_today

Updated On:

Products

Datacom DATACOM - AD Ideal CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC Easytrieve Report Generator for Common Services INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware

Issue/Introduction



How to assure that my MVS debugging tool does not limit creating a full SYSMDUMP?

 

Environment

z/OS

Resolution

To dynamically disable an MVS debugging tool that could prevent creation of a full SYSMDUMP, you can add any of the DD DUMMY JCL statement(s) for the related product to your runtime execution:

 //IDIOFF DD DUMMY IBM FAULT ANALYZER OFF       
 //IDIREPRT DD DUMMY IBM FAULT ANALYZER OFF 
 //ABNLIGNR DD DUMMY ABEND-AID OFF
 //ESPYIBM DD DUMMY EYE-SPY OFF
 //CAOESTOP DD DUMMY CA-OPT II & CA-SYMDUMP OFF
 //DMBENAN DD DUMMY TURN OFF DUMPMASTER
 //PSPOFF DD DUMMY TURN OFF SOFTWORKS PERFORMANCE ESSENTIAL