This appendix provides instructions for running the installation and service EXECs listed below.
The installation EXECs are:
Installs DB2 RXSQL on minidisks or in SFS directories.
Calls ELOLKED EXEC to link-edit DB2 RXSQL.
Loads the DB2 RXSQL package into a DB2 Server for VM or non-DB2 Server for VM application server.
Installs DB2 RXSQL secondary-level HELP tables in a DB2 Server for VM application server.
Link-edits DB2 RXSQL.
The service EXECs are:
The |I5697ELO EXEC installs DB2 RXSQL on minidisks or in SFS directories. It does not format the minidisks on which it is installing DB2 RXSQL. You must ensure that the minidisks can be written to.
Before running the |I5697ELO EXEC, ensure that:
If DB2 RXSQL and DB2 are installed on separate minidisks, you need four free addresses. Otherwise, you need two free addresses.
For information on these files, refer to Figure 9.
Before running the |I5697ELO EXEC, ensure that you have access to the following disks:
>>-I5697ELO---------------------------------------------------->< |
When you run the |I5697ELO EXEC, you must decide whether DB2 RXSQL is to be installed on separate disks or on DB2 Server for VM disks. If you are installing DB2 RXSQL on DB2 Server for VM disks, refer to "Installing DB2 RXSQL on DB2 Server for VM Minidisks or SFS Directories". If not, refer to "Installing DB2 RXSQL on Separate Minidisks or SFS Directories".
If you are installing DB2 RXSQL on DB2 Server for VM disks, you are prompted to specify whether the DB2 Server for VM files reside on minidisks or in SFS directories.
The EXEC then displays the following defaults for the DB2 Server for VM production minidisk or SFS directory.
For minidisks the defaults are:
For SFS directories the defaults are:
You must either accept these default values or supply different values.
The EXEC then displays the following defaults for the DB2 Server for VM service minidisk or SFS directory.
For minidisks the defaults are:
For SFS directories the defaults are:
You must either accept the default values or supply different values.
The DB2 Server for VM production and service disks are then accessed with write access, and the DB2 RXSQL files loaded on the DB2 Server for VM disks.
The |I5697ELO EXEC calls ELOLKED EXEC to do the system link-edit.
A message with a return code of 888 displays when processing is completed. The DB2 RXSQL distribution tape is positioned at the tape mark following the end of the last DB2 RXSQL file on the tape (file 4).
If you are installing DB2 RXSQL on separate disks, you are prompted to specify whether the installation is on minidisks or in SFS directories, and whether the DB2 Server for VM system is installed on minidisks or in SFS directories.
The EXEC then displays the following defaults for the DB2 RXSQL production minidisk or SFS directory.
For minidisks the defaults are:
For SFS directories the defaults are:
You must either accept the default values or supply different values.
The EXEC then displays the following defaults for the DB2 RXSQL service minidisk or SFS directory.
For minidisks the defaults are:
For SFS directories the defaults are:
You must either accept the default values or supply different values.
The EXEC then displays the following defaults for the DB2 Server for VM production minidisk or SFS directory.
For minidisks the defaults are:
For SFS directories the defaults are:
You must either accept the default values or supply different values.
The EXEC then displays the following defaults for the DB2 Server for VM service minidisk or SFS directory.
For minidisks the defaults are:
For SFS directories the defaults are:
You must either accept the default values or supply different values.
The DB2 RXSQL production and service minidisks or SFS directories are then accessed with write access, and the DB2 Server for VM production and service minidisks or SFS directories are accessed with read-only access. The DB2 RXSQL files are also loaded on the DB2 RXSQL production and service disks.
The |I5697ELO EXEC calls the ELOLKED EXEC to do the system link-edit.
A message with a return code of 888 displays when processing is completed. The DB2 RXSQL distribution tape is positioned at the tape mark following the end of the last DB2 RXSQL file on the tape (file 4).
|If the I5697ELO EXEC is not successful:
An error message identifies the problem. Correct the error and rerun the |I5697ELO EXEC.
| Note: | The error message output is spooled to the printer. |
The ELOAMOD EXEC loads the DB2 RXSQL package into a DB2 Server for VM or non-DB2 Server for VM application server. The DB2 RXSQL package has been preprocessed with the blocking option.
To run the ELOAMOD EXEC, you must have:
SQLINIT DBNAME(server_name)
If you are loading DB2 RXSQL into the default DB2 Server for VM application server, the server_name is SQLDBA.
To run the ELOAMOD EXEC, you must have:
>>-EXEC ELOAMOD----+--------------------------+----------------->
'-CONnect(SQLDBA/password)-'
>-----+-------------------+------------------------------------><
'-SQLDS(-+-Yes-+--)-'
'-No--'
|
This option is valid only when you are loading the DB2 RXSQL package into a DB2 Server for VM application server and are not using the DRDA protocol.
This option is useful when you are including several ELOAMOD invocations in an EXEC.
| Note: | SQLDS(YES) should be specified if loading the RXSQL package into a DB2 Server for VSE application server. The DRDA protocol must still be used even when loading RXSQL into a DB2 Server for VSE application server. |
If you are loading the DB2 RXSQL package into a non-DB2 application server, you must have DBA authority and the ability to use the DRDA protocol.
If you are loading the DB2 RXSQL package into a DB2 application server, and DRDA protocol is being used, you are prompted to specify whether or not you want to continue. If you want to continue the installation using the DRDA protocol, you must have DBA authority.
ELOAMOD does the following:
The following message is displayed when the package is successfully loaded into the application server.
+--------------------------------------------------------------------------------+ |PORTABLE PACKAGE RELOAD completed successfully. | +--------------------------------------------------------------------------------+
If the ELOAMOD EXEC is not successful:
An error message identifies the problem. Correct the error and rerun the ELOAMOD EXEC.
| Note: | The error message output is spooled to the printer. |
The ELOHLPLD EXEC installs DB2 RXSQL secondary-level HELP tables into the DB2 application server. Secondary-level HELP is not supported on non-DB2 application servers, or when using the DRDA protocol.
Before running the ELOHLPLD EXEC, ensure that you have the following:
SQLINIT DBNAME(SQLDBA)
To run the ELOHLPLD EXEC, you must have:
>>-EXEC ELOHLPLD----+--------------------------+---------------><
'-CONnect(SQLDBA/password)-'
|
ELOHLPLD does the following:
The ELOHELPI EXEC does the following:
The following message is displayed when the HELP tables are successfully installed in the application server:
+--------------------------------------------------------------------------------+ |SECONDARY LEVEL TABLES installed successfully. | +--------------------------------------------------------------------------------+
If the ELOHLPLD EXEC is not successful:
An error message identifies the problem. Correct the error and rerun the ELOHLPLD EXEC.
| Note: | The error message output is spooled to the printer. |
The ELOLKED EXEC link-edits DB2 RXSQL and creates the following files on the DB2 RXSQL production disk:
You can invoke this EXEC directly from CMS. It is also called from the I5688ELO EXEC, the ELOSCOR EXEC, and the preventive service EXECs.
To run the ELOLKED EXEC, you must have:
For information on these files, refer to Figure 9.
To run the ELOLKED EXEC, you must have:
This syntax is valid if used from CMS.
>>-ELOLKED----+--------------------------------+---------------><
'-file_mode_1--+--------------+--'
'-file_mode_2--'
|
is V.
The ELOLKED EXEC link-edits DB2 RXSQL.
If DB2 RXSQL was installed separately from the DB2 Server for VM files, you must link and access the DB2 RXSQL disks. If DB2 RXSQL was installed with the DB2 Server for VM files, it is unnecessary to link and access the DB2 RXSQL disks. You only have to link and access the DB2 Server for VM disks in write mode.
To perform a DB2 RXSQL system link-edit, do the following:
ELOLKED file_mode_1 file_mode_2
The following message is displayed when the link-edit is successfully completed:
+--------------------------------------------------------------------------------+ |DB2 RXSQL link-edit has been performed successfully. | +--------------------------------------------------------------------------------+
| Note: | The RXSQL MODULE, EXECSQL MODULE, and RXSQL LOADLIB files are created by this EXEC. |
If the ELOLKED EXEC is not successful:
An error message identifies the problem. Correct the error and rerun the ELOLKED EXEC.
| Note: | The error message output is spooled to the printer. |
This EXEC is supplied with DB2 RXSQL and resides on the service disk. It applies the service based on the contents of the corrective service tape. It does not use service files for other IBM products, but leaves them on the MAINT work minidisk.
To run the ELOSCOR EXEC, you must have:
>>-ELOSCOR----------------------------------------------------->< |
The ELOSCOR EXEC determines whether a link-edit is necessary. If it is, the ELOSCOR EXEC calls the ELOLKED EXEC. The appropriate link-edits are done and the MODULE and LOADLIB files on the DB2 RXSQL production disk are replaced. For information on the prerequisites and authorization required to run the ELOLKED EXEC, refer to "The ELOLKED EXEC".
If the package has been serviced, the ELOSCOR EXEC issues a message indicating that the DB2 RXSQL package must be reloaded. You must reload this package into each application server into which DB2 RXSQL was installed. For information on loading the DB2 RXSQL package, refer to "The ELOAMOD EXEC".
The ELOSHLP EXEC services the DB2 RXSQL secondary-level HELP tables. It services the AMENG HELP text as well as any national language support language that was installed. It is not supported for non-DB2 application servers, or when using the DRDA protocol.
To run the ELOSHLP EXEC, you must have:
SQLINIT DBNAME(SQLDBA)
To run the ELOSHLP EXEC, you must have:
>>-EXEC ELOSHLP----+------------------+------------------------->
'-LANGkey(langkey)-'
>-----+--------------------------+-----------------------------><
'-CONnect(SQLDBA/password)-'
|
ELOSHLP does the following:
The following message is displayed when the HELP tables are serviced successfully:
+--------------------------------------------------------------------------------+ |SECONDARY LEVEL HELP TABLES serviced successfully. | +--------------------------------------------------------------------------------+
If the ELOSHLP EXEC is not successful:
An error message identifies the problem. If the error occurred during DBS Utility processing, check the console listing for more details. Correct the error and rerun the ELOSHLP EXEC. The LASTING GLOBALV file contains the point at which the service EXEC had an error. Do not modify or delete this file. The temporary files ELO$TXT1 MACRO A and ELO$TXT2 MACRO A may have been created on your A disk. Do not modify or delete them. They will be used when you invoke the ELOSHLP EXEC again to complete the service.
| Note: | The error message output is spooled to the printer. |