In
<off6e52a22.284c8f8c-on85257deb.004d3287-80257deb.005b2...@prudential.com>,
on 02/13/2015
at 04:35 PM, Ken MacKenzie <[email protected]> said:
>In the old days, as far as I remember though I can't prove it, you
>used to be able to look at a load library member, check for a
>certain string (e.g. C2 mm/dd/yy hh:mm:ss) and establish that the
>module - or even modules had been compiled as COBOL II.
According to z/OS MVS Program Management: User's Guide and Reference,
SA22-7643-09, program objects support IDR data.
>Wit the advent of program objects on PDSEs and Enterprise COBOL we
>don't appear to have that luxury.
What happened to AMBLIST?
>Any thoughts?
If it were me, I'd use the BINDER for PDSE and Unix program objects
rather than post-processing AMBLIST LISTIDR output.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
