What to do when a SARSTC SARPAR08 Message is Received
Article ID: 29763
Updated On: 06-20-2024
Products
Issue/Introduction
SARSTC receives the error:
SARPAR08 (CARD nnn) SEQUENCE ERROR IN TABLE - ID=xxxxxxxxxxxx PRECEDES ID=xxxxxxxxxxxx
A return of a U0001 error, from the SARVERO job, indicates that errors were found in the table.
This article explains the process to solve this issue.
Environment
Component: VIEW
Resolution
A SARPAR08 message indicates where in the ERO table there is a "/report-id ..." entry that is out of order.
The message is an indication that a start of the SARSTC task has stopped, due to the entries being out of order.
As the table is searched top-down and in a sequential manner, it is necessary to have more specific entries come before generic entries.
The SARSTC task can be started once the ERO table is deemed to be in proper order.
The ERO table is defined in SARSTC with:
//SARPATAB DD DISP=SHR,DSN=...
where the statement points to a file or library member used for the table.
To verify the ERO table, use the following JCL:
//XXXXXXXX JOB ...
//SARVERO EXEC PGM=SARVERO,PARM='view_hlq[,TABLE]' <=== Modify DB name
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== Modify, if used
//SARBKLST DD SYSOUT=*
//SARPATAB DD DISP=SHR,DSN=ero_table <=== Modify DSN for table
//
In the above, a report is written to the file specified in the "//SARBKLST DD", similar to the Backup Cycle output found in the View SARSTC archival task.
The TABLE option (PARM='view_hlq,TABLE') will execute only table syntax checking and will not do backup simulation.
Additional Information
Note: The backup simulation may run for 30 minutes or longer.
Feedback
