For Programmers: Free Programming Magazines  


Home > Archive > Cobol > March 2006 > IBM Enterprise COBOL - compiler options that impact "behavior"









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author IBM Enterprise COBOL - compiler options that impact "behavior"
William M. Klein

2006-03-30, 6:55 pm

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-...3PG30/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


Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com