×
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.
Just a note for those of you who use a procedure to handle calls to
QCMDEXC. I have a program that has a QCMDEXC procedure which simply
figures out the length of the command and calls QCMDEXC passing the
command and the length.
In that same program I have another procedure called TESTADDR that calls
a WorksRight Software program to validate a postal address. The
WorksRight program requires a message file override, so in the TESTADDR
procedure I had:
QCMDEXC('OVRMSGF MSGF(QUSERMSG) TOMSGF(MLMESG)');
In this situation, the override is only in effect while control is in
the QCMDEXC procedure. When control returned to the TESTADDR procedure,
the override was gone. I guess I should of realized this since a
procedure is another entry on the call stack.
I replaced the QCMDEXC procedure call with a straight program call in
the TESTADDR procedure and the override stayed in effect for the call to
the WorksRight program.
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
