Step 1: Define Program, Transaction, and Library Entries

Starting Your Product › How to Configure Without CA CSM › Update the CICS Tables (INST0060) › Step 1: Define Program, Transaction, and Library Entries

Step 1: Define Program, Transaction, and Library Entries

Update the CICS tables to define program and transaction entries.

Before you begin defining program and transaction entries, check that the following assigned values meet your site requirements:

Input statements to the CICS system definition file utility program DFHCSDUP:
```
sysview.CNM4BSAM(CICSCSD)
```
Sample JCL for the system definition file utility program provided in member CSDUTIL of SAMPLIB (after job INST0110 is executed, which involves copying installation members to a sample library).

To define program and transaction entries

Modify the INST0060 member in the sysview.SAMPJCL data set to the standards of your site.
Submit the member INST0060.
When the job ends with a condition code of 0, the following CICS transactions have been defined:

Transaction	Use
GSVS	Starts the CICS Data Collector manually. This transaction requires the CA SYSVIEW Option for CICS.
GSVT	Terminates the CICS Data Collector manually. This transaction requires the CA SYSVIEW Option for CICS.
GSVI	Identifies the CICS Data Collector that uses this transaction as an internal transaction to the function requests. The transaction cannot be executed directly. It is started internally by the GSVS transaction. This transaction requires the CA SYSVIEW Option for CICS.
SYSV	Identifies the CA SYSVIEW online interface. This transaction does not require the CA SYSVIEW Option for CICS.

Note: For more information about the CICS system definition file utility program, see the IBM CICS Resource Definition Guide or the IBM CICS Operations and Utilities Guide.