×
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 -
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.
As an Amazon Associate we earn from qualifying purchases.
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.