Weird INTRDR with REXX JCL steps

2009-11-10 Thread Todd Burrell
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

Re: Weird INTRDR with REXX JCL steps

2009-11-10 Thread Itschak Mugzach
Todd, In SDSF enter INPUT ON to see of the systsin is empty or not. But the best way is to enter the exec name as a parameter to IKJEFT01 (e.g. //stepx exec pgm=ikjeft01,parm=mkperm,...). ITschak On Tue, Nov 10, 2009 at 7:43 PM, Todd Burrell z...@cdc.gov wrote: I'm having a strange JCL/REXX

SV: Weird INTRDR with REXX JCL steps

2009-11-10 Thread Thomas Berg
List [mailto:ibm-m...@bama.ua.edu] För Todd Burrell Skickat: den 10 november 2009 18:43 Till: IBM-MAIN@bama.ua.edu Ämne: 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

Re: Weird INTRDR with REXX JCL steps

2009-11-10 Thread Burrell, C. Todd (CDC/OCOO/ITSO) (CTR)
Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Itschak Mugzach Sent: Tuesday, November 10, 2009 12:50 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Weird INTRDR with REXX JCL steps Todd, In SDSF enter INPUT ON to see of the systsin is empty

Re: Weird INTRDR with REXX JCL steps

2009-11-10 Thread Hal Merritt
[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

Re: Weird INTRDR with REXX JCL steps

2009-11-10 Thread McKown, John
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hal Merritt Sent: Tuesday, November 10, 2009 12:37 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Weird INTRDR with REXX JCL steps Add a // or /* as the last statement of the job

Re: Weird INTRDR with REXX JCL steps

2009-11-10 Thread Martin Kline
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. Although you have already found a work-around, I suspect you were not writing all of the lines from your REXX code. Did you also close the OUTFIL DD by including the

Re: Weird INTRDR with REXX JCL steps

2009-11-10 Thread Ed Finnell
In a message dated 11/10/2009 12:40:57 P.M. Central Standard Time, john.mck...@healthmarkets.com writes: always put in a /*EOF as well. Nothing like being paranoid! NO GOATS, NO GLORY! Whatever happened to debugging? Write the output to a file and see what you got both ways and compare

Re: Weird INTRDR with REXX JCL steps

2009-11-10 Thread Pinnacle
- Original Message - From: Hal Merritt hmerr...@jackhenry.com Newsgroups: bit.listserv.ibm-main Sent: Tuesday, November 10, 2009 1:38 PM Subject: Re: Weird INTRDR with REXX JCL steps Add a // or /* as the last statement of the job. What he said, but I would do both /* // Regards

Re: Weird INTRDR with REXX JCL steps

2009-11-10 Thread Hunkeler Peter (KIUP 4)
What he said, but I would do both /* // While a // definitely denotes the end of the JCL for the current job, /* does not. /* terminates the current sysin dataset (note that DLM= may denote a different sequence). Why not put the data on the stack and use address TSO submit * from the REXX