If a program or procedure crashes you can find the Message text within the
Program Status Data Structure Position 91-180.
Program Status Data structure can be included within the Global D-Specs of
each RPG Source.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
Modernization ? Education ? Consulting on IBM i
IBM Champion since 2020
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
"Train people well enough so they can leave, treat them well enough so they
don't want to. " (Richard Branson)
"Learning is experience ? everything else is only information!" (Albert
Einstein)
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jay Vaughn
Sent: Monday, 17 April 2023 14:51
To: RPG programming on the IBM i (AS/400 and iSeries)
<rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: monitor downstream
Let's say I have an RPGPGM1 that does the following...
monitor;
RPGPGM2();
on-error;
// check %status();
end-mon.
It is my understanding that if RPGPGM2 pgm fails, then our %status will only
report a 202 and will not give us the details as to why.
Is there anyway in RPGPGM1, to get the exact reason why RPGPGM2 failed,
without adding a msg parm on RPGPGM2 and bubbling the message up?
thanks
Jay
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
midrange.com
