A major clue that 'OC' is not an exec is the absence of SYSPROC or SYSEXEC in the job stream. That pretty much indicates a load module somewhere in linklist or LPA. There are tools previously discussed here to track down such a module.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tony Thigpen Sent: Tuesday, May 17, 2016 5:01 AM To: [email protected] 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: >> 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" rexx and I can not find it in any of >> the normal libraries that I have been told are used by our jobs. > > Wouldn't it be a TSO Command Processor (not a rexx exec), and thus in > SYS1.CMDLIB ? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
