Re: Trying to capture JES2 Job Log
AH, but you didn't include that in your list of parms. The default is YES. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Schwartz, Alan Sent: Thursday, April 19, 2012 10:16 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Trying to capture JES2 Job Log 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:IBM-MAIN@bama.ua.edu] On Behalf Of Staller, Allan Sent: Friday, March 30, 2012 10:06 AM To: IBM-MAIN@bama.ua.edu 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, 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. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
>From Jorge's original post(which also answers my previous question regarding the output of $DOUTCLASS(K)): Hello: We can't view the STC jes job log when our started tasks ended. When they are executing we can view the jes job log, but after they ended we can view only the SYSPRINT. We've reviewed all the JES2PARM parameters and we don't see anything wrong: JOBCLASS(STC) TIME=(1440,00), COMMAND=EXECUTE, BLP=YES, AUTH=ALL, MSGLEVEL=(1,1), IEFUJP=YES, IEFUSO=YES, OUTDISP=(HOLD,HOLD), LOG=YES, OUTPUT=YES, PERFORM=000, PROCLIB=00, REGION=0K, TYPE6=YES, TYPE26=YES, MSGCLASS=K OUTCLASS(K) BLNKTRNC=YES, OUTDISP=(HOLD,HOLD) OUTPUT=PRINT, TRKCELL=YES -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
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:IBM-MAIN@bama.ua.edu] On Behalf Of Staller, Allan Sent: Friday, March 30, 2012 10:06 AM To: IBM-MAIN@bama.ua.edu 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, 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. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
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, 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. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
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. Alan Schwartz ITO Global Service Operations and Engineering Affiliated Computer Services, LLC, A Xerox Company 1500 Towerview Rd. Eagan, MN 55121-1346 p. 612.266.3150 m. 651.274.5819 f. 612.266.3196 www.xerox.com/businessservices -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Staller, Allan Sent: Friday, March 30, 2012 9:11 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Trying to capture JES2 Job Log Try changing the MSGLEVEL to (1,1) or make this a started job with the MSGLEVEL=(1,1) on the job card. Check the fine manuals for info on STARTED JOBS. JOBCLASS(STC) AUTH=(ALL),BLP=YES,COMMAND=IGNORE, CONDPURG=NO,IEFUJP=NO,IEFUSO=NO, JESLOG=(NOSPIN),LOG=NO,MSGLEVEL=(2, 1),MSGCLASS=7,OUTDISP=(,), OUTPUT=YES,PERFORM=000,PROCLIB=00, QAFF=(ANY),REGION=0004M,SWA=ABOVE, TIME=(30,00),TYPE26=NO, TYPE6=NO,XEQCOUNT=() XEQMEMBER(MVS2)=(MAXIMUM=*, CURRENT=283), XEQMEMBER(MVS1)=(MAXIMUM=*, CURRENT=280), XEQMEMBER(MVS3)=(MAXIMUM=*, CURRENT=179) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
Try changing the MSGLEVEL to (1,1) or make this a started job with the MSGLEVEL=(1,1) on the job card. Check the fine manuals for info on STARTED JOBS. JOBCLASS(STC) AUTH=(ALL),BLP=YES,COMMAND=IGNORE, CONDPURG=NO,IEFUJP=NO,IEFUSO=NO, JESLOG=(NOSPIN),LOG=NO,MSGLEVEL=(2, 1),MSGCLASS=7,OUTDISP=(,), OUTPUT=YES,PERFORM=000,PROCLIB=00, QAFF=(ANY),REGION=0004M,SWA=ABOVE, TIME=(30,00),TYPE26=NO, TYPE6=NO,XEQCOUNT=() XEQMEMBER(MVS2)=(MAXIMUM=*, CURRENT=283), XEQMEMBER(MVS1)=(MAXIMUM=*, CURRENT=280), XEQMEMBER(MVS3)=(MAXIMUM=*, CURRENT=179) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
JOBCLASS(STC) AUTH=(ALL),BLP=YES,COMMAND=IGNORE, CONDPURG=NO,IEFUJP=NO,IEFUSO=NO, JESLOG=(NOSPIN),LOG=NO,MSGLEVEL=(2, 1),MSGCLASS=7,OUTDISP=(,), OUTPUT=YES,PERFORM=000,PROCLIB=00, QAFF=(ANY),REGION=0004M,SWA=ABOVE, TIME=(30,00),TYPE26=NO, TYPE6=NO,XEQCOUNT=() XEQMEMBER(MVS2)=(MAXIMUM=*, CURRENT=283), XEQMEMBER(MVS1)=(MAXIMUM=*, CURRENT=280), XEQMEMBER(MVS3)=(MAXIMUM=*, CURRENT=179) Alan Schwartz ITO Global Service Operations and Engineering Affiliated Computer Services, LLC, A Xerox Company 1500 Towerview Rd. Eagan, MN 55121-1346 p. 612.266.3150 m. 651.274.5819 f. 612.266.3196 www.xerox.com/businessservices -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Staller, Allan Sent: Friday, March 30, 2012 8:04 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Trying to capture JES2 Job Log Check the MSGLEVEL setting in JES2 (JOBCLASS(STC) or JOBDEF). I've been away for a while but ready to revisit this at it's a real irritant. It shouldn't be this difficult. I checked a task I can cycle as needed. When I view the stc via SDSF all portions (except internal text) show msgclass of 7 which is what is desired. NP DDNAME StepName ProcStep DSID OwnerC Dest Rec-Cnt JESJCLIN 1 *BYPASS* 7 2 JESMSGLG JES2 2 *BYPASS* 7 2 JESJCL JES2 3 *BYPASS* 7 34 JESYSMSG JES2 4 *BYPASS* 7 2 $INTTEXT JES2 5 *BYPASS* A 9 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
Check the MSGLEVEL setting in JES2 (JOBCLASS(STC) or JOBDEF). I've been away for a while but ready to revisit this at it's a real irritant. It shouldn't be this difficult. I checked a task I can cycle as needed. When I view the stc via SDSF all portions (except internal text) show msgclass of 7 which is what is desired. NP DDNAME StepName ProcStep DSID OwnerC Dest Rec-Cnt JESJCLIN 1 *BYPASS* 7 2 JESMSGLG JES2 2 *BYPASS* 7 2 JESJCL JES2 3 *BYPASS* 7 34 JESYSMSG JES2 4 *BYPASS* 7 2 $INTTEXT JES2 5 *BYPASS* A 9 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
Alan, Check with your EOS administrators. When we use to have reports sent to EOS, I needed to have them setup something to allow me to see the reports. We also coded a report ID in the JCL DD statement. I no longer have an EOS to look at, so I'm not able to tell you more. Thank you and have a Terrific day! Jonathan Goossen, DTM ACT Mainframe Storage Group Personal: 651-361-4541 Department Support Line: 651-361- For help with communication and leadership skills checkout Woodwinds Toastmasters IBM Mainframe Discussion List wrote on 03/29/2012 04:02:13 PM: > From: "Schwartz, Alan" > To: IBM-MAIN@bama.ua.edu > Date: 03/29/2012 04:05 PM > Subject: Re: Trying to capture JES2 Job Log > Sent by: IBM Mainframe Discussion List > > I've been away for a while but ready to revisit this at it's a real > irritant. It shouldn't be this difficult. > > I checked a task I can cycle as needed. When I view the stc via SDSF > all portions (except internal text) show msgclass of 7 which is what is > desired. > > NP DDNAME StepName ProcStep DSID OwnerC Dest > Rec-Cnt > JESJCLIN 1 *BYPASS* 7 > 2 > JESMSGLG JES2 2 *BYPASS* 7 > 2 > JESJCL JES2 3 *BYPASS* 7 > 34 > JESYSMSG JES2 4 *BYPASS* 7 > 2 > $INTTEXT JES2 5 *BYPASS* A > 9 > > But when I stop the task and the output goes to EOS I just get JESJCL > and JESSYSMSG. I still think it might be an EOS issue. Vendor can't > help > > Alan Schwartz > ITO Global Service Operations and Engineering > 1500 Towerview Rd. > Eagan, MN 55121-1346 > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On > Behalf Of Lizette Koehler > Sent: Thursday, March 15, 2012 2:38 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Trying to capture JES2 Job Log > > > > > I'm attempting to save started task output in our output management > database. We > > use EOS. I changed the JOBCLASS(STC) MSGCLASS to the class EOS uses > > and I > get > > the JESJCL and > > > > JESYSMSG files and that's all. Any clues what else I might need to > > alter > to capture the > > JESMSGLG file? > > > > > > > > You need to have your MSGCLASS and SYSOUT Class go to the same place. > Are they both coded the same? > > > I typically see the following > > JESMSGLG JES2 This is the JOBLOG > JESJCL JES2 This the JCL with substitutions > JESYSMSG JES2 This is each step statistics (datasets, ucb, > etc...) > > If you set MSGCLASS=X, all three should go to output class X unless you > have exits. Or do you have a JOBCARD added to your STC that uses a > different MSGCLASS? Is the STC being started with a MSGCLASS other than > what you > want? You can issue S STCNAME,MSGCLASS=Y > > > Lizette > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
Hi Alan, Try adding a sysprint dd statement. I did that to a few STC here. Worked. HTH, Linda - Original Message - From: "Alan Schwartz" To: IBM-MAIN@bama.ua.edu Sent: Thursday, March 29, 2012 2:02:13 PM Subject: Re: Trying to capture JES2 Job Log I've been away for a while but ready to revisit this at it's a real irritant. It shouldn't be this difficult. I checked a task I can cycle as needed. When I view the stc via SDSF all portions (except internal text) show msgclass of 7 which is what is desired. NP DDNAME StepName ProcStep DSID Owner C Dest Rec-Cnt JESJCLIN 1 *BYPASS* 7 2 JESMSGLG JES2 2 *BYPASS* 7 2 JESJCL JES2 3 *BYPASS* 7 34 JESYSMSG JES2 4 *BYPASS* 7 2 $INTTEXT JES2 5 *BYPASS* A 9 But when I stop the task and the output goes to EOS I just get JESJCL and JESSYSMSG. I still think it might be an EOS issue. Vendor can't help Alan Schwartz ITO Global Service Operations and Engineering 1500 Towerview Rd. Eagan, MN 55121-1346 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Thursday, March 15, 2012 2:38 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Trying to capture JES2 Job Log > > I'm attempting to save started task output in our output management database. We > use EOS. I changed the JOBCLASS(STC) MSGCLASS to the class EOS uses > and I get > the JESJCL and > > JESYSMSG files and that's all. Any clues what else I might need to > alter to capture the > JESMSGLG file? > > > You need to have your MSGCLASS and SYSOUT Class go to the same place. Are they both coded the same? I typically see the following JESMSGLG JES2 This is the JOBLOG JESJCL JES2 This the JCL with substitutions JESYSMSG JES2 This is each step statistics (datasets, ucb, etc...) If you set MSGCLASS=X, all three should go to output class X unless you have exits. Or do you have a JOBCARD added to your STC that uses a different MSGCLASS? Is the STC being started with a MSGCLASS other than what you want? You can issue S STCNAME,MSGCLASS=Y Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
I've been away for a while but ready to revisit this at it's a real irritant. It shouldn't be this difficult. I checked a task I can cycle as needed. When I view the stc via SDSF all portions (except internal text) show msgclass of 7 which is what is desired. NP DDNAME StepName ProcStep DSID OwnerC Dest Rec-Cnt JESJCLIN 1 *BYPASS* 7 2 JESMSGLG JES2 2 *BYPASS* 7 2 JESJCL JES2 3 *BYPASS* 7 34 JESYSMSG JES2 4 *BYPASS* 7 2 $INTTEXT JES2 5 *BYPASS* A 9 But when I stop the task and the output goes to EOS I just get JESJCL and JESSYSMSG. I still think it might be an EOS issue. Vendor can't help Alan Schwartz ITO Global Service Operations and Engineering 1500 Towerview Rd. Eagan, MN 55121-1346 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Thursday, March 15, 2012 2:38 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Trying to capture JES2 Job Log > > I'm attempting to save started task output in our output management database. We > use EOS. I changed the JOBCLASS(STC) MSGCLASS to the class EOS uses > and I get > the JESJCL and > > JESYSMSG files and that's all. Any clues what else I might need to > alter to capture the > JESMSGLG file? > > > You need to have your MSGCLASS and SYSOUT Class go to the same place. Are they both coded the same? I typically see the following JESMSGLG JES2 This is the JOBLOG JESJCL JES2 This the JCL with substitutions JESYSMSG JES2 This is each step statistics (datasets, ucb, etc...) If you set MSGCLASS=X, all three should go to output class X unless you have exits. Or do you have a JOBCARD added to your STC that uses a different MSGCLASS? Is the STC being started with a MSGCLASS other than what you want? You can issue S STCNAME,MSGCLASS=Y Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Trying to capture JES2 Job Log
> > I'm attempting to save started task output in our output management database. We > use EOS. I changed the JOBCLASS(STC) MSGCLASS to the class EOS uses and I get > the JESJCL and > > JESYSMSG files and that's all. Any clues what else I might need to alter to capture the > JESMSGLG file? > > > You need to have your MSGCLASS and SYSOUT Class go to the same place. Are they both coded the same? I typically see the following JESMSGLG JES2 This is the JOBLOG JESJCL JES2 This the JCL with substitutions JESYSMSG JES2 This is each step statistics (datasets, ucb, etc...) If you set MSGCLASS=X, all three should go to output class X unless you have exits. Or do you have a JOBCARD added to your STC that uses a different MSGCLASS? Is the STC being started with a MSGCLASS other than what you want? You can issue S STCNAME,MSGCLASS=Y Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Trying to capture JES2 Job Log
I'm attempting to save started task output in our output management database. We use EOS. I changed the JOBCLASS(STC) MSGCLASS to the class EOS uses and I get the JESJCL and JESYSMSG files and that's all. Any clues what else I might need to alter to capture the JESMSGLG file? Alan Schwartz ITO Global Service Operations and Engineering Affiliated Computer Services, LLC, A Xerox Company 1500 Towerview Rd. Eagan, MN 55121-1346 p. 612.266.3150 m. 651.274.5819 f. 612.266.3196 www.xerox.com/businessservices -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
