To all who replied to this earlier and to Jorge Garcia who just started a similarly named question I found my problem. For some reason our JOBCLASS(STC) has LOG=NO coded. This prevents the stc from being assigned an output group and dest (and possibly some other attributes).
Changing LOG to YES allowed the job log to be archived with the rest of the stc output. This may not be Jorges problem but it's something he should check. Alan Schwartz -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Staller, Allan Sent: Friday, March 30, 2012 10:06 AM To: [email protected] Subject: Re: Trying to capture JES2 Job Log See my previous comment regarding STARTED JOBS. This should allow you to just provide the 1 override. The SDSF XDC command can also be used to capture the JESMSGLG prior to shutdown. I do not currently use started jobs MSGLEVEL=1 is what comes up in my case. This may be the default for STARTED JOBS (supplied in the absence of particular parameter). A quick search did not turn up where the MSGLEVEL=1 is being specified. HTH, <snip> I'm getting somewhere. While the JOBCLASS(STC) clearly shows MSGLEVEL=(2,1) when I look at an active stc I see //IFOM JOB MSGLEVEL=1 So now the question is why is the start ignoring the MSGLEVEL from JOBCLASS(STC)? We use OPS/MVS for automation and it just uses a normal S task. I don't want to try and alter all the starts to have MSGLEVEL=(1,1). That's what JOBCLASS(STC) is supposed to do. Or so I thought. </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
