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
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 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
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.