Step 4—Create CICS definitions

Part 1: Create CICS definitions for the tablesONLINE transactions and libraries

Create CICS definitions for the tablesONLINE transactions and libraries that will be accessed under CICS.

Member TBOL60 in your.prefix.SRC provides the input to define tablesONLINE to CICS using the CICS resource definition program, DFHCSDUP.

If you are using VSAM libraries, member TBOL60V in your.prefix.SRC provides sample definitions for the tablesONLINE and CICS VSAM libraries.

If you are using BDAM libraries, member DFHFCTOL in your.prefix.SRC provides sample definitions for the tablesONLINE and CICS BDAM libraries.

Note:

If you will be using tablesONLINE in an MRO environment, please see the Notes and restrictions.

Note:

See TWA size for tablesONLINE/CICS transactions for the TWA size to use for the CICS definitions in member TBOL60.

Part 2: Enable mixed case characters (optional)

Perform only if you want mixed case character input.

To enable tablesONLINE transactions to capture mixed case characters when editing tableBASE tables, the tablesONLINE transactions require the setting of UCTRAN to TRANID on the associated CICS terminals.

Terminal LU names and definition methods vary by installation. To assist you, the group DKLUCTRN contains templates for terminal definitions. A sample input to update the CSD using the CICS resource definition program DFHCSDUP is supplied in your.prefix.SRC member DKLUCTRN. You must modify these templates to suit the installation requirements.

Installations that use the auto-install facility of CICS to define terminals must make sure that the auto-install program will use the appropriate model definition. For more information on the CICS auto-install facility, please see IBM’s CICS Resource Definition Guide and CICS Customization Guide.