Question & Answer
Question
What should I do when S-TAP abend ? Do I restart STAP or do IPL ? What must I collect for Support to investigate the issue ?
Answer
Go back to historical events, what happened before the abend ?
- Was there a new policy pushed ?
- If so, was there STAP restart followed by policy pushed ?
- Did the abend occurs an hour or more after a new policy was pushed ? If so, the cause could be cleanup process.
Whatever the reason, STAP service should not abend. Please verify if the ABEND is reproducible with the following:
A. After abend, restart STAP. An IPL is not necessary, only a restart of STAP.
B. After STAP service is back, does it ABEND again ? If yes means the issue is reproducible then open support ticket.
C. Provide the outputs from the following to tech support.
First you need to recreate the abend and provide a dump and enable trace parameters as follows:
- Add the following parameters to the parm file:
- ZIIP_TCP(N) -
TRACECOMPILE( Y ) -
STAP_TRACE_POLICY(Y) -
STAP_LOG_EVENTS(Y) -
3. Restart S-TAP
4. Upon S-TAP startup, if it stays up, please run the following commands:
a. Run the command /F <stapstc>,STAP (where <stapstc> is the jobname of the STAP started task.
b. Recreate the abend
c. Run the command /F <stapstc>,STAP again
d. Run the command /F <stapstc>,DDX
6. Remove from the STAP parm file:
- TRACECOMPILE( Y ) -
STAP_TRACE_POLICY(Y) -
STAP_LOG_EVENTS(Y) -
7. Note that running with STAP_LOG_EVENTS(Y) will log significant amounts of data to the log, so it is recommended not run a long time with it enabled.
8. Change parm ZIIP_TCP(N) - to ZIIP_TCP(Y) - in parm file.
9. Provide the resulting dump and job log to support
D. If no dump created in C and the job logs do not contain sufficient information to diagnose the abend then setup a SLIP as follows to create a dump while recreate the abend:
SLIP SET,ID=STAP,A=SVCD,C=0C1,SDATA=(CSA,LSQA,NUC,PSA,RGN,SWA,SQA,TRT),JOBNAME=<stpstc>,END
where <stpstc> is the jobname of the STAP started task.
Please terse the resulting dump and supply it to tech support.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22014519