ESOTERIC decomissioning
You can find entries in a catalog that specify an esoteric. They look like x'8000' (tape) or x'2000' (disk) where is a binary sequence number. Other than say JES2 EXIT 6 or something similar, it would be harder to identify jobs that specify an esoteric. A batch job will JCL error if it specifies an esoteric that no longer exists. The problem with esoterics in the catalog is that there is a sequence number included in the device type entry, so if you remove one, all the other ones with larger sequence numbers will change; so if there are esoterics in catalog entries, they may point to a different esoteric. IIRC z/OS uses the real device type, so someone would have had to use IDCAMS DEFINE (or equivalent) to create a catalog entry that specifies an esoteric. Bill [EMAIL PROTECTED] wrote: > G'day > I did do a fair amount of reading on the list to see if someone has > already done something of this sort. Apparently yes but with way more > experience than I have. Hence asking for help. > > We are in the process of decomissioning old ESOTERICs. I would like to > know if there is a possibility for me to track who is using a > particular ESOTERIC. To the best of my knowledge this is not available > in SMF, can't be directly figured out from the CATALOG entries through > DEVTYPE. I read most of what Bruce Black and others discussed. Still > can't see the light. > > Any help is greatly appreciated. > > brgds > @sh. -- 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
Re: ESOTERIC decomissioning
There is the utility IEFESO in SAMPLIB, in conjunction with the member IEFESOJL. You can modify the asm code to your liking. We did some very basic changes to it to get what we wanted. I ended up with a report like this: Data set FAC.CB.CH.CIMSDISK.BKPOCT03 was found to be cataloged using esoteric CARTF02645 1 Data set FAC.CB.CH.CIMSDISK.OCT03 was found to be cataloged using esoteric CARTF02651 1 Data set FAC.CB.SPD.HSTAUG92 was found to be cataloged using esoteric CARTF19845 1 Data set FAC.COB2TEST was found to be cataloged using esoteric Data set FAC.HM.HELPERS2 was found to be cataloged using esoteric Data set FAC.MVS.SMFAPR01.P1 was found to be cataloged using esoteric CARTR00123 1 Data set FAC.MVS.SMFAPR01.P1 was found to be cataloged using esoteric CARTR00048 1 Data set FAC.PP.LINKLIB was found to be cataloged using esoteric Data set FAC.TP.HELPERS.TCPTSTwas found to be cataloged using esoteric Of course, you probably should scan JCL libraries and change to using a Generic name like '3480'. gabe [EMAIL PROTECTED] wrote: > G'day > I did do a fair amount of reading on the list to see if someone has > already done something of this sort. Apparently yes but with way more > experience than I have. Hence asking for help. > > We are in the process of decomissioning old ESOTERICs. I would like > to know if there is a possibility for me to track who is using a > particular ESOTERIC. To the best of my knowledge this is not > available in SMF, can't be directly figured out from the CATALOG > entries through DEVTYPE. I read most of what Bruce Black and others > discussed. Still can't see the light. > > Any help is greatly appreciated. > > brgds > @sh. -- 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
Re: ESOTERIC decomissioning
At 17:16 -0600 on 11/16/2005, Big Iron wrote about ESOTERIC decomissioning: The problem with esoterics in the catalog is that there is a sequence number included in the device type entry, so if you remove one, all the other ones with larger sequence numbers will change; so if there are esoterics in catalog entries, they may point to a different esoteric. IIRC z/OS uses the real device type, so someone would have had to use IDCAMS DEFINE (or equivalent) to create a catalog entry that specifies an esoteric. I may be wrong but I have the impression that if you open a cataloged dataset that has an esoteric device type, the catalog is automatically updated (I think at close time) to have the correct device type (IOW: As you access datasets, any esoterics are replaced with the correct device type value for that volume). -- 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
Re: ESOTERIC decomissioning
On Wed, 16 Nov 2005 17:16:58 -0600, Big Iron <[EMAIL PROTECTED]> wrote: > >The problem with esoterics in the catalog is that there is a >sequence number >included in the device type entry, so if you remove one, all the other ones >with larger sequence numbers will change; so if there are esoterics in >catalog entries, they may point to a different esoteric. This hasn't been an issue since MVS/ESA V5. You assign tokens (a number) in the HCD along with the esoteric, so if you remove an esoteric the tokens for the ones that remain don't change. If you currently have no tokens assigned in your HCD, just assign them. Regards, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America and Farmers Insurance Group mailto: [EMAIL PROTECTED] Systems Programming expert at http://Search390.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: ESOTERIC decomissioning
Mark, If Tokens were assigned, wouldn't any current cataloged dataset using an esoteric have to be uncataloged, then cataloged? Or at least assign a Token that matches the entry in the table. gabe -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark Zelden Sent: Thursday, November 17, 2005 7:09 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: ESOTERIC decomissioning On Wed, 16 Nov 2005 17:16:58 -0600, Big Iron <[EMAIL PROTECTED]> wrote: > >The problem with esoterics in the catalog is that there is a sequence >number included in the device type entry, so if you remove one, all the >other ones with larger sequence numbers will change; so if there are >esoterics in catalog entries, they may point to a different esoteric. This hasn't been an issue since MVS/ESA V5. You assign tokens (a number) in the HCD along with the esoteric, so if you remove an esoteric the tokens for the ones that remain don't change. If you currently have no tokens assigned in your HCD, just assign them. Regards, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America and Farmers Insurance Group mailto: [EMAIL PROTECTED] Systems Programming expert at http://Search390.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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 -- 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
Re: ESOTERIC decomissioning
One could presumably assign tokens to match the existing numbers associated with those esoterics, Bill On Thu, 17 Nov 2005 08:14:17 -0800, Gabe Torres <[EMAIL PROTECTED]> wrote: >Mark, > If Tokens were assigned, wouldn't any current cataloged dataset using >an esoteric have to be uncataloged, then cataloged? Or at least assign >a Token that matches the entry in the table. > >gabe > > > >-Original Message- >From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On >Behalf Of Mark Zelden >Sent: Thursday, November 17, 2005 7:09 AM >To: IBM-MAIN@BAMA.UA.EDU >Subject: Re: ESOTERIC decomissioning > >On Wed, 16 Nov 2005 17:16:58 -0600, Big Iron ><[EMAIL PROTECTED]> >wrote: > >> >>The problem with esoterics in the catalog is that there is a sequence >>number included in the device type entry, so if you remove one, all the > >>other ones with larger sequence numbers will change; so if there are >>esoterics in catalog entries, they may point to a different esoteric. > >This hasn't been an issue since MVS/ESA V5. You assign tokens (a >number) in the HCD along with the esoteric, so if you remove an esoteric >the tokens for the ones that remain don't change. > >If you currently have no tokens assigned in your HCD, just assign them. > >Regards, > >Mark >-- >Mark Zelden >Sr. Software and Systems Architect - z/OS Team Lead Zurich North America >and Farmers Insurance Group >mailto: [EMAIL PROTECTED] >Systems Programming expert at http://Search390.com/ateExperts/ Mark's >MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
