If the module TBDKUSID of prior releases has never been customized skip this step and go to Step 2—Customize CICS startup JCL.
If, in a previous release of tablesONLINE/CICS, you have modified the module TBDKUSID, this modification needs to be reflected in the load module supplied with the current version.
If you are upgrading from tablesONLINE Release 5.1, copy the existing Release 5.1 TBDKUSID into the load library for the current version, replacing the delivered version. If you are upgrading from a release earlier than 5.1; the recommended choice is to then reapply your changes to the new source version of TBDKUSID supplied with the current version. Recompile and relink it for use, replacing the TBDKUSID load module supplied with the delivered version.
TBDKUSID will be executed according to the SECURITY IO IND field in the Constants table. Set SECURITY IO IND field as shown in Table 2.
| I |
TBDKUSID to be executed at system startup. |
| O |
TBDKUSID to be executed at system exit. |
| Y |
TBDKUSID to be executed at both system startup and exit. |
If you wish to continue using your old version of TBDKUSID, change the SECURITYPGM VERSION field in the TBOLCNST table from 6 to 4 for Release 4.2, or 5 for Release 5.0.1. Save the changes.
To edit TBOLCNST, select option 9 (edit constants), on the tablesONLINE Administrator menu. Then replace the TBDKUSID load module supplied with the delivered version with your Release 4.0 or 5.0 version of TBDKUSID (that is, first change TBOLCNST, then replace TBDKUSID).