Re: Call stack inquiry performance - QWVRCSTK vs QMHSNDPM+QMHRCVPM

Is that means that there is a way for a program that running on a high
call stack to register a request processor/handler that wait for *RQS
message from program on the lower call stack and process it? That would
be cool if that is possible. If my assumption is true, anybody know how
to register a request processor/handler?

"Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx> wrote in message
news:<mailman.2250.1218132657.2545.rpg400-l@xxxxxxxxxxxx>...

Request messages (*RQS) is how the operating system runs commands.

When

you type a command into a command-line, it's sent as a request message

to a request processor. The request processor reads the request

message

to get the command to run.

Personally, I'd use a *DIAG message for this. If you don't want it to

show up in the job log, remove it after you've retrieved the call

stack

info.

Lim Hock-Chai wrote:

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.