RE: MCH3203 when pressing attn key

I have seen this before, basically this was the issue - '
in one program and it allows the attn key to call up
an attention program, that program allows calls to
another program, which in turn allows a call to the
first program; and thus the error.

It sounds like you need some checking before allowing
users to continue nested calls; or they need to be
instructed more clearly -

Here we just eliminated the ability to call certain
programs from with-in the attention program which
contained calls to other programs that it really
came from in the first place;

It does get confusing, but that helps you to understand
why the AS/400 does not know what to do either.

HTH

Mark



-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Sean Porterfield
Sent: Thursday, March 28, 2002 2:08 PM
To: MIDRANGE-L
Subject: MCH3203 when pressing attn key


We have an odd problem that just showed up yesterday morning.  I tried
searching the archives for MCH3203 but didn't find anything that related.

When some users press their attention key, they get a message saying their
job is ending immediately.  It actually kills off both jobs, if they are
signed on a system request.  Strangely, this does not affect everyone.  It's
not related to specific terminals, just specific user profiles it seems.

Anyone have any ideas?  We are at V4R4 probably not the latest cum.

Looking in the job log, I see:

"Message . . . . :   Job ended abnormally because of error code MCH3203."
Cause . . . . . :   The job was ended by the system because an error was
  found, and the job was in a condition where the process default exception
  handler (QMHPDEH) could not be given control. The system will not give
control to QMHPDEH when the job is in between the starting phase and the
problem phase, or between the problem phase and the ending phase. Some of
the more common error codes and their meanings follow: MCH0802 - The program
that the job routed to must have parameters, but it is not allowed to have
any parameters passed to it. MCH1604 - A system object is damaged.  The most
likely object is the program to which the job is routed. MCH3203 - A machine
function check occurred.  The most likely cause is that the program stack
for a routing step was nested too deeply.  This is probably due to repeated
calling of the programs. MCH3402 - A system object is destroyed or has
header damage.  This is most commonly caused by deleting a program that is
active in the program stack.  It may also be caused by deleting the event
handlers, external exception handlers, or the program to which the job was
routed. MCH3403 - The program to which the job was routed was saved with
storage freed. If MCH3203 is not previously described, display the message
(DSPMSGD command) to see what is causing the error.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.