Hi all:
I'm still trying to figure this out while I still have access to
the system.
A few things -- I am just a general user. I have no authorities
on/with this system. I don't even have access to ask the systems
people questions. So I do know that exits are involved. They are
running TPM (Thru Put Manager) and some other operations control
stuff.
I changed my JOB to contain MSGLEVEL=(1,1) from just =1. No joy.
I also used SV to look at the whole JOB, then did an EX all,
followed by F IEF prefix all. No Joy with this one either.
My compatriots on this project who have also been software
developers are baffled. We don't know why I hit this and they do
not get this.
But, like I said earlier, we have received a stop work order
so... I doubt we will ever know why.
On 4/24/2025 5:54 AM, Jeremy Nicoll wrote:
On Wed, 23 Apr 2025, at 22:05, Leonard D Woren wrote:
As to the IEFC452I, I ran a few quick tests and I am unable to come up
with a job that containsIEFC452I without also some other IEF message
later, giving the detail for the JCL error. IEFC452I seems to be in
the joblog (dsid 2) and the other IEF message(s) are in job messages
(dsid 4). IEFC452I also appears in SYSLOG, but not the other IEF
messages when it's a normal batch job.
Does that mean - if the OP couldn't find the extra messages - that they
didn't have MSGLEVEL=(1,1) in their JOB card? Or that their MSGCLASS
was something that got purged from the spool immediately?
--
Regards,
Steve Thompson
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
