From: Art Tostaine To: All

I recently added a new remote location to our AS/400, and I want to have the new users run in their own interactive subsystem. I created a new subsystem QINTERT, and I created additional generic workstation name entries in both QINTER and QINTERT.

Even though QINTER's generic workstation entry is DSP0*, and all of the remote location's workstations are named DSPTxxxxx, if QINTERT is not active, they will come up under QINTER.

From: Ernie Malaga To: Art Tostaine

Both QINTER and QINTERT need to have two workstation entries as indicated in 6.

Both QINTER and QINTERT need to have two workstation entries as indicated in Figure 6.

When you do this, DSPT* display stations will not come up under QINTER, even if QINTERT is down, because of the AT(*ENTER) parameter. AT(*SIGNON) means that the subsystem should grab the display station and present the sign-on display when you start up the system; AT(*ENTER) means that the subsystem should grab the display station only when the user presses the Enter key after typing in TFRJOB JOBQ(QINTER). The AT parameter (and its valid values) are extremely unintuitive; they should get the prize for such if there ever is a contest.

From: John Brown To: Art Tostaine

One problem that I had when setting up dual interactive subsystems was that QINTER had a workstation entry of *All plus the WSE of DSP*. I removed the *All WSE from Qinter. Everything comes up okay now. If you use this method, you need to make sure that every device name (i.e., DSP* or DSPT*) is associated with a specific subsystem.

TechTalk: Interactive Subsystems

Figure 6 Workstation entries

 Figure 6: Workstation Entries Subsystem || Workstation || AT( Name || Name ------------------------------------------------- QINTER || DSP0* || *SIGN || DSPT* || *ENT ------------------------------------------------- QINTERT || DSPT* || *SIGN || DSP0* || *ENT