Re: GRSRNL Example
I don't have a need to re-invent the Bible, so Sam's word (has always been) is good for me... 😊 zN -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Conley Sent: Tuesday, June 30, 2020 12:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example On 6/30/2020 1:52 PM, Knutson, Samuel wrote: > GRS User Experiences Converting all Reserves Plus Best Practice Tips > and Tricks > <https://www.share.org/p/do/sd/topic=50&sid=3961> > https://www.share.org/p/do/sd/topic=50&sid=3961 > > Circa 2008 but mostly still relevant. > > Thanks, Sam > Sam's session is THE BIBLE on converting GRS reserves. I used it in all my GRS sites. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to <mailto:lists...@listserv.ua.edu> lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRSRNL Example
On 6/30/2020 1:52 PM, Knutson, Samuel wrote: GRS User Experiences Converting all Reserves Plus Best Practice Tips and Tricks https://www.share.org/p/do/sd/topic=50&sid=3961 Circa 2008 but mostly still relevant. Thanks, Sam Sam's session is THE BIBLE on converting GRS reserves. I used it in all my GRS sites. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRSRNL Example
Everything old is new again... Hope y’all are well! Thanks Sam. Sent from my iPad. I take no responsibility for autocorrect... On Jun 30, 2020, at 10:52 AM, Knutson, Samuel wrote: GRS User Experiences Converting all Reserves Plus Best Practice Tips and Tricks https://www.share.org/p/do/sd/topic=50&sid=3961 Circa 2008 but mostly still relevant. Thanks, Sam -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: GRSRNL Example Been a while since I've done this. Anyone have a good example of a GRSRNL for a Sysplex? DASD only shared among the Sysplex members. TIA! zN The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRSRNL Example
GRS User Experiences Converting all Reserves Plus Best Practice Tips and Tricks https://www.share.org/p/do/sd/topic=50&sid=3961 Circa 2008 but mostly still relevant. Thanks, Sam -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: GRSRNL Example Been a while since I've done this. Anyone have a good example of a GRSRNL for a Sysplex? DASD only shared among the Sysplex members. TIA! zN The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FW: GRSRNL Example
Thanks Tom. There are some (old) memory fragments telling me that. There are a lot of defaults, and a lot of quirks. IIRC, if you change the name of DAE (such as DAESHR, which btw, can only be a max of 28 character), you should not include the new name. There used to be a list of the "quirks" someplace. Not sure if there was a Redbook or a WSC whitepaper/flash. Like I said, I haven't touched this in (dare I say?) decades... Think the last time I looked at this was when Nicole Fagan was GRS support at IBM. Hope you're doing well Tom! zN -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Conley Sent: Monday, June 29, 2020 1:05 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: FW: GRSRNL Example On 6/29/2020 2:47 PM, Norman Hollander wrote: > Perfect! Thanks... Don't have ACF2, but I can figure out the RACF ones. > > Norman, Don't put RACF in your exclusion list, it isn't necessary. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRSRNL Example [EXTERNAL]
You are correct Paul. If one member of the Sysplex has a different GRSRNL than the other(s), you will get the 064 wait state. Whenever I change PARMLIB members, I create a new IEASYS which includes any new members. That way, if you have a brain fart along the way, you can easily backout. I'd have to check if the SETGRSRNL command replaces the entire list, or appends the new list. GRSRNL can have multiple members. So if you want IBM's (00) and yours appended, you could easily do that. zN -Original Message- From: IBM Mainframe Discussion List On Behalf Of Feller, Paul Sent: Monday, June 29, 2020 12:57 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example [EXTERNAL] We don't update our GRSRNL to much. Last time it was update was in 2016. There is one thing you might want to watch. We ran into an issue one time when changes did get made an lpar got IPL before a SET GRSRNL=xx command was issues. The lpar would not IPL, it went into a wait state. I don't recall how we got out of the situation. We may have backed out the changes and then IPLed. After that we may have put the changes back in and did the SET GRSRNL=xx command. It has been a few years. So now we have a warning at the top of the member indicating this issue could happen if the SET GRSRNL=xx command does not get done before an IPL is done. Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jesse 1 Robinson Sent: Monday, June 29, 2020 2:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example [EXTERNAL] The two examples given--from Richard Pinion and Jerry Edington--differ quite significantly aside from entries for optional products that a shop may or may not run. Our list, which has evolved over many decades, resembles Jerry's much more than Richard's. I'm not aware of any problems here, but I have to question whether all entries are necessary/useful. This an arena where entries get added but seldom removed. Is there a consensus for spare vs. verbose? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 11:47 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):FW: GRSRNL Example CAUTION EXTERNAL EMAIL Perfect! Thanks... Don't have ACF2, but I can figure out the RACF ones. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Edgington, Jerry Sent: Monday, June 29, 2020 11:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example Here is what I have. // /* SYSTEMS EXCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.DCMLIB) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(SYS1.DUMP) // /* SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN */ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4) // /* SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/ // RNLDEF RNL(CON) TYPE(PATTERN) QNAME(*) /* CONVERT ALL RESERVES */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(IGDCDSXS)/* SMS RESOURCE NAME */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIGGV2)/* CATALOGS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZRACF)/* RACF DATABASE */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZVVDS)/* VVDS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSVTOC) /* DISK VTOC */ //
Re: GRSRNL Example
Seems to me that too many extraneous entries could take extra processing to scan the entries each time, and would take up extra storage. I think moving to more generic (or pattern) type of entries may have an advantage. Definitely need the reserves converted. Be sure you are only sharing DASD within the Sysplex. Outside needs special handling (and you would not be able to use Star mode). There is a lot more reporting (D GRS commands), and GRS monitoring that would help determine how effective the list is. zN -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jesse 1 Robinson Sent: Monday, June 29, 2020 12:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example The two examples given--from Richard Pinion and Jerry Edington--differ quite significantly aside from entries for optional products that a shop may or may not run. Our list, which has evolved over many decades, resembles Jerry's much more than Richard's. I'm not aware of any problems here, but I have to question whether all entries are necessary/useful. This an arena where entries get added but seldom removed. Is there a consensus for spare vs. verbose? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 11:47 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):FW: GRSRNL Example CAUTION EXTERNAL EMAIL Perfect! Thanks... Don't have ACF2, but I can figure out the RACF ones. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Edgington, Jerry Sent: Monday, June 29, 2020 11:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example Here is what I have. // /* SYSTEMS EXCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.DCMLIB) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(SYS1.DUMP) // /* SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN */ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4) // /* SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/ // RNLDEF RNL(CON) TYPE(PATTERN) QNAME(*) /* CONVERT ALL RESERVES */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(IGDCDSXS)/* SMS RESOURCE NAME */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIGGV2)/* CATALOGS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZRACF)/* RACF DATABASE */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZVVDS)/* VVDS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSVTOC) /* DISK VTOC */ // /* SYSTEMS INCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(IXGLOGR) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSIKJBC) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSZVOLS) /* AUTO TAPE SWITCHING AND VOLUMES */ /* */ // /* CA ACF2 */ // RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.LOGONIDS) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.ALTLIDS) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.RULES) RNLDEF RNL(EXCL) TYPE(SP
Re: FW: GRSRNL Example
On 6/29/2020 2:47 PM, Norman Hollander wrote: Perfect! Thanks... Don't have ACF2, but I can figure out the RACF ones. Norman, Don't put RACF in your exclusion list, it isn't necessary. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRSRNL Example [EXTERNAL]
Paul, That can happen, if the GRSRNL is out sync between LPARs. You would need to setup the LPAR with GRSRNL that is currently running on the LPAR which is still up. Then after the LPAR is up and running, you might be able to issue SET GRSRNL=xx, depending upon the changes. I have hit that situation before. :) Jerry -Original Message- From: IBM Mainframe Discussion List On Behalf Of Feller, Paul Sent: Monday, June 29, 2020 3:57 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example [EXTERNAL] This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. We don't update our GRSRNL to much. Last time it was update was in 2016. There is one thing you might want to watch. We ran into an issue one time when changes did get made an lpar got IPL before a SET GRSRNL=xx command was issues. The lpar would not IPL, it went into a wait state. I don't recall how we got out of the situation. We may have backed out the changes and then IPLed. After that we may have put the changes back in and did the SET GRSRNL=xx command. It has been a few years. So now we have a warning at the top of the member indicating this issue could happen if the SET GRSRNL=xx command does not get done before an IPL is done. Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jesse 1 Robinson Sent: Monday, June 29, 2020 2:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example [EXTERNAL] The two examples given--from Richard Pinion and Jerry Edington--differ quite significantly aside from entries for optional products that a shop may or may not run. Our list, which has evolved over many decades, resembles Jerry's much more than Richard's. I'm not aware of any problems here, but I have to question whether all entries are necessary/useful. This an arena where entries get added but seldom removed. Is there a consensus for spare vs. verbose? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 11:47 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):FW: GRSRNL Example CAUTION EXTERNAL EMAIL Perfect! Thanks... Don't have ACF2, but I can figure out the RACF ones. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Edgington, Jerry Sent: Monday, June 29, 2020 11:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example Here is what I have. // /* SYSTEMS EXCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.DCMLIB) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(SYS1.DUMP) // /* SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN */ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4) // /* SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/ // RNLDEF RNL(CON) TYPE(PATTERN) QNAME(*) /* CONVERT ALL RESERVES */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(IGDCDSXS)/* SMS RESOURCE NAME */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIGGV2)/* CATALOGS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZRACF)/* RACF DATABASE */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZVVDS)/* VVDS */ RNLDEF RNL(CON) TYPE(GENERIC)
Re: GRSRNL Example [EXTERNAL]
We don't update our GRSRNL to much. Last time it was update was in 2016. There is one thing you might want to watch. We ran into an issue one time when changes did get made an lpar got IPL before a SET GRSRNL=xx command was issues. The lpar would not IPL, it went into a wait state. I don't recall how we got out of the situation. We may have backed out the changes and then IPLed. After that we may have put the changes back in and did the SET GRSRNL=xx command. It has been a few years. So now we have a warning at the top of the member indicating this issue could happen if the SET GRSRNL=xx command does not get done before an IPL is done. Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jesse 1 Robinson Sent: Monday, June 29, 2020 2:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example [EXTERNAL] The two examples given--from Richard Pinion and Jerry Edington--differ quite significantly aside from entries for optional products that a shop may or may not run. Our list, which has evolved over many decades, resembles Jerry's much more than Richard's. I'm not aware of any problems here, but I have to question whether all entries are necessary/useful. This an arena where entries get added but seldom removed. Is there a consensus for spare vs. verbose? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 11:47 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):FW: GRSRNL Example CAUTION EXTERNAL EMAIL Perfect! Thanks... Don't have ACF2, but I can figure out the RACF ones. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Edgington, Jerry Sent: Monday, June 29, 2020 11:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example Here is what I have. // /* SYSTEMS EXCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.DCMLIB) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(SYS1.DUMP) // /* SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN */ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4) // /* SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/ // RNLDEF RNL(CON) TYPE(PATTERN) QNAME(*) /* CONVERT ALL RESERVES */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(IGDCDSXS)/* SMS RESOURCE NAME */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIGGV2)/* CATALOGS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZRACF)/* RACF DATABASE */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZVVDS)/* VVDS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSVTOC) /* DISK VTOC */ // /* SYSTEMS INCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(IXGLOGR) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSIKJBC) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSZVOLS) /* AUTO TAPE SWITCHING AND VOLUMES */ /* */ // /* CA ACF2 */ // RNLDEF RNL(EXCL) TYPE(
Re: GRSRNL Example
The two examples given--from Richard Pinion and Jerry Edington--differ quite significantly aside from entries for optional products that a shop may or may not run. Our list, which has evolved over many decades, resembles Jerry's much more than Richard's. I'm not aware of any problems here, but I have to question whether all entries are necessary/useful. This an arena where entries get added but seldom removed. Is there a consensus for spare vs. verbose? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 11:47 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):FW: GRSRNL Example CAUTION EXTERNAL EMAIL Perfect! Thanks... Don't have ACF2, but I can figure out the RACF ones. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Edgington, Jerry Sent: Monday, June 29, 2020 11:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example Here is what I have. // /* SYSTEMS EXCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.DCMLIB) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(SYS1.DUMP) // /* SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN */ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4) // /* SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/ // RNLDEF RNL(CON) TYPE(PATTERN) QNAME(*) /* CONVERT ALL RESERVES */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(IGDCDSXS)/* SMS RESOURCE NAME */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIGGV2)/* CATALOGS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZRACF)/* RACF DATABASE */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZVVDS)/* VVDS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSVTOC) /* DISK VTOC */ // /* SYSTEMS INCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(IXGLOGR) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSIKJBC) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSZVOLS) /* AUTO TAPE SWITCHING AND VOLUMES */ /* */ // /* CA ACF2 */ // RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.LOGONIDS) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.ALTLIDS) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.RULES) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.ALTRULES) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.INFOSTG) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.ALTINFO) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSVSAM) RNAME(ACF.ACF2) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(ACF.ACF2) /* */ -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: GRSRNL Example Been a while since I've done this. Anyone have a good example of a GRSRNL for a Sysplex? DASD only shared among the
FW: GRSRNL Example
Perfect! Thanks... Don't have ACF2, but I can figure out the RACF ones. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Edgington, Jerry Sent: Monday, June 29, 2020 11:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GRSRNL Example Here is what I have. // /* SYSTEMS EXCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.DCMLIB) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(SYS1.DUMP) // /* SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN */ // /* */ RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4) // /* SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/ // RNLDEF RNL(CON) TYPE(PATTERN) QNAME(*) /* CONVERT ALL RESERVES */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(IGDCDSXS)/* SMS RESOURCE NAME */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSIGGV2)/* CATALOGS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZRACF)/* RACF DATABASE */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSZVVDS)/* VVDS */ RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SYSVTOC) /* DISK VTOC */ // /* SYSTEMS INCLUSION RESOURCE NAME LIST*/ // /* */ RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(IXGLOGR) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSIKJBC) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSZVOLS) /* AUTO TAPE SWITCHING AND VOLUMES */ /* */ // /* CA ACF2 */ // RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.LOGONIDS) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.ALTLIDS) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.RULES) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.ALTRULES) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.INFOSTG) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF.ACF2.ALTINFO) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSVSAM) RNAME(ACF.ACF2) RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(ACF.ACF2) /* */ -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: GRSRNL Example This message was sent from an external source outside of Western & Southern&
Re: GRSRNL Example
) /* */ -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: GRSRNL Example This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. Been a while since I've done this. Anyone have a good example of a GRSRNL for a Sysplex? DASD only shared among the Sysplex members. TIA! zN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GRSRNL Example
This is what we are using. /* SYSTEMS EXCLUSION RESOURCE NAME LIST - RNLDEF STATEMENTS*/ - - - - - - - - - - - - - - - - - - 1 Line(s) not Displayed RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.DEVB.DAE) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.FXPA.DAE) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.PRDA.DAE) RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.BRODCAST) - - - - - - - - - - - - - - - - - - 7 Line(s) not Displayed /* SYSTEM INCLUSION RESOURCE NAME LIST - RNLDEF STATEMENTS */ - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SPFEDIT) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSZVOLS) - - - - - - - - - - - - - - - - - - 3 Line(s) not Displayed /* SYSTEM INCLUSION RESOURCE NAME LIST - RNLDEF STATEMENTS */ - - - - - - - - - - - - - - - - - - 3 Line(s) not Displayed /* RESERVE CONVERSION RESOURCE NAME LIST - RNLDEF STATEMENTS */ - - - - - - - - - - - - - - - - - - 2 Line(s) not Displayed RNLDEF RNL(CON) TYPE(PATTERN) QNAME(*) - - - - - - - - - - - - - - - - - - 5 Line(s) not Displayed -Original Message- From: IBM Mainframe Discussion List On Behalf Of Norman Hollander Sent: Monday, June 29, 2020 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: GRSRNL Example [External Email. Exercise caution when clicking links or opening attachments.] Been a while since I've done this. Anyone have a good example of a GRSRNL for a Sysplex? DASD only shared among the Sysplex members. TIA! zN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
GRSRNL Example
Been a while since I've done this. Anyone have a good example of a GRSRNL for a Sysplex? DASD only shared among the Sysplex members. TIA! zN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
