> 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 'REQUESTPROCESSOR', 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. ---------- Fra: PaulMmn <PaulMmn@ix.netcom.com> Til: MIDRANGE-L@midrange.com Emne: Routing Entries / was Re: Signon Information Screen Dato: 8. oktober 1999 06:39 >Please excuse my ignorance in this manner, but how I can change routing >program? >Thanks in advance > >Matt Zajac A routing program is just like any other program. It just has special placement. Write a program to do whatever you want to have happen whenever anyone signs on: Force them to display their messages, display the on-line bulletin board, show them their Office/400 Mailbox, write home to Mother, etc. The last instruction executed in the program should be TFRCTL QCMD This is usually a CLProgram, but could be RPG. Try not to clutter up the program too much; your signon process will be delayed by whatever this program does. And, the simpler the program, the less likely it is to get errors. Make sure the program works! Compile and test! This program will be seen by the whole world! Well, at least everyone who uses QINTER. Examine the QINTER susbsystem description. You will notice there is one section labeled, "Routing Entries." Now, I don't know what a plain vanilla subsystem description looks like any more; ours has been mutiliated until even IBM wouldn't know it. (: However, there are a few routing entries that most Interactive subsystems have: An entry, numbered 9999 or other high number with a compare value of *ANY Entries with compare values of QCMDI and/or QCMDB 'other' entries The entries for QCMDI and QCMDB should (?) link to program QCMD. You need to replace QCMD with -your- program (which eventually links to program QCMD). But first-- CRTDUPOBJ QINTER QSYS *SBSD TOLIB(yourlib) And change your normal 'startup' procedure to use -your- copy of QINTER, not IBM's. The reason you copy it to 'yourlib' is because installing the next release of the operation system will restore IBM's SBSD in library QSYS, undoing all of the work you're about to do. Now the fun. You need to use the CHGRTGE command. CHGRTGE SBSD(yourlib/QINTER) SEQNBR(###) PGM(yourlib/yourpgm) Replace the ### with the number of the existing entry with compare value 'QCMDI.' Repeat with the entry for 'QCMDB' If you only have QCMDI or QCMDB, that's OK. We probably have System/38 routing entries. Or, if there isn't an entry besides the *ANY, ADDRTGE SBSD(yourlib/QINTER) SEQNBR(###) PGM(yourlib/yourpgm) CMPVAL('QCMDI' 1) CLS(*SBSD) MAXACT(*NOMAX) POOLID(1) PROMPT THIS COMMAND! I'm not sure about the CMPVAL parm!!! Repeat for CMPVAL('QCMDB' 1) If you've done any system tuning, the POOLID may need the number you've previously set. Replace the ### with a unique number less than the 9999 of the *ANY entry. When you sign on to the QINTER subsystem your job is compared to the 'Compare Values' in the routing entries. When a match is found, your job executes the 'Program' in the entry. The comparison is done in order by the 'Sequence Number.' The *ALL entry is a 'catch all;' if your job doesn't match any other entry, it -will- match the *ANY entry. Now, sign on to a terminal session. TFRJOB QCTL and sign on again, but make sure the signon screen has been issued by subsystem QCTL. MAKE SURE ALL OF THE USERS HAVE SIGNED OFF OF THE SYSTEM!!! ENDSBS QINTER <--- all of your signon screens will disappear DSPSBS QINTER <--- repeat until you get a screen that lets you know nothing was found STRSBS yourlib/QINTER <--- your signon screens should re-appear Find another terminal session. Check to see if it's for QINTER. Sign on and see if your program does what you had in mind. IF YOU HAVE PROBLEMS: - You're still signed on at a different terminal session to the QCTL sbs. - If you've made your own copy of QINTER, the original is still there, ready to use. - To go back to the original QINTER: ENDSBS QINTER DSPSBS QINTER <--- repeat until it's not running STRSBS QSYS/QINTER Good luck! It only -seems- tricky! (: --Paul E Musselman PaulMmn@ix.netcom.com >Please excuse my ignorance in this manner, but how I can change routing >program? >Thanks in advance > >Matt Zajac > >>>> PaulMmn <PaulMmn@ix.netcom.com> 09/30 9:27 PM >>> >Or, change the routing program in the QINTER subsystem. You'll be able to >display messages, show the OV/400 New Mail screen, display a special >message screen, etc. etc. > >--Paul E Musselman >PaulMmn@ix.netcom.com > > > > >>If you don't want to mess with the actual signon screen itself, you >>could include a call to your own display program within the user's >>INLPGM. >> >>This way you could get as fancy as you want, even ask for user feedback, >>filter messages by user, etc. >> >>"McGoldrick,Michael" wrote: >>> >>> Hello, >>> >>> Our IT manager wants us to include a user information screen in the signon >>> process to the AS400. We have looked at changing the actual signon >>>screen but >>> don't want to clutter it with too much information. Is there anyway to >>>have a >>> screen simillar to the Signon Information screen included when the user >>>signs >>> on. Can this page be edited or can we include our own page(s)?. >>> >>> Any help would be appreciated, >>> Thanks, >>> Michael +--- | 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: email@example.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: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.