Re: Where do started PROC errors go?
Lizette wrote >Check the JES2 INIT Deck for the STCCLAS and see what it has for DISP. I don't know if what I do on a test system is relevant (or is something that I should have been doing differently for decades) but $TSTCCLASS,CONDPURG=NO sometimes helps me to get output from a started task (and probably relates to what Lizette wrote). Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
I haven't had it enough to develop a strong preference, although I found the homemade Slivowitz at DGS to be too sweet for my taste. In fact, before that I had never heard of sweet Slivowitz. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of David Spiegel [dspiegel...@hotmail.com] Sent: Thursday, May 21, 2020 10:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Hi Slivovitz drinkers, Which brand do you prefer? Regards, David On 2020-05-21 22:39, Jesse 1 Robinson wrote: > It may not be echt, but I like my Slivowitz well iced. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > robin...@sce.com > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Seymour J Metz > Sent: Thursday, May 21, 2020 5:27 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Where do started PROC errors go? > > CAUTION EXTERNAL EMAIL > > I would like a virtual Slivowitz; please don't refrigerate. > > > -- > Shmuel (Seymour J.) Metz > https://eur05.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.gmu.edu%2F~smetz3&data=02%7C01%7C%7C4f2a1a64809b4e98893508d7fdf959a1%7C84df9e7fe9f640afb435%7C1%7C0%7C637257119702470001&sdata=%2BqBiUmE7sxszSzZe%2BUnFoJ9cBgEMGvLP8tPz2EGkE7E%3D&reserved=0 > > > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of > Tom Brennan [t...@tombrennansoftware.com] > Sent: Thursday, May 21, 2020 8:12 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > Maybe we should all have a six-pack in the fridge that we're not allowed to > touch until someone offers one. > > On 5/21/2020 4:44 PM, Jesse 1 Robinson wrote: >> Sam Virtual Adams. >> >> . >> . >> J.O.Skip Robinson >> Southern California Edison Company >> Electric Dragon Team Paddler >> SHARE MVS Program Co-Manager >> 323-715-0595 Mobile >> 626-543-6132 Office ⇐=== NEW >> robin...@sce.com >> >> -----Original Message- >> From: IBM Mainframe Discussion List On >> Behalf Of Charles Mills >> Sent: Thursday, May 21, 2020 4:39 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: (External):Re: Where do started PROC errors go? >> >> CAUTION EXTERNAL EMAIL >> >> It did not but now it does and it works! >> >> Gosh, got it right on the first try. Guessed at the changes to make to the >> below and seem to have gotten them all right on the first try. >> >> I owe you all a virtual beer in Boston. >> >> Charles >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Wayne Bickerdike >> Sent: Thursday, May 21, 2020 12:52 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Where do started PROC errors go? >> >> Charles did your setup include something like this? >> >> RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) >> PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER >> STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH >> RACLIST(STARTED) >> >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, send >> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Hi Slivovitz drinkers, Which brand do you prefer? Regards, David On 2020-05-21 22:39, Jesse 1 Robinson wrote: It may not be echt, but I like my Slivowitz well iced. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 5:27 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Where do started PROC errors go? CAUTION EXTERNAL EMAIL I would like a virtual Slivowitz; please don't refrigerate. -- Shmuel (Seymour J.) Metz https://eur05.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.gmu.edu%2F~smetz3&data=02%7C01%7C%7C4f2a1a64809b4e98893508d7fdf959a1%7C84df9e7fe9f640afb435%7C1%7C0%7C637257119702470001&sdata=%2BqBiUmE7sxszSzZe%2BUnFoJ9cBgEMGvLP8tPz2EGkE7E%3D&reserved=0 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tom Brennan [t...@tombrennansoftware.com] Sent: Thursday, May 21, 2020 8:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Maybe we should all have a six-pack in the fridge that we're not allowed to touch until someone offers one. On 5/21/2020 4:44 PM, Jesse 1 Robinson wrote: Sam Virtual Adams. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, May 21, 2020 4:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Where do started PROC errors go? CAUTION EXTERNAL EMAIL It did not but now it does and it works! Gosh, got it right on the first try. Guessed at the changes to make to the below and seem to have gotten them all right on the first try. I owe you all a virtual beer in Boston. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 12:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Charles did your setup include something like this? RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH RACLIST(STARTED) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
It may not be echt, but I like my Slivowitz well iced. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 5:27 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Where do started PROC errors go? CAUTION EXTERNAL EMAIL I would like a virtual Slivowitz; please don't refrigerate. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tom Brennan [t...@tombrennansoftware.com] Sent: Thursday, May 21, 2020 8:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Maybe we should all have a six-pack in the fridge that we're not allowed to touch until someone offers one. On 5/21/2020 4:44 PM, Jesse 1 Robinson wrote: > Sam Virtual Adams. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > robin...@sce.com > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Charles Mills > Sent: Thursday, May 21, 2020 4:39 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Where do started PROC errors go? > > CAUTION EXTERNAL EMAIL > > It did not but now it does and it works! > > Gosh, got it right on the first try. Guessed at the changes to make to the > below and seem to have gotten them all right on the first try. > > I owe you all a virtual beer in Boston. > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Wayne Bickerdike > Sent: Thursday, May 21, 2020 12:52 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > Charles did your setup include something like this? > > RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) > PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER > STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH > RACLIST(STARTED) > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Old Peculier for a Yorkshireman :) On Fri, May 22, 2020 at 10:26 AM Seymour J Metz wrote: > I would like a virtual Slivowitz; please don't refrigerate. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf > of Tom Brennan [t...@tombrennansoftware.com] > Sent: Thursday, May 21, 2020 8:12 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > Maybe we should all have a six-pack in the fridge that we're not allowed > to touch until someone offers one. > > On 5/21/2020 4:44 PM, Jesse 1 Robinson wrote: > > Sam Virtual Adams. > > > > . > > . > > J.O.Skip Robinson > > Southern California Edison Company > > Electric Dragon Team Paddler > > SHARE MVS Program Co-Manager > > 323-715-0595 Mobile > > 626-543-6132 Office ⇐=== NEW > > robin...@sce.com > > > > -Original Message- > > From: IBM Mainframe Discussion List On > Behalf Of Charles Mills > > Sent: Thursday, May 21, 2020 4:39 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: (External):Re: Where do started PROC errors go? > > > > CAUTION EXTERNAL EMAIL > > > > It did not but now it does and it works! > > > > Gosh, got it right on the first try. Guessed at the changes to make to > the below and seem to have gotten them all right on the first try. > > > > I owe you all a virtual beer in Boston. > > > > Charles > > > > > > -----Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Wayne Bickerdike > > Sent: Thursday, May 21, 2020 12:52 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Where do started PROC errors go? > > > > Charles did your setup include something like this? > > > > RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) > PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER > STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH > RACLIST(STARTED) > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
I would like a virtual Slivowitz; please don't refrigerate. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tom Brennan [t...@tombrennansoftware.com] Sent: Thursday, May 21, 2020 8:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Maybe we should all have a six-pack in the fridge that we're not allowed to touch until someone offers one. On 5/21/2020 4:44 PM, Jesse 1 Robinson wrote: > Sam Virtual Adams. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > robin...@sce.com > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Charles Mills > Sent: Thursday, May 21, 2020 4:39 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Where do started PROC errors go? > > CAUTION EXTERNAL EMAIL > > It did not but now it does and it works! > > Gosh, got it right on the first try. Guessed at the changes to make to the > below and seem to have gotten them all right on the first try. > > I owe you all a virtual beer in Boston. > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Wayne Bickerdike > Sent: Thursday, May 21, 2020 12:52 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > Charles did your setup include something like this? > > RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) PERMIT > MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER STARTED > MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH RACLIST(STARTED) > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Maybe we should all have a six-pack in the fridge that we're not allowed to touch until someone offers one. On 5/21/2020 4:44 PM, Jesse 1 Robinson wrote: Sam Virtual Adams. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, May 21, 2020 4:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Where do started PROC errors go? CAUTION EXTERNAL EMAIL It did not but now it does and it works! Gosh, got it right on the first try. Guessed at the changes to make to the below and seem to have gotten them all right on the first try. I owe you all a virtual beer in Boston. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 12:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Charles did your setup include something like this? RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH RACLIST(STARTED) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Yep, and different OUTCLASS's. So either the doc. is wrong (or misread) or something stepped in and changed the disposition. Either way, it's ALL still on the spool until all the out groups are purged (not considering the effects of SPIN). First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, May 21, 2020 7:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [External Email. Exercise caution when clicking links or opening attachments.] It's all there in ST: DDNAME StepName ProcStep DSID OwnerC Dest Rec-Cnt JESJCLIN 1 K 2 JESMSGLG JES2 2 K LOCAL6 JESJCL JES2 3 K LOCAL 18 JESYSMSG JES2 4 K LOCAL 20 $INTTEXT JES2 5 A 7 SYSTSPRT QMONITOR 101 H LOCAL 34 Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jackson, Rob Sent: Thursday, May 21, 2020 3:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Ah, I was looking at a mushed-up email, and it was hard to see all of it. And yeah, the Init and Tuning reference seems to say what you suggest. All I know is when it doesn't show up in the output or held queue when you expect it to, some part of the output was not purged, so you can see it all in ST. Could it be a report collection product changing it via SSI? We have a bunch of JES2 exits in our shop that change these things; I suppose that's another possibility. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 6:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [External Email. Exercise caution when clicking links or opening attachments.] Doesn't this take precedence: JOBCLASS(STC) TIME=(1440,00), /* Job Step Time ...ss... WS*/ COMMAND=EXECUTE,/* Execute Commands ..r.. WS*/ BLP=NO, /* Ignore BLP parm ...l. WS*/ AUTH=ALL, /* Allow all Cmds . WS*/ MSGLEVEL=(1,1), /* Job, All Msgse WS*/ IEFUJP=YES, /* Take SMF Job Purge Exit IEFUJP WS*/ IEFUSO=YES, /* Take SYSOUT Excess Exit IEFUSO WS*/ OUTDISP=(PURGE,HOLD), /*WS*/ LOG=YES,/* Print JES2 JOB LOG LOGWS*/ OUTPUT=YES, /* Produce Output for Job OUTPUT WS*/ PERFORM=000,/* SRM Performance Group 0 PERFORM hwnc*/ PROCLIB=00, /* Use //PROC00 DD hwnc*/ REGION=0K, /* Region Size hwnc*/ /* (format changed SP410) */ TYPE6=YES, /* Produce SMF 6 Records TYPE6 WS*/ TYPE26=YES, /* Produce SMF 26 Records TYPE26 WS*/ MSGCLASS=K /* Default Message Class STCMCLAS WS*/ -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jackson, Rob [rwjack...@firsthorizon.com] Sent: Thursday, May 21, 2020 5:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? He was sending that one SYSOUT to class H; the output class for JOBCLASS(STC) was K. I'm sure K wasn't set to PURGE. And the output doesn't really go away until it ALL goes away. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 5:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [External Email. Exercise caution when clicking links or opening attachments.] I don't understand how it is still there for ST to find. shouldn't JES2 have purged it due to the OUTDISP=(PURGE,HOLD)? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Charles Mills [charl...@mcn.org] Sent: Thursday, May 21, 2020 5:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Thanks all! - Yes, SDSF ST finds it. Why is it visible in ST but not in H or O? - Problem is the lack of a userid. I will get that fixed up. Back here if I hit something else I cannot solve. Charles -Original Message---
Re: Where do started PROC errors go?
Sam Virtual Adams. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, May 21, 2020 4:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Where do started PROC errors go? CAUTION EXTERNAL EMAIL It did not but now it does and it works! Gosh, got it right on the first try. Guessed at the changes to make to the below and seem to have gotten them all right on the first try. I owe you all a virtual beer in Boston. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 12:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Charles did your setup include something like this? RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH RACLIST(STARTED) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
It did not but now it does and it works! Gosh, got it right on the first try. Guessed at the changes to make to the below and seem to have gotten them all right on the first try. I owe you all a virtual beer in Boston. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 12:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Charles did your setup include something like this? RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH RACLIST(STARTED) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
It's all there in ST: DDNAME StepName ProcStep DSID OwnerC Dest Rec-Cnt JESJCLIN 1 K 2 JESMSGLG JES2 2 K LOCAL6 JESJCL JES2 3 K LOCAL 18 JESYSMSG JES2 4 K LOCAL 20 $INTTEXT JES2 5 A 7 SYSTSPRT QMONITOR 101 H LOCAL 34 Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jackson, Rob Sent: Thursday, May 21, 2020 3:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Ah, I was looking at a mushed-up email, and it was hard to see all of it. And yeah, the Init and Tuning reference seems to say what you suggest. All I know is when it doesn't show up in the output or held queue when you expect it to, some part of the output was not purged, so you can see it all in ST. Could it be a report collection product changing it via SSI? We have a bunch of JES2 exits in our shop that change these things; I suppose that's another possibility. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 6:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [External Email. Exercise caution when clicking links or opening attachments.] Doesn't this take precedence: JOBCLASS(STC) TIME=(1440,00), /* Job Step Time ...ss... WS*/ COMMAND=EXECUTE,/* Execute Commands ..r.. WS*/ BLP=NO, /* Ignore BLP parm ...l. WS*/ AUTH=ALL, /* Allow all Cmds . WS*/ MSGLEVEL=(1,1), /* Job, All Msgse WS*/ IEFUJP=YES, /* Take SMF Job Purge Exit IEFUJP WS*/ IEFUSO=YES, /* Take SYSOUT Excess Exit IEFUSO WS*/ OUTDISP=(PURGE,HOLD), /*WS*/ LOG=YES,/* Print JES2 JOB LOG LOGWS*/ OUTPUT=YES, /* Produce Output for Job OUTPUT WS*/ PERFORM=000,/* SRM Performance Group 0 PERFORM hwnc*/ PROCLIB=00, /* Use //PROC00 DD hwnc*/ REGION=0K, /* Region Size hwnc*/ /* (format changed SP410) */ TYPE6=YES, /* Produce SMF 6 Records TYPE6 WS*/ TYPE26=YES, /* Produce SMF 26 Records TYPE26 WS*/ MSGCLASS=K /* Default Message Class STCMCLAS WS*/ -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jackson, Rob [rwjack...@firsthorizon.com] Sent: Thursday, May 21, 2020 5:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? He was sending that one SYSOUT to class H; the output class for JOBCLASS(STC) was K. I'm sure K wasn't set to PURGE. And the output doesn't really go away until it ALL goes away. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 5:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [External Email. Exercise caution when clicking links or opening attachments.] I don't understand how it is still there for ST to find. shouldn't JES2 have purged it due to the OUTDISP=(PURGE,HOLD)? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Charles Mills [charl...@mcn.org] Sent: Thursday, May 21, 2020 5:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Thanks all! - Yes, SDSF ST finds it. Why is it visible in ST but not in H or O? - Problem is the lack of a userid. I will get that fixed up. Back here if I hit something else I cannot solve. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Bingo Allan. If I have a jobcard, I'll use MSGCLASS=X and in the SYSOUT SYSOUT=* Same JCL in an STC and SYSOUT=* does indeed disappear goes to a different (disappearing class) On Fri, May 22, 2020 at 6:11 AM Allan Staller wrote: > S STCNAME...MSGCLASS=(held sysout class). > > I.e. ODISP=(keep,keep) > > -Original Message- > From: IBM Mainframe Discussion Lis
Re: Where do started PROC errors go?
Ah, I was looking at a mushed-up email, and it was hard to see all of it. And yeah, the Init and Tuning reference seems to say what you suggest. All I know is when it doesn't show up in the output or held queue when you expect it to, some part of the output was not purged, so you can see it all in ST. Could it be a report collection product changing it via SSI? We have a bunch of JES2 exits in our shop that change these things; I suppose that's another possibility. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 6:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [External Email. Exercise caution when clicking links or opening attachments.] Doesn't this take precedence: JOBCLASS(STC) TIME=(1440,00), /* Job Step Time ...ss... WS*/ COMMAND=EXECUTE,/* Execute Commands ..r.. WS*/ BLP=NO, /* Ignore BLP parm ...l. WS*/ AUTH=ALL, /* Allow all Cmds . WS*/ MSGLEVEL=(1,1), /* Job, All Msgse WS*/ IEFUJP=YES, /* Take SMF Job Purge Exit IEFUJP WS*/ IEFUSO=YES, /* Take SYSOUT Excess Exit IEFUSO WS*/ OUTDISP=(PURGE,HOLD), /*WS*/ LOG=YES,/* Print JES2 JOB LOG LOGWS*/ OUTPUT=YES, /* Produce Output for Job OUTPUT WS*/ PERFORM=000,/* SRM Performance Group 0 PERFORM hwnc*/ PROCLIB=00, /* Use //PROC00 DD hwnc*/ REGION=0K, /* Region Size hwnc*/ /* (format changed SP410) */ TYPE6=YES, /* Produce SMF 6 Records TYPE6 WS*/ TYPE26=YES, /* Produce SMF 26 Records TYPE26 WS*/ MSGCLASS=K /* Default Message Class STCMCLAS WS*/ -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jackson, Rob [rwjack...@firsthorizon.com] Sent: Thursday, May 21, 2020 5:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? He was sending that one SYSOUT to class H; the output class for JOBCLASS(STC) was K. I'm sure K wasn't set to PURGE. And the output doesn't really go away until it ALL goes away. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 5:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [External Email. Exercise caution when clicking links or opening attachments.] I don't understand how it is still there for ST to find. shouldn't JES2 have purged it due to the OUTDISP=(PURGE,HOLD)? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Charles Mills [charl...@mcn.org] Sent: Thursday, May 21, 2020 5:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Thanks all! - Yes, SDSF ST finds it. Why is it visible in ST but not in H or O? - Problem is the lack of a userid. I will get that fixed up. Back here if I hit something else I cannot solve. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Bingo Allan. If I have a jobcard, I'll use MSGCLASS=X and in the SYSOUT SYSOUT=* Same JCL in an STC and SYSOUT=* does indeed disappear goes to a different (disappearing class) On Fri, May 22, 2020 at 6:11 AM Allan Staller wrote: > S STCNAME...MSGCLASS=(held sysout class). > > I.e. ODISP=(keep,keep) > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Wayne Bickerdike > Sent: Thursday, May 21, 2020 2:52 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > [CAUTION: This Email is from outside the Organization. Unless you > trust the sender, Don't click links or open attachments as it may be a > Phishing email, which can steal your Information and compromise your > Computer.] > > Charles did your setup include something like this? > > RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) > PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER > STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH > RACLIST(STARTED) > > On Fri,
Re: Where do started PROC errors go?
Doesn't this take precedence: JOBCLASS(STC) TIME=(1440,00), /* Job Step Time ...ss... WS*/ COMMAND=EXECUTE,/* Execute Commands ..r.. WS*/ BLP=NO, /* Ignore BLP parm ...l. WS*/ AUTH=ALL, /* Allow all Cmds . WS*/ MSGLEVEL=(1,1), /* Job, All Msgse WS*/ IEFUJP=YES, /* Take SMF Job Purge Exit IEFUJP WS*/ IEFUSO=YES, /* Take SYSOUT Excess Exit IEFUSO WS*/ OUTDISP=(PURGE,HOLD), /*WS*/ LOG=YES,/* Print JES2 JOB LOG LOGWS*/ OUTPUT=YES, /* Produce Output for Job OUTPUT WS*/ PERFORM=000,/* SRM Performance Group 0 PERFORM hwnc*/ PROCLIB=00, /* Use //PROC00 DD hwnc*/ REGION=0K, /* Region Size hwnc*/ /* (format changed SP410) */ TYPE6=YES, /* Produce SMF 6 Records TYPE6 WS*/ TYPE26=YES, /* Produce SMF 26 Records TYPE26 WS*/ MSGCLASS=K /* Default Message Class STCMCLAS WS*/ -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jackson, Rob [rwjack...@firsthorizon.com] Sent: Thursday, May 21, 2020 5:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? He was sending that one SYSOUT to class H; the output class for JOBCLASS(STC) was K. I'm sure K wasn't set to PURGE. And the output doesn't really go away until it ALL goes away. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 5:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [External Email. Exercise caution when clicking links or opening attachments.] I don't understand how it is still there for ST to find. shouldn't JES2 have purged it due to the OUTDISP=(PURGE,HOLD)? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Charles Mills [charl...@mcn.org] Sent: Thursday, May 21, 2020 5:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Thanks all! - Yes, SDSF ST finds it. Why is it visible in ST but not in H or O? - Problem is the lack of a userid. I will get that fixed up. Back here if I hit something else I cannot solve. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Bingo Allan. If I have a jobcard, I'll use MSGCLASS=X and in the SYSOUT SYSOUT=* Same JCL in an STC and SYSOUT=* does indeed disappear goes to a different (disappearing class) On Fri, May 22, 2020 at 6:11 AM Allan Staller wrote: > S STCNAME...MSGCLASS=(held sysout class). > > I.e. ODISP=(keep,keep) > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Wayne Bickerdike > Sent: Thursday, May 21, 2020 2:52 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > [CAUTION: This Email is from outside the Organization. Unless you > trust the sender, Don't click links or open attachments as it may be a > Phishing email, which can steal your Information and compromise your > Computer.] > > Charles did your setup include something like this? > > RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) > PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER > STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH > RACLIST(STARTED) > > On Fri, May 22, 2020 at 5:33 AM Wayne Bickerdike > wrote: > > > Two things, no definition for the STC in RACF. > > > > If I have difficulty diagnosing STC problems, I run them as a job in > > JCL to capture error messages. > > > > > > > > On Fri, May 22, 2020 at 5:14 AM Seymour J Metz wrote: > > > >> He posted messages showing that the STC ran normally. His primary > >> problem is OUTDISP; once he fixes that we can see whether the > >> userid is causing other problems. > >> > >> > >> -- > >> Shmuel (Seymour J.) Metz > >> https://apc01.safelinks.protection.outlook.com/?url=http:%2F%2Fmason. > >> gmu.edu%2F~smetz3&data=02%7C01%7Callan.staller%40HCL.COM%7C8156 > >> 95 > >
Re: Where do started PROC errors go?
He was sending that one SYSOUT to class H; the output class for JOBCLASS(STC) was K. I'm sure K wasn't set to PURGE. And the output doesn't really go away until it ALL goes away. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, May 21, 2020 5:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [External Email. Exercise caution when clicking links or opening attachments.] I don't understand how it is still there for ST to find. shouldn't JES2 have purged it due to the OUTDISP=(PURGE,HOLD)? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Charles Mills [charl...@mcn.org] Sent: Thursday, May 21, 2020 5:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Thanks all! - Yes, SDSF ST finds it. Why is it visible in ST but not in H or O? - Problem is the lack of a userid. I will get that fixed up. Back here if I hit something else I cannot solve. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Bingo Allan. If I have a jobcard, I'll use MSGCLASS=X and in the SYSOUT SYSOUT=* Same JCL in an STC and SYSOUT=* does indeed disappear goes to a different (disappearing class) On Fri, May 22, 2020 at 6:11 AM Allan Staller wrote: > S STCNAME...MSGCLASS=(held sysout class). > > I.e. ODISP=(keep,keep) > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Wayne Bickerdike > Sent: Thursday, May 21, 2020 2:52 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > [CAUTION: This Email is from outside the Organization. Unless you > trust the sender, Don't click links or open attachments as it may be a > Phishing email, which can steal your Information and compromise your > Computer.] > > Charles did your setup include something like this? > > RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) > PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER > STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH > RACLIST(STARTED) > > On Fri, May 22, 2020 at 5:33 AM Wayne Bickerdike > wrote: > > > Two things, no definition for the STC in RACF. > > > > If I have difficulty diagnosing STC problems, I run them as a job in > > JCL to capture error messages. > > > > > > > > On Fri, May 22, 2020 at 5:14 AM Seymour J Metz wrote: > > > >> He posted messages showing that the STC ran normally. His primary > >> problem is OUTDISP; once he fixes that we can see whether the > >> userid is causing other problems. > >> > >> > >> -- > >> Shmuel (Seymour J.) Metz > >> https://apc01.safelinks.protection.outlook.com/?url=http:%2F%2Fmason. > >> gmu.edu%2F~smetz3&data=02%7C01%7Callan.staller%40HCL.COM%7C8156 > >> 95 > >> bad7c4430c0e0e08d7fdc08e1f%7C189de737c93a4f5a8b686f4ca9941912%7C0%7 > >> C0 > >> %7C637256875802443954&sdata=yrxVy3cUu7HVu23lPvqIkCAxcwCqRQm4GJw > >> wB > >> Ocm9VQ%3D&reserved=0 > >> > >> > >> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > >> behalf of Christopher Y. Blaicher [cblaic...@syncsort.com] > >> Sent: Thursday, May 21, 2020 2:48 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Where do started PROC errors go? > >> > >> Generally the job name is the name of the PROC you issued the start for. > >> Have you tried using the ST option of SDSF? Also, some errors get > >> put on the bottom of the queue. Also, did you look in the SYSLOG? > >> You should see the start and end messages > >> > >> Chris Blaicher > >> Technical Architect > >> Syncsort, Inc. > >> > >> -Original Message- > >> From: IBM Mainframe Discussion List > >> [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Binyamin Dissen > >> Sent: Thursday, May 21, 2020 2:38 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Where do started PROC errors go? > >> > >> [ External - This message originated Externally. Use proper > >> judgement and caution with attachments, links, or responses. ] > >> > >> Try running the PRO
Re: Where do started PROC errors go?
I don't understand how it is still there for ST to find. shouldn't JES2 have purged it due to the OUTDISP=(PURGE,HOLD)? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Charles Mills [charl...@mcn.org] Sent: Thursday, May 21, 2020 5:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Thanks all! - Yes, SDSF ST finds it. Why is it visible in ST but not in H or O? - Problem is the lack of a userid. I will get that fixed up. Back here if I hit something else I cannot solve. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Bingo Allan. If I have a jobcard, I'll use MSGCLASS=X and in the SYSOUT SYSOUT=* Same JCL in an STC and SYSOUT=* does indeed disappear goes to a different (disappearing class) On Fri, May 22, 2020 at 6:11 AM Allan Staller wrote: > S STCNAME...MSGCLASS=(held sysout class). > > I.e. ODISP=(keep,keep) > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Wayne Bickerdike > Sent: Thursday, May 21, 2020 2:52 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > [CAUTION: This Email is from outside the Organization. Unless you trust > the sender, Don’t click links or open attachments as it may be a Phishing > email, which can steal your Information and compromise your Computer.] > > Charles did your setup include something like this? > > RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) > PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER > STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH > RACLIST(STARTED) > > On Fri, May 22, 2020 at 5:33 AM Wayne Bickerdike > wrote: > > > Two things, no definition for the STC in RACF. > > > > If I have difficulty diagnosing STC problems, I run them as a job in > > JCL to capture error messages. > > > > > > > > On Fri, May 22, 2020 at 5:14 AM Seymour J Metz wrote: > > > >> He posted messages showing that the STC ran normally. His primary > >> problem is OUTDISP; once he fixes that we can see whether the userid > >> is causing other problems. > >> > >> > >> -- > >> Shmuel (Seymour J.) Metz > >> https://apc01.safelinks.protection.outlook.com/?url=http:%2F%2Fmason. > >> gmu.edu%2F~smetz3&data=02%7C01%7Callan.staller%40HCL.COM%7C815695 > >> bad7c4430c0e0e08d7fdc08e1f%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0 > >> %7C637256875802443954&sdata=yrxVy3cUu7HVu23lPvqIkCAxcwCqRQm4GJwwB > >> Ocm9VQ%3D&reserved=0 > >> > >> ________ > >> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > >> behalf of Christopher Y. Blaicher [cblaic...@syncsort.com] > >> Sent: Thursday, May 21, 2020 2:48 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Where do started PROC errors go? > >> > >> Generally the job name is the name of the PROC you issued the start for. > >> Have you tried using the ST option of SDSF? Also, some errors get > >> put on the bottom of the queue. Also, did you look in the SYSLOG? > >> You should see the start and end messages > >> > >> Chris Blaicher > >> Technical Architect > >> Syncsort, Inc. > >> > >> -Original Message- > >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > >> On Behalf Of Binyamin Dissen > >> Sent: Thursday, May 21, 2020 2:38 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Where do started PROC errors go? > >> > >> [ External - This message originated Externally. Use proper > >> judgement and caution with attachments, links, or responses. ] > >> > >> Try running the PROC in a batch job. > >> > >> You do realize that without proper setup the STC is probably using a > >> different userid. > >> > >> On Thu, 21 May 2020 09:11:10 -0700 Charles Mills > >> wrote: > >> > >> :>I have a program that runs successfully in a job. I just cloned the > >> JCL :>appropriately into a PROC. When I issue a START for the PROC I > >> get a started :>message and an ended message but no clue as to why it > >> failed. (It is :>supposed to be long-running, so ending is a >
Re: Where do started PROC errors go?
Thanks all! - Yes, SDSF ST finds it. Why is it visible in ST but not in H or O? - Problem is the lack of a userid. I will get that fixed up. Back here if I hit something else I cannot solve. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Bingo Allan. If I have a jobcard, I'll use MSGCLASS=X and in the SYSOUT SYSOUT=* Same JCL in an STC and SYSOUT=* does indeed disappear goes to a different (disappearing class) On Fri, May 22, 2020 at 6:11 AM Allan Staller wrote: > S STCNAME...MSGCLASS=(held sysout class). > > I.e. ODISP=(keep,keep) > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Wayne Bickerdike > Sent: Thursday, May 21, 2020 2:52 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > [CAUTION: This Email is from outside the Organization. Unless you trust > the sender, Don’t click links or open attachments as it may be a Phishing > email, which can steal your Information and compromise your Computer.] > > Charles did your setup include something like this? > > RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) > PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER > STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH > RACLIST(STARTED) > > On Fri, May 22, 2020 at 5:33 AM Wayne Bickerdike > wrote: > > > Two things, no definition for the STC in RACF. > > > > If I have difficulty diagnosing STC problems, I run them as a job in > > JCL to capture error messages. > > > > > > > > On Fri, May 22, 2020 at 5:14 AM Seymour J Metz wrote: > > > >> He posted messages showing that the STC ran normally. His primary > >> problem is OUTDISP; once he fixes that we can see whether the userid > >> is causing other problems. > >> > >> > >> -- > >> Shmuel (Seymour J.) Metz > >> https://apc01.safelinks.protection.outlook.com/?url=http:%2F%2Fmason. > >> gmu.edu%2F~smetz3&data=02%7C01%7Callan.staller%40HCL.COM%7C815695 > >> bad7c4430c0e0e08d7fdc08e1f%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0 > >> %7C637256875802443954&sdata=yrxVy3cUu7HVu23lPvqIkCAxcwCqRQm4GJwwB > >> Ocm9VQ%3D&reserved=0 > >> > >> ____________________ > >> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > >> behalf of Christopher Y. Blaicher [cblaic...@syncsort.com] > >> Sent: Thursday, May 21, 2020 2:48 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Where do started PROC errors go? > >> > >> Generally the job name is the name of the PROC you issued the start for. > >> Have you tried using the ST option of SDSF? Also, some errors get > >> put on the bottom of the queue. Also, did you look in the SYSLOG? > >> You should see the start and end messages > >> > >> Chris Blaicher > >> Technical Architect > >> Syncsort, Inc. > >> > >> -Original Message- > >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > >> On Behalf Of Binyamin Dissen > >> Sent: Thursday, May 21, 2020 2:38 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Where do started PROC errors go? > >> > >> [ External - This message originated Externally. Use proper > >> judgement and caution with attachments, links, or responses. ] > >> > >> Try running the PROC in a batch job. > >> > >> You do realize that without proper setup the STC is probably using a > >> different userid. > >> > >> On Thu, 21 May 2020 09:11:10 -0700 Charles Mills > >> wrote: > >> > >> :>I have a program that runs successfully in a job. I just cloned the > >> JCL :>appropriately into a PROC. When I issue a START for the PROC I > >> get a started :>message and an ended message but no clue as to why it > >> failed. (It is :>supposed to be long-running, so ending is a > >> failure.) I don't think it is a :>JCL error because I get a JCL error > >> message in that case, and I have :>evidence that it actually ran "some." > >> :> > >> :>The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I > >> have strong :>evidence that the program is getting far enough that it > >> would have written :>several lines to SYSTSPRT. > >
Re: Where do started PROC errors go?
Bingo Allan. If I have a jobcard, I'll use MSGCLASS=X and in the SYSOUT SYSOUT=* Same JCL in an STC and SYSOUT=* does indeed disappear goes to a different (disappearing class) On Fri, May 22, 2020 at 6:11 AM Allan Staller wrote: > S STCNAME...MSGCLASS=(held sysout class). > > I.e. ODISP=(keep,keep) > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Wayne Bickerdike > Sent: Thursday, May 21, 2020 2:52 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > [CAUTION: This Email is from outside the Organization. Unless you trust > the sender, Don’t click links or open attachments as it may be a Phishing > email, which can steal your Information and compromise your Computer.] > > Charles did your setup include something like this? > > RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) > PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER > STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH > RACLIST(STARTED) > > On Fri, May 22, 2020 at 5:33 AM Wayne Bickerdike > wrote: > > > Two things, no definition for the STC in RACF. > > > > If I have difficulty diagnosing STC problems, I run them as a job in > > JCL to capture error messages. > > > > > > > > On Fri, May 22, 2020 at 5:14 AM Seymour J Metz wrote: > > > >> He posted messages showing that the STC ran normally. His primary > >> problem is OUTDISP; once he fixes that we can see whether the userid > >> is causing other problems. > >> > >> > >> -- > >> Shmuel (Seymour J.) Metz > >> https://apc01.safelinks.protection.outlook.com/?url=http:%2F%2Fmason. > >> gmu.edu%2F~smetz3&data=02%7C01%7Callan.staller%40HCL.COM%7C815695 > >> bad7c4430c0e0e08d7fdc08e1f%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0 > >> %7C637256875802443954&sdata=yrxVy3cUu7HVu23lPvqIkCAxcwCqRQm4GJwwB > >> Ocm9VQ%3D&reserved=0 > >> > >> ____________________ > >> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > >> behalf of Christopher Y. Blaicher [cblaic...@syncsort.com] > >> Sent: Thursday, May 21, 2020 2:48 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Where do started PROC errors go? > >> > >> Generally the job name is the name of the PROC you issued the start for. > >> Have you tried using the ST option of SDSF? Also, some errors get > >> put on the bottom of the queue. Also, did you look in the SYSLOG? > >> You should see the start and end messages > >> > >> Chris Blaicher > >> Technical Architect > >> Syncsort, Inc. > >> > >> -Original Message- > >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > >> On Behalf Of Binyamin Dissen > >> Sent: Thursday, May 21, 2020 2:38 PM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Where do started PROC errors go? > >> > >> [ External - This message originated Externally. Use proper > >> judgement and caution with attachments, links, or responses. ] > >> > >> Try running the PROC in a batch job. > >> > >> You do realize that without proper setup the STC is probably using a > >> different userid. > >> > >> On Thu, 21 May 2020 09:11:10 -0700 Charles Mills > >> wrote: > >> > >> :>I have a program that runs successfully in a job. I just cloned the > >> JCL :>appropriately into a PROC. When I issue a START for the PROC I > >> get a started :>message and an ended message but no clue as to why it > >> failed. (It is :>supposed to be long-running, so ending is a > >> failure.) I don't think it is a :>JCL error because I get a JCL error > >> message in that case, and I have :>evidence that it actually ran "some." > >> :> > >> :>The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I > >> have strong :>evidence that the program is getting far enough that it > >> would have written :>several lines to SYSTSPRT. > >> :> > >> :>I see nothing in SDSF, even with PREFIX * and OWNER *. > >> :> > >> :>Where is my output going? How do I determine that? How do I view it? > >> :> > >> :>There is nothing in the PROC statement: //procname PROC and no > >> operands on :>the START other than the PROC name. The program is > >> IKJEFT01 and a Rexx EXEC :>FWIW. Again, it works i
Re: Where do started PROC errors go?
S STCNAME...MSGCLASS=(held sysout class). I.e. ODISP=(keep,keep) -Original Message- From: IBM Mainframe Discussion List On Behalf Of Wayne Bickerdike Sent: Thursday, May 21, 2020 2:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Charles did your setup include something like this? RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH RACLIST(STARTED) On Fri, May 22, 2020 at 5:33 AM Wayne Bickerdike wrote: > Two things, no definition for the STC in RACF. > > If I have difficulty diagnosing STC problems, I run them as a job in > JCL to capture error messages. > > > > On Fri, May 22, 2020 at 5:14 AM Seymour J Metz wrote: > >> He posted messages showing that the STC ran normally. His primary >> problem is OUTDISP; once he fixes that we can see whether the userid >> is causing other problems. >> >> >> -- >> Shmuel (Seymour J.) Metz >> https://apc01.safelinks.protection.outlook.com/?url=http:%2F%2Fmason. >> gmu.edu%2F~smetz3&data=02%7C01%7Callan.staller%40HCL.COM%7C815695 >> bad7c4430c0e0e08d7fdc08e1f%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0 >> %7C637256875802443954&sdata=yrxVy3cUu7HVu23lPvqIkCAxcwCqRQm4GJwwB >> Ocm9VQ%3D&reserved=0 >> >> >> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on >> behalf of Christopher Y. Blaicher [cblaic...@syncsort.com] >> Sent: Thursday, May 21, 2020 2:48 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Where do started PROC errors go? >> >> Generally the job name is the name of the PROC you issued the start for. >> Have you tried using the ST option of SDSF? Also, some errors get >> put on the bottom of the queue. Also, did you look in the SYSLOG? >> You should see the start and end messages >> >> Chris Blaicher >> Technical Architect >> Syncsort, Inc. >> >> -Original Message----- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Binyamin Dissen >> Sent: Thursday, May 21, 2020 2:38 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Where do started PROC errors go? >> >> [ External - This message originated Externally. Use proper >> judgement and caution with attachments, links, or responses. ] >> >> Try running the PROC in a batch job. >> >> You do realize that without proper setup the STC is probably using a >> different userid. >> >> On Thu, 21 May 2020 09:11:10 -0700 Charles Mills >> wrote: >> >> :>I have a program that runs successfully in a job. I just cloned the >> JCL :>appropriately into a PROC. When I issue a START for the PROC I >> get a started :>message and an ended message but no clue as to why it >> failed. (It is :>supposed to be long-running, so ending is a >> failure.) I don't think it is a :>JCL error because I get a JCL error >> message in that case, and I have :>evidence that it actually ran "some." >> :> >> :>The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I >> have strong :>evidence that the program is getting far enough that it >> would have written :>several lines to SYSTSPRT. >> :> >> :>I see nothing in SDSF, even with PREFIX * and OWNER *. >> :> >> :>Where is my output going? How do I determine that? How do I view it? >> :> >> :>There is nothing in the PROC statement: //procname PROC and no >> operands on :>the START other than the PROC name. The program is >> IKJEFT01 and a Rexx EXEC :>FWIW. Again, it works in a job. >> :> >> :>Thanks, >> :>Charles >> >> -- >> Binyamin Dissen >> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furl >> defense.com%2Fv3%2F__http%3A%2F%2Fwww.dissensoftware.com__%3B!!I6-MEf >> EZPA!YOjsBluCmNaipeBYZjqxb7U9D_dMSn_ENJK4MNP5J_cc5ogXo4k6DoI05UXVcc_Z >> uA%24&data=02%7C01%7Callan.staller%40HCL.COM%7C815695bad7c4430c0e >> 0e08d7fdc08e1f%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637256875 >> 802443954&sdata=NSfQ%2FMbui1Nb9ExxAsuil0npRskyp%2BoKBhBN%2BCsq8j8 >> %3D&reserved=0 >> >> Director, Dissen Software, Bar & Grill - Israel >> >> >> Shou
Re: Where do started PROC errors go?
I don't know whether he is doing anyhing that requires authorization. What I do know is that he won't see his output unless he changes or overrides his OUTDISP. OTOH, it's certainly cleaner to assign an appropriate userid to every started task. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Wayne Bickerdike [wayn...@gmail.com] Sent: Thursday, May 21, 2020 3:33 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Two things, no definition for the STC in RACF. If I have difficulty diagnosing STC problems, I run them as a job in JCL to capture error messages. On Fri, May 22, 2020 at 5:14 AM Seymour J Metz wrote: > He posted messages showing that the STC ran normally. His primary problem > is OUTDISP; once he fixes that we can see whether the userid is causing > other problems. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf > of Christopher Y. Blaicher [cblaic...@syncsort.com] > Sent: Thursday, May 21, 2020 2:48 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > Generally the job name is the name of the PROC you issued the start for. > Have you tried using the ST option of SDSF? Also, some errors get put on > the bottom of the queue. Also, did you look in the SYSLOG? You should see > the start and end messages > > Chris Blaicher > Technical Architect > Syncsort, Inc. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Binyamin Dissen > Sent: Thursday, May 21, 2020 2:38 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > [ External - This message originated Externally. Use proper judgement and > caution with attachments, links, or responses. ] > > Try running the PROC in a batch job. > > You do realize that without proper setup the STC is probably using a > different userid. > > On Thu, 21 May 2020 09:11:10 -0700 Charles Mills wrote: > > :>I have a program that runs successfully in a job. I just cloned the JCL > :>appropriately into a PROC. When I issue a START for the PROC I get a > started :>message and an ended message but no clue as to why it failed. (It > is :>supposed to be long-running, so ending is a failure.) I don't think it > is a :>JCL error because I get a JCL error message in that case, and I have > :>evidence that it actually ran "some." > :> > :>The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I have > strong :>evidence that the program is getting far enough that it would have > written :>several lines to SYSTSPRT. > :> > :>I see nothing in SDSF, even with PREFIX * and OWNER *. > :> > :>Where is my output going? How do I determine that? How do I view it? > :> > :>There is nothing in the PROC statement: //procname PROC and no operands > on :>the START other than the PROC name. The program is IKJEFT01 and a Rexx > EXEC :>FWIW. Again, it works in a job. > :> > :>Thanks, > :>Charles > > -- > Binyamin Dissen > https://urldefense.com/v3/__http://www.dissensoftware.com__;!!I6-MEfEZPA!YOjsBluCmNaipeBYZjqxb7U9D_dMSn_ENJK4MNP5J_cc5ogXo4k6DoI05UXVcc_ZuA$ > > Director, Dissen Software, Bar & Grill - Israel > > > Should you use the mailblocks package and expect a response from me, you > should preauthorize the dissensoftware.com domain. > > I very rarely bother responding to challenge/response systems, especially > those from irresponsible companies. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Charles did your setup include something like this? RDEFINE STARTED MYSTC.* OWNER(SYS1) AUDIT(FAILURES(READ)) UACC(NONE) PERMIT MYSTC.* CLASS(STARTED) GENERIC ID(WAYNE) ACCESS(ALTER) RALTER STARTED MYSTC.* STDATA(USER(STCOPER) GROUP(GROUPZ)) SETROPTS REFRESH RACLIST(STARTED) On Fri, May 22, 2020 at 5:33 AM Wayne Bickerdike wrote: > Two things, no definition for the STC in RACF. > > If I have difficulty diagnosing STC problems, I run them as a job in JCL > to capture error messages. > > > > On Fri, May 22, 2020 at 5:14 AM Seymour J Metz wrote: > >> He posted messages showing that the STC ran normally. His primary problem >> is OUTDISP; once he fixes that we can see whether the userid is causing >> other problems. >> >> >> -- >> Shmuel (Seymour J.) Metz >> http://mason.gmu.edu/~smetz3 >> >> >> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf >> of Christopher Y. Blaicher [cblaic...@syncsort.com] >> Sent: Thursday, May 21, 2020 2:48 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Where do started PROC errors go? >> >> Generally the job name is the name of the PROC you issued the start for. >> Have you tried using the ST option of SDSF? Also, some errors get put on >> the bottom of the queue. Also, did you look in the SYSLOG? You should see >> the start and end messages >> >> Chris Blaicher >> Technical Architect >> Syncsort, Inc. >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Binyamin Dissen >> Sent: Thursday, May 21, 2020 2:38 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Where do started PROC errors go? >> >> [ External - This message originated Externally. Use proper judgement >> and caution with attachments, links, or responses. ] >> >> Try running the PROC in a batch job. >> >> You do realize that without proper setup the STC is probably using a >> different userid. >> >> On Thu, 21 May 2020 09:11:10 -0700 Charles Mills >> wrote: >> >> :>I have a program that runs successfully in a job. I just cloned the JCL >> :>appropriately into a PROC. When I issue a START for the PROC I get a >> started :>message and an ended message but no clue as to why it failed. (It >> is :>supposed to be long-running, so ending is a failure.) I don't think it >> is a :>JCL error because I get a JCL error message in that case, and I have >> :>evidence that it actually ran "some." >> :> >> :>The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I have >> strong :>evidence that the program is getting far enough that it would have >> written :>several lines to SYSTSPRT. >> :> >> :>I see nothing in SDSF, even with PREFIX * and OWNER *. >> :> >> :>Where is my output going? How do I determine that? How do I view it? >> :> >> :>There is nothing in the PROC statement: //procname PROC and no operands >> on :>the START other than the PROC name. The program is IKJEFT01 and a Rexx >> EXEC :>FWIW. Again, it works in a job. >> :> >> :>Thanks, >> :>Charles >> >> -- >> Binyamin Dissen >> https://urldefense.com/v3/__http://www.dissensoftware.com__;!!I6-MEfEZPA!YOjsBluCmNaipeBYZjqxb7U9D_dMSn_ENJK4MNP5J_cc5ogXo4k6DoI05UXVcc_ZuA$ >> >> Director, Dissen Software, Bar & Grill - Israel >> >> >> Should you use the mailblocks package and expect a response from me, you >> should preauthorize the dissensoftware.com domain. >> >> I very rarely bother responding to challenge/response systems, especially >> those from irresponsible companies. >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, send >> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > > -- > Wayne V. Bickerdike > > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Two things, no definition for the STC in RACF. If I have difficulty diagnosing STC problems, I run them as a job in JCL to capture error messages. On Fri, May 22, 2020 at 5:14 AM Seymour J Metz wrote: > He posted messages showing that the STC ran normally. His primary problem > is OUTDISP; once he fixes that we can see whether the userid is causing > other problems. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf > of Christopher Y. Blaicher [cblaic...@syncsort.com] > Sent: Thursday, May 21, 2020 2:48 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > Generally the job name is the name of the PROC you issued the start for. > Have you tried using the ST option of SDSF? Also, some errors get put on > the bottom of the queue. Also, did you look in the SYSLOG? You should see > the start and end messages > > Chris Blaicher > Technical Architect > Syncsort, Inc. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Binyamin Dissen > Sent: Thursday, May 21, 2020 2:38 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where do started PROC errors go? > > [ External - This message originated Externally. Use proper judgement and > caution with attachments, links, or responses. ] > > Try running the PROC in a batch job. > > You do realize that without proper setup the STC is probably using a > different userid. > > On Thu, 21 May 2020 09:11:10 -0700 Charles Mills wrote: > > :>I have a program that runs successfully in a job. I just cloned the JCL > :>appropriately into a PROC. When I issue a START for the PROC I get a > started :>message and an ended message but no clue as to why it failed. (It > is :>supposed to be long-running, so ending is a failure.) I don't think it > is a :>JCL error because I get a JCL error message in that case, and I have > :>evidence that it actually ran "some." > :> > :>The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I have > strong :>evidence that the program is getting far enough that it would have > written :>several lines to SYSTSPRT. > :> > :>I see nothing in SDSF, even with PREFIX * and OWNER *. > :> > :>Where is my output going? How do I determine that? How do I view it? > :> > :>There is nothing in the PROC statement: //procname PROC and no operands > on :>the START other than the PROC name. The program is IKJEFT01 and a Rexx > EXEC :>FWIW. Again, it works in a job. > :> > :>Thanks, > :>Charles > > -- > Binyamin Dissen > https://urldefense.com/v3/__http://www.dissensoftware.com__;!!I6-MEfEZPA!YOjsBluCmNaipeBYZjqxb7U9D_dMSn_ENJK4MNP5J_cc5ogXo4k6DoI05UXVcc_ZuA$ > > Director, Dissen Software, Bar & Grill - Israel > > > Should you use the mailblocks package and expect a response from me, you > should preauthorize the dissensoftware.com domain. > > I very rarely bother responding to challenge/response systems, especially > those from irresponsible companies. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
He posted messages showing that the STC ran normally. His primary problem is OUTDISP; once he fixes that we can see whether the userid is causing other problems. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Christopher Y. Blaicher [cblaic...@syncsort.com] Sent: Thursday, May 21, 2020 2:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? Generally the job name is the name of the PROC you issued the start for. Have you tried using the ST option of SDSF? Also, some errors get put on the bottom of the queue. Also, did you look in the SYSLOG? You should see the start and end messages Chris Blaicher Technical Architect Syncsort, Inc. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Binyamin Dissen Sent: Thursday, May 21, 2020 2:38 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [ External - This message originated Externally. Use proper judgement and caution with attachments, links, or responses. ] Try running the PROC in a batch job. You do realize that without proper setup the STC is probably using a different userid. On Thu, 21 May 2020 09:11:10 -0700 Charles Mills wrote: :>I have a program that runs successfully in a job. I just cloned the JCL :>appropriately into a PROC. When I issue a START for the PROC I get a started :>message and an ended message but no clue as to why it failed. (It is :>supposed to be long-running, so ending is a failure.) I don't think it is a :>JCL error because I get a JCL error message in that case, and I have :>evidence that it actually ran "some." :> :>The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I have strong :>evidence that the program is getting far enough that it would have written :>several lines to SYSTSPRT. :> :>I see nothing in SDSF, even with PREFIX * and OWNER *. :> :>Where is my output going? How do I determine that? How do I view it? :> :>There is nothing in the PROC statement: //procname PROC and no operands on :>the START other than the PROC name. The program is IKJEFT01 and a Rexx EXEC :>FWIW. Again, it works in a job. :> :>Thanks, :>Charles -- Binyamin Dissen https://urldefense.com/v3/__http://www.dissensoftware.com__;!!I6-MEfEZPA!YOjsBluCmNaipeBYZjqxb7U9D_dMSn_ENJK4MNP5J_cc5ogXo4k6DoI05UXVcc_ZuA$ Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Check the JES2 INIT Deck for the STCCLAS and see what it has for DISP. Next, if there is a SYSOUT Repository ($avers for example) maybe all output from the STC will be in there If you have a JCL Scan utility (Like JCLPLUS) then scan the JCS All else, slap a job card on it with TYPRUN=SCAN and see what that says. Sometimes in SDSF a ST function can find the output you cannot see Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, May 21, 2020 9:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Where do started PROC errors go? I have a program that runs successfully in a job. I just cloned the JCL appropriately into a PROC. When I issue a START for the PROC I get a started message and an ended message but no clue as to why it failed. (It is supposed to be long-running, so ending is a failure.) I don't think it is a JCL error because I get a JCL error message in that case, and I have evidence that it actually ran "some." The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I have strong evidence that the program is getting far enough that it would have written several lines to SYSTSPRT. I see nothing in SDSF, even with PREFIX * and OWNER *. Where is my output going? How do I determine that? How do I view it? There is nothing in the PROC statement: //procname PROC and no operands on the START other than the PROC name. The program is IKJEFT01 and a Rexx EXEC FWIW. Again, it works in a job. Thanks, Charles -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Generally the job name is the name of the PROC you issued the start for. Have you tried using the ST option of SDSF? Also, some errors get put on the bottom of the queue. Also, did you look in the SYSLOG? You should see the start and end messages Chris Blaicher Technical Architect Syncsort, Inc. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Binyamin Dissen Sent: Thursday, May 21, 2020 2:38 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where do started PROC errors go? [ External - This message originated Externally. Use proper judgement and caution with attachments, links, or responses. ] Try running the PROC in a batch job. You do realize that without proper setup the STC is probably using a different userid. On Thu, 21 May 2020 09:11:10 -0700 Charles Mills wrote: :>I have a program that runs successfully in a job. I just cloned the JCL :>appropriately into a PROC. When I issue a START for the PROC I get a started :>message and an ended message but no clue as to why it failed. (It is :>supposed to be long-running, so ending is a failure.) I don't think it is a :>JCL error because I get a JCL error message in that case, and I have :>evidence that it actually ran "some." :> :>The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I have strong :>evidence that the program is getting far enough that it would have written :>several lines to SYSTSPRT. :> :>I see nothing in SDSF, even with PREFIX * and OWNER *. :> :>Where is my output going? How do I determine that? How do I view it? :> :>There is nothing in the PROC statement: //procname PROC and no operands on :>the START other than the PROC name. The program is IKJEFT01 and a Rexx EXEC :>FWIW. Again, it works in a job. :> :>Thanks, :>Charles -- Binyamin Dissen https://urldefense.com/v3/__http://www.dissensoftware.com__;!!I6-MEfEZPA!YOjsBluCmNaipeBYZjqxb7U9D_dMSn_ENJK4MNP5J_cc5ogXo4k6DoI05UXVcc_ZuA$ Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Try running the PROC in a batch job. You do realize that without proper setup the STC is probably using a different userid. On Thu, 21 May 2020 09:11:10 -0700 Charles Mills wrote: :>I have a program that runs successfully in a job. I just cloned the JCL :>appropriately into a PROC. When I issue a START for the PROC I get a started :>message and an ended message but no clue as to why it failed. (It is :>supposed to be long-running, so ending is a failure.) I don't think it is a :>JCL error because I get a JCL error message in that case, and I have :>evidence that it actually ran "some." :> :>The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I have strong :>evidence that the program is getting far enough that it would have written :>several lines to SYSTSPRT. :> :>I see nothing in SDSF, even with PREFIX * and OWNER *. :> :>Where is my output going? How do I determine that? How do I view it? :> :>There is nothing in the PROC statement: //procname PROC and no operands on :>the START other than the PROC name. The program is IKJEFT01 and a Rexx EXEC :>FWIW. Again, it works in a job. :> :>Thanks, :>Charles -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Where do started PROC errors go?
Is your proc in the IEFJOBS or IEFPDSI concatenation? Does it have a JOB statement? What messages did you get after the START? Is the MSGCLASS a purge class? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Charles Mills [charl...@mcn.org] Sent: Thursday, May 21, 2020 12:11 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Where do started PROC errors go? I have a program that runs successfully in a job. I just cloned the JCL appropriately into a PROC. When I issue a START for the PROC I get a started message and an ended message but no clue as to why it failed. (It is supposed to be long-running, so ending is a failure.) I don't think it is a JCL error because I get a JCL error message in that case, and I have evidence that it actually ran "some." The PROC includes //SYSTSPRT DD SYSOUT=H. (H is a held class.) I have strong evidence that the program is getting far enough that it would have written several lines to SYSTSPRT. I see nothing in SDSF, even with PREFIX * and OWNER *. Where is my output going? How do I determine that? How do I view it? There is nothing in the PROC statement: //procname PROC and no operands on the START other than the PROC name. The program is IKJEFT01 and a Rexx EXEC FWIW. Again, it works in a job. Thanks, Charles -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
