Yes, the ++++++++ may be a problem, because that means you're most likely running with an undefined user which means RACF is most likely stopping the task from running unless every dataset it is hitting has a UACC allowing access. You need to define a security profile in the STARTED class with your proc name to grant access.
The other thing is the OUTDISP=(PURGE) in jes2parm. That's telling JES2 to purge the output when the task completes. Rex -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Charles Mills Sent: Thursday, May 21, 2020 11:47 AM To: [email protected] Subject: Re: [External] Where do started PROC errors go? All that is in SYSLOG is S myproc,MSGCLASS=H IRR813I NO PROFILE WAS FOUND IN THE STARTED CLASS FOR 446 myproc WITH JOBNAME myproc. RACF WILL USE ICHRIN03. $HASP100 myproc ON STCINRDR IEF695I START myproc WITH JOBNAME myproc IS ASSIGNED TO USER ++++++++ $HASP373 myproc STARTED $HASP395 myproc ENDED Is that USER ++++++++ a problem? I'm not getting any RACF messages. Here is JES2PARM JOBCLASS(STC) TIME=(1440,00), /* Job Step Time ...mmmmss....... WS*/ COMMAND=EXECUTE, /* Execute Commands ..........r...... WS*/ BLP=NO, /* Ignore BLP parm ...........l..... WS*/ AUTH=ALL, /* Allow all Cmds ............aaaa. WS*/ MSGLEVEL=(1,1), /* Job, All Msgs ................e 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 LOG WS*/ 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*/ (I have "ALL CLASSES" in SDSF.) Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Pommier, Rex Sent: Thursday, May 21, 2020 9:23 AM To: [email protected] Subject: Re: [External] Where do started PROC errors go? Charles, A couple things to check. Is there anything in the SYSLOG showing what happened to the task? Check your JES2PARM member of parmlib. In there, you should find a JOBCLASS(STC) stanza. What does that show for LOG, MSGCLASS, MSGLEVEL, OUTDISP and OUTPUT? Rex -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Charles Mills Sent: Thursday, May 21, 2020 11:11 AM To: [email protected] Subject: [External] 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 [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
