Re: [EXTERNAL] Re: Silly JES2 question

2023-03-01 Thread Dave Jousma
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, the others are just for the users convenience when 
>> submitting a job, or changing jobclasses in SDSF.
>
>Yes, you *were* right.
>However it is no longer true. Since z/OS 2.1 AFAIR.
>JESJOBS class. Srchfor JES.JOBCLASS.OWNER and JES.JOBCLASS.SUBMITTER
>
>--

Well, there you go.   Just learned something new again.Thanks for that 
Radoslaw!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [EXTERNAL] Re: Silly JES2 question

2023-02-28 Thread Radoslaw Skorupka

W dniu 28.02.2023 o 15:18, Dave Jousma pisze:

On Tue, 28 Feb 2023 14:12:03 +, Pommier, Rex  
wrote:


At this point we don't have a system limitation on who can use which job class. 
 It's on my list of to-dos.

We have security on some commands, limiting who can use 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 job classes.

Do you limit who can use those classes?


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, the others are just for the users convenience when submitting 
a job, or changing jobclasses in SDSF.


Yes, you *were* right.
However it is no longer true. Since z/OS 2.1 AFAIR.
JESJOBS class. Srchfor JES.JOBCLASS.OWNER and JES.JOBCLASS.SUBMITTER

--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [EXTERNAL] Re: Silly JES2 question

2023-02-28 Thread Dave Jousma
On Tue, 28 Feb 2023 14:12:03 +, Pommier, Rex  
wrote:

>At this point we don't have a system limitation on who can use which job 
>class.  It's on my list of to-dos.  
>
>We have security on some commands, limiting who can use 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 job classes.
>
>Do you limit who can use those classes?
>

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, the others are just for the users convenience when submitting 
a job, or changing jobclasses in SDSF.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [EXTERNAL] Re: Silly JES2 question

2023-02-28 Thread Pommier, Rex
At this point we don't have a system limitation on who can use which job class. 
 It's on my list of to-dos.  

We have security on some commands, limiting who can use 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 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.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [EXTERNAL] Re: Silly JES2 question

2023-02-27 Thread Paul Gilmartin
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 rejected for such reasons, is the rejection reported in the
program's job log?

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [EXTERNAL] Re: Silly JES2 question

2023-02-27 Thread Jeremy Nicoll
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.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [EXTERNAL] Re: Silly JES2 question

2023-02-27 Thread Pommier, Rex
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 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 ...

--
Jeremy Nicoll - my opinions are my own.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [EXTERNAL] Re: Silly JES2 question

2023-02-27 Thread Pommier, Rex
We have no exits in place looking for anything like this.  Methinks it's a 
waste of a line of JCL.  

Thanks,

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Thompson
Sent: Monday, February 27, 2023 4:45 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] 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:19 PM, Pommier, Rex wrote:
> 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
> //CTRNORST  DD  DUMMY
> //SYSUT1   DD   DATA,DLM='**'
> /*$VS,'F CICSA,CESN USERID=,PS='
> /*$VS,'F CICSA,FOCT C,FILEABC;'
> **
> //SYSUT2   DD  SYSOUT=(*,INTRDR)
> //SYSINDD  DUMMY
> /*$ << my question
> //SYSPRINT DD  SYSOUT=*
> /*
>
> FOCT is a home-grown transaction that closes or opens CICS files.  At the end 
> of the job step is a JES2 command line that appears to do absolutely nothing. 
>  Am I correct in thinking this does nothing and can be removed?  We run a 
> pretty much vanilla JES2 system with no obscure user exits or anything that 
> would be looking for something like this.  The JCL reference manual says 
> nothing about having an empty JES2 command statement.
>
> TIA,
> Rex
>
>
>
> --
> The information contained in this message is confidential, protected from 
> disclosure and may be legally privileged. If the reader of this message is 
> not the intended recipient or an employee or agent responsible for delivering 
> this message to the intended recipient, you are hereby notified that any 
> disclosure, distribution, copying, or any action taken or action omitted in 
> reliance on it, is strictly prohibited and may be unlawful. If you have 
> received this communication in error, please notify us immediately by 
> replying to this message and destroy the material in its entirety, whether in 
> electronic or hard copy format. Thank you.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Regards, Steve Thompson

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: [EXTERNAL] Re: Silly JES2 question

2023-02-27 Thread Pommier, Rex
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 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 to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN