S STCNAME...MSGCLASS=(held sysout class). I.e. ODISP=(keep,keep)
-----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> 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 <wayn...@gmail.com> 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 <sme...@gmu.edu> 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 <charl...@mcn.org> >> 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 <bdis...@dissensoftware.com> >> 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 >> >> >> 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 ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
