Are you aware that proper use of the BC1PDSIN processor utility program can help prevent S001 abends?

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench

Issue/Introduction

Are you aware you getting S001 abends when using the BC1PDSIN processor?

Environment

Release:
Component: ENDBAS

Resolution

S001 abends can occur when CONLIST (or other programs) within a processor attempt to read a file that has been allocated but not initialized. When a file is allocated without being initialized it does not contain an end of file marker. A subsequent READ operation can result in a S001 abend.

CA Endevor support recommends the use of BC1PDSIN within a processor to do both the allocation and initialization of temporary listing files to avoid S001 abends.

However, it is very important to note that in order for BC1PDSIN to initialize the files, their DDNAME must be C1INITXX or C1LISTXX. Any other DDNAME will result in the file not being initialized and a possible S001.

Example:

//INIT     EXEC PGM=BC1PDSIN 
//C1LIST01 DD DSN=&&COBLIST,DISP=(,PASS),
//            SPACE=(CYL,(5,5)),UNIT=&WRKUNIT,
//            DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INITXY DD DSN=&&LNKLIST,DISP=(,PASS),
//            SPACE=(TRK,(5,5)),UNIT=&WRKUNIT,
//            DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//LIST02   DD DSN=&&BNDLIST,DISP=(,PASS),          <=== this file will not
//            SPACE=(TRK,(5,5)),UNIT=&WRKUNIT,          be initialized because
//            DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)    of its DDNAME

 

Additional Information

For more information on the CA Endevor Change Manager processor utility program BC1PDSIN please refer to the Extended Processor Guide.