IBM Mainframe Forum

If the DISP parameter for a dataset is DISP=(NEW,PASS,CATLG), What will happen when the JCL is run? The first time? The second time?

what is gda .. can any explain with example?

Could you explain what you mean by "gda"? I just did a search of the JCL Language Reference and User's Guide manuals and neither one has a single reference to "gda". This is not a term used in JCL, and how does it relate to the DISP parameter that is the subject of your post?

Hello and welcome to the forum,

What will happen when the JCL is run? The first time? The second time?

This depends on what happens when the process is run. . . It also depends on what else has happened with the dataset between runs.

As Robert asks - what is GDA? Is this possibly supposed to be GDS (i.e. a typo)? Is this a completely different question?

instead of gdg.. Generating data group... i miss-spelled gda...... can u explain about gdg

What do you need to know about a GDG that is not already explained in the JCL Language Reference and Users Guide manuals?

Hello,

Generating data group... i miss-spelled gda......

As is this. . .

The word is Generation rather than Generating. . . Which would be most difficult (impossible) to find in any manual. These are also sometimes called Generation Data Sets (GDS).

In our business using the correct words is critical for any kind of communication or personal research.

As Dick said, terminology in IT is absolutely critical since similar terms may mean very different things. So far you've proved that you cannot provide a three-letter acronym without misspelling it. And the manuals provide everything you care to know about GDGs. If you have questions AFTER reading them, we can provide guidance -- but you need to read them first; we're neither a manual reading service nor a code (JCL) providing service.

As far as this goes,

If the DISP parameter for a dataset is DISP=(NEW,PASS,CATLG), What will happen when the JCL is run? The first time? The second time?

the questions as stated cannot be answered. The kinds of things we need to know to be able to adequately answer are: Is the data set permanent or temporary? Is the data set under SMS control or not? Is the data set a GDG or not (and if it is, what is the generation limit and which generation is being added)? And why on earth would such a weird disposition be used anyway -- pass the data set to the next step if this step runs normally but catalog the data set if this step abends?

Hi Robert,

And why on earth would such a weird disposition be used anyway -- pass the data set to the next step if this step runs normally but catalog the data set if this step abends?

A few times i've seen this used (in testing) so that the content of a "new" dataset can be seen when the process abends. If the step ran correctly the dataset was "passed" and disposed of later in the test job. More often it was (new, catlg, catlg) for testing and then (new, catlg, delete) when the testing was pretty well finished.

Once upon a time (back in the day of mft/mvt) i seem recall minor wars about the overhead of cataloging versus passing a dataset . . .

My practice has been for a very long time is to only pass datasets with dsn=&&xxxx.tttt.uuu

fwiw. . .

d

In this at the starting of the job a new pds/ps depending on your code is created. In(PASS) normal termination of of the job ps/pds is passed to the next Job, In abnormal termination of the job the ps/pds is Cataloged.