Pre-installation and Maintenance Requirements

Before you install the ADABAS Interface, you should be aware of installation prerequisites and consider maintenance procedures that affect the installation process. This section describes pre-installation and maintenance requirements. They apply to both MVS and CMS, except where noted.

The instructions in this appendix assume that the person performing the installation and maintenance procedures has a working knowledge of MVS or CMS. If you are installing the ADABAS Interface with the FOCUS Multi-Session Option (MSO), MSO knowledge is required. Knowledge of FOCUS and ADABAS is not required.

Your ADABAS database administrator should provide you with site-specific information.

Read this appendix thoroughly before installing the ADABAS Interface to ensure correct installation.

Software Requirements

Before you install the ADABAS Interface, review the following list of software requirements:

• ADABAS must be installed and fully operational. If it is not, contact your ADABAS database administrator.
• FOCUS must be installed and fully operational. If it is not, contact your FOCUS database administrator or consult the appropriate FOCUS installation guide for installation instructions.

You also need to know the FOCUS release. There are two ways to identify your release:

• Check the label of the distribution tape used to install FOCUS; the release number is printed on it.
• Start FOCUS if it is already installed. The release is displayed each time you begin a session.

Every copy of FOCUS has a release number.

Memory Requirements

Enough main memory must be available to execute FOCUS, ADABAS, and the ADABAS Interface. The memory needed is approximately 1440K for FOCUS and 300K for the Interface. Refer to the appropriate ADABAS documentation for ADABAS requirements.

The Interface is fully re-entrant and can run in the 31-bit operating environment.

Maintenance

There are no maintenance procedures that you must perform regularly to ensure proper functioning of the ADABAS Interface. However, the following two situations require maintenance:

• If you install a new release of FOCUS, you must also reinstall the ADABAS Interface from the same release.
• If you receive a program temporary fix (PTF) that affects the ADABAS Interface, it will be accompanied by a cover letter containing installation instructions. If you still have installation questions after reading the cover letter, contact Information Builders Customer Support Services (CSS) in New York at (800) 736-6130 or (212) 736-6130, or your local Information Builders representative.

Using the DDCARD ddname to Specify Site Defaults

ADABAS supports the use of the DDCARD ddname to specify site or session defaults for ADABAS, including the default database number, mode (multiple vs. single user), and other parameters.

If you choose a Supervisor Call (SVC) number or database number other than the default, you must allocate the DDCARD ddname to the ADARUN parameter file in your FOCUS CLIST or batch JCL for MVS. Your ADABAS database administrator can provide the name of the ADARUN parameter file for your site.

In this appendix, examples refer to the ADARUN parameter file as follows:

SOFTWARE.AG.ADARUN

In MVS/TSO, batch, and CMS, the ADABAS Interface recognizes this DDCARD ddname and, if allocated, respects the specified defaults.

Note: If the database number is specified with the DBNO attribute in an Access File, the Interface uses the specified number for the ADABAS call. If an Access File does not contain a value for the DBNO attribute, the Interface uses the default specified in the DDCARD ddname. If the DDCARD ddname is not allocated, the Interface uses the default DBNO of 0. Therefore, the order of the DBNO selection is:

1. Access File

2. DDCARD ddname

3. Default of DBNO=0

For more information on the DDCARD ddname, consult your Software AG documentation.

Note: MSO does not support the use of the DDCARD ddname. The SVC number is contained in the ADABAS load library module ADALNK. During installation of the ADABAS Interface, the SVC number is placed in the FADALINK load module, from which it is read. See the section on executing the ADABAS Interface under MSO in Getting Started, for more information.