Re: Route jobs to different subsystms -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hi Chris -

I need to find a way to route a interactive job to a particular subsystem by the IP interface they come in on, or by the initial program.

IMO, the best way is to use your own routing program in all of the subsystems involved. As has already been mentioned, TFRJOB is the command to use. Each subsystem needs to have *NOMAX jobq attached. You actually transfer to the jobq, not the subsystem. You need to monitor for various errors on the TFRJOB.

You can use a special routing data value on TFRJOB to keep from going into a loop. The special value would be on a routing entry with QCMD as the program to call. The catch-all entry would have your special program. Or not use the special value and have your program determine if the user is already in the right subsystem. If so, TFRCTL QCMD. If not, TFRJOB.

You can use the method shown here http://www.ke9nr.net/iseries/faqs/devipaddr.shtml to determine the IP address of the device.

Ken http://www.ke9nr.net/ Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.