×
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 06-Nov 08:14 -0800, Jeff Young wrote:
I has been ages since I have had to do this.
Do I just send the message to *PRV or *EXT?
The CPP is /transferred to/ vs called from the Command Analyzer
feature, so the invoker of the command is the /previous/ caller in the
stack. The External message queue is a special location rather than the
effective stack [i.e. the call message queue], so avoid using that
except when specifically that target is desired; I believe there is even
a restriction for sending *ESCAPE messages there, I do not recall.
FWiW: If another program were left in the stack between the calling
program [e.g. a CLP invoking the command] and the CPP, then the message
would be sent previous to that [hopefully static] program name; i.e. the
message is sent relative, minus one caller, to the known and consistent
caller [typically by name, per "Call stack entry identifier"] of the CPP
from a *CMD invocation.
Do I need a special message id or can I use the generic CPF9898?
That generic message provided by the OS *can be* utilized, and
hard-coded or dynamically-built message data to describe the failure,
but that is IMO a poor choice as a /design/ decision. Certainly
qualifies for the various expressions prefixed with: /Good enough for/
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
