View - SARSTC Started Task Fails With S500-2 Abend

Products

• OM View

Issue/Introduction

The SARSTC task kept failing, with a S500-2 abend, each time it was restarted. We are seeing the following messages in the SARSTC task logs:

IEC141I 013-C8,IGG0193K,SAR

CCSR010E SARSDAPI S013 at 2E646476 LMOD SARSDIM CSECT SARSDIM

IEF403I SARSTC - STARTED - TIME=11.12.03
SARSTC00  CA View 14.0.02 is initialized
IEA995I SYMPTOM DUMP OUTPUT  008
SYSTEM COMPLETION CODE=500  REASON CODE=00000002
TIME=11.12.03  SEQ=61566  CPU=4008  ASID=01D3
PSW AT TIME OF ERROR  070C1000   80FF49B4  ILC 2  INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN

Environment

z/OS, 14.0, SARSTC, ABEND, S013, S500

Cause

View was attempting to collect the output from a task or job that likely abended, and left the dataset to be collected out in the JES queue with no end of file (EOF) marker. We are unsure of which JES sysout dataset is causing the task to abend.

Resolution

View's SARSTC task was continually abending, each time it was restarted because it kept attempting to collect this same dataset. 

A dump, on a S500 abend, contained information on the problem report by identifying the SYSOUT ID and JOBID. 

Once identified via the SVCDUMP, the offending report was manually purged from the JES spool. 

The SARSTC task was then started, and processed remaining reports from the JES queue as expected. 

*NOTE*

An alternate way of identifying the offending report without analyzing an SVC dump would be to:

 . Set SARINIT ARCHMSG=YES. This will cause View to issue a SARSTC22 message for each report it attempts to collect.
 . Start the SARSTC task. 
 . In the next abended run, find the SARSTC22 message in the SARSTC logs to identify the offending SYSOUTID and JOBID. 
 . Purge the report from the JES spool. 
 . As many additional SARSTC22 messages would be generated with ARCHMSG=YES, consider setting SARINIT ARCHMSG=NO.  
 . Start the SARSTC task.