Re: Separate subsystems -- MIDRANGE-L

Hi Dave

Instead of using workstation names which is not so controllable these days (PQADEV* devices in particular are a problem) you can use routing entries to solve your problem.

Off the top of my head you will need to do the something along the of the following to achieve what you want:

- add a routing entry to your QINTER subsystem description with a value of 'QINTERA' - specify a program on the routing entry of 'TFRQINTERA' (obviously it needs to be accessible to the end user) - write a program 'TFRQINTERA' that when called does a TFRJOB to the desired susbsyetm - in the target subsystem ensure there is an *ANY routing entry specifying QCMD - alter the job descriptions of the affected users to specify RTGDTA 'QINTERA' - test it to make sure it works ;)

The only niggle I have had with this is that the transfer job step can cause an additional screen to be displayed when transferring to the target subsystem (from memory this occurs when there are messages to be displayed)

Hope this helps
Regards
Evan Harris

At 05:53 a.m. 19/04/2005, you wrote:

I have been asked by a client to create separate subsystems for their interactive users.

I have done this before but am drawing a blank as to how to direct the users to the correct subsystem. Some of the users have unique device names such as DAVE1 but others are still using QPADEV* taype names

How do I direct the users to the correct subsystem or where can I go to learn the process gain
TIA
Dave Willenborg

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.