Troubleshooting
Problem
In some cases an S0C4 abend could occur in an IWSz module such as EQQZHTCL but it will be followed by another abend such as 4039 or 4042 which is taken by LE code. This can overwrite the S0C4 dump which would be more useful for troubleshooting purposes.
To ensure that the S0C4 abend dump is preserved, set a SLIP for the controller task as follows:
SL SET,ID=nnnn,C=0C4,A=SVCD,JOBNAME=xxxx,
SD=(ALLNUC,ALLPSA,CSA,GRSQ,LPA,RGN,SQA,SUM,TRT),END
SD=(ALLNUC,ALLPSA,CSA,GRSQ,LPA,RGN,SQA,SUM,TRT),END
You can make the ID of the SLIP (nnnn) anything that does not conflict with any other SLIPs you are using (you can display a list of these
with the console command "D SLIP") and xxxx should be set to your controller subsystem name.
If you set some SLIPs after an IPL via automation or via the IEACMDxx parmlib member you can add the above
SLIP to the member that will be processed after an IPL.
For example if your IEACMDxx member has:
COM='SET SLIP=00'
You can add the above SLIP to your parmlib member IEASLP00.
If you get a dump written because of this SLIP please open a PMR with IWSz defect support team (that is, from SR report this as a problem
not a question).
Symptom
S0C4 abend in controller task
Diagnosing The Problem
If the S0C4 abend dump is written open a PMR to have the dump reviewed.
Document Location
Worldwide
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Component":"","Platform":[{"code":"PF034","label":"Windows Mobile"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Was this topic helpful?
Document Information
Modified date:
13 September 2019
UID
ibm10873078