Implementing DBS

This section describes the steps and procedures required to Implement DBS.

System Requirements

In order to implement and activate DBS:

• You must be running Version 7 of ThruPut Manager.
• The Control File must be in Version 7 format. If you are running ThruPut Manager Version 5, this requires a Control File conversion.

The scope of DBS is the same as that of your JES2 node.

DBS Facilities

The facilities provided to support DBS are summarized here.

Installation and Implementation

To install and implement DBS, you must:

1. Convert your Control File to Version 7. Although you can install the DBS modules without converting the Control File, the application cannot run, and a warning message will be issued.
2. Install the DBS modules as per the instructions contained in the accompanying Installer’s Guide.
3. Use the TMISPF command to initiate the TM Automation Services Dialog, then select TM Automation File Services from the Main Lobby to begin defining a DBS Configuration. For more information, see DBS Configuration Definition Considerations.
4. When DBS is installed according to the Installer’s Guide, the option name DBS is added to the selection of options that can be controlled through the OPTIONS keyword of the JES2 initialization statement TMPARM and the TM OPTIONS operator command. The default for this option is disabled. Change the JES2 initialization statement TMPARM to enable DBS.
5. Optionally, add the DBS keyword to the TM SMF initialization statement.
6. Stop TMSS on all systems.
7. Hotstart JES2. To enable DBS temporarily without a hotstart, you can use the operator command TM OPTIONS ENABLE DBS.
8. Restart ThruPut Manager on all systems.
9. Invoke the TM Automation Services dialog and activate the NEW Configuration.

After these steps have been completed, DBS is installed and ready to manage your tape devices.

DBS Configuration Definition Considerations

The DBS Configuration is kept in the Automation File, which is managed with ISPF dialogs.

Invoking the DBS Configuration Dialog

To define a DBS Configuration, first issue the TSO command under ISPF to invoke ThruPut Manager ISPF services:

TMISPFThis takes you to the Main Lobby for ThruPut Manager dialogs. From the list, select the BMC AMI Ops Automation for Batch ThruPut dialog. This brings up the Primary Options panel, from which you select TM Automation Services. You are now presented with a list of Automation File management options.

The Automation File is used by other ThruPut Manager services besides DBS, but it needs to be allocated and initialized only once. For our example, we assume that the file does not exist. Select the option to allocate and initialize a new file. This opens a window asking for details of the new Automation File.

Note that you need one Automation File for each JESplex.

JESplex Configuration

After you have provided a name for the Automation File, you are prompted for a descrip- tion of the JESplex. If you are running on the JESplex that will use the new file, you can have DBS automatically gather the information for you, otherwise you must provide it manually.

This JESplex description is common to all services that use the Automation File, including DBS. It includes:

• A description that will help identify the Automation File.
• The JES2 node name.
• The JES2 SPOOL data set name.
• The JES2 SPOOL volume prefix, required to ensure that the JESplex is uniquely identified.

All the information provided here can be edited later if necessary.

Defining the First Configuration

Once you have saved the JESplex information, you should select the DBS service and define a DBS Configuration.

A description of the steps to follow to define a Configuration is provided in the Managing the Configuration section.

The **BASE** Policy

When you save your first Configuration definition, DBS automatically creates a default Policy for you. A pop-up window prompts you to enter a description. The Policy has these characteristics:

• The Policy name, which cannot be altered, is “**BASE**”.
• All device counts are equal to the number of Device Numbers that you specified in your Configuration.
• The Work Group feature is turned OFF.

You are placed in Policy Edit mode, which allows you to manage the Device Counts for the Drive Pools defined in the Configuration, and to turn on and manage the Work Group feature.

Although you can edit the **BASE** Policy at this point, we recommend that you do not make this Policy a specialized one for these reasons:

• This is the Policy that an operator can always restore with a simple command.
• It is a good idea to maintain a stable **BASE** Policy that you can use as the starting point for creating all other Policies.

For a description of creating specialized Policies, see the section Managing Policies.

DBS Work Groups

DBS Work Groups are helpful in distributing tape devices among various types of work. For example, you might want to make sure that test jobs don’t exhaust a Drive Pool at the expense of production work. DBS allows you to do this by using JAL (or JECL) to assign jobs to different Work Groups. Each Work Group has limits on the minimum and maximum count of devices that it can allocate from the Drive Pool. Work Groups therefore determine “who gets what.”

The initial Configuration definition does not turn on the Work Groups feature. We recommend leaving Work Groups turned off until you are satisfied that you have defined your Configuration and Policies correctly, and that DBS is running smoothly. Work Groups are not mandatory, and you might find that your installation does not need them at all.

When defining the Work Groups, keep the following in mind:

• Choose descriptive names. This will help later when viewing displays or analyzing results.
• There are three possible Work Groups, each with two Subgroups. You do not have to use all of them, but you cannot add new ones.
• The three Work Groups are for organization purposes. You actually assign one of the six Subgroups to jobs.
• The Subgroups have an implied priority. All other things being equal, the Subgroup priority ranking is from Subgroup 1 to Subgroup 6, or left to right as seen in a display of Work Groups. This order cannot be changed.

SMF Monitoring of DBS Activity

A ThruPut Manager facility is provided for an installation to gather statistical information about the activity of DBS. An SMF record containing this information is generated at intervals of approximately every ten minutes.

Activating Data Collection for DBS

To collect data from the DBS application, you must indicate this on the TM SMF initialization statement:

Identifying DBS Records

DBS records are identified by their subtype of 240. The subtype is found in the field named SMFTMSTP in the DTM DBSMF mapping macro. Refer to this macro for details of the collected data.