Creating a new collection environment

The steps that are required to define the resources that are required to enable CICS® IA collection in your CICS regions. Review and submit the sample jobs that are configured.

When the configuration utility runs to define your CICS environment variables, the following output data sets are available.

hlq.SCIUSAMP.CICS
hlq.SCIUSAME.CICS
hlq.SCIUSQL.CICS
hlq.SCIUDAT1.CICS

Note: If the CICS IA collector is configured to be used with a UDB database, SCIUSQL and SCIUDAT1 are not created.

The data set hlq.SCIUSAMP.CICS contains the sample jobs that you require to define and maintain your CICS IA collector environment.

Step 1 - Defining the VSAM files

To create the CICS IA VSAM files that are used by CICS IA:

To define the CICS IA Control file.: Review and submit the sample job CIUJCLCC in hlq.SCIUSAMP.CICS. This job completes with a return code of 0.

To define the CICS IA collector files.: Review and submit the sample job CIUJCLCA in hlq.SCIUSAMP.CICS. This job completes with a return code of 0.

Step 2 - Defining the Command Flow resources

The CICS IA command flow feature uses CICS logstreams and GDGs to facilitate the offloading of captured data into the DB2® tables. To create these resources:

To define the logstream that is used by CICS IA.: Review and submit the sample job CIUJCDLS in hlq.SCIUSAMP.CICS. This job completes with a return code of 0.

To define the user GDG data sets that are used by CICS IA.: Review and submit the sample job CIUJCLCG in hlq.SCIUSAMP.CICS. This job completes with a return code of 0.
Note: You must define GDG data sets for every CICS user ID that wants to use the command flow feature.

Step 3 - Defining the IA resources to CICS

Before defining your resources to CICS make sure that the GRPLIST you have selected is defined in your GRPLIST SIT parameter for the required CICS region.

To define the main CICS resources that are required by CICS IA.: Review and submit the sample job CIUJCINT in hlq.SCIUSAMP.CICS. This job is configured to include all the resources that are required to be defined, based on your selections, when you run the configuration exec. For example, if you chose to use LIBRARY names. These definitions are included. This job also defines the resources that are required for NLS support. The CSD and group names that are selected in the configuration exec are used. This job completse with a return code of 4 which is acceptable.

To define the VSAM file resources that are required by CICS IA.

If you are using a single CICS region or VSAM RLS to share the files, review and submit the sample job CIUJCFIL in hlq.SCIUSAMP.CICS. If you are using an FOR to share the files, then review and submit the following jobs:

hlq.SCIUSAMP.CICS(CIUJCFIL) to define the CICS file resources locally or in a file-owning region. This job completes with a return code of 0.
hlq.SCIUSAMP.CICS(CIUJCFIR) to define the CICS file resources as remote to a file-owning region. This job completes with a return code of 0.

To define the web service resources that are required by CICS IA.: Review and submit the job CIUJCWEB in hlq.SCIUSAMP.CICS. This job completes with a return code of 0.

Step 4 - Defining the DB2 resources

If you want to collect DB2 resource information in your target CICS region, you must follow these steps:

To define the DB2 indexes for the SYSIBM tables: Review and submit the sample job CIUDBCT in hlq.SCIUSAMP.CICS. This job completes with a return code of 0.

To bind and package the DB2 plans that are required for DB2 collection

Review and submit the sample job CIUDBNT in hlq.SCIUSAMP.CICS. This job completes with a return code of 0.

Note:

If you select to configure CICS IA to collect DB2 resources, the DB2 resources for DB2TRAN and DB2ENTRY are defined in Step 4 - Defining the DB2 resources.
On any region where you want to collect DB2 data, ensure that the user ID under which CICS IA runs has GRANT permission to the batch plan created in the sample job SCIUSAMP.CICS(CIUDBNT). This permission enables the background transaction CINB to access the SYSIBM.SYSDUMMY1, SYSIBM.SYSPACKSTMT, and SYSIBM.SYSSTMT DB2 tables.

Step 5 - Tailoring your CICS startup job

To enable CICS IA to run in your CICS region, tailor your CICS startup JCL as follows:

Set the ICVR system initialization parameter to a minimum of 10 seconds; that is, ICVR=10000 or a larger value. If you do not set this, the Collector, or one of your own transactions, might end prematurely with an abend code of AICA.
If you use VSAM RLS to share the dependency data file and control record file across multiple regions, specify the system initialization parameter RLS=YES.
If you did not select to use the LIBRARY definitions or the CICS region is CICS TS V3.2 or earlier, you must add the following load libraries to the DFHRPL concatenation in the startup job JCL:
- hlq.SCIULOAD.
- hlq.SCIULODE (the default, English, national language: always required).
- Add hlq.SCIULODJ (if you require Japanese national language support)
Add the following DD statement for the CINT transient data message log:
```
//CIULOG DD SYSOUT=*
```
If this is a CICS IA Controlling Region and you are installing the web services resources, you require the following SIT options:
- TCPIP=YES
- SEC=YES
The TCPIPSERVICE resource definition contains the AUTHENTICATE(BASIC) parameter. HTTP Basic authentication is used to obtain a user ID and password from the plug-in. Basic authentication requires the SEC system initialization parameter to be set to YES. If SEC is set to NO, then the TCPIPSERVICE resource with BASIC authentication cannot be installed in the region. If you do not want to use this type of authentication, define AUTHENTICATE(NO) in the CIUDEFW sample file in hlq.SCIUSAMP.CICS before the CIUJCWEB job is run. However, if you use AUTHENTICATE(NO), you can work from the plug-in only as the CICS default user.

For more information about configuring TCP/IP, see Configuring support for communicating over a TCP/IP network in the CICS Transaction Server Knowledge Center.

You can now recycle the CICS region.
Check the web service installation results.
When the controlling region is started, after the successful completion of the CIUJCWEB job, you can check the resource definitions by using the CEMT INQUIRE PIPELINE and CEMT INQUIRE TCPIPSERVICE commands. If the resource installation was successful, you can now use the web service. If you experience any problems, check the results of the CIUJCWEB job and the resource definition details. Also, check that the WEBSERVICE and URIMAP resources were created. These resources are created automatically during the PIPELINE resource installation. You can issue the CEMT PERFORM PIPE(CIUWPIPE) SCAN command that re-creates the WEBSERVICE and URIMAP resources from the pipeline definition. The expected response code for this command is NORMAL.