On Wed, 27 Apr 2016 22:16:49 +0000, Lindy Mayfield <[email protected]> wrote:
> > Today I saw something I've never seen before. I wanted to know where a > started task was running from and normally the SDSF jes2 log shows which > > proclib it was loaded from. But it said it was instream, and looking at the > SJ jcl it didn't look "normal." Sounds like the startup JCL member contains a job card, that seems to suppress the normal IEFC001I message. Makes it tough to find where JCL comes from! It could also come from IEFJOBS DD concatenation in MSTJCLxx. > >$DPROCS showed something weird, I forget, but it was some proclib DD's, two or >3 of them, then the system proclibs by name (SYS1.PROCLIB, etc....). > The JES2 subsystem has multiple proclib concatenations defined, either static or dynamically via $ADD PROC commands. The output of $DPROCS will show ' STATIC PROCLIB, ' if a concatenation was coded in the JES2 startup proc. HTH Dana ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
