Add a // or /* as the last statement of the job.  

There used to be some issues where JES did not know if the submitted job stream 
was complete or not. The // or /* statement was a definitive delimiter for the 
job stream. 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of 
Todd Burrell
Sent: Tuesday, November 10, 2009 11:43 AM
To: IBM-MAIN@bama.ua.edu
Subject: Weird INTRDR with REXX JCL steps

I'm having a strange JCL/REXX issue that I am hoping someone can help with.  
I am running one job that does a listcat, and then depending on the RC from 
the listcat, it will run the final step of the first job which is a REXX exec 
that 
submits JCL to the internal reader.  Here is the JCL for this last job step:

//STEP2    EXEC   PGM=IKJEFT01,DYNAMNBR=240,COND=(0,LT,LISTCAT)   
//SYSTSPRT DD     SYSOUT=*                                        
//SYSEXEC  DD     DISP=SHR,DSN=SYS2.TECH.REXX                     
//INPUTFIL DD     DISP=SHR,DSN=MISC.DATASET.LISTCAT               
//OUTFIL   DD     SYSOUT=(*,INTRDR)                               
//SYSTSIN  DD     *                                               
 MKPERM                                                           

The problem is that this submits a second job that contains 4 steps, of which 
one is similar to this step (REXX exec with SYSTSIN).  It appears that when I 
try to submit the second job through the INTRDR the SYSTSIN in my REXX 
step of the second job gets lost.  I can submit the JCL manually and it works 
fine.  Here's the JCL from the bad step of the second job:

//MKALTER  EXEC  PGM=IKJEFT01,REGION=8M,DYNAMNBR=300  
//SYSEXEC  DD DSN=SYS2.TECH.REXX,DISP=SHR             
//INPUTFIL DD DSN=AB07.PERMMIG.LISTINGS(+1),DISP=SHR  
//OUTFIL   DD DSN=AB07.PERMMIG.ALTERS(+1),UNIT=SYSDA, 
//  SPACE=(CYL,(100,100),RLSE),DISP=(,CATLG)          
//SYSTSPRT DD SYSOUT=*                                
//SYSTSIN  DD *                                       
  MKPERMLC                                            

When I let the job go through the INTRDR the MKPERMLC REXX exec does not 
execute, but when I manually run the JCL this step works fine. 

Does anyone have any ideas about this one? 

Thanks 

Todd Burrell

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to