Mainframe, MVS and zOS Discussion

The difference between "DD DUMMY" and "DD DSN=empty.dataset" on an input is simply that you need to have an empty dataset allocated which is consuming disk space. Attempting to read either will result in the same outcome; end of file   NOPE when processing a single dataset that ...

from the IBM url of IBM DEVELOPER IBM Developer for z/OS® (IDz) is a modern and robust toolset designed for developing and maintaining IBM z/OS applications using DevOps practices. It enables you to deliver more work faster, with improved quality and greater agility. implementing IDz is not like cha...

why not speak to your operations support to see what is already in place ???

read and meditate on

https://www.redbooks.ibm.com/redbooks/pdfs/sg246366.pdf

most of the questions asked on zOS basics will have an answer there

pretty old but the concepts useful to beginners still applyy to the latest zOS versions

useless topic ...
if you have a question about IBM Developer just ask it
no reason to waste time with useless questions

why should we be thankful for trump inviting zuckerberg to dinner ?

REMEMBER ...
depending on the system setup
the jobs might not be executed in the sequence you see in the submitted file
 

yess

the TS does NOT want to process all the generations
he wants  to pull all the generations names into a file

instead of the nothing attached it would be more useful to see the jes job log with all the related messages

did Your organization consider XMITIP

https://groups.io/g/xmitip

here is a rexx script that will tabulate the block sizes and the relative capacity given the record length usin a record length of 1 will reproduce the capacity table of the manual the rexx script #! /usr/bin/env rexx Trace "o" numeric digits  16 _cmd = "blksxtrk" parse arg args ...

YES

if in step 1 you create gdg_file(+1)

in the second step you will have to refer to it with gdg_file(+1)

the newly created generations will be rolled in at the end of the job

read the manuals, all is explained very well there


 

There is no limit on number fo records because of JOINKEYS, I've used it for millions of records.   pretty primitive answer not based on FACTS, all *Sort* products have a record count limit based on the dasd space available for the sortwk datasets and the relevant *Sort* manuals will tell to custom...

What is correct way of doing it then?

there are a few ways of doing it, all of them technically correct,

since we do not know anything about your organizations standards 
any answer we might give could be wrong

keep talking to your senior to find out your organization recommended way
 

if there is a limit, the syncsort manuals will tell

if you do not have available a CICS environment that you can tweak for your needs you can only learn what you can understand from the documentation ( the cics manuals for example ) but you cannot experiment see here for an example https://www.ibm.com/docs/en/txseries/8.2?topic=channels-example-chann...

where are you facing problems ?
with the logic, or with the code ?