Thanks Peter, I'll take a look at that option. Our PC people compile into QA and from that point it remains as is so that tested code is what goes into production.
Charles (Chuck) Hardee Senior Systems Engineer/Database Administration EAS Information Technology Thermo Fisher Scientific 300 Industry Drive | Pittsburgh, PA 15275 Phone +1 (724) 517-2633 | Mobile +1 (412) 877-2809 | FAX: +1 (412) 490-9230 [email protected] | www.thermofisher.com WORLDWIDE CONFIDENTIALITY NOTE: Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent of a system responsible for delivering the message to the intended recipient, is prohibited. If you are not the intended recipient, please inform the sender and delete all copies. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Farley, Peter x23353 Sent: Thursday, August 04, 2016 6:22 PM To: [email protected] Subject: Re: Question about the COBOL compiler Don't your auditors flag that kind of life cycle setup? If a program is recompiled after being tested in QA then you are putting untested code into production, even if it's the same source and compiler. Around here the programmer does the final compile (but only in the SDLC system under its rules) and the load modules, sources and compile listings are copied through to QA and then to Production with no changes. What is tested is what gets to production that way. However, I have to retract my prior statement that COBOL doesn't support adding "cards" to the output object code. For your particular case, the compiler NAME option may be all you need: Default is: NONAME, or NAME(NOALIAS) if only NAME is specified Abbreviations are: None If you specify NAME(ALIAS), and your program contains ENTRY statements, a link-edit ALIAS card is generated for each ENTRY statement. The NAME or NAME(ALIAS) option cannot be used for compiling programs that will be prelinked with the Language Environment prelinker. HTH Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Hardee, Chuck Sent: Thursday, August 04, 2016 5:49 PM To: [email protected] Subject: Re: Question about the COBOL compiler That would definitely work Peter, but ultimately I will not be the one compiling the program for production. I am developing a system level service routine that will be used by the application programmers but when it goes into production it will be a production control person that will be compiling it. I guess I'll have to bite the bullet and modify the compile panels to support additional parms. Charles (Chuck) Hardee Senior Systems Engineer/Database Administration EAS Information Technology <Snipped> -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Farley, Peter x23353 Sent: Thursday, August 04, 2016 5:33 PM To: [email protected] Subject: Re: Question about the COBOL compiler Unlike HLASM and predecessors, there is no "PUNCH" command to output arbitrary "cards" to the object output from COBOL. About all I can think of is to go ahead and submit the compile/link job that the panels produce, then cancel the job before it completes, then use SJ from SDSF to edit the JCL to add the ALIAS statement to the LKED SYSIN DD. Nothing automated, but it will get the job done. HTH Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Hardee, Chuck Sent: Thursday, August 04, 2016 5:22 PM To: [email protected] Subject: Re: Question about the COBOL compiler Compiler version: PP 5655-G53 IBM Enterprise COBOL for z/OS 3.4.1 V3R2 What I need is this: INCLUDE OBJLIB(PROGRAMA) ALIAS ENTRYB(NTRYPTB) NAME PROGRMA(R) Our compile panels generate the INCLUDE and NAME statements. However, I need to have the ALIAS in there as well. Our panels don't allow for additional statements like ALIAS and I don't want to dig into them and add the support for them. I suspect few, if any, other than me in this special usage, will ever need something like this. As to dynamic or static, not really relevant, but for the record, all of our programs are, by standard and policy, compiled with DYNAM enabled. C- Charles (Chuck) Hardee Senior Systems Engineer/Database Administration EAS Information Technology <Snipped> -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Bill Woodger Sent: Thursday, August 04, 2016 5:14 PM To: [email protected] Subject: Question about the COBOL compiler Somewhat (when you have a "batch compile - a compile of a load of separate programs in one hit). But not really, there was a bit of recent discussion of this here, a topic by Frank Swarbrick. Which compiler are you using? You want to CALL dynamically, or statically? -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
