×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Inside the DO(), test H1 and make your processing contingent on that?
What if there is an unexpected error but no dump?
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of James H. H. Lampert via MIDRANGE-L
Sent: Wednesday, August 10, 2022 4:20 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Subject: Detecting dumps in a CL program?
I have a CL program that calls a bunch of RPG programs.
The calls are in the form:
CALL FOO
MONMSG MSGID(CEE9901) EXEC(DO)
SNDMSG MSG('We experienced a problem with the +
FOO program, and are skipping the rest +
of this run.') TOMSGQ(QSYSOPR FROBOZZ)
GOTO CMDLBL(SKIPTHIS)
Normally, this works quite well. But today, we experienced an anomaly,
such that we would like very much for the CL program to respond
differently if a dump is taken on one of the called RPG programs.
I will note that when an *expected* error occurs, the RPG program will
respond with a SETON of indicators H1 and LR, followed by a RETURN. The
*unexpected* errors *don't* have an explicit SETON of H1. Can I maybe
use that?
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
