TBOPT dataset coding

The TBOPT dataset can be a sequential file, a member of a data set, or, for CICS, a VSAM dataset. The TBOPT dataset can be specified for all interfaces, including VTS. The dataset must contain fixed-length 80-byte records.

The TBOPTV functionality has been integrated into TBOPT, allowing for a single source of run-time parameter input. TBOPTV is still maintained for backwards compatibility. If both TBOPT and TBOPTV are used, TBOPT is read first. If a keyword is present in both TBOPT and TBOPTV, initialization will fail with return code 200.

The data in TBOPT uses the same parameter names and values as are coded on the TBOPTGEN macro for the defaults, with the exception of LIB-LIST. TBOPT uses LIBnn to specify tableBASE libraries to update the tableBASE Library List.

Each parameter is entered on a single line in the dataset. The parameter may begin in any column. A line beginning with an asterisk (*) denotes a comment. Comments may also be added after the parameter value. A semicolon may be used to indicate line end. Comments may follow the semi-colon.

Although each region may have defined its own TBOPT dataset, all regions can share a sequential DASD dataset, and CICS regions can share a VSAM TBOPT dataset.

Starting with Version 7, some parameters can only be coded in TBOPTGEN, for security reasons.

A sample TBOPT dataset for a batch region follows:

Figure 125. Sample TBOPT
Sample TBOPT

  1. ListOptions=Y is handy for diagnostic purposes; TESTLIB is first for batch testing.
  2. With the exception of the LISTOPTIONS parameter, parameters must appear only once in the TBOPT file. The form KEYWORD=* indicates that the site default is to be used. The form KEYWORD=0 indicates that the default value of a parameter that takes a character string be nullified.