Chapter 6. Integrating Tivoli Decision Support for OS/390 215
Figure 6-6 Installing via batch status
6. Populate the OPC_WORKSTATION lookup table with the details from the
TWS for z/OS controller from which you will be collecting data and,
subsequently, on which the data will be reported.
How you choose to perform the install determines how you populate the table.
Online
If you installed online, you are already in the right location. Select the
OPC_WORKSTATION table and press Enter.
–Batch
If you installed via batch, you have to:
i. Select option 2 (Administration) from the TDS for OS390 Primary Menu
panel and press Enter.
ii. Select option 4 (Tables) from the Administration menu and press Enter.
iii. Select the OPC_WORKSTATION table and press F10 (Actions).
iv. Tab across to the Edit menu and press Enter.
v. Select option 3 (ISPF) and press Enter.
Regardless of how you populate the OPC_WORKSTATION lookup table, you
are presented with the panel that is shown in Figure 6-7 on page 216.
216 Integrating IBM Tivoli Workload Scheduler with Tivoli Products
Figure 6-7 Empty lookup table
The OPC_SYSTEM_ID value to code should correspond to the value coded
on the LOGID parameter of the BATCHOPT initialization statement. This
statement is contained in the PDS member of the data set that is referenced
by the EQQPARM DD statement in the current plan extend or replan batch
job. Example 6-1 shows this code in our installation.
Example 6-1 Location of BATCHOPT
//EQQPARM DD DISP=SHR,DSN=TWS.INST.PARM(BATCHOPT)
The WORKSTATION_NAME, WORKSTATION_TYPE, and DESCRIPTION
fields should be populated with the values that are defined in the Workstation
descriptions option of the TWS for z/OS database (option 1.1 from the
OPERATIONS PLANNING AND CONTROL panel).
Note: If the LOGID parameter is not coded on the BATCHOPT initialization
statement, the default value of 01 is being used. You should code this
value in the OPC_WORKSTATION table.
Chapter 6. Integrating Tivoli Decision Support for OS/390 217
Figure 6-8 shows part of our populated table.
Figure 6-8 Coding the lookup table
Code a row for every workstation that is defined to the Tivoli Workload
Scheduler for z/OS controller to ensure that they can all be reported upon.
Press F3 (Exit) to save the changes. A confirmation appears, as shown in
Example 6-2.
Example 6-2 Successful table changes
The table changes are saved successfully.
If you installed online, you are returned to the Components panel, as shown
in Figure 6-9 on page 218. Note the Status and Date fields are now
populated.
Important: The workstation names and types must use uppercase letters.
The workstation type values C, G, and P should be coded as COMPUTER,
GENERAL, and PRINTER respectively. The description field can be a mix
of both upper and lowercase letters.
218 Integrating IBM Tivoli Workload Scheduler with Tivoli Products
Figure 6-9 Component installed notification
If you installed via batch, you are returned to the Tables panel.
The “TWS for z/OS - OPC Component” is now fully installed and is ready for the
collection of data. Information on collecting data is discussed in 6.4, “Collecting
TWS for z/OS data” on page 233. However, before you collect data, you first
need to identify the data.

Get Integrating IBM Tivoli Workload Scheduler with Tivoli Products now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.