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



There is a keyword in your DDS that tells the system what message queue
to use when displaying the subfile-message. The keyword is SFLPGMQ.
There should be a variable associated with this keyword. The value you
put in this variable is where the message need to be sent. The easiest
way to do this is to use the program name as the value for this variable
and when you execute the QMHSNDPM, specified the Program name as the
call stack (Call Stack Counter should be 0).


"Roger Harman" <RHarman@xxxxxxxxxx> wrote in message
news:<mailman.2392.1234287434.26163.rpg400-l@xxxxxxxxxxxx>...
With OPM programs, we've used message subfiles for years and have
always
called a CL to send the message (from a message file) to the message
subfile.

I'm now converting some of these to use procedures like: MsgqClear()
and MsgqWrite(MyMsgId). This encapsulates the QMHRMVPM & QMHSNDPM
calls
and takes care of the library, message file, etc. The code was
copy/pasted from a Search400 article by Kent Milligan - the only
difference is that I put it in a procedure (not in a service program)
rather than inline.

I can see the messages in the joblog but nothing is appearing in the
subfile. I've tried changing the call stack name and counter values
to
see if that was the issue. I can see (with F1, F9) that it changes
the
"TO PROCEDURE" but still no success.

It seems so simple but I'm stuck. Any suggestions? Thanks.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.