Andrew, Debug Tool does include the Load Module Analyzer feature which can identify the language translator (compiler or assembler) used to generate the object for CSECTs in a load module or program object. IBM File Manager for z/OS also has the View Load Module function (option 3.10.1 in the File Manager ISPF dialog). This provides many options for displaying information about CSECTs including the compiler level and compiler options. See https://www.ibm.com/support/knowledgecenter/en/SSXJAV_14.1.0/com.ibm.filemanager.doc_14.1/base/lmselpan.html. You can also run this function in batch. See https://www.ibm.com/support/knowledgecenter/en/SSXJAV_14.1.0/com.ibm.filemanager.doc_14.1/base/vlmfun.html .
Regards, Peter Van Dyke (HCL) On Thu, Jan 25, 2018 at 3:04 AM, Andrew Arentsen <[email protected] > wrote: > Hi all, > > We are in the midst of a migration to Enterprise COBOL 6.2 and I'm trying > to find a way to report on the compiler version of program objects in a > particular load library. I've got the COBANALZ program (CBT File 321) > working, but it seems to choke on CICS programs that were compiled with > the integrated compiler at version 6.2; COBANALZ abends with a S0C4-11. > From the output in SYSPRINT, it seems that the previous program was "held > on to." Here's an example where CZMVS032 is the program it choked on and > CZMVS031 was reported on successfully just before: > > ... > ------------ Info > ------------------------------------------------------------ > ----------------------- > > > Program: CZMVS032 is COBOL Enterprise Version 06 Release 02 Mod-Level 00 > > > ------------ Timestamps > ------------------------------------------------------------ > ----------------- > > > Compiled program name CZMVS031 > Date: 24.01.2018 (european) 24.Jan.2018 (long) Time: 10:32:36 > > ------------ Statistics > ------------------------------------------------------------ > ----------------- > ... > > > COBANALZ does report successfully on COBOL 4.2 CICS programs that used the > integrated compiler or the CICS translator. I've also researched AMBLIST, > but that doesn't seem to allow me to report on an entire PDSe. > > Does anyone know if there's a way to report on the compiler version used > for an entire PDSe? We have IDz, Debug Tool 14.0 if those could be used. > > Thanks for any input, or a suggestion of a better list to post this on. > > Andrew Arentsen > > ********************************************************************** > This e-mail is confidential. If you are not the intended recipient, you > must not disclose or use the information contained in it. If you have > received this e-mail in error, please tell us immediately by return e-mail > and delete the document. > > ---------------------------------------------------------------------- > 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
