TMSAUDIT Abend - INCORE SORT CAPACITY EXCEEDED/TMSPTRS Abend - INCORE SORT CAPACITY EXCEEDED

Products

• CA 1 Flexible Storage

Issue/Introduction

TMSAUDIT is failing (ABEND=S000 U0016 REASON=00000000) in what looks like a sort issue. The failing job output shows: 

-INSTALLATION OPTIONS IN MFX LOAD LIBRARY WILL BE USED                 
-ALTERNATE PARM USED                                                   
-SYSDIAG= 2214688, 3518555, 3518555, 3514875                           
-13,888K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,            
-   64K BYTES RESERVE REQUESTED, 12,256K BYTES USED                    
-32K BYTES OF EMERGENCY SPACE ALLOCATED                                
-11,768K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16-MEGABYTE LINE,
-   0 BYTES RESERVE REQUESTED, 11,768K BYTES USED                      
-G=27066                                                               
-INCORE SORT CAPACITY EXCEEDED                                         
-INSERT      27066, DELETE          0                                  
-SYNCSMF  CALLED BY SYNCSORT; RC=0000                                  

 

Environment

Release : 14.0

Component : CA 1 Tape Management

Cause

The dynamically invoked sort (SyncSort in this case), which is called by TMSAUDIT/TMSPTRS processing, needs more working storage (whether virtual storage or DASD SORTWK) to successfully process. 

Resolution

The storage available to SyncSort for the AuditTMSPTRS job needs to be increased, whether via increases in virtual storage or DASD SORTWK storage.  The customer was able to resolve the problem by adding 3 SORTWK DD's to the TMSAUDIT job, such as: 

//SORTWK01  DD UNIT=3390,SPACE=(CYL,(50,50))
//SORTWK02  DD UNIT=3390,SPACE=(CYL,(50,50))
//SORTWK03  DD UNIT=3390,SPACE=(CYL,(50,50))

Note: In the current 14.0 release of CA1, the sample JCL being shipped for TMSAUDIT/TMSPTRS does NOT include any SORTWKnn DD's, and the TMSAUDIT/TMSPTRS documentation does not show these DD's in the sample JCL (CA1 Utilities and Reports manual).