Re: Command validation program

>Hi Vernon, thank you for your time:
>
>On Sat, 23 May 1998, Vernon Hamberg wrote:
>
>>
>> VAnya
>>
>> >
>> >    Passing command name as a parameter is not an option. So far, I
>> >tried sending messages to various system programs previously on the stack
>> >(QCMD, QUOCMD ...), but none was "willing" to return that information.
>> >However, sending ESCAPE message, returns command name to joblog, but than
>> >it's too late :))). Still, command name must be somewhere around. What am
>> >I missing?
>>
>> Ooh! Intriguing idea. Are you using the same validation program for
>> multiple commands?
>
>
>       I'd like to. There are a few similar commands with the same set of
>parameters, and I would like to perform checking and (application) loging
>from one spot.  That's why I need command name.
>
>Vanya


How 'bout a 'hidden' (ie constant) parameter on the command that contains
the name of the command?  Never appears when you prompt the command, but is
passed along as a regular parameter as if it had been keyed in.

I've used this to pass a varying parameter (ie library name) to the Command
Processing Program.  That way I can have 'Fire Up Live Environment' and
'Fire Up Test Environment' commands, but use the same program.

--Paul E Musselman
PaulMmn@ix.netcom.com


+---
| 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
+---