With Release 6 tablesONLINE/CICS takes advantage of the read/write capabilities of VTS to remove tableBASE transaction affinities associated with using CICS MRO within a single LPAR. When first installed tablesONLINE/CICS will use the local TSR for these tables. In order to take advantage of VTS, the tables that control the operation of the tablesONLINE/CICS must be in a VTS-TSR named DK1S. (See Use of temp tables and TS queues.) The following modifications are required.

  1. Rename the TBSOSVTS table to TBSYSVTS.

    During initialization tablesONLINE/CICS 6.0 will look for a table named TBSYSVTS. The presence of this table in the DK1S VTS-TSR indicates that tablesONLINE/CICS is being used with VTS.

    The TBSOSVTS table is installed with tablesONLINE/CICS and can be found in the TBSYSLB library. The renaming of this table to TBSYSVTS will enforce the sharing of the tablesONLINE control tables (TBSYSLB, TBAPPLB, TBACTLB, and TBDICLB) by opening them into the DK1S VTS-TSR rather than the local TSR.

  2. Display the option to Edit the TBSYSVTS table in the Administrator menu.

    The menu option to edit the TBSYSVTS table is hidden from display. Follow the instructions provided in the chapter “Building Applications” of the tablesONLINE/CICS User’s Guide, for editing the TBOLMENU or XXXXMENU table. The entries that make up this menu are identified in the MENU table by the TB ADMIN Screen name. The Select Symbol—VTS row is displayed; change the Display Indicator to Y.

  3. Modify TBSYSVTS.

    The TBSYSVTS table must be modified to indicate into which VTS-TSRs a library’s tables are to be opened. The modification of this table provides a means of using other VTS-TSRs in addition to the default DK1S.

    The delivered defaults are set so that PRODLIB tables are opened into a VTS-TSR names PROD, TESTLIB tables are opened into a VTS-TSR name TEST, and the MAINLIB tables are opened into a VTS-TSR named VTS1, as shown in Figure 39. Obviously, you will need to modify this table to reflect your installation.

    If this table does not indicate which VTS-TSR a library’s tables should be opened into, then the tables will be opened in the DK1S VTS-TSR.
    Figure 39. Edit the TBSYSVTS table
    Edit the TBSYSVTS table
  4. Ensure the VTS-TSR DK1S is initialized.

    During tablesONLINE/CICS initialization, if the TBSYSVTS table is found and the DK1S VTS-TSR is not up, you will receive an error message indicating that the DK1S VTS-TSR needs to be started before launching tablesONLINE/CICS. For more information on initializing a VTS-TSR, please see the tableBASE Installation Guide and the sample JCL shown in Figure 40.

    Figure 40. Sample JCL code for initializing the DK1S VTS-TSR
    Sample JCL code for initializing the DK1S VTS-TSR

    Although other VTS-TSRs may be used with tablesONLINE CICS (as indicated in the TBSYSVTS table), DK1S must always be present during tablesONLINE/CICS initialization.

  5. The region must be terminated and reinitiated.

    This will cause the tablesONLINE control tables (TBSYSLB, TBAPPLB, TBACTLB, and TBDICLB) to be loaded into DK1S where they can then be shared among regions in the LPAR. The TBSYSVTS table will indicate which VTS-TSR other tables should be opened in, as shown in Figure 39.