Re: monitor downstream

Am 17.04.2023 um 14:59 schrieb stefan@xxxxxxxxxx:

Eventually use a db2 for i service in RPGPGM1 and read the joblog. To make that easier you can send a "marker msg" to the joblog prior to the call to RPGPGM2 so you know where to start looking in the joblog.

Best regards

Stefan

--
No trees were killed in the sending of this message, but a large number of electrons were terribly upset.

Stefan Tageson
+46 732 369934
stefan@xxxxxxxxxx

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jay Vaughn
Sent: Monday, April 17, 2023 2:51 PM
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.


--
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.