I replied too quickly; he's creating 366 GDG definitions, in which case he can use a system symbol in his DD statement. Unless what he meant is that he wants to define a singe base for the entire year, in which case my reply stands.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Mark Jacobs - Listserv <[email protected]> Sent: Monday, March 12, 2018 1:53 PM To: [email protected] Subject: Re: GDG with timestamp Unless you're using it for something else, the ACCOUNT-INFO field in the catalog entry can be altered to provide the information you need. Not ideal for sure, but can be used. Mark Jacobs Peter<mailto:[email protected]> March 12, 2018 at 1:47 PM Ok thanks for confirming on this... Would have been if it had this feature On 12-Mar-2018 11:14 PM, "Seymour J Metz" <[email protected]><mailto:[email protected]> wrote: > The GDG base is fixed; the GDS has a low level qualifier identifying the > generation and version, colloquially know as goovoo. If you want the date > or anything else from system symbols in the name, don't use a GDS. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3<http://mason.gmu.edu/~smetz3> > > ________________________________________ > From: IBM Mainframe Discussion List > <[email protected]><mailto:[email protected]> on behalf > of Peter <[email protected]><mailto:[email protected]> > Sent: Monday, March 12, 2018 1:32 PM > To: [email protected]<mailto:[email protected]> > Subject: Re: GDG with timestamp > > So using dynamic systems symbols I can make use &YYMMDD, but should I > mention any special value in GDG base to use the dynamic system symbols ? > > On 12-Mar-2018 10:31 PM, "[email protected] > IBM-Main"<mailto:[email protected]> < > [email protected]<mailto:[email protected]>> wrote: > > > The LogFile went to DASD, and the create date was in the VTOC > information, > > For tape files, CA1 would record the create date also. > > > > The GDG Base itself had a create date of early December, The Files in the > > GDG would have create dates when they were created by the +1 .. > > > > Note the 23:00 to 23:59 log would have the create date of the "Next Day" > > as it was created just after midnight, but the GDGBase it was written to > > had the correct log date. (most of the time), Not sure when the logic in > > their log program switched it to the "next" day. If the application was > > down from ~00:00 to ~ 00:15 it would then switch to the "next day" for > the > > logs writting. > > > > Really was not a issue, when the application teams were aware of that > > issue and would code the "next days" gdgbase in to get and random next > day > > data. > > > > ----- Original Message ----- From: "Peter" > > <[email protected]><mailto:[email protected]> > > Newsgroups: bit.listserv.ibm-main > > To: <[email protected]><mailto:[email protected]> > > Sent: Monday, March 12, 2018 12:48 PM > > Subject: Re: GDG with timestamp > > > > > > So how would the GDG base definition would look like so that all the tape > >> GDG has creation date ? > >> > >> On 12-Mar-2018 10:09 PM, "[email protected] > >> IBM-Main"<mailto:[email protected]> < > >> [email protected]<mailto:[email protected]>> wrote: > >> > >> Years ago, we had a vendor application that was setup to create a Hourly > >>> Log File in a GDG. > >>> > >>> Sometime in early December a Step in the Monthly Cycle jobs would > create > >>> the GDG's for the next year (A program created 366 Define GDG Cards) , > >>> Then > >>> trigger a "Admin" job that had the authority to create GDG's. > >>> > >>> GDGnames were Pxx.ApplName.LOGFILES.Syymmdd with one for each day of > the > >>> year. > >>> > >>> Internal to the application it knew what date it was from the system > >>> clock, and starting at 1am (local) would create a +1 Generation (with > >>> the > >>> 00:00-00:59 Logs) at 2am next one ... with the correct GDGbase Name. > >>> > >>> I think we had something like 250 cycles defined in the base, incase > of a > >>> restart of the application it would create a new +1 or a system IPL .. > >>> > >>> The Application code never could figure out Daylight Saving time.. Also > >>> was clueless on leap year, it would create Feb 29th every year even if > it > >>> was not a leap year. > >>> > >>> > >>> > >>> We had other application that did log files at "Flat Files" with Date > and > >>> Time as last two nodes of the dataset names that were generated > >>> dynamically > >>> when created. > >>> > >>> ----- Original Message ----- From: "Peter" > >>> <[email protected]><mailto:[email protected]> > >>> Newsgroups: bit.listserv.ibm-main > >>> To: <[email protected]><mailto:[email protected]> > >>> Sent: Monday, March 12, 2018 11:50 AM > >>> Subject: GDG with timestamp > >>> > >>> > >>> Hi > >>> > >>>> > >>>> Apology for the dummy question > >>>> > >>>> For the GDG to have timestamp on its every generation, how do I ensure > >>>> that > >>>> timestamp gets appended with all that generation created ? > >>>> > >>>> Could someone please point me as I am little confused here. > >>>> > >>>> > >>>> Peter > >>>> > >>>> ------------------------------------------------------------ > ---------- > >>>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>>> send email to [email protected]<mailto:[email protected]> > >>>> with the message: INFO > IBM-MAIN > >>>> > >>>> > >>> ---------------------------------------------------------------------- > >>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>> send email to [email protected]<mailto:[email protected]> > >>> with the message: INFO IBM-MAIN > >>> > >>> > >> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected]<mailto:[email protected]> > >> with the message: INFO IBM-MAIN > >> > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected]<mailto:[email protected]> > > with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected]<mailto:[email protected]> with > the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected]<mailto:[email protected]> with > the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN Please be alert for any emails that may ask you for login information or directs you to login via a link. If you believe this message is a phish or aren't sure whether this message is trustworthy, please send the original message as an attachment to '[email protected]<mailto:[email protected]>'. Seymour J Metz<mailto:[email protected]> March 12, 2018 at 1:43 PM The GDG base is fixed; the GDS has a low level qualifier identifying the generation and version, colloquially know as goovoo. If you want the date or anything else from system symbols in the name, don't use a GDS. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3<http://mason.gmu.edu/~smetz3> ________________________________________ From: IBM Mainframe Discussion List <[email protected]><mailto:[email protected]> on behalf of Peter <[email protected]><mailto:[email protected]> Sent: Monday, March 12, 2018 1:32 PM To: [email protected]<mailto:[email protected]> Subject: Re: GDG with timestamp So using dynamic systems symbols I can make use &YYMMDD, but should I mention any special value in GDG base to use the dynamic system symbols ? On 12-Mar-2018 10:31 PM, "[email protected] IBM-Main"<mailto:[email protected]> < [email protected]<mailto:[email protected]>> wrote: > The LogFile went to DASD, and the create date was in the VTOC information, > For tape files, CA1 would record the create date also. > > The GDG Base itself had a create date of early December, The Files in the > GDG would have create dates when they were created by the +1 .. > > Note the 23:00 to 23:59 log would have the create date of the "Next Day" > as it was created just after midnight, but the GDGBase it was written to > had the correct log date. (most of the time), Not sure when the logic in > their log program switched it to the "next" day. If the application was > down from ~00:00 to ~ 00:15 it would then switch to the "next day" for the > logs writting. > > Really was not a issue, when the application teams were aware of that > issue and would code the "next days" gdgbase in to get and random next day > data. > > ----- Original Message ----- From: "Peter" > <[email protected]><mailto:[email protected]> > Newsgroups: bit.listserv.ibm-main > To: <[email protected]><mailto:[email protected]> > Sent: Monday, March 12, 2018 12:48 PM > Subject: Re: GDG with timestamp > > > So how would the GDG base definition would look like so that all the tape >> GDG has creation date ? >> >> On 12-Mar-2018 10:09 PM, "[email protected] >> IBM-Main"<mailto:[email protected]> < >> [email protected]<mailto:[email protected]>> wrote: >> >> Years ago, we had a vendor application that was setup to create a Hourly >>> Log File in a GDG. >>> >>> Sometime in early December a Step in the Monthly Cycle jobs would create >>> the GDG's for the next year (A program created 366 Define GDG Cards) , >>> Then >>> trigger a "Admin" job that had the authority to create GDG's. >>> >>> GDGnames were Pxx.ApplName.LOGFILES.Syymmdd with one for each day of the >>> year. >>> >>> Internal to the application it knew what date it was from the system >>> clock, and starting at 1am (local) would create a +1 Generation (with >>> the >>> 00:00-00:59 Logs) at 2am next one ... with the correct GDGbase Name. >>> >>> I think we had something like 250 cycles defined in the base, incase of a >>> restart of the application it would create a new +1 or a system IPL .. >>> >>> The Application code never could figure out Daylight Saving time.. Also >>> was clueless on leap year, it would create Feb 29th every year even if it >>> was not a leap year. >>> >>> >>> >>> We had other application that did log files at "Flat Files" with Date and >>> Time as last two nodes of the dataset names that were generated >>> dynamically >>> when created. >>> >>> ----- Original Message ----- From: "Peter" >>> <[email protected]><mailto:[email protected]> >>> Newsgroups: bit.listserv.ibm-main >>> To: <[email protected]><mailto:[email protected]> >>> Sent: Monday, March 12, 2018 11:50 AM >>> Subject: GDG with timestamp >>> >>> >>> Hi >>> >>>> >>>> Apology for the dummy question >>>> >>>> For the GDG to have timestamp on its every generation, how do I ensure >>>> that >>>> timestamp gets appended with all that generation created ? >>>> >>>> Could someone please point me as I am little confused here. >>>> >>>> >>>> Peter >>>> >>>> ---------------------------------------------------------------------- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to [email protected]<mailto:[email protected]> >>>> with the message: INFO IBM-MAIN >>>> >>>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected]<mailto:[email protected]> >>> with the message: INFO IBM-MAIN >>> >>> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected]<mailto:[email protected]> with >> the message: INFO IBM-MAIN >> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected]<mailto:[email protected]> with > the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN Please be alert for any emails that may ask you for login information or directs you to login via a link. If you believe this message is a phish or aren't sure whether this message is trustworthy, please send the original message as an attachment to '[email protected]<mailto:[email protected]>'. Peter<mailto:[email protected]> March 12, 2018 at 1:32 PM So using dynamic systems symbols I can make use &YYMMDD, but should I mention any special value in GDG base to use the dynamic system symbols ? On 12-Mar-2018 10:31 PM, "[email protected] IBM-Main"<mailto:[email protected]> < ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN Please be alert for any emails that may ask you for login information or directs you to login via a link. If you believe this message is a phish or aren't sure whether this message is trustworthy, please send the original message as an attachment to '[email protected]<mailto:[email protected]>'. [email protected] IBM-Main<mailto:[email protected]> March 12, 2018 at 1:01 PM The LogFile went to DASD, and the create date was in the VTOC information, For tape files, CA1 would record the create date also. The GDG Base itself had a create date of early December, The Files in the GDG would have create dates when they were created by the +1 .. Note the 23:00 to 23:59 log would have the create date of the "Next Day" as it was created just after midnight, but the GDGBase it was written to had the correct log date. (most of the time), Not sure when the logic in their log program switched it to the "next" day. If the application was down from ~00:00 to ~ 00:15 it would then switch to the "next day" for the logs writting. Really was not a issue, when the application teams were aware of that issue and would code the "next days" gdgbase in to get and random next day data. Peter<mailto:[email protected]> March 12, 2018 at 12:48 PM So how would the GDG base definition would look like so that all the tape GDG has creation date ? On 12-Mar-2018 10:09 PM, "[email protected] IBM-Main"<mailto:[email protected]> < ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN Please be alert for any emails that may ask you for login information or directs you to login via a link. If you believe this message is a phish or aren't sure whether this message is trustworthy, please send the original message as an attachment to '[email protected]<mailto:[email protected]>'. -- Mark Jacobs Time Customer Service Global Technology Services The standard you walk past is the standard you accept. Lt. Gen. David Morrison This electronic message, including any attachments, may contain proprietary, confidential or privileged information for the sole use of the intended recipient(s). You are hereby notified that any unauthorized disclosure, copying, distribution, or use of this message is prohibited. If you have received this message in error, please immediately notify the sender by reply e-mail and delete it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
