Don't know the answer to 'normal' but you are welcome to this FWIW

/* CONSCMD: Rexx to issue any arbitrary console command via SDSF */      
rc=isfcalls('ON')                                                 
Address SDSF ,                                                    
  "ISFEXEC '/" || Arg(1) || "'"                                   
rc=isfcalls('OFF')                                                

//stepname EXEC PGM=IRXJCL,                               
//         PARM='CONSCMD  some.console.command      '         
//*             :        :                             :  
//* NAME OF EXEC <------>:                             :  
//* ARGUMENT             :<--------------------------->:  
//SYSEXEC  DD   DSN=pds.where.above.stored,DISP=SHR         

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Tony Thigpen
Sent: Monday, May 16, 2016 8:21 AM
To: [email protected]
Subject: JCL "COMMAND" statements

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?

2) What is the 'normal' method to issue console commands synchronized with the 
job execution?

--
Tony Thigpen

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to