Thank you all for your help and patience with my RACF command ignorance ...

Yes, the explanation for "OMVS auto-create" is of course FACILITY 
BPX.UNIQUE.USER. I RDELETEd that and now the program fails as expected.

Well, more or less as expected. I think I knew this before but I got excited by 
the thread on the MVS-OE list about testing for the OMVS segment and issuing a 
diagnostic. However the program in question is written in C++ and any "no OMVS 
segment" failure occurs before the first line of user (my) code gets executed, 
so there is no diagnosing it in the program. Yes, I could front-end LE 
initialization but I think that is overkill for this particular problem.

Don't get me wrong: BPX.UNIQUE.USER seems to be goodness and I will put that 
back now that testing is completed.

Thanks again,

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Lizette Koehler
Sent: Wednesday, March 8, 2017 7:19 PM
To: [email protected]
Subject: Re: Which C library functions imply dub?

A snippet from Robert's presentation

To help replace BPX.DEFAULT.USER, z/OS 1.11 introduced the FACILITY class 
profile BPX.UNIQUE.USER. Defining this newer profile causes RACF to 
automatically add OMVS segments and assign ids to users and groups that do not 
already have segments. RACF creates the segments when the user first accesses 
Unix (i.e., dubs). BPX.UNIQUE.USER works in combination with FACILITY class 
profile BPX.NEXT.USER, which defines the uid and gid number ranges to be used 
for automatic id assignment. Use of these profiles requires your databases to 
be in the Application Identity Mapping (AIM) structure.

Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] 
> On Behalf Of Lizette Koehler
> Sent: Wednesday, March 08, 2017 8:14 PM
> To: [email protected]
> Subject: Re: Which C library functions imply dub?
> 
> What version of z/OS is this on?
> 
> I am thinking that RACF (or your SAF) is using an auto assign of the UID.
> There was a change when you had to specify the UID in the OMVS 
> Segment, then a change happened and the system went from 
> BPX.UNIQUE.USER To BPX.NEXT.USER
> 
> See Robert H's very nice presentation
> http://www.rshconsulting.com/racftips/RSH_Consulting__RACF_Tips__April
> _2011.pd
> f
> 
> 
> Lizette
> 
> 
> > -----Original Message-----
> > From: IBM Mainframe Discussion List 
> > [mailto:[email protected]] On Behalf Of Charles Mills
> > Sent: Wednesday, March 08, 2017 7:16 PM
> > To: [email protected]
> > Subject: Re: Which C library functions imply dub?
> >
> > So do OMVS segments get "auto-created?"
> >
> > I run ALU ROMVSNO NOOMVS and then LU ROMVSNO OMVS. I get
> >
> > NO OMVS INFORMATION
> >
> > Then I run a program that ought to require an OMVS segment. It runs 
> > to a normal completion.
> >
> > I then do another LU ROMVSNO OMVS and I get
> >
> > OMVS INFORMATION
> > ----------------
> > UID= 0000990013
> > HOME= /u
> > PROGRAM= /bin/sh
> > CPUTIMEMAX= NONE
> > ASSIZEMAX= NONE
> > FILEPROCMAX= NONE
> >
> > What gives?
> >
> > Charles
> >

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to