Read compiler listing VSAM file

Manigandan Aravindhan · New User Joined: 09 Oct 2007 Posts: 81 Location: India

Hi,
To read the cobol compile listing information, I used to go to listing VSAM file thru Endevor and read it. But using this I can read only one module listing at a time....Is there any of automating to get all the listing in a PDS? Using Rexx

Is there any utility provided by Endevor to read listing VSAM file through REXX?

dbzTHEdinosauer · Posted: Sun Sep 18, 2011 8:05 pm

not sure if CA provides a REXX API,
but you could invoke a process whereby you could generate from the listing a printfile, which you could direct to a PDS.

but why would you want to create this PDS?
from a space standpoint, would be wasteful.

if you really want a pds for listings (again see no need)
you could have your site support modify the endevor GENERATE jcl
to feed this pds and then it would always be up-to-date.

Manigandan Aravindhan · New User Joined: 09 Oct 2007 Posts: 81 Location: India

Hi Dick,
Thanks, I hear your point on space constraint.

I'm trying to get the source of the variable by getting the variable as input. By getting the variable as input find from where it is getting populated and generate the report for all the input variables.

In compiler listing we would have numbers assigned to all the variables and the line number where it is getting populated. So thought it would be easy if i could read the listing VSAM backend thru REXX by calling any utility or submitting thru JCL, then generate the report I needed through REXX by reading it.

I used to see this listing in ENDEVOR foreground currently. If not Endevor providing is there any other utility to read the compiler listing VSAM file?

Thanks in advance

dbzTHEdinosauer · Posted: Mon Sep 19, 2011 11:17 am

when you go into the ddio file utilities
at my site, it is option 5.5 from TSO debugging option(main option 3)
you can print a module from the ddio file.
i would trap that jcl and use it as a model/skeleton to print all members of the ddio fle.

but better is the modification of GENERATE JCL to output the compiler listing to your pds.

and I reiterate, do not fool yourself calling the CA listings (or ddio) file a VSAM file.
it is proprietary in structure and you need a CA routine to decode.

as far as your report,
just reporting on the source field for a destination field may not be enough.
you probably will have to work backwards (thru intermediate fields/DB or VSAM columns/field)
to generate a truely useful report.

you maybe better off just generating a report which can cross-reference modules that populate db2 columns/vsam fields.