I am personally annoyed that we even have to have two separate compile procs; one for batch and one for CICS. I would like to be able to just have PROCESS CICS on a CICS program and have the necessary program binder statements generated automatically. It would probably have to generate proper INCLUDE statements to statically link the CICS 'stubs', etc.
If I want to build a DLL I include PROCESS DLL. Etc. ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Bill Woodger <[email protected]> Sent: Friday, August 5, 2016 10:49 AM To: [email protected] Subject: Question about the COBOL compiler If you don't know what harmful things there are, consult the Binder/Linkage-editor manual. Like compiling this program and linking it as another, for a simple one. It is rare that IBM ask me anything (although it did happen once, if IBM can be thought of as one person who works for IBM). Even if you no longer want arbitrary, but limited binder/linke-editor control cards... Most people won't want the flexibility because they will have distinct was to process distinct types of programs. You don't have a program you want to use as a DLL, then poke it through a CICS process, and hope to be able to tidy it up at the end. You have a "this is how you do a DLL" process. Note, it is possible to prevent the use of CBL/PROCESS cards, and possible to "nail-in" compiler installation options (by option). For many sites, reliable compiler output gives them far more flexibility, perhaps? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
