View - SARSTC Started Task Failed With S500-2 Abend

Products

• View

Issue/Introduction

The SARSTC task failed with a S500-2 abend, with these messages:

IEC141I 013-C8,IGG0193K,SAR

CCSR010E SARSDAPI S013 at 2E646476 LMOD SARSDIM CSECT SARSDIM

Here is information from the SARSTC log:

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

Release : 14.0

Resolution

View's SARSTC task was continually abending, as it was having difficulties in its
 attempting to collect a report for which no ending values were found. 

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

The report was resultingly purged from the JES spool. 

The SARSTC task was then started, and processed reports as expected. 

To identify the report in another way:

 . Set SARINIT ARCHMSG=YES. 
 . Start the SARSTC task. 
 . In the next abended run, a SARSTC22 message will be displayed noting the ID and JobID. 
 . Purge the report from the JES spool. 
 . It is then recommended to set SARINIT ARCHMSG=NO, as many messages would then 
   be generated. 
 . Start the SARSTC task. 

Note: 

 . There was a report, in the View database, with an OPEN Location, that was
   suspected and investigated, but it proved to not be the problem report. 

 . On the OPEN report, used was the View procedure of:

 . . Issue a "C" command, for Clean, in the "Sel" column to left of the report. 
 . . Have a View backup run. 
 . . Issue a "C" command a minimum of 4 hours later from the first issue. 
 . . The report will then show a DISK Location.