×
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 29 Jan 2013 14:07, Vernon Hamberg wrote:
<<SNIP>>
Chuck, I'm sure you're familiar with this KB - I forget the link -
and it might be overkill for this situation.
To find the KB - it is doc #28942837 - title is "Receiving Messages
from the Joblog after the Program Is off the Callstack"
The situation presented by the OP is handling a *FC for a prior
exception which gave rise to the CPF9999 [aka *FC]; very specifically.
Thus the preceding exception was to the *SAME program stack. Using the
technique in that KB article is hardly appropriate as compared to the
ultra-simple resolution of issuing one RCVMSG MSGTYPE(*EXCP) RMV(*YES)
followed by a RCVMSG MSGTYPE(*EXCP). There seems little reason to
complicate the scenario for the OP with that [or changing to use MONMSG
CPF0000, or even something like the Resend Exception Message API, even
if that might be reasonably be inferred as the desired]; i.e. better to
stick with the most succinct resolution for the exact code given.?
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
