You will get a lot of answers. However, you need to consider what you need for
your shop. Assigning OMVS Segments correctly will make your Auditors and PCI
requirements happier.
I recommend the following
1) Join the RACF list and post these types of questions there. You will have a
better audience.
IBMMAIN is a general list. You will get answers but I think you get better
answers when you post to a group that is focused in an area like RACF
To join - go to this URL RACF
http://www.listserv.uga.edu/archives/racf-l.html
Click the LOGIN REQUIRED button, enter a new userid and Password (if you have
not already joined). Then respond to the Confirmation Email.
2) Go to http://www.rshconsulting.com/ and look through the PDFs that are
posted there. Robert Hansel has a lot of great detail on how to manage RACF
and Users
There is a PDF on Replacing BPX.DEFAULT.USER
Issue#2: How will you assign GIDs
• Manually
• Automated (e.g., create GID from department number)
• Sequentially ‐ BPX.NEXT.USER
• Automatically ‐ BPX.UNIQUE.USER
When setting up the RACF USS environment, I think it is good to understand what
can be exposed in your shop. UID(0) is not a good way to setup your USS.
Using BPX.
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Mainframe Mainframe
> Sent: Thursday, June 18, 2015 2:48 AM
> To: [email protected]
> Subject: Re: OMVS segment Issue
>
> Thanks . But when customer is trying to use ping command, they getting
> below error.
>
> CEE5101C During initialization, the callable service BPX1MSS failed.
>
> The system return code was 0000000156 , the reason code was 0B0C00FC
> .
>
> The application will be terminated.
>
>
>
> When I checked for this error, I found below link
>
>
>
> http://www-304.ibm.com/support/knowledgecenter/SS2L7A_5.2.0/doc/ccv-
> install-omvs.html
>
>
>
> and this link talks about this issue, I found below steps
>
>
>
> 1. Define an OMVS segment in RACF for the TSO user IDs that invoke CICS
> Configuration Manager clients.
>
> 2. Allow the TSO user IDs to execute BPX* programs
>
> So, I am not sure what kind of access do I need to give for their user id to
> have ping access.
>
>
>
> On Thu, Jun 18, 2015 at 3:04 PM, Lucas Rosalen <[email protected]>
> wrote:
>
> > Is there any profile protecting BPX* programs in PROGRAM class? Or a
> > generic one, like **.
> > That would be my first bet.
> >
> > Lucas
> > On Jun 18, 2015 11:12 AM, "Mainframe Mainframe"
> > <[email protected]>
> > wrote:
> >
> > > we getting below error while using ping command on tso and
> > > getting failed with
> > >
> > >
> > >
> > > CEE5101C During initialization, the callable service BPX1MSS failed.
> > >
> > > The system return code was 0000000156 , the reason code was
> > > 0B0C00FC .
> > >
> > > The application will be terminated.
> > >
> > >
> > >
> > > When I checked for this error, I found below link
> > >
> > >
> > >
> > >
> > >
> > http://www-
> 304.ibm.com/support/knowledgecenter/SS2L7A_5.2.0/doc/ccv-in
> > stall-omvs.html
> > >
> > >
> > >
> > > and this link talks about this issue, I found below steps
> > >
> > >
> > >
> > > 1. Define an OMVS segment in RACF for the TSO user IDs that invoke
> CICS
> > > Configuration Manager clients.
> > >
> > > 2. Allow the TSO user IDs to execute BPX* programs
> > >
> > >
> > >
> > > But there are many BPX.** profile available in system like
> > >
> > >
> > > BPX.DAEMON
> > >
> > > BPX.FILEATTR.APF
> > >
> > > BPX.FILEATTR.PROGCTL
> > >
> > > BPX.FILEATTR.SHARELIB
> > >
> > > BPX.SERVER
> > >
> > > BPX.SUPERUSER
> > >
> > >
> > > etc
> > >
> > >
> > > Which one to give access, not sure for this ping issue to get resolved.
> > >
> > >
> > > Please suggest.
> > >
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
