Well, what is the impact if you run twice in the same day? JCL Errors, erroneous data? How do you know if the data was not collected because it was not there or it just failed to run?
Personally, I would rather have function that explicitly create the GDG for the day, then have a preprocessor step that would then determine what data sets need to go into the stream. Build the JCL as needed. I would also try to provide a log of what files were created and which ones were note for problem analysis if needed. OTOH: If you may have missing generations, why not use GDGs as they are normally created. Just create a log process to indicate where or not that days GDG was done and why. Lizette ---> Snip >I want to create twelve GDGs, prefix.whatever.JAN, prefix.whatever.FEB >and so forth. > >Then, instead of creating prefix.whatever.JAN(+1) I want to create >prefix.whatever.JAN.G(day-of-month-with-leading-zeroes)V00 with >DISP=(NEW,CATLG). > >In essence one generation per day of month, with missing generations if we >don't run that day (state holiday or whatever). > >Then I want to be able to read prefix.whatever.JAN as the complete set, >as you can do with GDGs. > >Are there any holes in this theory that I'm overlooking? > <----- UnSnip ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
