How can I direct Interactive jobs to specific subsystems?

260 pts.
Tags:
AS/400
AS/400 subsystem
We have 2 interactive subsystems. One was intended for all the interactive jobs of the IT department. The other was for all non-IT users. The idea being - if necessary, the non-IT user subsystem could be ended while IT people were still logged on fixing a problem or whatever. When interactive sessions are started the devices are created with generic "virtual" device names QPADEV*. Do we need non-generic device names to be able to assign them to a subsystem?

Software/Hardware used:
as/400
ASKED: January 28, 2013  4:42 PM
UPDATED: January 28, 2013  4:51 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Yes, if you create non-generic device description you can control this issue with the Work Station Entry Names in the subsystem descriptions.

Years ago, I did something with the TFRJOB command. If it is your initial signon program, you should be able to transfer to a different subsystem.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    By using a naming convention, you can directly control what devices are attached to what subsystems. If all devices use the same convention, you have three general (and potentially troublesome) methods available. Other methods can probably be created.   For the first of the three, you can use ADDWSE to add workstation name entries one by one to your chosen subsystems. You might add QPADEV0001 to the first interactive subsystem, and add QPADEV0002 to the second for example. The immediate problem with that would be that it's more difficult to know when a given user is going to get the appropriate QPADEV* device.   A second method would be to have initial programs for everyone so that a TFRJOB routed to a second subsystem for either normal users or IT users (or perhaps both).   You might only have this in the initial program for normal users. IT users would stay where they started, while normal users would be transferred. If the 'normal user' subsystem was inactive, the TFRJOB would receive a CPF1364 *ESCAPE message. The program could then end the job normally or display an error screen explaining that interactive services were not available.   Or you could set a routing program in the first subsytem. If the job was determined to be for a normal user, the routing program would run the TFRJOB command with similar behavior to the initial program.   The most direct way to avoid those three is simply to use ADDWSE to associate all QPADEV* devices to your main interactive subsystem. And have IT staff use devices that have names starting with a different pattern, e.g., IT*. Associate the IT* devices to the IT subsystem with ADDWSE.   No programming is involved if you do it directly with named devices. No programming maintenance is needed in the future. No need to mess with initial programs nor routing programs. It's straightforward and clean. IT staff should be trained enough to know how to configure their devices (or perhaps they shouldn't be part of IT staff and have access to IT resources).   Note that an exit point is available if you want to create programming that assigns device names to users under programmed control.   Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following