Re: Weird thought on misuse of a GDG.
In 93891f43642f3c419a7d75acc2b1db6f3c68cc9...@exchangemb2.dhs.state.ia.us, on 06/11/2012 at 02:58 PM, Roberts, John J jrobe...@dhs.state.ia.us said: Also, what is the significance of the V00 part of the qualifier? It's the version. I was always led to believe that it was a vestige of something that was never implemented. Reminds me of the Samuel Clemens obituary. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Weird thought on misuse of a GDG.
But in today's world, without SCRATCH in the definition, the oldest GDG does not get scratched. It gets rolled off the GDG base and becomes a normal cataloged dataset entry. So it stays in the catalog, and can be referenced by absolute name. I wonder if this would ever be of some use to anyone. What happens when you hit GV00? Does it wrap to GV00 or G0001V00? If so, you could be attempting to catalog a name that already exists. Not a problem for most generation datasets, but I would guess that someone would trip over this someday. Especially if z/OS lasts another 50 years ;-) Also, what is the significance of the V00 part of the qualifier? I was always led to believe that it was a vestige of something that was never implemented. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Weird thought on misuse of a GDG.
With the SCRATCH set you can write it to tape with a tape retention of the number of years for the tape to be kept for a similar result. You either need the tape volser to access it, or you need to catalog it without rolling it in. This will avoid the generation wrap around that is likely if you are creating these fast enough to need more than 255. Thank you and have a Terrific day! Jonathan Goossen, DTM ACT Mainframe Storage Group Personal: 651-361-4541 Department Support Line: 651-361- For help with communication and leadership skills checkout Woodwinds Toastmasters. IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 06/11/2012 02:46:37 PM: From: McKown, John john.mck...@healthmarkets.com To: IBM-MAIN@bama.ua.edu Date: 06/11/2012 02:47 PM Subject: Weird thought on misuse of a GDG. Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Perhaps I didn't get enought sleep during staff meeting, ah I mean last night. But I just had the weirdest thought enter my head. There have been many complaints about the limit of 255 entries in a GDG. Now, I won't debate that at all. But how many people who want more actually need to address the older GDG levels by goovoo number, or do GDG-ALL processing on them? If you have an application where you don't want GDG-ALL, and don't really need to access older GDG levels by relative generation number, what about defining the GDG with a LIMIT of 255 and NOSCRATCH? In the old world of CVOL processes, old GDGs fell off and became uncatalogued. But in today's world, without SCRATCH in the definition, the oldest GDG does not get scratched. It gets rolled off the GDG base and becomes a normal cataloged dataset entry. So it stays in the catalog, and can be referenced by absolute name. I wonder if this would ever be of some use to anyone. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid- West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Weird thought on misuse of a GDG.
The V00 allows you to fix a dataset and replace it with V01. Lets say you have G0001V00 through G0005v00 and you realize that G0003V00 is bad. You can run a job to copy and fix G0003V00 to G0003V01. It will still fall as the middle generation of the 5 datasets. I think I had to do that once, but I can't remember why. I believe when you catalog the V01 generation, the old one gets uncatalogued. Eric Bielefeld - Original Message - From: Roberts, John J jrobe...@dhs.state.ia.us Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@bama.ua.edu Sent: Monday, June 11, 2012 2:58 PM Subject: Re: Weird thought on misuse of a GDG. But in today's world, without SCRATCH in the definition, the oldest GDG does not get scratched. It gets rolled off the GDG base and becomes a normal cataloged dataset entry. So it stays in the catalog, and can be referenced by absolute name. I wonder if this would ever be of some use to anyone. What happens when you hit GV00? Does it wrap to GV00 or G0001V00? If so, you could be attempting to catalog a name that already exists. Not a problem for most generation datasets, but I would guess that someone would trip over this someday. Especially if z/OS lasts another 50 years ;-) Also, what is the significance of the V00 part of the qualifier? I was always led to believe that it was a vestige of something that was never implemented. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Weird thought on misuse of a GDG.
The V00 is the version. I have seen it used once for a conversion. The regular production system kept creating the V00 version while they were testing the new jobs that created the V01 version. When the new jobs went into production replacing the old jobs, they went in creating the V00 version. That was the explanation I received when I questioned the programmer when I saw the V01 on the tapes that I was responsible for. Thank you and have a Terrific day! Jonathan Goossen, DTM ACT Mainframe Storage Group Personal: 651-361-4541 Department Support Line: 651-361- For help with communication and leadership skills checkout Woodwinds Toastmasters. IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 06/11/2012 02:58:51 PM: From: Roberts, John J jrobe...@dhs.state.ia.us To: IBM-MAIN@bama.ua.edu Date: 06/11/2012 02:59 PM Subject: Re: Weird thought on misuse of a GDG. Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu But in today's world, without SCRATCH in the definition, the oldest GDG does not get scratched. It gets rolled off the GDG base and becomes a normal cataloged dataset entry. So it stays in the catalog, and can be referenced by absolute name. I wonder if this would ever be of some use to anyone. What happens when you hit GV00? Does it wrap to GV00 or G0001V00? If so, you could be attempting to catalog a name that already exists. Not a problem for most generation datasets, but I would guess that someone would trip over this someday. Especially if z/OS lasts another 50 years ;-) Also, what is the significance of the V00 part of the qualifier? I was always led to believe that it was a vestige of something that was never implemented. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Weird thought on misuse of a GDG.
From a vague memory, the Vnn was to be used if you had to do a file fix type operation and recreate a specific generation. The system did not help with a way to do this, but if you did it yourself by deleting the V00 version and the cataloguing a V01 (and now-a-days do a ROLLIN), you could access the V01 version using the same relative generation. Or you could do something like: //FIXFILE EXEC PGM=FILEFIX //INPUT DD DSN=GDG.G0127V00,DISP=(OLD,DELETE,KEEP) //OUTPUT DD DSN=GDG.G0127V01,DISP=(NEW,CATLG,DELETE), // ... OTHER PARAMETERS //* then the GDG.G0127V01 would replce GDG.G0127V00 as GDG(-n). And it would be documented that this was a different version, in records such as SMF. I don't remember anybody ever doing it. Personally, I sort of like the UNIX way where I put the ISO date time (ISO 8601 / RFC 3339 format) as the last node. Wish I had a simplier way to do it. Note that it is exactly difficult. Just fiddly to me. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Roberts, John J Sent: Monday, June 11, 2012 2:59 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Weird thought on misuse of a GDG. But in today's world, without SCRATCH in the definition, the oldest GDG does not get scratched. It gets rolled off the GDG base and becomes a normal cataloged dataset entry. So it stays in the catalog, and can be referenced by absolute name. I wonder if this would ever be of some use to anyone. What happens when you hit GV00? Does it wrap to GV00 or G0001V00? If so, you could be attempting to catalog a name that already exists. Not a problem for most generation datasets, but I would guess that someone would trip over this someday. Especially if z/OS lasts another 50 years ;-) Also, what is the significance of the V00 part of the qualifier? I was always led to believe that it was a vestige of something that was never implemented. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Weird thought on misuse of a GDG.
W dniu 2012-06-11 21:58, Roberts, John J pisze: But in today's world, without SCRATCH in the definition, the oldest GDG does not get scratched. It gets rolled off the GDG base and becomes a normal cataloged dataset entry. So it stays in the catalog, and can be referenced by absolute name. I wonder if this would ever be of some use to anyone. What happens when you hit GV00? Does it wrap to GV00 or G0001V00? If so, you could be attempting to catalog a name that already exists. Not a problem for most generation datasets, but I would guess that someone would trip over this someday. Especially if z/OS lasts another 50 years ;-) There is no need to wait 50 years, usually it takes 30 minutes during ... JCL course. I've taught so many groups where there was at least one guy who wanted to check it. ;-) BTW: Much more cumbersome may be can I submit JOB A from JOB A, recurrently? BTW2: In real world datasets, even generated more than daily is ENOUGH. 255 is not of course. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2012 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.410.984 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Weird thought on misuse of a GDG.
At 14:58 -0500 on 06/11/2012, Roberts, John J wrote about Re: Weird thought on misuse of a GDG.: Also, what is the significance of the V00 part of the qualifier? I was always led to believe that it was a vestige of something that was never implemented. It allows you to create a replacement version of Generation without breaking the sequence. Lets say that for some reason you need to replace the contents of X.G0500V00. If you make the replacement X.G0500V01, it will replace the V00 copy in the relative sequence. IOW: When X(-1) is X.G0501V00, X(-2) is X.G0500V01 (in lieu of the replaced V00). This is useful for example if you want to move old files from TAPE to DASD (the V00 signaling that the file was copied to DASD from its original TAPE volume). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
