The CONPARMX output can be read from SYSIN and that is addition to the SYSOPTF which can reference symbolics. We compile twice (initial entry stage and again on first move to next stage). For 6.3 (which is better than 6.1 or 6.2) we have:
//* Include MDECK option for the entry stage compile only
// IF entrystage THEN
//SYSOPTF DD DATA,DLM=@@
&COBPARM
MDECK
@@
// ELSE
//SYSOPTF DD DATA,DLM=@@
&COBPARM
@@
// ENDIF
//SYSIN DD *
CBL ARCH(&#ARCH),INITCHECK
// IF entrystage THEN
// DD *
CBL NUMCHECK,PARMCHECK
CBL DIAGTRUNC,RULES(NOEVENP,NOLXPRF),SERVICE('&C1ELEMENT'),SSR,TEST
CBL LIST,MAP,TERM,VBREF
/*
// IF ('&DEBUG' NE 'YES') THEN
// DD *
CBL OPT(1)
/*
// ENDIF
// ELSE
// IF ('&DEBUG' EQ 'YES') THEN
//* Post entry stage debugging when needed
// DD *
CBL OPT(1),TEST(EJPD)
/*
// ELSE
// DD *
CBL NOSOURCE,NOXREF
CBL OPT(2),STGOPT,NOTEST(DWARF)
/*
// ENDIF
// ENDIF entrystage THEN ELSE
// DD DSN=&&ELMOUT,
// DISP=(OLD,DELETE)
Original Message:
Sent: 09-14-2021 08:44 AM
From: John Dueckman
Subject: COBOL compiler options
Don't forget about Endevor's builtin ability using CONPARMX :)
Original Message:
Sent: 09-10-2021 05:03 PM
From: Diego Bordon
Subject: COBOL compiler options
Hi Philip
do you know in which manual I can read more about this SYSOPTF option?
I'm running out of space on the parm statement and there are a lot of compile option that we would like to code for testing.
Thanks in advance. Diego.
Original Message:
Sent: 05-09-2018 05:03 PM
From: Philip Gineo
Subject: COBOL compiler options
looks like a cool option instead of putting COBOL compiler options on the PARM statement. This works for COBOL 6.1, you'd have to test it for the version of COBOL you're on.
//COMPILE EXEC PGM=***,PARM='OPTFILE'
//STEPLIB DD ...
//SYSLIB DD ...
//SYSIN DD ...
//SYSOPTF DD *
MAP,LIST,XREF,ARCH(11),SSRANGE,OPT(0),RENT,DATA(31),RMODE(ANY)
SYSOPTF CAN BE A FILE – THERE ARE NO CHARACTER LIMITS WITH SYSOPTF