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 can be protected by OPERCMDS, but this is not
the case.
3. $ is just command prefix. It is not a command. If you type that on
console and press ENTER you will get IEE707I $ NOT EXECUTED.
4. However in this case no command or pseudo-command will be issued. So
no IEE707I, nor ICH408I. Nothing.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 27.02.2023 o 23:19, Pommier, Rex pisze:
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)
//SYSIN DD 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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
