Configuring an interactive subsystem

 

The information in this section explains how to set up a new interactive subsystem.

These steps are described as if the commands are entered manually. However, you can easily re-create your configurations for recovery purposes by using a CL program to create your subsystems.

When you set up a new interactive subsystem you should consider how many devices will be allocated to that subsystem. Since the subsystem performs device management functions, such as presenting the signon display and handling device error recovery, you might want to limit the number of devices allocated to a single subsystem. See the Communications limits topic for more information.

This topic provides a synopsis of what is involved in configuring interactive subsystems. The experience reports about subsystems contain detailed explanations of each step and additional options available for each step.

1. Creating a library
   This example shows how to create a library to store your subsystem configuration objects.
2. Creating a class
   A class defines certain performance characteristics for your interactive subsystem. Follow this instruction to create a class.
3. Creating the subsystem description
   For each subsystem that you need to define, repeat this step to create the subsystem description.
4. Creating a job queue
   You can create a job queue for the subsystem using the same name as the subsystem name and add a job queue entry to the subsystem description.
5. Adding a routing entry
   The routing entries that are supplied with the system for QINTER have some additional functions. If you need those functions, add those routing entries to your customized subsystem descriptions.
6. Adding workstation entries
   Adding workstation entries to the subsystem description is a key step for assigning which devices are allocated to which subsystem.
7. Customizing QINTER
   When you begin using your own set of subsystems, you might not need to use QINTER. However, if you have a reason to continue to use QINTER, you need to ensure that QINTER is set up NOT to allocate the workstations that you want to run under your other subsystems. There are two possible ways to do this.
8. Configuring the console
   A final, but VERY important consideration regarding QINTER is the workstation type entry of *CONS for the console. Make sure that you do not accidentally prevent someone from signing on at the console. You prevent this from happening by not adding any workstation entries for the console to your custom interactive subsystems.
9. Assigning users to a specific subsystem
   You can use several techniques to assign device names and then associate those device names with users. After this is accomplished, you can use the workstation entries to get the user to the correct subsystem.

 

Parent topic:

Managing subsystems