IBM Enterprise COBOL - compiler options that impact "behavior"



This is a follow-up on an earlier IBM-MAIN thread.

I thought that it might be interesting AND USEFUL to "document" which IBM
Enterprise COBOL compiler options can "impact" run-time behavior. By this I
mean that the same source code will compile "cleanly" with any setting of these
options but that for programs that COMPLETE their "run" the "output" might be
different. (I phrase it this way to avoid options that impact "storage" usage
at compile or run-time. I am also "ignoring" performance differences.).

Looking at the list of options at:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IGY3PG30/CCONTENTS

My initial list of "potentially impacting" options is:

- ADV
- CICS (depending on suboptions)
- CODEPAGE
- CURRENCY
- DATEPROC
- DYNAM (only if CANCEL is used)
- FASTSRT (only if DECLARATIVES are used)
- INTDATE
- NUMPROC
- PGMNAME
- QUOTE/APOST (figurative constant, not literals)
- SQL (depending on suboptions)
- SSRANGE (if checking is turned on at run-time)
- THREAD
- TRUNC
- YEARWINDOW
- ZWB

****

Of you "IBM COBOL" types, do you have any opinions on any that I have missed -
or that I have included that you think do NOT impact run-time behavior?


--
Bill Klein
wmklein <at> ix.netcom.com


.



Relevant Pages

  • IBM Enterprise COBOL - compiler options that impact "behavior"
    ... This is a follow-up on an earlier IBM-MAIN thread. ... Enterprise COBOL compiler options can "impact" run-time behavior. ... at compile or run-time. ...
    (bit.listserv.ibm-main)
  • Re: IBM Enterprise COBOL - compiler options that impact "behavior"
    ... Enterprise COBOL compiler options can "impact" run-time behavior. ... usage at compile or run-time. ... This impacts runtime behavior whether or not DECLARATIVES are used, ...
    (bit.listserv.ibm-main)
  • Re: VACPP 3.08-problem with large source file?
    ... VAC fully buffers stdout but that behaviour is not the correct one for the given code. ... cannot compile the file LostKingdom.C produced with BF2C.EXE. ... Copyright IBM Corp. 1991, 1995. ... However, the latest ILINK.EXE will not be able to read the .obj file, at least not, if it contains debug info ...
    (comp.os.os2.programmer.misc)
  • Re: VACPP 3.08-problem with large source file?
    ... cannot compile the file LostKingdom.C produced with BF2C.EXE. ... Copyright IBM Corp. 1991, 1995. ... However, the latest ILINK.EXE will not be able to read the .obj file, at least not, if it contains debug info ...
    (comp.os.os2.programmer.misc)
  • Re: Virtual Storage Controls - Was Re: REGION=0M and LSQA
    ... years and years of experienced IBM design philosophy and debugging", ... Especially no debugging classes, It should would embarrass IBM to have a 3rd party offer something. ... dynamically-allocated data areas (thus avoiding user storage creep - see I ... so various techniques were used to compile the byte code ...
    (bit.listserv.ibm-main)