IBM Mainframe Forum

looks also that Your reading and understanding skills are pretty low

nothing is confusing on what we told You ...

first step run the listcat creating a sequential dataset
second step run Your frigging COBOL program reading the IDCAMS output and producing whatever output You want

for GDG the catalog date can be safely considered as the creation date

but as I said sort can do it better
http://ibmmainframes.com/about34829.html

That is why I am looking for alternatives.

plain stupid remark

I can do it with JCL, but my requirement should be fulfilled with COBOL.

pretty hard to believe, anyway who set the cobol requirement is an idiot

enrico-sorichetti wrote:looks also that Your reading and understanding skills are pretty low

nothing is confusing on what we told You ...

first step run the listcat creating a sequential dataset
second step run Your frigging COBOL program reading the IDCAMS output and producing whatever output You want

for GDG the catalog date can be safely considered as the creation date

but as I said sort can do it better
http://ibmmainframes.com/about34829.html

That is why I am looking for alternatives.

plain stupid remark

I can do it with JCL, but my requirement should be fulfilled with COBOL.

pretty hard to believe, anyway who set the cobol requirement is an idiot

Enrico...

Please stop scolding others...

I have to do everything with cobol. i would like to call LISTCAT is also from COBOL. I am not aware of that concept. If you know some thing, please let me know. If u dnt knw that, plz say alternatives. dnt scold others.

If u dnt knw that, plz say alternatives. dnt

this is not a chat room, learn to communicate properly

since You lack the good sense of listening to what people with lots more experience keep telling You
You deserve all the harsh comments you might get for Your lack of good sense, good judgement, and understanding

since we reply on our time and according to our experience we have the ethical duty on advising according to the best practices,
You are bound to accept(*) what we tell you and stop complaining about not getting what You ask for
(*) from a dialectic point of view

if You want to receive only answers that You like and if You want advice on implementing a stupid solution
You will have to hire a paid <lowly> consultant who for a proper fee will give You any low quality solution You will ask for

It is a silly "requirement" to do it in Cobol without an extremely good reason, which would be fun to know given that you don't know Cobol.

SORT, rexx, OK. Cobol? Silly.

BillyBoyo wrote:It is a silly "requirement" to do it in Cobol without an extremely good reason, which would be fun to know given that you don't know Cobol.

SORT, rexx, OK. Cobol? Silly.

Hi Billy...

I already completed the task with JCL, it is running succesfully... but rejected by our management, bcoz they need it in COBOL. Even though it is a silly requirement, i dont have choice. I have to do it. Here I am looking for some valueble information from experienced people like you. Actually, we are targeting a very big task. Implimenting LISTCAT is required at some stage in our task. Our people are planning to complete everything with COBOL. So I am looking for your suggestions...

Regards,
Srikant

Can you explain what this program is supposed to do?

I have to chip on this. If your management is asking you to do such a task that you need to clarify to the management that their requirements and solution are a waste of time and money $$$$. I could write more, but it is a waste of my time. This is what really ticks me off, people are making requirements and decisions that have no idea what they are doing or anything about the environment that they are working with.

BillyBoyo wrote:Can you explain what this program is supposed to do?

The ultimate task of our program will take a copy a disk file into tape.

1. listout the current date generations around 300 for different types of gdgs and also they have different attributes.
2. search each and every generation with certain set of keys.
3. if the keys found, then the dataset need to be copied into tape from disk, and discarded when not found.
4. all the tape files need to be documented along with corresponding disk file and date.

skankatala wrote:

BillyBoyo wrote:Can you explain what this program is supposed to do?

The ultimate task of our program will take a copy a disk file into tape.

1. listout the current date generations around 300 for different types of gdgs and also they have different attributes.
2. search each and every generation with certain set of keys.
3. if the keys found, then the dataset need to be copied into tape from disk, and discarded when not found.
4. all the tape files need to be documented along with corresponding disk file and date.

You realize, do you not, that item 1 is pretty much meaningless in English?

Run the Listcat. "Parse" the output (rexx, sort, something) to give a list of datasets to the Cobol program.

Do all the "dynamic" stuff to open, read, close in the Cobol program. Produce two output datasets, one being a list of files which have at least one of your matching keys on (no need to read everything) the other a list of those with no match (which will have been read in their entirety, assuming you don't have any "keyed" files). List 1 plus List 2 should match the input list. This should be programmatically confirmed.

Feed the list 1 into your standard backup utility, having added necessary control information. Feed list 2 into a "whatever you want to do with those" utility, again having had control information added. Rexx, sort, something for the control cards.

Keep it as simple as possible. If you are going to be reading hundreds of files (or n generations of hundreds of files) you are going to need to check everything, and that means "automation". Do not try to jam everything into the Cobol program. It would be an idiotic thing to do. If you have a client/boss who insists, I'll write a little note that you can pass on to them with my best wishes.

You will already have covered file sizings, yes? Do some "time trials" with a quick-and-dirty program. You might have to break it up into logical pieces to get it running in a manageable amount of time, depending on how much data/how many files.