Compiler Directives

[SailorHugh]

I have 2 COBOL programs, PGM1 and PGM2, both to be compiled as CICS programs and batch programs. PGM1 will also call PGM2. Is there a means to direct the compiler to compile code EXEC CICS LINK('PGM2') COMMAREA(PGM2-LINK-AREA) END-EXEC if I am compiling PGM1 as a CICS program, or to compile CALL PGM-PGM2 USING PGM2-LINK-AREA if PGM1 is being compiled as a batch program? Keep in mind that once these programs leave the Development area, they will be compiled by idiots.

[dbzTHEdinosauer]

actually, it sounds as if they are being developed by idiots.
if not idiots, people who know nothing of COBOL and CICS.

cobol compiler directives have nothing to do with the CICS API instructions that
are converted to COBOL by the CICS pre-compiler.

you mention that you want to use these programs both in cics and batch.
1. depends on the methodology employed by your site. Is it the old,
crap from the 80's where you need a batch version and a cics version?

2. most intelligent design (nothing to do with the idiot religious crap from the states)
involves separating the environment from the business logic.
does program a or b require any cics instructions? (queue reads, vsam reads?)
if not, which ever module that invokes program A, should invoke via a cobol call,
same for A calling B.
then you only have 1 run-module for each program.
kicker here is getting a copy of the run-module into both the CICS application loadlib and the batch application loadlib.
but, have no idea of your site standards/set-up.
what have others done in the past?