GDG is great in most circumstances. When you have unpredictable/unknown level of databse update activities the number of database regeneration log datasets created can varies a lot. During database recovery/regeneration (whether DR situation or not) you want to be sure the latest dataset to be on disk and not moved to multi file cart. We all know reading from multi-dataset tape/cart can be a pain. This is just one example.
I am not sure which set my sysprog used. We were in a relatively small shop. On Thu, Apr 9, 2009 at 7:48 AM, Ted MacNEIL <[email protected]> wrote: > >I was a DBA not a sysprog so I asked my sysprog to changed the JES exit to > support the specification of date and time as part of the new output > dataset name. > >This allows me to do such things as managing the deletion of obsolete > backups etc by dataset creation date and time instead of GDG generations. > > What was wrong with GDG's? > > Your exit request still has issue. > The same one that using SYSTEM SYMBOLS in Batch JCL. > > Which set do you use: > 1. Submitting system? > 2. Converting system? > 3. Executing system? > > IBM's choice follows the principle of 'least astonishment'. > Unless you have a single image environment, you have an exposure. > > - > Too busy driving to stop for gas! > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
