On Wed, 1 Mar 2023 00:04:16 +0100, Radoslaw Skorupka
wrote:
>W dniu 28.02.2023 o 15:18, Dave Jousma pisze:
>>
>> There is no native z/OS support to limit who can use what job classes. We
>> had to RYO inserting SAF calls in IEFUJI, IKJEFF10, and ISFUSR.IEFUJI is
>> the real gate keeper,
Few notes:
1. Folks mentioned JOBCLASS definition in regard to operator commands.
However COMMAND=EXECUTE does *not* mean "any command will be accepted.
Every command will be *RACF-checked* using OPERCMDS profiles. So, D A,L
will probably be accepted, but FORCE not.
2. Even unknown command ca
them.
Rex
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Jeremy Nicoll
Sent: Monday, February 27, 2023 5:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Silly JES2 question
On Mon, 27 Feb 2023, at 23:09, Pommier, Rex wrote:
We have COMMAND=EXECUTE on a couple j
Message-
>From: IBM Mainframe Discussion List On Behalf Of
>Jeremy Nicoll
>Sent: Monday, February 27, 2023 5:58 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: [EXTERNAL] Re: Silly JES2 question
>
>On Mon, 27 Feb 2023, at 23:09, Pommier, Rex wrote:
>> We have COMMAND
ebruary 27, 2023 5:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Silly JES2 question
On Mon, 27 Feb 2023, at 23:09, Pommier, Rex wrote:
> We have COMMAND=EXECUTE on a couple job classes.
Do you limit who can use those classes?
Does anything (RACF or whatever) limit which co
On Mon, 27 Feb 2023 23:58:25 +, Jeremy Nicoll wrote:
>On Mon, 27 Feb 2023, at 23:09, Pommier, Rex wrote:
>> We have COMMAND=EXECUTE on a couple job classes.
>
>Do you limit who can use those classes?
>
>Does anything (RACF or whatever) limit which commands can
>be executed?
>
If a command is r
On Mon, 27 Feb 2023, at 23:09, Pommier, Rex wrote:
> We have COMMAND=EXECUTE on a couple job classes.
Do you limit who can use those classes?
Does anything (RACF or whatever) limit which commands can
be executed?
--
Jeremy Nicoll - my opinions are my own.
--
We have COMMAND=EXECUTE on a couple job classes.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Jeremy Nicoll
Sent: Monday, February 27, 2023 5:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Silly JES2 question
On Mon, 27 Feb 2023, at 22:48, Steve Smith
On Mon, 27 Feb 2023, at 22:48, Steve Smith wrote:
> JES2 ignores command statements imbedded in a job anyway.
Doesn't that depend on the COMMAND= parm in the JES2 jobclass
that the job is running in, in theory? Or has that parameter option
been removed?
I suppose some sites might allow it ...
-
ERNAL] Re: Silly JES2 question
/*$ may be used as a JES2 command. Now, do you have an exit that looks for
this and takes some action?
I was studying the JCL REF after not having really read one for 5 or so years,
to find new stuff done to/with/for JCL|JECL.
Steve Thompson
On 2/27/2023 5:
That's what I was thinking. We have no exits looking for it.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Smith
Sent: Monday, February 27, 2023 4:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Silly JES2 question
Looks to me as useless a
Looks to me as useless as the trailing /*. It may be interpreted as
another useless /*. JES2 ignores command statements imbedded in a job
anyway.
sas
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email
/*$ may be used as a JES2 command. Now, do you have an exit that
looks for this and takes some action?
I was studying the JCL REF after not having really read one for 5
or so years, to find new stuff done to/with/for JCL|JECL.
Steve Thompson
On 2/27/2023 5:19 PM, Pommier, Rex wrote:
Hi all
Hi all,
I have a silly question that I'm pretty sure I know the answer to but want
verification in case there's some obscure reason for having this. We have
multiple batch job steps that close and open CICS files within the JCL. They
look similar to this:
//STEP010 EXEC PGM=IEBGENER
14 matches
Mail list logo
