IBM Mainframe Forum

Dear
I work in a datacenter. Some body wrties the cobol program and compiles it. Oother persons test this and give them to runing environment. I am responsible to give loade modules name and date and time of compiling ina a spreadsheet, then if there are equal to loadmodules(in date and time of compiling ) in the specied PDS on spread sheet I must copy this load modules from development PDS (for example from DEVLGROP.ACCTBILL.LOAD to TESTGROP.ACCTBILL.LOAD ).
Because some developer changes and recompile some of this program, therefore loadmodules produced in newer date&time(for compile). This developers doeing wrong but I must prevent this. I must not rely on loaudmodule member name. Therefor compiling date and time is important parameter for me. I responsible to recognizing development and test gropu to be same in thier environment. This picture show our development PDS liberary.

Maybe do a Google for COBANAL and talk to your management about whether you can use it at your site.

There are also a couple of licensed products which do what you want, if you management prefers to spend money.

However, since it looks like you are using Cobol II, it doesn't look like they do like that sort of thing...

Only one Cobol program per load?

Dear friends
Whit best regards and thank you , The AMBLIST pgm and LISTLOAD control statement lists detail information of any load module that used in main loadmodule. It was very boring for me and I coudn't find any way to do.
Is there any techniques in ISPF ( so I can use it by a JCL )only for comparing members size? For example I use a macro or same things. What I must to do? Which lanquage I must know to write a program for this purpose and use it by JCL?

Are you only interested in Cobol II programs, or any others?

If you do the full LISTLOAD to a dataset, you should be able to use your Sort product to locate and output the details for all Cobol II programs. Remember you'll need the loadmodule name as well.

That is if you are not going to bother with COBANAL, which is free, and already produces what you want and more (again you'd have to cut down the output).

I've even got a Cobol program which does it, but that would cost you money

These users thanked the author BillyBoyo for the post:

Mehdi shri (Wed May 30, 2012 11:17 pm)

I want to use a macro or same things. What I must to do? Which lanquage I must know to write a program for this purpose and use it by JCL?

Use JCL to run AMBLIST, output to a file. Use Sort to extract from that file, loadmodule name, program name, date/time compiled, to a file. Browse the file. If you want to use a macro to browse the file, do so.

for comparing members size?

The member list for a load module dataset will give you the member size. It will give you also the TTR. The TTR is an offset from the beginning of the dataset. If you replace a member, it's TTR will change. If you capture the member list periodically and then compare with the prior generation, you should be able to figure out which members changed.

note: If you compress a PDS, then likely the TTRs will change, giving many false positives.

Use the LMMLIST service of ISPF to get the member list information.

note: if someone uses AMASPZAP to alter a load module, neither the size nor the TTR will change (nor your eyecatcher dates). I do not think you can detect such a change without saving the entire load module and doing a compare.

Pedro wrote:... note: If you compress a PDS, then likely the TTRs will change, giving many false positives.

The TTRs will change after a "compress," but I don't think the order of the members change. The member with the highest TTR before the "compress" will still have the highest TTR after the "compress" and is still the most recently added member.

The length of the load module and the length of individual parts of the load module are available in the LISTLOAD output from AMBLIST.

It will even tell you about AMASPZAP changes, but I doubt you'll ever see any.

Use AMBLIST to list one loadmodule. Print it. Familiarise yourself with where to find the information you want. Write some Sort cards to include/omit the information you want/don't want.

Once you've got the basics working, try it with two or three modules. Make the output sufficiently fancy for your task.

Run with the whole report.

These users thanked the author BillyBoyo for the post:

Mehdi shri (Tue Jun 05, 2012 10:24 am)

This is part of the directory of a source type PDS -

The first column after the member name is the directory TTR, the remaining four columns are a calculated TTR for the first and last records followed by the CCHHR of the first and last physical records in the member.

I then "compressed" the dataset and reran the program, and got this result -