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



On 28-Jun-2016 12:30 -0500, Buck Calabro wrote:
On 6/28/2016 12:51 PM, Monnier, Gary wrote:
This appears to me to be a program failing and the invoking module
not handling errors. It looks like your CL is failing and
returning to your RPG, and runs again.

Try placing an error indicator on the call to your CLP. You can
then handle the error how you see fit. It could be a timing issue
where your CPYF tables are locked when the CLP is first run.

Might explain why it's occasionally re-running. Imagine that the CL
runs, gets an error and someone answers the QSYSOPR messages with a C
to cancel the CLP and then an R to re-try in the RPG.


I doubt that, per:

The chosen snippet of joblog, unless highly redacted, would presumably contain _something_ indicative of that effect.? The CLP has no monitors, so if there were any failure in the CLP, there would be expected to show a *FC and a CPA0701, the reply message. If the CLP did somehow terminate directly to the RPG [without any visible CL run-time handling], then the equivalent RPG run-time default handler and its inquiry equivalent to CPA0701 would presumably have appeared, again with the reply message, plus any preceding error messages are unlikely to get removed by the RPG program.? And most notably, the apparent _normal_ CL program /RETURN/ [the RETURN message F/QCLRTNE] effect shown, seems to contradict any speculation that the CL failed in any way.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.