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



Hhhmm. Didn't think about that when I decided to use *RQS. The main
reason I was avoiding *DIAG is because it might shows up in the joblog
and *DIAG command could give an impression of something is wrong. Since
I have code to remove the message, I guess I'll just change it to use
*DIAG. Thanks.



"Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx> wrote in message
news:<mailman.2007.1218061781.2545.rpg400-l@xxxxxxxxxxxx>...
Why do you use *RQS type?? Seems like you could have strange results
if
you happen to have a request-handler running at that call-stack level.

What was wrong with *DIAG?

Lim Hock-Chai wrote:
Ok. Use QMHSNDPM and specified the program name that I want to
check on
the stack entry parameter works. I get CPF2479 when program is not
in
the stack. (Note: Instead of *DIAG message type, I use *RQS message
type and do a QMHRCVPM to remove it.) Not sure if this method is
faster
than QWVRCSTK or not. But it sound like it should.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.