Why Consider Multiple Subsystems?

Interactive Subsystem Configuration
Interactive users are users who run 5250 display station sessions. These sessions are connected from twinax, remote workstation, Telnet, 5250 Display Station Pass-through, Virtual Terminal API-based applications and various Web-based connections, such as WebFacing, IBM WebSphere* Host Access Transformation Server (HATS) and iSeries Access for the Web 5250 support.


The following steps explain how to set up a new interactive subsystem. It's recommended that the number of devices allocated to a single interactive subsystem be limited to 250 to 300, so you should create the appropriate number of interactive subsystems given the number of users on your system.

One of the first planning steps is to determine the subsystem naming convention you want to use. The naming convention could be something as simple as INTER1, INTER2, INTER3, etc., something more reflective of the type of work (INVENTORY, ORDERENT, PGMR) or reflective of the geographic location where your users reside (EAST, CENTRAL, WEST). Decide on a naming convention that will be meaningful for your system administration.

The following steps are described as if the commands are entered manually (Note: You should use a CL program to create your subsystems so you can easily re-create your configurations for recovery purposes):

1. Create a library to store your subsystem configuration objects in. In this example, we use SBSLIB:

CRTLIB SBSLIB TEXT (‘Library to hold subsystem configuration objects')

2. Create a class. The class defines certain performance characteristics for your interactive subsystem. To create a class that's identical to the QINTER class, enter the command:

CRTCLS SBSLIB/INTER1 RUNPTY(20) TIMESLICE(2000) PURGE(*YES) DFTWAIT(30)TEXT(‘Custom Interactive Subsystem Class')

3. You can use the QINTER class in QGPL for your custom interactive subsystems, create a single class to use for all of your interactive subsystems or create a class for each interactive subsystem. Which you choose depends on whether you want to customize some of the performance settings for particular subsystems. IBM-supplied subsystems are shipped with a class created for each subsystem, with the name of the class being the same as that of the subsystem. So if you don't create a class for each subsystem with the same name as the subsystem, you must specify the class name on the Add Routing Entry (ADDRTGE) command because the default for the CLS parameter is *SBSD, meaning the class name has the same name as the subsystem description.


Dawn May is an IBM i consultant. She owns Dawn May Consulting, LLC in the Greater Boston area.

comments powered by Disqus



2019 Solutions Edition

A Comprehensive Online Buyer's Guide to Solutions, Services and Education.


Analyzing Disk Watcher Data

Knowing how to collect and analyze your performance data can help improve your system’s performance

An Introduction to Job Watcher Green-Screen Commands

Although Job Watcher now has a GUI, green screeners won’t be left out with four new green-screen commands.

IBM Systems Magazine Subscribe Box Read Now Link Subscribe Now Link iPad App Google Play Store
IBMi News Sign Up Today! Past News Letters