Re: Command validation program - Conclusion

        Hi all, 
        and thank you very much for your valuable input. Team work rules,
as usual. Here is what I found out using all ideas and some of my
experiments:

        I used "Receive Program Message" - API with these key parameters:

        format No. 0100
        current call-stack position (*)
        call-stack entry number 3
        message type *LAST
        
After calling this API, command name and all parameters start from
position no. 49 of message data. 

        It's important to know that this setup will work only for
validation program, not for main process program. Reason for it is that
those two programs have different positions on the call-stack; there is
one more system program involved with validation program and therefore
val. pgm. is two stack-positions away from command processor (I gues that
call-stack entry number should be changed to 2 in case of main program,
but didn't try). 

        Also, message type *REQ didn't work for me, because once request
message is processed by command processor, it's considered to be *OLD, and
I have to chose some type that would enable API to receive *ALL messages.

P.S.
        I'd like to apologize to people who were upset with my previous
comment (about first college year ...). I simply tried to make a joke, to
be funny, but it looks that I missed the target. Once again, sorry guys
and no hard feelings.

BTW, this is one-line(simple) and API (AS-ish) solution.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---