Integrating IBM Tivoli Workload Scheduler with Tivoli Products

222 Integrating IBM Tivoli Workload Scheduler with Tivoli Products

6.3 Creating the collect application

When you have set up the TWS for z/OS component and have discussed the

tracklog data management, you are ready to collect the tracklog data. It is best to

collect the data using a TWS for z/OS application so that it is automated and can

be tied into the creation of the daily tracklog data set.

In our example installation, the tracklog data is the only data that was collected.

However, if we were already collecting one or more other types of log data, we

would need to plan how the tracklog data collect application would integrate with

existing applications.

Some things to consider are:

򐂰 Existing application naming convention

򐂰 Existing job name naming convention

򐂰 Existing special resource naming convention

It is worth noting that there is no predefined way of setting up a TWS for z/OS

environment for managing a Tivoli Decision Support for OS/390 database. So,

we assume that there will be more than one Tivoli Decision Support for OS/390

database installed on the SC64 system at some point in the future and that more

than one TWS for z/OS controller will be collected into our initial Tivoli Decision

Support for OS/390 database.

6.3.1 Standardization considerations

Standardization of names is important if you are managing a multi Tivoli Decision

Support for OS/390 database environment that collects several different types of

data from several different systems. It introduces economies of scale and

enables you to easily tell from either the application or job name what is being

collected from where and into which database. Additionally, it also enables you to

automate the creation of the applications and job names, which you can then

load into the TWS for z/OS database using the batch loader facility and into the

relevant JCL library respectively.

With these standards in mind, we set up an application in TWS for z/OS called

TDS#01#TWS#01#DC, where:

򐂰 TDS reflects that it is a Tivoli Decision Support for OS/390 application.

򐂰 01 reflects that it is the first Tivoli Decision Support for OS/390 database on

the system.

򐂰 TWS reflects that it is a TWS for z/OS related application.

򐂰 01 reflects that it is processing data from the system with LOGID(01) coded.

򐂰 DC reflects that it is a daily data collection application.

Chapter 6. Integrating Tivoli Decision Support for OS/390 223

The application contains a dummy start operation, a T01T01C1 collect job

operation, and a dummy end operation. The collect job name is made up of the

following characters:

򐂰 T reflects that it is a Tivoli Decision Support for OS/390 job.

򐂰 01 reflects that it is the first Tivoli Decision Support for OS/390 database on

the system.

򐂰 T reflects that it is a TWS for z/OS related job.

򐂰 01 reflects that it is collecting LOGID(01) data.

򐂰 C reflects that it is a collect job.

򐂰 1 gives it uniqueness.

If a second TWS for z/OS controller were collected, the application would be

called TDS#01#TWS#02#DC with job name T01T02C1, and a third application

would be called TDS#01#TWS#03#DC with job name T01T03C1.

These names were chosen so that we could also have the following applications

and job names in our Tivoli Decision Support for OS/390 database:

򐂰 TDS#01#SMF#63#DC for the daily collect of SMF data from the SC63

system with a job name of T01S63C1.

򐂰 TDS#01#SMF#64#DC for the daily collect of SMF data from the SC64

system with a job name of T01S64C1.

򐂰 TDS#01#IMS#63#DC for the daily collect of IMS data from the SC63 system

with a job name of T01I63C1.

򐂰 TDS#01#IMS#64#DC for the daily collect of IMS data from the SC64 system

with a job name of T01I64C1.

We can then use similar names for collecting data into a second Tivoli Decision

Support for OS/390 database:

򐂰 TDS#02#TWS#01#DC for the daily collect of TWS for z/OS data from a

system with LOGID(01) coded with a job name of T02T01C1. This would be a

different TWS for z/OS to that collected by the T01T01C1 job.

򐂰 TDS#02#TWS#02#DC for the daily collect of TWS for z/OS data from a

system with LOGID(02) coded with a job name of T02T02C1. This would be a

different TWS for z/OS to that collected by the T01T02C1 job.

򐂰 TDS#02#SMF#65#DC for the daily collect of SMF data from the SC65

system with a job name of T02S65C1.

򐂰 TDS#02#SMF#70#DC for the daily collect of SMF data from the SC70

system with a job name of T02S70C1.