Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
try a batch 3.13 (generate your JCL for the jobstep using 2 as the execution mode, also requesting that you be allowed to edit the jcl before execution.
then concatenate the 100 gdg gens (using the full name).
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
I believe that you wish to find the generation rather than the version. The two terms are both valid but have totally different meanings. Please make sure that you use the correct terminology to elicit the best replies.
This topic has been recently discussed on the forum, and there is a search button at the top of this page.
Joined: 21 Mar 2008 Posts: 161 Location: bangalore
hi expat,
i know this rule, i searched the forum with keywords Generation,version,generation searching,gdg generation searching none i could match with what i needed.....thats why i went on to post .
please can you suggest me the recent topic that was discussed.
Look at the output created in step0300 and if the generated JCL looks right then change the following statement in step0300
Code:
//SORTOUT DD SYSOUT=*
to
Code:
//SORTOUT DD SYSOUT=(*,INTRDR)
dbzTHEdinosauer wrote:
try a batch 3.13 (generate your JCL for the jobstep using 2 as the execution mode, also requesting that you be allowed to edit the jcl before execution.
then concatenate the 100 gdg gens (using the full name).
dbz,
I guess you meant option 3.15 instead of 3.13 (superc). And ISRSUPC can handle a GDG base in batch mode , you don't have to concatenate all the versions manually and ISRSUPC does not give you the concatenation number , except that it treats all of them as a single dataset and just gives the line #