Mark,
No, we missed that too. AND, I see there is now an AUTH=(ALLOPER) and an
AUTH=(ALLUSER), which I now need to investigate and see what's under them.
At 03:53 PM 10/4/2005, you wrote:
Speaking of SDSF authorizations...
Did anyone using ISFPRMxx or ISFPARMS notice that you can now
I havew a problem with SDSF under z/OS 1.4. I have a user who needs to
see jobs which are not hers. She can see a listing of all the jobs she
just can't look at any output.
The folling are the SDSFPARMS entries that I have set up but they don't
work. She still gets 'Not authorized for job' message
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of John C. Wolf
Sent: Tuesday, October 04, 2005 1:22 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF authorizing
I havew a problem with SDSF under z/OS 1.4. I have a user who needs to
see jobs
Did you refresh the SDSF server?
Did you have the user re-enter SDSF (as in =s) after doing so?
[...(SFA),OFFSET(5) is easier.]
Bob
John C. Wolf wrote:
I havew a problem with SDSF under z/OS 1.4. I have a user who needs to
see jobs which are not hers. She can see a listing of all the jobs
:[EMAIL PROTECTED]
Behalf Of McKown, John
Sent: Tuesday, October 04, 2005 2:50 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SDSF authorizing
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of John C. Wolf
Sent: Tuesday, October 04, 2005 1:22 PM
Yes I did a 'f sdsf,refresh,m=22' after SDSF said that it had refreshed
the parms I had our user logoff TSO and log back on no go.
We use ACF2 here and we control our SDSF users via the SDFF parms and
don't use ACf2
--
For
Does she have the appropriate RACF authorities in the JESSPOOL class?
We use ACF2 here and she can look at her own jobs output all right.
We control our SDSF users via the SDSF parm route.
John Wolf
--
For IBM-MAIN subscribe /
, October 04, 2005 12:41 PM
Subject: Re: SDSF authorizing
Does she have the appropriate RACF authorities in the JESSPOOL class?
We use ACF2 here and she can look at her own jobs output all right.
We control our SDSF users via the SDSF parm route.
John Wolf
Rich,
In your message you asked me to have her do a who and you were right the
relevant fieldes GRPINDEX=48,GRPNAME=ISF00048 are for the group which is
directly ahead of her and their IUID is IUID(DFSA) which is the high order
four bytes of her id which is DFSADJP.
So what should I do? should I
Speaking of SDSF authorizations...
Did anyone using ISFPRMxx or ISFPARMS notice that you can now
specify AUTH(ALL) as of z/OS 1.5 instead of listing all of the
individual commands? I didn't until the SDSF PTF was applied
to support the new CK (Health Checker) command and I went to
add the new
Yes. The most restrictive entries have to be first.
Bob
John C. Wolf wrote:
Rich,
In your message you asked me to have her do a who and you were right the
relevant fieldes GRPINDEX=48,GRPNAME=ISF00048 are for the group which is
directly ahead of her and their IUID is IUID(DFSA) which is the
@BAMA.UA.EDU
Subject: Re: SDSF authorizing
Rich,
In your message you asked me to have her do a who and you were right
the
relevant fieldes GRPINDEX=48,GRPNAME=ISF00048 are for the group which
is
directly ahead of her and their IUID is IUID(DFSA) which is the high
order
four bytes of her id which
OK I moved her entrie above the DSFA entrie and she still gets put into
the group that is defined to the IUID(DSFA) which is now after
IUID(DSFADJP). I am noe think that I will have to define a unice IUID for
all DSFA users.
Does this sound right?
If any one wants to e-amil me please use my work
13 matches
Mail list logo