IEF404I / IEF403I

[Lucas Rosalen]

Hello folks,

We had an issue today where we noticed IEF404I (job end) and IEF403I (job
start) messages were not arriving at SYSLOG or NETLOG of a z/OS 1.11 system
running in a 4-system sysplex with all others running z/OS 1.13.

Issue started on Nov 26th but was only really discovered today (other than
some small automation issues noticed).

No IPLs have taken place and no MPF adjustements had been made, IEF404I
just suddenly stopped arriving (IEF403I had stopped arriving way before Nov
26th, but it doesn't trigger anything in out automation).

We had fixed this by issuing:
1. SETCON MONITOR,JOBNAMES=(OFF)
2. SETCON MONITOR,JOBNAMES=(ON) >> this command alone didn't work, just
worked when issued after the #1 one

I also do not see any SETCON MONITOR,JOBNAMES=(OFF) being issued after last
IEF404I arrived at our SYSLOG.

Have any of you guys seem a behavior like that?
Although it's working fine now, I wanted to make sure this won't happen
again, so any insight is very much appreciated.

Thanks,


-------------------------------------------------------------------------------------------------------------------------------
*Lucas Rosalen*
***@gmail.com / ****@br.ibm.com <***@br.ibm.com>*
[phone]

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Ed Finnell]

Something disruptive happened. If you got no Dumps or SIM messages EREP
produces mini trail of
abends in LOGREC.


In a message dated 12/3/2014 1:32:35 P.M. Central Standard Time,
***@GMAIL.COM writes:

Have any of you guys seem a behavior like that?
Although it's working fine now, I wanted to make sure this won't happen
again, so any insight is very much appreciated.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN