SARSTC Archival Task Abends with S001-001

Document ID : KB000124941
Last Modified Date : 18/01/2019
Show Technical Document Details
Issue:
The client's SARSTC archival task abended with a S001-001 condition.
The matter had to do with a job number exceeding the last slot available in the current SARACT file.
The current SARACT file was 30 years old, before expansion of a JES job number.
The client does not do anything with the accounting data.
Environment:
CA View - All Releases
Resolution:
The S001-001 condition is received when SARXTD is trying to find a slot in the SARACT account file, for a job number that is beyond the highest slot number in the file. 
With that, another, larger, file is needed. 

Note: Reallocation of the accounting file will remove any data that was contained in the original file. 

To create a larger file: 

. Rename the current accounting file. 

. Run the following SARINACT JCL, to allocate a larger SARACT file: 

//XXXXXXXX JOB ... 
//SARINACT EXEC PGM=SARINACT 
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== Modify, if used 
//SYSPRINT DD SYSOUT=* 
//SARACT DD DSN=VIEW.SARACT, <=== Modify DSN 
// DISP=(,CATLG), 
// UNIT=SYSDA,VOL=SER=nnnnnn, 
// SPACE=(6160,4546,,CONTIG) 
// 

In the above JCL, SPACE=(6160,4546,,CONTIG) defines the number of contiguous blocks that will contain the 28-byte accounting records (4546 x (6160 / 28)) = 1000120), up to a maximum job number of 1000120.