On Mon, May 16, 2016 at 10:21 AM, Tony Thigpen <t...@vse2pdf.com> wrote:
> I have spent most of my life as a z/VSE and z/VM systems programmer, but > during the last year, I have been managing a couple of z/OS systems in our > small outsourcing shop. > > At this point, I would consider myself just a very knowledgeable, but > still novice z/OS systems programmer. So, be gentle with your replies. :-) > And, please don't laugh. > > Last night/this morning, I have stumped because I noticed that some JCL > set up by a previous systems programmer was not working as it appeared it > should. [At least, until I read the manual.] > > We have many jobs set up something like thus: > > //STEP1 EXEC PGM=IEFBR14 > //COMMD1 COMMAND 'S CICSPTOR' > //WAIT1 EXEC PGM=WAITRCAB,PARM='30' wait 30 seconds > //STEP2 EXEC PGM=IEFBR14 > //COMMD1 COMMAND 'S CICSPDOR' > //WAIT2 EXEC PGM=WAITRCAB,PARM='30' wait 30 seconds > //STEP3 EXEC PGM=IEFBR14 > //COMMD1 COMMAND 'S CICSPAOR1' > //COMMD1 COMMAND 'S CICSPAOR2' > //WAIT3 EXEC PGM=WAITRCAB,PARM='30' wait 30 seconds > //* > > I, of course, though the commands would be synchronized with the execution > JCL. But, we were seeing timing errors that could not be corrected by just > increasing the wait timers. So, I started looking for the problem and found > that all the commands were being issued to the console before the first > IEFBR14 even executed. > > I was totally surprised when I found that IBM documents the COMMAND jcl > card as being processed during the JCL conversion phase and not during the > execution phase. *And* that a previous systems programmer must not have > known it either. > > So, now I have 2 questions for the knowledgeable people on the list: > > 1) Are there any other jcl statements that are executed outside the normal > execution phase? > If you see anything like: /*$VS,'... some z/OS command' it will be executed when read. > > 2) What is the 'normal' method to issue console commands synchronized with > the job execution? I know three. The first is "insecure" and has what many consider a "nasty" requirement. That is to use IEBGENER to copy the command(s) to the INTRDR. This is insecure and a security problem because it allows anyone to issue commands via the INTRDR. The INTRDR needs to be granted the authority to do this. A better way is to download file 246 from http://www.cbttape.org/cbtdowns.htm . This is a batch program which will use the MGCR macro to issue z/OS operator commands. It must be in an APF authorized library. You can user its use by _not_ placing it on the LINKLIST, and securing access to the APF library using your ESM (RACF, TSS, ACF2, other). The last method is to run SDSF in batch and issue commands like you would as a TSO user. I just saw where Ed has a fourth method. -- The unfacts, did we have them, are too imprecisely few to warrant our certitude. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
