TechTalk: Interactive Subsystems

Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

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 
BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  •  

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: