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 > 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 <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://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
