IBM Mainframe Forum

Hi
I want to find a load module in my loadlib PDS that is for example compiled at this time >>> 20120101235900
Is ther any way to find it by this parameter(compiling time).
Or is there a PGM to use it in a JCL to do this purpose.

First of all, your question is basically meaningless. Many, perhaps most, load modules contain many programs that were compiled at various dates. Most load modules contain the date and time they were linked, and for most load modules, the compile date, but not the time, for the component programs. This data is called IDR data. Many programmers insert the compile date and time into the binary program text, but there is no standard as to the location and format.

The IBM supplied AMBLIST utility can extract the IDR data. It is documented in "MVS Diagnosis: Tools and Service Aids" for your z/OS release. AMBLIST cannot use date and time as selection criteria.

These users thanked the author steve-myers for the post:

Mehdi shri (Tue May 29, 2012 9:52 am)

Hello,

Just curious. . .

How might you knw the exact compile time and not know the "loadmodule" name?

As mentioned, AMBLIST should provide the info you want (for all included modules), but you should use the executable name.

If you want to find out at execution time, there is a COBOL Intrinsic function named When-Compiled.
Of course, you have to include this in the program source and recompile.
FYI only.

Dear friends
I must copy series of load modules from a PDS to another PDS on periods of the times . This load module's compiling time (and size) must be equal to ones thas specified at checklist for me(in an excel sheet). Therefor I must check them one by one in load modules. This this time consuming and difficult for me. I want to use a utility to do this for me.

Well, then you probably have two choices. I grant, neither are appealing.

• Use the LISTIDR function in AMBLIST, and write a program to analyze the output.
• Write an Assembler program to analyze the load module members. This is not terribly difficult; I could knock something together in a couple of days, but I've been writing Assembler code to read load modules for more than 30 years. Load module records are described in "MVS Program Management: Advanced Facilities" for your z/OS release.

These users thanked the author steve-myers for the post:

Mehdi shri (Wed May 30, 2012 10:58 am)

It may be boring and time consuming but that is what work is about. But you do have a problem - load modules are not compiled - they are linked or bound. You may have to ask someone more experienced where to look if you cannot follow any of the advice given here.

Hello,

Is there no change management software in use?

As there can only be 1 member of a given name in a pds, what should be done if a module in the library does not have the same date/size as the spreadsheet?

If there is a change to some module that needs to be promoted, how would the "wrong" module be in the library from which promotions are done?

Somewhat scary to me. . . I've supported more than 100 different data centers and none of them does this kind of compare. . .

Therefor I must check them one by one in load modules.

Given Steve-Myers' response about composite load modules,can you elaborate on what kind of check you do manually?

Mehdi shri wrote:Dear friends
I must copy series of load modules from a PDS to another PDS on periods of the times . This load module's compiling time (and size) must be equal to ones thas specified at checklist for me(in an excel sheet). Therefor I must check them one by one in load modules. This this time consuming and difficult for me. I want to use a utility to do this for me.

If you are copying load modules, forget compile date/time.

You need the data/time of the link/bind, not of the compile.

How about you get the "copy requester" to give you the information from AMBLIST on their library, then, after you do the copy, you run AMBLIST on your library.

You don't have to do it on the whole library, just specify the members being copied.