This is a discussion on COBOL/CICS/DB2 - COBOL for MVS and compile option DYNAM - cobol ; Hello all System: z/OS and LE for MVS Why is it possible to compile a COBOL/CICS/DB2 program with the options: NODYNAM . . . ????? nowerdays thats not the state of the art, because: IMS could be called dynamic COBOL ...
System: z/OS and LE for MVS
Why is it possible to compile a COBOL/CICS/DB2 program with the
NODYNAM . . . ?????
nowerdays thats not the state of the art, because:
IMS could be called dynamic
COBOL and ASSEMBLER could be called dynamic
why not inside of a CICS environment
I asked this question, because i mus used the same sources in two
DB2 Batch (IMS/DSN) - one compile and link
DB2 CICS - a second compile and link
i have to manage two sources inside a revision environment!!!
The first source could be compiled with the option: DYNAM for batch -
and all calls are managed by COBOL and MVS
in CICS, the precompiler sets the COBOL options to NODANM. Therefore i
need a second source to manage the environment. I must use the
CICS-link library to link the DSNHLI and i can NOT use the same module
in IMS/TSO, because they need different HLI's: for IMS propagator
DSNHLI from IMS for DSN propagator DSNHLI from DB2.
I would link a DB2 module without a specific DSNHLI.......
Is DFHECI unable to be called dynamic? IMS module DFSLI000 could.
Why does DB2 precompiler generate calls like: CALL 'DSNHLI' USING
PLIST-x, instead of CALL DSNHLI USING PLIST-x, where DSNHLI ist
defined as a variable inside the working-storage section?
I am not pleased about this situation.
I hope, that you could follow my intention... :-)
i am not so stable in english
Einen schoenen Tag