Creating a subsystem description

 

You can create a subsystem description in two ways. You can copy an existing subsystem description and change it, or you can create an entirely new description. The following are two approaches that you can use:

1. To copy an existing subsystem description, using the character-based interface, follow the following instructions:
   1. Create a Duplicate Object (CRTDUPOBJ) of an existing subsystem description. (You can also use the Work with Objects (WRKOBJ) or Work with Objects using Programming Development Manager (WRKOBJPDM) commands.)
   2. Change the copy of the subsystem description so that it functions in the manner that you require. For example, you will need to remove the job queue entry because it identifies the job queue that the original subsystem uses. Then you will need to create a new job queue entry that specifies the parameters that the new subsystem will use.

      Remember to review the autostart job entries, the workstation entries, the prestart job entries, and the communication entries, and verify that there are no conflicts between the two subsystems. For example, verify that the workstation entries do not cause both subsystems to allocate the same display devices.

2. To create an entirely new subsystem description, use the character-based interface and follow the following instructions:
   1. Create a Subsystem Description (CRTSBSD).
   2. Create a Job Description (CRTJOBD).
   3. Create a Class (CRTCLS) for Add Prestart Job Entry (ADDPJE) and Add Routing Entry (ADDRTGE).
   4. Add Work Entries to the subsystem description.

      • Add Workstation Entry (ADDWSE )

      • Add Job Queue Entry (ADDJOBQE)

      • Add Communications Entry (ADDCMNE)

      • Add Autostart Job Entry (ADDAJE)

      • Add Prestart Job Entry (ADDPJE)
   5. Add Routing Entries (ADDRTGE) to the subsystem description.

• Adding autostart job entries
  You use the character-based interface to add an autostart job entry. An autostart job starts automatically when the associated subsystem starts. These jobs generally perform initialization work that is associated with a particular subsystem. Autostart jobs can also perform repetitive work or provide centralized service functions for other jobs in the same subsystem.

• Adding communications entries
  Each communication entry describes one or more communication device, device types, or remote location for which the subsystem will start jobs when program start requests are received. The subsystem can allocate a communication device if the device is not currently allocated to another subsystem or job. A communications device that is currently allocated may eventually be de-allocated, making it available to other subsystems. To add a communications entry to the subsystem description, use the character-based interface.

• Adding job queue entries
  A job queue entry identifies a job queue from which jobs are selected for running in the subsystem. Jobs started from a job queue are batch jobs. You add a job queue entry using the character-based interface.

• Adding prestart job entries
  Prestart job entries identify prestart jobs that may be started when the subsystem is started or when the Start Prestart Jobs (STRPJ) command is entered. You can add prestart job entries to the subsystem description by using the character-based interface.

• Adding routing entries
  Each routing entry specifies the parameters used to start a routing step for a job. Routing entries identify the main storage subsystem pool to use, the controlling program to run (typically the system-supplied program QCMD), and additional run-time information (stored in the class object). To add a routing entry to a subsystem description, use the character-based interface.

• Adding workstation entries
  A workstation entry is used when a job is started when a user signs on or transfers an interactive job from another subsystem. You can specify the following items in a workstation entry. Parameter names are given in parentheses. Use the character-based interface to add workstation entries.

• Creating a signon display file
  The signon display file is used to show signon displays at workstations that are allocated to the subsystem. The signon display file can be changed when the subsystem is active. However, the new signon display file is not used until the next time the subsystem is started. To create a signon display file, use the character-based interface.

• Specifying the new signon display
  A subsystem uses the signon display file that is specified in the SGNDSPF parameter of the subsystem description to create the signon display at a user workstation. To change the signon display file from the default (QDSIGNON) to one that you have created, use the character based interface.

 

Parent topic:

Managing subsystems

Related concepts
Subsystems Subsystem description

Related information
Experience Report: Subsystem Configuration