CICS® IA uses an
ISPF dialog that runs REXX execs to assist you in configuring your CICS IA environments.
CICS IA takes the SMPE target
data sets as input, updates the required members with the variable
names you provide and then saves the information to customized output
data sets. The customized data sets are then used to create your environments.
The ISPF dialog is split into three main categories:
- Configuring or updating your DB2® environment. CICS IA stores all the collected
data in a CICS IA database.
The CICS IA plug-in can then
access the data through a JDBC Type 4 connection. Use the ISPF dialog
to input the DB2 variables that
are required, such as DB2 version.
These variables are used to populate the output data sets for DB2 configuration. You can use
the output data sets to run the tasks that are required to create
the DB2 environment. These tasks
include the following:
- Creating the CICS IA database.
- Creating the Stored Procedures.
- Binding and granting access to the CICS IA
plans.
- Configuring or updating your Collector environment. The CICS IA collector uses several CICS GLUEs and TRUEs to collect
the data that you request, and stores the data in VSAM data sets and
user logstreams. Use the ISPF dialog to input the variables that are
required. These variables are used to populate the output data sets
for a Collection configuration. You can use the output data sets to
run the tasks that are required to set up the collector. These tasks
include the following:
- Allocating the VSAM files.
- Allocating the resources that are required for Command Flow collection.
- Allocating the CICS resource
definitions.
- Allocating the CICS file
resource definitions.
- Allocating Atomservice resource definitions.
- Creating and binding DB2 objects
that are required by the Collector.
- Configuring or updating a DB2 UDB
environment. CICS IA provides
jobs to unload CICS IA data
into CSV files. These files can be used to populate the IBM® supported UDB databases. CICS IA also provides the Definition Data Language
(DDL) sample to create a UDB on Windows NT. This DDL is provided only as a sample. CICS IA also supplies sample tasks to run in
your UDB environment. The sample tasks help you to load the tables
from the CSV files. Use the configuration exec to customize the sample
to task to your site's standards and naming conventions.
The ISPF dialog saves your customization variables in two places.
- In your ISPF profile data set that is allocated to the ISPPROF
file at logon. This data set is typically ‘userid.ISPPROF’. In this
data set, there is a membercalled CIUCPROF.
- In an ISPTABL data set that is concatenated to your ISTLIB file.
By default this file is allocated as ‘userid.ISPTABL’. The data set
name that you use is stored in your ISPF profile. You can change this
name as described in Modify your settings.
Data set allocation
The CICS IA configuration exec allocates data sets
that save your configuration output. These data sets are allocated
by the esoteric device group SYSDA.
Some of the sample jobs
that are used to allocate files that are required by CICS IA also uses the SYSDA esoteric device
group. You can change this value by updating the OUTPUT DEVICE TYPE
value in your configuration.