And I suppose, you could fail to dub if you don't have a large
enough region or who knows what else? At least querydub is going
to let you gracefully handle a majority of the customer configuration
errors that result in the 2 a.m. calls where your customer support
has to ask, "have you defined an OMVS RACF segment for the user?"
While we've had dozens of these issues, I can't remember ever 
having to tell a customer how to setup their UID or GID. Could it
be better? Sure. Does it at least conform to an 80/20 rule?
Certainly.

In article <caarmm9r74hfqppcxyobfhmvqpjev5ght5l2nczs16m_uvct...@mail.gmail.com> 
you wrote:
> On 8 March 2017 at 11:20, Don Poitras <[email protected]> wrote:
> > That's what querydub tells you.

> Well, kind of...

> > ---
> > QDB_DUB_MAY_FAIL  The task has not been dubbed; an attempt to dub the
> > task may fail. The most likely reason for failure may be a missing or
> > incomplete user security profile; or the lack of an OMVS segment.

> And for
> QDB_DUB_OKAY The task has not been dubbed; an attempt to dub
> the task will probably succeed. The service has
> determined that an OMVS segment exists for the
> task. However, it has not checked for other
> potential errors. It is possible that the task may not
> have the proper UID and GID set up in the security
> profile, causing a subsequent dub failure.

> So you can get a QDB_DUB_OKAY from querydub(), and then it can fail on
> exactly the kinds of security system setup things that I listed in the
> post on MVS-OE. Have I mentioned how much I dislike this wishy-washy
> approach to code and explanations in the UNIX world...? It took a fair
> bit of complaining before IBM added the _BPX_SHAREAS=MUST option;
> before that you could only set _BPX_SHAREAS=YES, and if it couldn't
> honour it, well it just silently ignored it.

> Tony H.

-- 
Don Poitras - SAS Development  -  SAS Institute Inc. - SAS Campus Drive
[email protected]           (919) 531-5637                Cary, NC 27513

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

Reply via email to