The understanding from the Endevor manual is that NOCOND is the default if the option is not specified on the ALLOC statement and that if some datasets are not found, that processing will be halted.
The generate job ran with an ALLOC statement with neither COND or NOCOND specified. Some datasets were missing and the processor has produced some C1A0015I messages but the processing continued.
C1A0015I ALLOC=COND DATA SET NOT ALLOCATED: DDNAME=DD01, DSN=iprfx.sys1.subsys1.COBOPTS
C1A0015I ALLOC=COND DATA SET NOT ALLOCATED: DDNAME=DD01, DSN=iprfx.sys1.subsys1.COBOPTS
The DD statement is coded as:
//DD01 DD DSN=iprfx.&C1SI.&C1SU..COBOPTS,
// DISP=SHR,ALLOC=LMAP,MONITOR=COMPONENTS
What is the default for COND/NOCOND?
All Supported Releases
The reason you are seeing the ALLOC=COND as the default is because your site has Deferred File Creation active.
The processor would need to be changed to include NOCOND:
//*+--------------------------------------------------
//*| COBOPTS - CHECK FOR COBOPTS TYPE
//*+--------------------------------------------------
//COBOPTS EXEC PGM=FILEAID,MAXRC=8
//SYSPRINT DD SYSOUT=&ZOUT,FREE=CLOSE,SPIN=NO
//DD01 DD DSN=iprfx.&C1SI.&C1SU..COBOPTS,
// DISP=SHR,ALLOC=(LMAP,NOCOND),MONITOR=COMPONENTS