The number at the end identifies a Multi-Line WTO (MLWTO). The subsequent lines of the WTO start with that number. This means that messages can be pieced together when an MLWTO is interspersed with other messages in the log.
Lennie -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Schmitt, Michael Sent: 23 April 2025 14:13 To: [email protected] Subject: Re: [EXTERNAL] Re: [IBM-MAIN] IEFC452I !?! The number at the end isn't a statement number. I created the error with a job with only 9 cards. But I can't find documentation of what, exactly, it is. It kind of looks like a sequence number that is increasing for every system message on the LPAR, for the purpose of associating messages that are multiple lines. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Steve Thompson Sent: Tuesday, April 22, 2025 9:17 PM To: [email protected] Subject: Re: [EXTERNAL] Re: [IBM-MAIN] IEFC452I !?! Love your sense of humor. On 4/22/2025 9:22 PM, Tabor, Richard J wrote: > With all my years of experience, I was finally able to get a job to fail with > a JCL error (after 7 tries) - my last JCL error occurred in the late 80's. > > M 4040000 FUP7 25112 17:57:34.54 JOB01117 00000090 IEFC452I JCERRJCE - > JOB NOT RUN - JCL ERROR 384 > ... > M 4008000 FUP7 25112 17:58:34.59 STC10966 00000080 AOF568I 17:58:34 : > STATUS OF NTVF7 OUTBOUND GATEWAY TO DOMAIN 386 > E 386 00000080 ING01 IS INACTIVE - > TARGET DOMAIN ING01 IS NOT ACTIVE > M 4008000 FUP7 25112 17:58:34.61 STC10966 00000080 AOF568I 17:58:34 : > STATUS OF NTVF7 OUTBOUND GATEWAY TO DOMAIN 387 > E 387 00000080 ING02 IS INACTIVE - > TARGET DOMAIN ING02 IS NOT ACTIVE > M 4008000 FUP7 25112 17:58:34.62 STC10966 00000080 AOF568I 17:58:34 : > STATUS OF NTVF7 OUTBOUND GATEWAY TO DOMAIN 388 > E 388 00000080 ING03 IS INACTIVE - > TARGET DOMAIN ING03 IS NOT ACTIVE > > I'm guessing that mysterious number all the way to the right has nothing to > do with the number of JCL statements. > > I would love to show you the JCL I used to produce this, but I would have to > eliminate everyone on this list. > > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of Steve Thompson > Sent: Tuesday, April 22, 2025 2:26 PM > To: [email protected] > Subject: [EXTERNAL] Re: [IBM-MAIN] IEFC452I !?! > > **** External Email - Use Caution **** > > Thank you. > > I forgot to mention that I did run this with TYPRUN=SCAN and get the same > message. > > And to be sure, I have been running this JOB off an for the past month. > > I have gotten file not found. That was the first thing I checked, using "F > FOUND" and that typically shows me the missing DSN. > > Not on/with this failure. > > And submitting it again -- the suffixing number of the error is different, > and is greater than the number of JCL statements in this JOB. So that doesn't > seem related. > > Regards, > Steve Thompson > > > > On 4/22/2025 5:01 PM, Ramsey Hallman wrote: >> The version prior to 3.1 is 2.5 of z/OS. >> >> >From the error message, it does not necessarily have to be the job >>> name. It >> could be other JCL issues. >> >> IEFC452I text - JOB NOT RUN - JCL ERROR >> >> Explanation >> >> Depending on the message text, one of the following: >> >> JOBFAIL >> >> The error was detected on a JOB statement and the job name is not >> known. >> >> INVALID >> The system detected an error in a JOB or other JCL statement, and >> the job name (the label on the JOB statement) is invalid. >> >> jobname >> The system detected an error in a JCL statement, or the job was >> cancelled while on the input queue. >> >> procstep >> The procedure was specified in the first operand of a START command. >> In this case, either the procedure was not found in SYS1.PROCLIB or, >> if found, the procedure had an error in a JCL statement. Message >> IEE122I or IEE132I will always follow this message. >> >> The error message appears in the SYSOUT data set. >> >> This message can also be issued for various environmental errors, >> such as an error occurring while trying to read a record from the >> JCL text data set or an I/O error occurring while trying to get >> procedure statements. >> >> System action >> >> If the operator cancelled the job, all steps of the job, beginning >> with the step currently being processed, will be ended. Otherwise, >> the job will not be initiated; no steps will be processed. If >> procstep appears, the START command will not be run. >> >> Operator response >> >> If the job name appears, none. If procstep appears, either reenter >> the START command with the correct procedure name, or, if the >> procedure name is correct, notify the application programmer. >> >> Programmer response >> >> Check the procedure for errors. >> >> Source >> >> Converter >> >> Module >> >> IEFCNJRT >> >> Routing code >> >> 2,10 >> >> Descriptor code >> >> 4 >> >> On Tue, Apr 22, 2025 at 3:53 PM Steve Thompson <[email protected]> wrote: >> >>> Hi all, got a weird one. >>> >>> I am running the same JOB over and over processing different files. >>> All that changes is the suffix on an output DSN that identifies the >>> DATA cycle of this execution, and the SORTIN DD/DSN contents (some >>> have a single file some have up to 15 files). Data may be on disk or >>> tape. TPM holds the job until HSM restore completes if that is why >>> the data is on tape. >>> >>> I would love to show you the JCL, but I am NOT allowed. Suffice to >>> say security controls. >>> >>> I have taken the JOB cards off another one of these JOBs that ran >>> successfully and replaced the JOB card (one from a prior submission >>> of this specific JOB). >>> >>> And I still get this error. The last thing it says is 748. >>> Since I don't have 700 JCL statements, that isn't the problem. >>> Besides this is supposedly a JOB card error!! >>> >>> BTW, sometimes the files I have been told to pick disappear before I >>> can get the JCL updated and submitted, so I do get file not found >>> errors. But this is not the issue here. >>> >>> I have a copy of the full tech library for the Version of z/OS just >>> prior to 3.1 (can't remember the V/R). And it is not helping me with >>> this. >>> >>> -- >>> Thanks for your help/insight in advance. >>> >>> Steve Thompson ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
