This chapter outlines the prerequisites for installing RXSQL on either CMS minidisks or in CMS Shared File System directories (SFS directories). It also gives a brief description of the installation process, explains the DB2 RXSQL machine-readable material, and details the VM storage requirements.
The following are the hardware and software requirements for running DB2 RXSQL.
RXSQL requires the following hardware:
DB2 RXSQL requires the following software:
|It is assumed that the DB2 Server for VM relational database manager |Version 7 Release 1 is installed using the defaults |mentioned in this manual. If this is not the situation, you must |substitute the values that your site used to install the DB2 Server for VM |system for the defaults in this manual.
The DB2 RXSQL and DB2 products do not support mixed CP and CMS releases, as supported by VM/ESA.
In this manual, the VM/ESA environment will refer to |VM/ESA Version 2 Release 3 or later. The term VM will be used to refer to the VM/ESA environment, unless there is a specific reference to a particular release.
The VM/ESA environment supports the installation of DB2 RXSQL on CMS minidisks and SFS directories.
The DB2 Server for VM system must be installed and operational before DB2 RXSQL can be installed. The recommended installation procedures for the DB2 system create:
If the DB2 system is installed on minidisks:
If the DB2 system is installed in SFS directories:
The DB2 RXSQL files are installed on production and service minidisks or in production and service SFS directories. All users must be linked to the RXSQL production minidisk or SFS directory for all DB2 RXSQL operations but the RXSQL service minidisk or SFS directory is only required for service activities or installation. The RXSQL production and service disks must be owned by the same user ID.
DB2 RXSQL consists of two modules:
DB2 RXSQL also includes a DB2 RXSQL LOADLIB, which is loaded as a CMS nucleus extension.
The term disk will refer to both minidisks and SFS directories for the remainder of this manual.
You can install DB2 RXSQL files on the same disks that the DB2 Server for VM files, or other product files, are on. However, production files should be stored separately from service files. For example, you should not install DB2 RXSQL production files on the disk where DB2 Server for VM service files reside.
To install DB2 RXSQL files on disks, you require three virtual machines and their associated user IDs. In this manual, our suggested installation uses the MAINT, SQLUSER, and SQLMACH user IDs, but you can use any equivalent machine identifier (user ID).
The MAINT user ID is used to attach tapes, link the disks in write mode on which DB2 RXSQL files will be loaded, link the DB2 Server for VM disks, and issue VMFPLC2 commands. If you do not use the MAINT user ID, you must obtain a user ID with which you can perform these functions.
The SQLMACH user ID is the DB2 Server for VM database machine. In this manual, the SQLMACH user ID owns the DB2 RXSQL disks. If your installation does not use SQLMACH, substitute the name of your DB2 Server for VM database machine where SQLMACH is used.
The name of the database that is generated during the installation of the DB2 system is SQLDBA. SQLDBA is also the name of the application server in which the database is generated. In this manual, SQLDBA is the name of the application server in which DB2 RXSQL is installed if you are installing DB2 RXSQL into a DB2 application server. If your installation does not use the SQLDBA application server, substitute the name of your DB2 application server where SQLDBA is used.
The SQLUSER user ID is the DB2 Server for VM user machine. It is used to link the production and service files in read mode and to load the RXSQL package into the application server. If your installation does not use SQLUSER, substitute the name of your DB2 Server for VM user machine where SQLUSER is used.
The remainder of this section describes the four phases necessary for installation. The first two phases are done once. The next two are repeated for each application server into which RXSQL will be installed. The fourth phase is optional.
Before installing DB2 RXSQL, you must set up the disks and ensure there is enough free space for one of the following situations:
Free space on the work disks of the user ID that will be used to do the installation in VM (MAINT) and the user ID that will install the DB2 RXSQL package into the application servers (SQLUSER) is also required.
In this phase, DB2 RXSQL is installed in a VM environment. The product load library and the product module are also created on the DB2 RXSQL production minidisk or in the DB2 RXSQL production SFS directory.
When DB2 RXSQL is installed in a VM/ESA environment, the installation EXEC issues a prompt asking whether you want to install DB2 RXSQL on minidisks or in SFS directories.
If you are installing on the DB2 minidisks and the DB2 Server for VM database machine is running, you must shut down the database during this phase because you need exclusive write access. If you are not installing on DB2 Server for VM minidisks, it is not necessary to bring down the database.
This activity is done for each DB2 Server for VM application server in which DB2 RXSQL will be made available. The DB2 Server for VM database machine must be started before you can install the DB2 RXSQL package into an application server.
An authorization ID called SQLDBA that has DBA authority must exist on the DB2 Server for VM application server into which you are installing RXSQL.
The following is installed in each application server:
Space is required in each application server for one DB2 RXSQL package. The installation process loads this package into an available public dbspace that has been reserved for packages.
| Note: | You do not install HELP tables (and do not, therefore, have to acquire a dbspace) if you are upgrading to DB2 RXSQL Version 7 Release 1 and have an earlier version of the HELP tables in the application server. Instead, you must run the ELOSHLP EXEC to update your help files. See "The ELOSHLP EXEC" for more information. |
In each application server in which you install DB2 RXSQL HELP tables, you should add or make available a dbspace with the following characteristics:
A manual verification procedure is part of this phase. It verifies the installation of DB2 RXSQL by testing some of its functions.
To do this step, your DB2 Server for VM installation must have the ability to use the Distributed Relational Database Architecture(TM) (DRDA(R)) protocol, and you must have DBA authority.
In this phase, you load the DB2 RXSQL package into each non-DB2 Server for VM application server in which DB2 RXSQL is to be installed. This phase must be repeated for each application server in which DB2 RXSQL is to be available. The DBS Utility package must be installed before installing DB2 RXSQL in a non-DB2 Server for VM application server.
The following is installed in each application server:
Space is required in each application server for one DB2 RXSQL package.
| Note: | The RXSQL HELP tables are not supported for non-DB2 Server for VM application servers. |
The DB2 RXSQL machine-readable material is provided on magnetic tape (reel or cartridge).
DB2 RXSQL can be ordered on its own distribution tape or on a tape that contains other products. In this manual, DB2 RXSQL tape files are referred to as tape file 1, tape file 2, and so on, and correspond to the sequence of DB2 RXSQL files on the distribution tape.
| Note: | Do not change the CMS files supplied by IBM on the DB2 RXSQL production or
service disks. They may be replaced by service updates.
More information on enabling an NLS Language for REXX can be found on Chapter 3, Installing a REXX SQL NLS Language. |
Runtime DB2 RXSQL requires at least 500K (K is 1024 bytes) of storage.
The following disks are required for DB2 RXSQL:
The DB2 RXSQL production disk must be available for all DB2 RXSQL operations during installation.
The DB2 RXSQL service disk is not required for normal DB2 RXSQL processing. The service disk must, however, be available for service activities or installation.
Both production and service disks must be owned by the same virtual machine.
This virtual machine exists in all VM environments. It is used to load information from the DB2 RXSQL distribution tape, including the EXECs supplied by IBM, to the work disk of the MAINT machine during installation.
The following information details the minidisk requirements for installing RXSQL on the MAINT machine:
The minidisk block size is 4096 bytes, unless otherwise stated.
Figure 1. MAINT Machine Minidisk Free-Space Requirements for Installation
| Minidisk | Virtual Address | Access Mode | 3350 Cylinders | 3375 Cylinders | 3380 Cylinders | 3390 Cylinders | 9345 Cylinders | FB-512 Blocks |
|---|---|---|---|---|---|---|---|---|
| MAINT machine: Work minidisk for installation | 194 or 191 | A or C | 4 | 5 | 3 | 3 | 4 | 3600 |
This virtual machine or its equivalent is in all VM environments that have the DB2 Server for VM relational database manager installed. SQLMACH is used to identify the DB2 Server for VM database machine that owns:
The following information describes the free space requirements for installing DB2 RXSQL production and service files.
If you are installing RXSQL on the same minidisks or SFS directories as are used for the DB2 Server for VM files, there must be free space for the DB2 RXSQL files on the disks. Figure 2 and Figure 3 show the amount of free space that is required. You can then refer to SQLUSER Machine to continue reading about DB2 RXSQL VM requirements.
If you are installing DB2 RXSQL on minidisks or SFS directories other than those used for the DB2 Server for VM files, you must modify the SQLMACH VM directory entries for minidisk installation, or use the MODIFY USER command for SFS installation. Figure 2 and Figure 3 show the amount of free space that needs to be defined.
Figure 2. Minimum Requirements for DB2 RXSQL SQLMACH Machine Minidisks
| Minidisks | Virtual Address | 3350 Cylinders | 3375 Cylinders | 3380 Cylinders | 3390 Cylinders | 9345 Cylinders | FB-512 Blocks |
|---|---|---|---|---|---|---|---|
| SQLMACH machine: Production minidisk | 198 | 3 | 4 | 2 | 2 | 2 | 2400 |
| SQLMACH machine: Service minidisk | 199 | 8 | 9 | 6 | 5 | 6 | 7500 |
Figure 3. Minimum Requirements for DB2 RXSQL SQLMACH Machine SFS Directories
| SFS Directories | Directory Name | 4K Blocks |
|---|---|---|
| SQLMACH machine: Production SFS directory | VMSYS:SQLMACH.RXSQL.PRODUCTION | 300 |
| SQLMACH machine: Service SFS directory | VMSYS:SQLMACH.RXSQL.SERVICE | 1000 |
This virtual machine or its equivalent exists in all VM environments that have the DB2 relational database manager installed. It is used to install the DB2 RXSQL package into application servers and to verify DB2 RXSQL installation.
If you are installing DB2 RXSQL on minidisks other than those used for the DB2 Server for VM files, the SQLUSER VM directory entries may be updated to automatically link the DB2 RXSQL minidisks to SQLUSER.
The free space requirements for installing RXSQL on the SQLUSER disk are shown in Figure 4 and Figure 5.
The SQLUSER machine needs read/write access to a minidisk with free space equal to at least 1 cylinder of an IBM 3380 storage device, or read/write authority to an SFS directory with free space equal to at least 150 blocks.
Figure 4. SQLUSER Machine Minidisk Free-Space Requirements for Installation
Minidisk
Virtual Address
Access Mode
3350 Cylinders
3375 Cylinders
3380 Cylinders
3390 Cylinders
9345 Cylinders
FB-512 Blocks
Block Size
SQLUSER machine: Work minidisk for installation
191
A
1
1
1
1
1
930
1024
Figure 5. SQLUSER Machine SFS Directory Free-Space Requirements for Installation
| SFS Directory | Directory Name | Access Mode | 4K Blocks |
|---|---|---|---|
| SQLUSER machine: Work SFS directory for installation | VMSYSU:SQLUSER | A | 150 |