Re: JCL "COMMAND" statements - Follow-up question

On Wed, 18 May 2016 12:23:33 -0400, Tony Thigpen wrote: >One other question. > >Is there a way to wait between multiple commands when using the TSO >command processor? > >I am guessing that I will need to create a small REXX that waits based >on a parm. > could you call BPXBATCH or BPXWUNIX to

Re: JCL "COMMAND" statements - Follow-up question

"CALL *(BPXBATCH) 'SH sleep 20' ASIS" is what I usually use -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Thigpen Sent: Wednesday, May 18, 2016 12:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL "COMM

Re: JCL "COMMAND" statements - Follow-up question

One other question. Is there a way to wait between multiple commands when using the TSO command processor? I am guessing that I will need to create a small REXX that waits based on a parm. Tony Thigpen Tony Thigpen wrote on 05/17/2016 08:01 AM: Thanks. It turns out that "OC" is part of

Re: JCL "COMMAND" statements - Follow-up question

Where is your SYSEXEC and/or SYSPROC -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ted MacNEIL Sent: Tuesday, May 17, 2016 3:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL "COMMAND" statements - Follow-up question

Re: JCL "COMMAND" statements - Follow-up question

OC is part of OPS/MVS. So you need to look in its libraries. -teD   Original Message   From: Jeremy Nicoll Sent: Tuesday, May 17, 2016 07:30 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: JCL "COMMAND" statements - Follow-up question On Tue, 17 May 2

Re: JCL "COMMAND" statements - Follow-up question

@LISTSERV.UA.EDU Subject: (External):Re: JCL "COMMAND" statements - Follow-up question Thanks. It turns out that "OC" is part of OPS/MVS, so I now can document the job. Tony Thigpen Jeremy Nicoll wrote on 05/17/2016 07:30 AM: > On Tue, 17 May 2016, at 12:19, Tony Thigpen wrote: &g

Re: JCL "COMMAND" statements - Follow-up question

Thanks. It turns out that "OC" is part of OPS/MVS, so I now can document the job. Tony Thigpen Jeremy Nicoll wrote on 05/17/2016 07:30 AM: On Tue, 17 May 2016, at 12:19, Tony Thigpen wrote: OK, dumb question time. My job is working with some JCL I found in another job: //STEP01 EXEC

Re: JCL "COMMAND" statements - Follow-up question

OK, dumb question time. My job is working with some JCL I found in another job: //STEP01 EXEC PGM=IKJEFT1A,REGION=0M //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTERM DD SYSOUT=* //SYSTSOUT DD SYSOUT=* //SYSTSIN DD * OC C('DS QD,TYPE=ALL,ONLINE') /* But, I want to look at the "OC"