Re: IRRPRMxx
On 3/14/2018 3:31 AM, Barbara Nitz wrote: Tom, The way I read this is that the PARMLIB member does not agree with the ICHRDSNT already in use by the RACF sharing group. Are you absolutely sure that the PARMLIB member is correct and agrees with your current ICHRDSNT in every respect? If so, then I would open a PMR for this issue. thanks for giving me a different interpretation of the message. There was an unintended difference in the statistics section. We have reIPL'd, and the message is gone. So no sysplex wide IPL necessary! :-) Barbara Barbara, Wunderbar! Glad it helped. Tom -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IRRPRMxx
Tom, >The way I read this is that the PARMLIB member does not agree with the >ICHRDSNT already in use by the RACF sharing group. Are you absolutely >sure that the PARMLIB member is correct and agrees with your current >ICHRDSNT in every respect? If so, then I would open a PMR for this issue. thanks for giving me a different interpretation of the message. There was an unintended difference in the statistics section. We have reIPL'd, and the message is gone. So no sysplex wide IPL necessary! :-) Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IRRPRMxx
I think I'd start with ===>D PARMLIB,ERROR just to make sure what we're chasing is in the right concatenation. In a message dated 3/13/2018 4:26:56 AM Central Standard Time, pinnc...@rochester.rr.com writes: ICHRDSNT already in use by the RACF sharing group. Are you absolutely sure that the PARMLIB member is correct and agrees with your current ICHRDSNT in every respect? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IRRPRMxx
On 3/13/2018 2:49 AM, Barbara Nitz wrote: Tom, Your 2.3 system will use the IRRPRMxx member and your 2.1 systems will continue to use the information you specified in the ICHRDSNT load module. All we did was take the information that we specify in the load module and put it in a parmlib member. We have not had any issues activating this support in a 2.1/2.3 sysplex environment. Are you saying that you did NOT get *ICH555A ICHRDSNT FOR MEMBER mem1 DOES NOT MATCH ICHRDSNT FOR IRRXCF00 GROUP. GROUP ICHRDSNT IS USED. CORRECT THE PROBLEM AFTER THE IPL TO AVOID A FUTURE SYSTEM OUTAGE. on your 2.3 system? If you did not - we certainly do get it. And the message clearly says that there is no ICHRDSNT on my 2.3 system (obviously, since the information now comes from a parmlib member). Barbara, The way I read this is that the PARMLIB member does not agree with the ICHRDSNT already in use by the RACF sharing group. Are you absolutely sure that the PARMLIB member is correct and agrees with your current ICHRDSNT in every respect? If so, then I would open a PMR for this issue. Tom -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IRRPRMxx
Tom, >Your 2.3 system will use the IRRPRMxx member and your 2.1 systems will >continue to use the information you specified in the ICHRDSNT load module. All >we did was take the information that we specify in the load module and put it >in a parmlib member. We have not had any issues activating this support in a >2.1/2.3 sysplex environment. Are you saying that you did NOT get *ICH555A ICHRDSNT FOR MEMBER mem1 DOES NOT MATCH ICHRDSNT FOR IRRXCF00 GROUP. GROUP ICHRDSNT IS USED. CORRECT THE PROBLEM AFTER THE IPL TO AVOID A FUTURE SYSTEM OUTAGE. on your 2.3 system? If you did not - we certainly do get it. And the message clearly says that there is no ICHRDSNT on my 2.3 system (obviously, since the information now comes from a parmlib member). Walt, unfortunately I cannot post to RACF-L from work, and from work I cannot get at my private email to establish a password at the list server to post from the web interface. (I keep forgetting to do that from my private pc!) We are currently planning to bring up one system in the 2.1 plex with 2.3, and once that works and we corrected all problems, we'll shut down everything and re-IPL the 2.3 system first. But it is a nuisance. And so far I haven't seen the messages when RACF uses only the parmlib member. I'll see that when we'll migrate the first monoplex to 2.3... Thanks, Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IRRPRMxx
Hi Barbara, Your 2.3 system will use the IRRPRMxx member and your 2.1 systems will continue to use the information you specified in the ICHRDSNT load module. All we did was take the information that we specify in the load module and put it in a parmlib member. We have not had any issues activating this support in a 2.1/2.3 sysplex environment. Our parmlib member looks something like this: DATABASE_OPTIONS SYSPLEX(DATASHARING) DATASETNAMETABLE ENTRY PRIMARYDSN(dataset1) BACKUPDSN(dataset2) UPDATEBACKUP(ALL) BUFFERS(255) Regards, Tom -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Barbara Nitz Sent: Monday, March 12, 2018 3:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IRRPRMxx This email originated from outside of the organization. We are in the process of migrating to z/OS 2.3, and I want to use the new IRRPRMxx parmlib member. The documentation in oa52560 is suspiciously silent on how to activate this in a sysplex data sharing environment, so I went through the RACF books. It seems that IRRPRMxx can only be activated with a sysplex wide IPL. Certainly it will not be used in a sysplex environment with two systems (when the other has toleration but still uses ICHDSNT due to it being 2.1): *ICH555A ICHRDSNT FOR MEMBER mem1 DOES NOT MATCH ICHRDSNT FOR IRRXCF00 GROUP. GROUP ICHRDSNT IS USED. CORRECT THE PROBLEM AFTER THE IPL TO AVOID A FUTURE SYSTEM OUTAGE. Is there a way that I just haven't seen to activate this via rolling IPL? (Right out of the box, obviously!) Barbara -- 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: IRRPRMxx
On Mon, 12 Mar 2018 02:19:40 -0500, Barbara Nitz <nitz-...@gmx.net> wrote: >We are in the process of migrating to z/OS 2.3, and I want to use the new >IRRPRMxx parmlib member. The documentation in oa52560 is suspiciously silent >on how to activate this in a sysplex data sharing environment, so I went >through the RACF books. > >It seems that IRRPRMxx can only be activated with a sysplex wide IPL. >Certainly it will not be used in a sysplex environment with two systems (when >the other has toleration but still uses ICHDSNT due to it being 2.1): >*ICH555A ICHRDSNT FOR MEMBER mem1 > DOES NOT MATCH ICHRDSNT FOR IRRXCF00 GROUP. > GROUP ICHRDSNT IS USED. > CORRECT THE PROBLEM AFTER THE IPL TO > AVOID A FUTURE SYSTEM OUTAGE. > >Is there a way that I just haven't seen to activate this via rolling IPL? >(Right out of the box, obviously!) Sounds like a question better directed to RACF-L, where the IBM RACF team will see it. My guess: Not within a single sysplex. (But that is purely a guess.) If you were willing and able to break systems off one-by-one into a new sysplex you could probably do it system-by-system, but I can't predict what would be involved in having a second active sysplex for your environment. -- Walt -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IRRPRMxx
We are in the process of migrating to z/OS 2.3, and I want to use the new IRRPRMxx parmlib member. The documentation in oa52560 is suspiciously silent on how to activate this in a sysplex data sharing environment, so I went through the RACF books. It seems that IRRPRMxx can only be activated with a sysplex wide IPL. Certainly it will not be used in a sysplex environment with two systems (when the other has toleration but still uses ICHDSNT due to it being 2.1): *ICH555A ICHRDSNT FOR MEMBER mem1 DOES NOT MATCH ICHRDSNT FOR IRRXCF00 GROUP. GROUP ICHRDSNT IS USED. CORRECT THE PROBLEM AFTER THE IPL TO AVOID A FUTURE SYSTEM OUTAGE. Is there a way that I just haven't seen to activate this via rolling IPL? (Right out of the box, obviously!) Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
