Re: Route jobs to different subsystms

[Ken Sims <mr3111@xxxxxxxxx>]

Hi Chris -

> The first problem with that is when you do a transfer job on the second 
> session you will see the following at logon:
> "Message queue CBECK is allocated to another job." (I can live with this once)
> They press enter and then see the following three messages:
>
> "TFRJOB command ended the routing step."
> "Routing step started in subsystem QCTL."
> "Message queue CBECK is allocated to another job."
> These I would need to get rid of these.

I don't think you have any choice here.  Either you use device names to put 
the users in the correct subsystem to start with, you leave them in the 
subsystem they started in, or you live with it.

> The IP address received at this time would not be of use, I need the IP of 
> the interface they came in on (Servers IP).

If each server IP address is in a different subnet, then you don't really 
need the server IP address, or you can figure out what it must be by using 
the interface information available in file QATOCIFC in QUSRSYS.

If they are in the same subnet, there are some new APIs that I believe 
became available in V5R2 which can probably give you the information you 
need, but I've never used them.  Perhaps someone else can point you in the 
right direction.

Another thought ... if the information about the interface is accessible 
very early in the process, you could use a telnet exit program to assign a 
device name which would put the device into the correct subsystem to start 
with and thereby avoid the need for a TFRJOB and also avoid the problems of 
hard-coding device names.

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.