CD SET,{NODUMP }
{OVER }
{ADD }
{SDUMP[=(option[,option]...)] }
[,Q={YES|NO}]
[,TYPE={XMEM|XMEME}]
[,BUFFERS={nnnnK|nnnM}]
[,AUXMGMT={ON|OFF}]
[,MAXSNDSP=sss]
[,MAXSPACE=xxxxxxxxM]
[,MSGTIME=yyyyy]
[,DEFERTND={YES|NO}]
[,SYSFAIL,STRLIST=(s-option[,s-option]...)]
[,NODUMP|OVER|ADD]
{{SYSABEND}[,SDATA=(option[,option]...) ][,NODUMP] }
{{SYSUDUMP} |,PDATA=(option[,option]...) |,OVER }
|,ADD
{SYSMDUMP[=(option[,option]...)][,NODUMP] }
|,OVER
|,ADD
{ABDUMP,TIMENQ=yyyy}
Where s-option represents:
STRNAME=strname
[,CONNAME=conname ]
[,ACCESSTIME={ENFORCE|NOLIMIT|NOLIM} ]
[,LOCKENTRIES ]
[,USERCNTLS ]
[,EVENTQS ]
[,(EMCONTROLS={ALL|(list))} ]
[,({COCLASS|STGCLASS|LISTNUM}={ALL|(list)} ]
[ {[,ADJUNCT={CAPTURE|DIRECTIO}][,ENTRYDATA={UNSERIALIZE|SERIALIZE}]} ]
[ {[,SUMMARY] }) ]
You cannot specify other parameters when specifying NODUMP. For example, you can specify CD SDUMP,NODUMP, but not CD SDUMP,Q=YES,NODUMP.
By quiescing most system activity during SVC dump global storage capture, the dump will contain a more consistent image of the state of the system. However, when collecting large amounts of data, the system can appear to be hung or sluggish.Using Q=NO reduces the impact to system availability, but may impact serviceability.
The CHNGDUMP quiesce (Q=YES|NO) setting overrides any QUIESCE specification made on the SDUMP or SDUMPX macro invocation.
However, if no Q= setting was specified for the CHNGDUMP command during the IPL, the QUIESCE specification on the SDUMP or SDUMPX macro invocation prevails. Note that if the QUIESCE option is omitted on the macro invocation, then the default is QUIESCE=YES.
A large BUFFERS value can improve the performance of collecting SVC dump data; however, it tends to negatively impact the general system performance, because it might reduce the number of real storage frames available to other applications.
For systems where large SVC dumps are typically generated, it is suggested to set MAXSPACE as 8000 megabytes.
If the system is reset to be dispatchable because the system has been kept non-dispatchable longer than sss seconds, a SNAPTRC is issued. You can use the WORKSHEET option in IPCS to view this SNAPTRC.
The CHNGDUMP command only provides two ways to change the MAXSPACE value: by using the SET,SDUMP invocation as described here; or by using the RESET,SDUMP invocation that resets all initial SDUMP parameters, including setting the MAXSPACE value to 500M.
You cannot delete this option with CHNGDUMP DEL. To change the value of MSGTIME, issue the CHNGDUMP command in the SET mode with a new value. If you change the MSGTIME value after the message IEA793A appears, the new value will be in affect immediately. If you set the MSGTIME value to 0, the system will not issue the message and it deletes the captured dump.
DEFERTND is specified in DUMP reply or in IEADMCxx | DEFERTND= is specified in DUMP reply or in IEADMCxx as: | DEFERTND= is specified by CHNGDUMP command as: | Result of DEFERTND is: |
---|---|---|---|
Used | Yes | Yes | Yes |
Used | Yes | No | Yes |
Used | No | Yes | No |
Used | No | No | No |
Not used | - | No | No |
Not used | - | Yes | Yes |
When ACCESSTIME=NOLIMIT is specified, the dump time limit is not in effect and the system will hold structure dump serialization until processing is completed.
(start1-end1,value2,start3-end3, …)
COCLASS is valid only for a coupling facility cache structure. If specified for a coupling facility list structure, the structure is not included in the dump.
When COCLASS=ALL is specified, the cast-out class controls for all cast-out classes are dumped along with the directory information for all entries within the classes (if SUMMARY is not specified).
When COCLASS=(list) is specified, the cast-out class controls for (list) are dumped along with the directory information for the entries in the requested cast-out classes (if SUMMARY is not specified). The values specified in a range are the decimal cast-out class values in the range 0–65535. When a requested class does not exist, it is not dumped.
STGCLASS is valid only for a coupling facility cache structure. If specified for a coupling facility list structure, the structure will not be included in the dump.
When STGCLASS=ALL is specified, the storage class controls for all storage classes are dumped along with the directory information for all entries within the classes (if SUMMARY is not specified).
When STGCLASS=(list) is specified, the storage class controls for (list) are dumped along with the directory information for the entries in the requested storage classes (if SUMMARY is not specified). The values specified are the decimal storage class values, 0–255. When a requested class does not exist, it is not dumped.
LISTNUM is only valid for a coupling facility list structure. If specified for a coupling facility cache structure, the structure is not included in the dump.
When LISTNUM=ALL is specified, the list controls for all lists in the coupling facility list structure are dumped along with the entry controls (if SUMMARY is not specified).
When LISTNUM=(list) is specified, the list controls for (list) are included in the dump along with the entry controls for those lists. The values specified are the decimal list values, 0–4294967295. The system ignores a zero in the case of LISTNUM. No error results. When a requested list does not exist, it is not dumped.
You may use the following keyword to further modify the STGCLASS, COCLASS and LISTNUM keywords:
ADJUNCT may not be specified with SUMMARY. If they are both specified, a syntax error is issued.
When ADJUNCT=CAPTURE is specified, the adjunct data is captured in the facility dump space along with the directory information while dumping serialization is held.
When ADJUNCT=DIRECTIO is specified, the adjunct data is written directly to the dump data set after the directory information is captured. The adjunct data is not captured in the structure dump table. The adjunct data may be changing as dumping proceeds.
ENTRYDATA may not be specified with SUMMARY. If they are both specified, a syntax error is issued.
When ENTRYDATA=UNSERIALIZE is specified, the entry data is dumped after structure dump serialization is released. The entry data may be changing relative to the entry controls that were captured while structure dump serialization was held.
When ENTRYDATA=SERIALIZE is specified, the entry data is dumped while serialization is held. If ACCESSTIME=ENFORCE is specified and the dump time limit expires before the entry data is written to the dump data set, the system continues to write the entry data to the dump data set even though serialization is not held.
SUMMARY may not be specified with ADJUNCT or ENTRYDATA. If it specified with either of these keywords, a syntax error is issued.
Number of Structures | Number of Ranges |
---|---|
47 | 6 |
46 | 16 |
45 | 26 |
44 | 36 |
⋮ | ⋮ |
You cannot specify other parameters when specifying NODUMP. For example, you can specify CD SYSABEND,NODUMP, but not CD SYSABEND,PDATA=option,NODUMP.
You cannot specify other parameters when specifying NODUMP. For example, you can specify CD SYSUDUMP,NODUMP, but not CD SYSUDUMP,PDATA=option,NODUMP.
You cannot specify other parameters when specifying NODUMP. For example, you can specify CD SYSMDUMP,NODUMP, but not CD SYSMDUMP=option,NODUMP.
Sets the approximate number of seconds that ABDUMP processing waits for obtaining required resources. The value may be changed up to the maximum of 9999. If this command is used to change the value from the IBM® default interval of 240 seconds, place the command into a COMMNDxx member of PARMLIB. That establishes the setting as the installation default when the system is IPLed. See z/OS MVS System Messages, Vol 6 (GOS-IEA) for the discussion in message IEA848I, DEADLOCK AVOIDED to find more information.
Whenever the TIMEENQ value is changed, the new value takes effect immediately. A value of 0 does not force an SVC dump to occur, because the resources required might be immediately available. You can not use CHNGDUMP DEL to delete this option.