Re: Routing Entries / was Re: Signon Information Screen

>> A routing program is just like any other program
>> The last instruction executed in the program should be
>>      TFRCTL   QCMD
>
>Just to clarify:
>What Paul talks about is a 'REQUEST  PROCESSOR', i.e. a program that
>processes the entri(es) of type request in the job's external
>messagequeue. QCMD is the standard requestprocessor, which is why he uses
>the "TFRCTL   QCMD" but you can do it in any way you
>like. A program invoked by an routing entry do not NEED to process any
>requestmessages.


Well, true-- ie you could set it up so when you sign on and match the
routing entry your job will execute program FRED, then go to end-of-job
without doing anything else.  Your routing entry could compare to jobname,
user profile, etc.  [these have starting positions other than 1...  anyone
have a list?]

The original question asked if it was possible to "include a user
information screen in the signon process,"  which is what -we- do.

Uh, I'll go out on a limb and guess that 'most people use routing programs
as I described.'  (:

Actually we do a -lot- (too much?) in our interactive routing program.
Display messages, change message queue to break mode (or don't display
messages and don't put the queue in break mode for certain devices),
display OV/400 messages (for the dwindling number still using OV), adjust
the interactive library list, show the bulletin board, select the menu to
be displayed based on a user's location (keyed from the user profile name),
configure some things in QTEMP we think are nifty for all users to have...
and MORE!

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