Re: Default OMVS segment
Hello, I am trying to setup BPX.UNIQUE.USER. While upgrading RACf template, I am getting below issues. //RACFAIM JOB (657),'VENKAT',CLASS=A,MSGCLASS=X,NOTIFY=SYSUID //STEP EXEC PGM=IRRIRA00,PARM=STAGE(3) //SYSPRINT DD SYSOUT=* IRR66017I The system is currently operating in stage 2. IRR66016I Unexpected RACF manager return code deleting entry G0 in class UNIXMAAP. Return code 80. Reason code 0. 80 (128) This is a data sharing mode return code. A coupling facility function had a problem when dealing with the ICB Can anybody help. Regards On Tue, Feb 11, 2014 at 7:36 PM, Staller, Allan allan.stal...@kbmg.comwrote: BPX.DEFAULT.USER is ignored in z/OS 2.1. This has widely been reported in IBM announcements The Migration Guide and this forum. Check the archives. Your choices are: 1) create the OMVS segment for this user manually. 2) Set up the BPX.UNIQUE.USER/BPX.NEXT.USER environment as described in the manuals. HTH, snip On newly installed z/OS 2.1 system we experiencing OMVS segment not defined issue $HASP373 EZAZSSI STARTED ICH408I JOB(OSNMPD ) STEP(OSNMPD ) CL(PROCESS ) 807 OMVS SEGMENT NOT DEFINED etc... We already defined Steps for setting up default OMVS segments. /snip -- 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: Default OMVS segment
You should join the RACF Group and ask this question. That group could be more helpful. Second, go to Robert Hansel's website. He has many RACF Papers that may help. http://www.rshconsulting.com/racfres.htm I would also review the following SHARE presentation as well https://share.confex.com/share/121/webprogram/Session13846.html And the z/OS V2.1 Migration Guide http://publibz.boulder.ibm.com/epubs/pdf/e0z2m192.pdf Section: z/OS UNIX actions to perform before installing z/OS V2R1 Use the BPX.UNIQUE.USER profile instead of BPX.DEFAULT.USER Description : Before z/OS V1R11, if the BPX.DEFAULT.USER profile in the FACILITY class was defined, users who accessed z/OS UNIX services who did not have an OMVS user or group segment were assigned the default OMVS segments for the length of the user session. All users of the default OMVS segments shared the same UID and GID. As of z/OS V1R11, if BPX.UNIQUE.USER has been defined, users who access z/OS UNIX services who do not have an OMVS user or group segment are automatically assigned an OMVS segment with a unique UID and GID. The new OMVS segments are added to the user and group profiles in the RACF database. As of z/OS V2R1 BPX.DEFAULT.USER has been removed. You may need IBM's assistance because of the shared downward leveled systems, to make it work in your shop. So if you are sharing with z/OS V1.13 and V1.12, then you should be able to do what you need in z/OS V2.1 and convert your lower level systems to use the same process. I am not sure if z/OS V2.1 has some STCs that require an OMVS segment or not. The OSMPD may require a valid OMVS Segment. Check the V2.1 Communication Server manuals or the RACF manuals. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of venkat kulkarni Sent: Monday, February 10, 2014 11:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Default OMVS segment Yes, z/OS V1.13 is planned to be the last release to support *BPX.DEFAULT.USER*. IBM recommends that we either use the BPX.UNIQUE.USER support that was introduced in z/OS V1.11, or assign unique UIDs to users who need them and assign GIDs for their groups. I found below link to enable BPX.UNIQUE.USER support http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r 12.ic ha700%2Fautosvc.htm But as I mentioned, we share the RACF database with downlevel systems, So as per this link we can enable automatic assignment of unique IDs on our current systems and enable default OMVS segment processing on our downlevel systems. In this situation, the two methods can coexist. On Tue, Feb 11, 2014 at 11:39 AM, Paul Gilmartin paulgboul...@aim.comwrote: On Tue, 11 Feb 2014 11:25:54 +0530, venkat kulkarni wrote: Hello, On newly installed z/OS 2.1 system we experiencing OMVS segment not defined issue $HASP373 EZAZSSI STARTED ICH408I JOB(OSNMPD ) STEP(OSNMPD ) CL(PROCESS ) 807 OMVS SEGMENT NOT DEFINED etc... We already defined Steps for setting up default OMVS segments. http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm .zos.r12.icha700%2Fdefomvs.htm Hmmm... You appear to be reading the 1.12 documentation attempting to configure a 2.1 system. I have heard mumblings that the default OMVS system is deprecated; near end-of-life. In the corresponding 2.1 document: http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.icha 700/russ.htm ... I see no mention of a default OMVS segment. Perhaps IBM finally got rid of the wretched thing. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Default OMVS segment
venkat kulkarni wrote: Yes, z/OS V1.13 is planned to be the last release to support *BPX.DEFAULT.USER*. IBM recommends that we either use the BPX.UNIQUE.USER support that was introduced in z/OS V1.11, or assign unique UIDs to users who need them and assign GIDs for their groups. snip Of course, if you are already using BPX.NEXT.USER, you can either continue using that, or choose to convert to BPX.UNIQUE.USER. If you have implemented neither one, UNIQUE is the way to go. One additional note is that NEXT requires the RACF DB to be at AIM stage 2, while UNIQUE requires AIM stage 3. (Both have been around a Long Time.) There's a not-so-new health check for AIM stage 3, that was added for z/OS R12 with UA64936 and for z/OS R13 with UA64937 in April 2012, and a related check to see whether UIDs will be automatically assigned. -- John Eells z/OS Technical Marketing IBM Poughkeepsie ee...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Default OMVS segment
BPX.DEFAULT.USER is ignored in z/OS 2.1. This has widely been reported in IBM announcements The Migration Guide and this forum. Check the archives. Your choices are: 1) create the OMVS segment for this user manually. 2) Set up the BPX.UNIQUE.USER/BPX.NEXT.USER environment as described in the manuals. HTH, snip On newly installed z/OS 2.1 system we experiencing OMVS segment not defined issue $HASP373 EZAZSSI STARTED ICH408I JOB(OSNMPD ) STEP(OSNMPD ) CL(PROCESS ) 807 OMVS SEGMENT NOT DEFINED etc... We already defined Steps for setting up default OMVS segments. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Default OMVS segment
On Tue, 11 Feb 2014 11:25:54 +0530, venkat kulkarni wrote: Hello, On newly installed z/OS 2.1 system we experiencing OMVS segment not defined issue $HASP373 EZAZSSI STARTED ICH408I JOB(OSNMPD ) STEP(OSNMPD ) CL(PROCESS ) 807 OMVS SEGMENT NOT DEFINED etc... We already defined Steps for setting up default OMVS segments. http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.icha700%2Fdefomvs.htm Hmmm... You appear to be reading the 1.12 documentation attempting to configure a 2.1 system. I have heard mumblings that the default OMVS system is deprecated; near end-of-life. In the corresponding 2.1 document: http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.icha700/russ.htm ... I see no mention of a default OMVS segment. Perhaps IBM finally got rid of the wretched thing. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Default OMVS segment
Yes, z/OS V1.13 is planned to be the last release to support *BPX.DEFAULT.USER*. IBM recommends that we either use the BPX.UNIQUE.USER support that was introduced in z/OS V1.11, or assign unique UIDs to users who need them and assign GIDs for their groups. I found below link to enable BPX.UNIQUE.USER support http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.icha700%2Fautosvc.htm But as I mentioned, we share the RACF database with downlevel systems, So as per this link we can enable automatic assignment of unique IDs on our current systems and enable default OMVS segment processing on our downlevel systems. In this situation, the two methods can coexist. On Tue, Feb 11, 2014 at 11:39 AM, Paul Gilmartin paulgboul...@aim.comwrote: On Tue, 11 Feb 2014 11:25:54 +0530, venkat kulkarni wrote: Hello, On newly installed z/OS 2.1 system we experiencing OMVS segment not defined issue $HASP373 EZAZSSI STARTED ICH408I JOB(OSNMPD ) STEP(OSNMPD ) CL(PROCESS ) 807 OMVS SEGMENT NOT DEFINED etc... We already defined Steps for setting up default OMVS segments. http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.icha700%2Fdefomvs.htm Hmmm... You appear to be reading the 1.12 documentation attempting to configure a 2.1 system. I have heard mumblings that the default OMVS system is deprecated; near end-of-life. In the corresponding 2.1 document: http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.icha700/russ.htm ... I see no mention of a default OMVS segment. Perhaps IBM finally got rid of the wretched thing. -- gil -- 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
