Well, at least ~one~ person actually addressed his question! I was beginning
to think I was going to have to research it myself, because no one else seemed
to want to answer and I was beginning to feel a sort of corporate embarrassment
about it.
---
Bob Bridges, robhbrid...@gmail.com, cell 336
Thank you all . It looks like security policies will have to be revisited .
I'll go back to the management and see if they are okay to get rid off this
requirement . As others have pointed out , JESJOBS and OPERCMDS would be the
way to go if they insist on keeping these rules .
I am also gonna
Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Robert Hahne [roberthahne...@hotmail.com]
Sent: Wednesday, May 6, 2020 4:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TSO/E SUBMIT exit
Hello listers ,
I understand this is a RACF question . But thought someone can help me here .
We have a r
acter.
Other exits, such as IKJEFF53 may also be affected by these actions.
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Robert Hahne
> Sent: Wednesday, May 06, 2020 1:35 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: TSO/E SUBMIT exit
>
On Wed, 6 May 2020 16:58:59 -0400, David Spiegel wrote:
>+1
+1
>
>On 2020-05-06 16:43, Frank Swarbrick wrote:
>> Are you still wanting to limit "non OPER" users to only those jobs beginning
>> with their user ID? If so, for gods sake why? Sounds very 1960s...
>>
And how do you prevent their foi
Hi Lizette,
But , the JOBCLASS profiles looks to be protecting only the class parameter
within the JCL . We are looking for something that enforce the jobname to start
with their userid
Regards,
Robert
--
For IBM-MAIN subscr
Mainframe Discussion List On Behalf Of
Robert Hahne
Sent: Wednesday, May 6, 2020 2:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO/E SUBMIT exit
Hi Lizette ,
Yes...we run JES2 and SDSF both
Regards,
Robert
From: IBM Mainframe Discussion List on behalf of
Lizette Koe
Hi Lizette ,
Yes...we run JES2 and SDSF both
Regards,
Robert
From: IBM Mainframe Discussion List on behalf of
Lizette Koehler
Sent: Thursday, May 7, 2020 2:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO/E SUBMIT exit
Do you run JES2? Do you have SDSF
Hi Lizette ,
Yes . We run JES2 and SDSF both
Regards,
Robert
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
ert
Hahne
Sent: Wednesday, May 6, 2020 2:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TSO/E SUBMIT exit
Hello listers ,
I understand this is a RACF question . But thought someone can help me here .
We have a requirement where TSO submit exit IKJEFF10 needs to be eliminated .
Currently it is
Do you run JES2? Do you have SDSF? Do you have z/OSEM?
Any tools?
Lizette
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Robert Hahne
Sent: Wednesday, May 6, 2020 1:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TSO/E SUBMIT exit
Hello listers ,
I understand
I agree ..It is a pretty old system and these exits have been out there for
very long and we might get rid off that restriction some time soon .
But , I wanted to eliminate this exit first and was wondering if RACF can do
that .
--
: IBM-MAIN@LISTSERV.UA.EDU
Subject: TSO/E SUBMIT exit
Hello listers ,
I understand this is a RACF question . But thought someone can help me here .
We have a requirement where TSO submit exit IKJEFF10 needs to be eliminated .
Currently it is written to ensure only those users with TSOAUTH
Hello listers ,
I understand this is a RACF question . But thought someone can help me here .
We have a requirement where TSO submit exit IKJEFF10 needs to be eliminated .
Currently it is written to ensure only those users with TSOAUTH(OPER) are
allowed to submit jobs with any name . Rest of t
14 matches
Mail list logo
