IBM Mainframe Forum

I don't see any 404's either. Where can I look to find such "exits"? A Control-O rule processes these 403 and 404's but again, it's exactly the same as that in another system.
I haven't unsuppressed them yet. Will report back when I do.

Thanks.

And like I said, jobs that run on a schedule still produce the msgid. I realize I'm not being very clear but please try to understand what I'm saying.

again I ask... what do You think the YES under the column headed SUPPRESS means ???

and why do You think that after somebody has told the system to suppress the message the same should be displayed anyway

read the system initialization and tuning about the details of the syntax of the MPFLSTxx parmlib member

here for example
http://publib.boulder.ibm.com/infocente ... mpflst.htm

when in one of Your posts You said the the MPFLST in use contained the IEF403I message
everybody believed that you had carried on the due diligence to try to understand the MPFLST implications
but unfortunately we were wrong

Hello,

Thanks for the output shown for "D MPF". This is very clear and the Required MSGID has been under the suppress Field. Z/OS is acting as designed. If you believe if its not then you might have to analyze the historical log, it could be weekly log.. analyzing for each schedule. Then It would be also best if you can OPEN a case with Control O support folks and they might give you more insights based on the Product DUMP.(Analyzing the Dumps).

Jaggz

Hi,

I updated MPF and this is the output now..



What's more weird is.. a few jobs which were submitted today (by a team mate no less), have produced the msgid. But a few of us are still not able to successfully produce a msgid in the syslog.

Make sure the same MPF settings are consistent throughout your sysplex. It could be that you and your colleague may log on to the same system but when you both submit a job, each job might run on a different system.

Check message $HASP373 for each job, which I think should indicate the SMF id of the system where your job ran.

Hi Pedro,

They're running on the same system. This particular system where I'm facing this problem, is a stand-alone.

Hi,

I was able to get it going after issuing these commands:



Thanks for the suggestions!

Thanks for letting us know.