×
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 Wed04-Apr-2011 13:47 , Rusling, John wrote:
The DFTPGM/CHGMSGD thing, is this causing a program to be called
whenever a certain message is received/intercepted?
The DFTPGM() is invoked only when that specific message [the MSGID()
named on CHGMSGD or ADDMSGD] is issued as an escape message, and when
that exception was considered to be an "unmonitored escape message";
i.e. when "this message is sent as an escape message to a program that
is not monitoring for it."
As well the *PGM coded and then specified on the DFTPGM() can perform
logic which effects nothing more than a RETURN if necessary conditions
are not in effect for which further processing is required. So for
example, if the DFTPGM() should not perform the WRKOBJLCK except when
the job name is 'GENASNS', the opening actions and logic for the CLP as
DFTPGM() might be:
pgm /* parms for a DftPgm? */
/* declarative section */
...
/* start of program processing */
rtvjoba job(&jobnam)
if cond(&jobnam *ne 'GENASNS') then(goto justexit)
/* other logic and actions below if no early exit */
...
justexit:
return
endpgm
Using the OVRMSGF after the CRTMSGF, MRGMSGF, and CHGMSGD for the
original testing further ensures only the test environment is affected
until the CHGMSGD is performed against the actual message file that will
be used by some select [per OVRMSGF] or all other jobs on the system.
Regards, Chuck
midrange.com
