Step 1: Prepare for tableBASE installation

Installation overview

Here is an overview of the tableBASE installation process:

1. You will copy datasets from a CD, FTP site (or email).
2. For each product that you have licensed, you will:
   1. set site-specific system naming-convention defaults for:
      1. load library
      2. tableBASE libraries
      3. sample libraries
      4. VTS-TSR image datasets
   2. tailor the product by performing some assemblies, link-edits, and moving of datasets
   3. run a test procedure to verify successful installation
   4. update your user documentation to reflect local naming-convention defaults

Recommended preparations

Before starting the installation process, consider the following:

• Dataset usage — Most of the datasets on the distribution media are for access by all of your users, (load modules would fall into this category). However, some datasets are for use only by the system installer or system administrator. The following sections outline the various uses for the datasets that will be installed. Be aware that the distribution media does not segregate them, for example, all JCL procedures are in one dataset. Therefore, if you want to prevent or limit access to any of these datasets, you may choose to place certain members on different libraries, perhaps with different levels of access.
• Dataset naming conventions — You will have to plan your site’s actual naming conventions, taking into account such things as: site standards, RACF (or other) access rules, and required DASD and VSAM volume locations.
  Note:

  tableBASE documentation, and any subsequently distributed package refer to the datasets as we have named them for distribution. Thus, the administrator may be asked to apply a fix package to:

  your.prefix.LOAD

  You must be able to identify your equivalent of it in order to apply the fix pack.

  If you are upgrading to a new release you may have already established naming conventions. However, it may still be valuable to consider using a unique naming convention for this release so it can be distinguished from previous releases in your applications.

• DASD volumes—you may have to decide on specific DASD volumes to suit your site standards for installed software.
• Authority considerations (for example, RACF)—you may also need to control user access to the various tableBASE datasets. Keep in mind that the restrictions on tableBASE libraries do not apply to tables once they are opened in a TSR. tableBASE provides other mechanisms to control access to tables in a TSR. For more information, see the tableBASE Administration Guide.
• Applicability of special notes and restrictions to your site—what are the special features of your site that need to be considered during the installation?

tableBASE Parameters

The installation involves tailoring the tableBASE software for optimal performance in both batch and on-line environments by setting execution-time parameters and switches. The parameters are listed in tableBASE run-time options. Chapters 3 through 11 provide details on which of these apply to a particular tableBASE component.

Default execution-time parameters can be modified by changing the default values or by specifying them at execution time.

To modify the default values for a specific interface, you will need to change the TBOPTGEN values in the appropriate member of the TBASE.SRC dataset, reassemble and relink it. Models for reassembling and relinking are supplied in the TBASE.CNTL data set. Procedures for performing this task are described in the chapters that follow.

At execution time, the default values can be overridden by specifying them in a dataset defined by DDNAME TBOPT. For details on coding the parameters in the TBOPT dataset, see tableBASE run-time options.

Enqueues

Integrity of tableBASE is achieved by issuing enqueue requests. The major enqueue name is TBLBASE. The scope of the enqueues is SYSTEMS.

Modifications to Global Resource Serialization (GRS) PARMLIB controls for your installation must not prevent the propagation of the major enqueue name throughout the complex. Failure to adhere to this can result in the corruption of the datasets on DASD shared between MVS images running tableBASE.

Since these requirements are beyond the scope of the tableBASE software, you must ensure that these conditions are met if the same datasets are to be shared among separate copies of the operating system.

Proceed to Step 2: Obtain installation files from installation media.