How To
Summary
Explain how to use SLIP commands to get a dump for further analysis
Objective
obtain a dump for zWS support to analyze
Environment
z/OS
Steps
The zWS Customization and Tuning Guide, Chapter 9. Miscellaneous customization, section
"Customizing IBM® Z Workload Scheduler messages" explains how to modify the EQQMLIB ( SEQQMSG0 ) member to
cause a message to be written to the SYSLOG in addition to the EQQMLOG, but does not show how to create a SLIP command
to get a dump generated.
A SLIP could also be set to get a dump for an abend code like S0C4 or U4039 if the job / task does not have a SYSMDUMP file
defined, or if for some other reason a dump is not being written (see https://www.ibm.com/support/pages/node/389979
ZWSTECHNOTE : z Workload Scheduler ( zWS ) ABENDS ARE NOT CREATING a SYSMDUMP )
For the SLIP for an abend code, it is only necessary to set a SLIP command, for example:
SL SET,ID=4039,C=U4039,A=SVCD,JOBNAME=OPCC,
SDATA=(PSA,SQA,LSQA,RGN,LPA,TRT,CSA,SWA,SUMDUMP,ALLNUC,GRSQ),END
If this command is stored in a system parmlib member IEASLPxx, then the SLIP can be set with console command:
SET SLIP=xx
For a SLIP on a message written to SYSLOG, some additional steps may be needed:
(1) Decide on the message that you want to obtain a dump for (i.e. a dump is written when this message gets written to SYSLOG
For example, message EQQZ052E
(2) Check in SEQQMSG0 to see if this message is ALREADY being written to SYSLOG (it has WTO=YES ). The member name in SEQQMSG0 will be the first 6 characters of the message number, so member EQQZ05 contains the definitions for messages EQQZ050 through EQQZ059. For this example, EQQZ052E is not written to SYSLOG by default. In member EQQZ05 there is:
EQQZ052 ' ' LINES=2
'E THE PARAMETER LIBRARY FILE, DDNAME = EQQPARM OR DDNAME = EQQYPARM'
'I COULD NOT BE OPENED'
'E THE PARAMETER LIBRARY FILE, DDNAME = EQQPARM OR DDNAME = EQQYPARM'
'I COULD NOT BE OPENED'
(3) Create a copy of the SEQQMSG0 member in another dataset concatenated to EQQMLIB for the task or job. For example
create a dataset ZWS.CUSTOM.V10R1M0.SEQQMSG0 similar to the normal EQQMLIB dataset ZWS.DA.V10R1M0.SEQQMSG0
and then copy member EQQZ05 into the "custom" dataset. Then add the "custom" dataset to EQQMLIB DD for example:
//EQQMLIB DD DISP=SHR,DSN=ZWS.CUSTOM.V10R1M0.SEQQMSG0
/// DD DISP=SHR,DSN=ZWS.DA.V10R1M0.SEQQMSG0
If you change EQQMLIB (any member) the task or job needs to be restarted to put the change into effect
NOTE: If you change the SEQQMSG0 file distributed with the product, your change will be lost if you install a new release or if a PTF changes the contents of the member you modified
(4) Set a SLIP command to get a dump when the message is written to SYSLOG:
example:
SLIP SET,ID=XXXX,MSGID=EQQZ052E,ACTION=SVCD,MATCHLIM=5,JOBNAME=CCCC,
SDATA=(PSA,SQA,LSQA,RGN,LPA,TRT,CSA,SWA,SUMDUMP,ALLNUC,GRSQ),END
where CCCC is the task or job which issues the message. MATCHLIM defaults to 1 (take one dump then
disable the SLIP). Increasing MATCHLIM will cause additional dumps to be taken before the SLIP
is disabled (in this example, 5 dumps would be taken).
(5) Wait for the dump to be written, then terse the dump and send in to the support team (attach to the case).
Related Information
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSWL3F","label":"IBM Z Workload Scheduler"},"ARM Category":[{"code":"a8m0z0000001fwTAAQ","label":"ZOS-\u003EIZWS-\u003ETroubleshooting"}],"ARM Case Number":"TS000000000","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
01 December 2023
UID
ibm17085863