This appendix provides a summary of the messages that you can receive when installing DB2 RXSQL.
The RXSQL installation and database generation EXECs provide error messages. If more detailed information is required, you are directed to the appropriate documentation.
This section is divided into two parts:
The following error messages may be displayed from any of the RXSQL
installation EXECs:
| CP FORCE command failed to force a logoff of userid. If command still fails after two attempts, check installation USERID class privileges. |
Explanation: The CP FORCE command failed to force a logoff of the owner of the DB2 RXSQL product disk.
System Action: The program ends with the return code of 111 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Ensure the USERID installing the product has class privilege of A or use another USERID that does.
| Error adding ELO message repository. RC = rc from the CMS SET LANGUAGE command. |
Explanation: The CMS SET LANGUAGE command failed while trying to add the DB2 RXSQL message repository.
System Action: The program ends with the return code of 24, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the SET LANGUAGE command.
| Error copying ELOUME TXTAMENG fm to the A disk as ELOUME TXTlang-id. RC = rc from the CMS COPYFILE command. |
Explanation: Your current CMS language is not American English and there is no DB2 RXSQL message repository in your language on the product distribution tape. There is a DB2 RXSQL message repository for American English on the distribution tape; however, the CMS COPYFILE command failed while trying to copy that message repository to your current CMS language.
System Action: The program ends with the return code of 24, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the COPYFILE command.
| Installation problem. ELOLANG EXEC & ELOLANMS EXEC not found. |
Explanation: Neither the ELOLANG EXEC (to load the message repository) nor the ELOLANMS EXEC (to display messages for the ELOLANG EXEC) were found.
System Action: The program ends with the return code of 24, and the user returns to CMS.
User Response: Contact the IBM Support Center.
| Installation problem. ELOLANG EXEC not found. |
Explanation: This message returns by the installation and service EXECs when the EXEC to load the message repository is missing (ELOLANG EXEC).
System Action: The program ends with the return code of 24, and the user returns to CMS.
User Response: Contact the IBM Support Center.
| Installation problem. ELOLANMS EXEC not found. |
Explanation: The EXEC to display messages for the ELOLANG EXEC (ELOLANMS EXEC) was not found.
System Action: The program ends with the return code of 24, and the user returns to CMS.
User Response: Contact the IBM Support Center.
| Neither the lang-id nor the AMENG message repository could be found (ELOUME TXTlang-id and ELOUME TXTAMENG). |
Explanation: The DB2 RXSQL message repository for American English, or for your current CMS language if other than American English, was not found on the DB2 RXSQL distribution tape.
System Action: The program ends with the return code of 24, and the user returns to CMS.
User Response: Contact the IBM Support Center.
| Return code = rcode. The DB2 RXSQL minidisks/directories have been successfully loaded. DB2 RXSQL link-edit has been completed successfully. Continue with the installation process described in the DB2 RXSQL manual. Briefly: Execute ELOAMOD EXEC to load the portable package and ELOHLPLD EXEC or ELOSHLP EXEC to load or migrate the HELP tables into each database where DB2 RXSQL is to be installed. |
Explanation: The installation of DB2 RXSQL has been completed successfully. However, verification of the installation is not yet possible.
System Action: The program ends with the return code of 888 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Continue with the installation process as described in the DB2 RXSQL manual.
| Tape not positioned at the end of the product and tape position is unknown. |
Explanation: An error occurred while positioning the tape and the position of the tape is unknown.
System Action: The program ends with a return code of 18 or 20 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: After verifying that your hardware is working properly and your tape is mounted correctly, re-execute the installation EXEC. If you are using INSTFPP, do not continue installation of other products. The tape position is unknown. Correct the problem and reinstall. If the problem persists, contact the IBM Support Center.
| The AMENG message repository could not be found. |
Explanation: Your current CMS language is American English; however, there is no DB2 RXSQL message repository for American English on the product distribution tape.
System Action: The program ends with the return code of 24, and the user returns to CMS.
User Response: Contact the IBM Support Center.
| The lang-id repository, ELOUME TXTlang-id could not be found. The AMENG repository will be used. |
Explanation: Your current CMS language is not American English and there is no DB2 RXSQL message repository in your language on the product distribution tape. There is, however, an American English message repository on the distribution tape and it will be used.
System Action: The program ends with the return code of 24, and the user returns to CMS.
User Response: If you want to operate DB2 RXSQL in a language other than American English, contact the IBM Support Center to acquire a message repository in your language.
| User requests exit from fn installation EXEC. |
Explanation: The user has requested an exit from the installation EXEC.
System Action: The program ends with the return code of 111, and the user returns to CMS.
User Response: Reexecute the installation EXEC.
The following error messages
may be displayed during the installation of RXSQL:
| ELO8502E | The number of tape files as specified by the Product Identifier File is nonnumeric. |
Explanation: The Product Identifier File (I5697ELO 071012) has nonnumeric characters in the fifth and sixth positions of the file type.
System Action: The program ends with the return code of 12 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Call the IBM Support Center to report the problem.
| ELO8503E | Product Identifier File not found. |
Explanation: The CMS LISTFILE command failed to find the Product Identifier File (I5697ELO 071012) on the work disk.
System Action: The program ends with the return code of 12 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Make sure that the first two tape files of the DB2 RXSQL product tape are loaded to the work disk. Reexecute the installation EXEC. If the problem persists, contact the IBM Support Center.
| ELO8504E | Problem occurred while performing the LISTFILE command on the Product Identifier File. RC =rc from the CMS LISTFILE command. |
Explanation: The LISTFILE command failed while trying to find the Product Identifier File (|I5697ELO 071012).
System Action: The program ends with the return code of 12 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the LISTFILE command. Correct the problem and reexecute the installation EXEC.
| ELO8506E | There is no tape drive available at virtual address 181. Please attach a tape drive as virtual address 181, mount the DB2 RXSQL distribution tape, and reexecute the EXEC I5697ELO. |
Explanation: The CMS QUERY command indicated that no virtual address exists for 181.
System Action: The program ends with the return code of 18 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Attach correct tape to virtual address 181 and reexecute the installation EXEC.
| ELO8507E | Tape scan failed to find the DB2 RXSQL Product Identifier File on the tape. Please mount the correct DB2 RXSQL distribution tape and re-execute the EXEC I5697ELO. |
Explanation: No DB2 RXSQL Product Identifier File (I5697ELO 071012) was found on the tape mounted on virtual address 181.
System Action: The program ends with the return code of 18 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: After verifying that the tape mounted on virtual address 181 is the DB2 RXSQL distribution tape, reexecute |I5697ELO. If the condition persists, contact the IBM Support Center.
| ELO8516E | Error accessing userid cuu as fm. RC = rc from the CMS ACCESS command. |
Explanation: A minidisk could not be accessed.
System Action: The program ends with the return code of 16 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the ACCESS command. Correct the problem and reexecute the installation EXEC.
| ELO8518E | Error linking to userid cuu1 as cuu2 with mode mode. RC = rc from CP LINK command. |
Explanation: A minidisk could not be linked. It is possible that the minidisk does not exist in the CP directory, the minidisk is linked by some other user, or an invalid link password was entered.
System Action: The program ends with the return code of 16 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Consult your CP command reference manual for details on the LINK command. If the minidisk does not exist in your CP directory, then refer to the Feature Program installation section for directory tailoring information. Otherwise, correct the problem and reexecute the installation EXEC.
| ELO8523E | Error loading type minidisk. RC = rc from the CMS VMFPLC2 command. |
Explanation: The minidisk may be full or a tape error has occurred.
System Action: The program ends with the return code of 25 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the VMFPLC2 command. Correct the problem and reexecute the installation EXEC.
| ELO8525E | DB2 RXSQL minidisks or directories have been successfully loaded, but the DB2 RXSQL link-edit completed with error messages. |
Explanation: The DB2 RXSQL disks have been successfully loaded, but the DB2 RXSQL link-edit program returned control to the main program with error messages.
System Action: The |I5697ELO EXEC ends after displaying the error messages from the DB2 RXSQL link-edit program.
User Response: Check the error messages returned from the DB2 RXSQL link-edit, and follow the corrective steps that they outline.
| ELO8527E | The DB2 RXSQL minidisks or SFS directories have not been successfully loaded. DO NOT CONTINUE with the DB2 RXSQL installation process. Please correct the error identified by previous messages and review the installation procedure. Then re-execute the I5697ELO EXEC. Return Code = rcode |
Explanation: The I5697ELO EXEC failed with the return code of 12, 16, 18, 20, 24, 25, 26, 36, 45, or 48.
System Action: The program ends with the return code of 12, 16, 18, 20, 24, 25, 26, 36, 45, or 48 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Correct the error identified by the previous error messages and reexecute the |I5697ELO EXEC.
| ELO8528E | DB2 RXSQL link-edit was unsuccessful. Please correct the problem and do the following to complete the installation: Execute ELOLKED to do the DB2 RXSQL link-edit. Execute ELOAMOD to load the portable package. Execute ELOHLPLD to install secondary level HELP. Return Code = rcode |
Explanation: The DB2 RXSQL disks have been successfully loaded, but the DB2 RXSQL link-edit failed.
System Action: The program ends with the return code of 24, 26, 29, 32, 36, or 48 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Correct the error identified by the previous error message. Reexecute the ELOLKED EXEC and continue the installation steps.
| ELO8529E | Look at the CMS file, ELOLK LKEDIT: - LINK-EDIT successful (if ELOLK LKEDIT contains only IEW0222 messages). - LINK-EDIT unsuccessful (if ELOLK LKEDIT contains error messages other than IEW0222). Return Code = rcode If DB2 RXSQL link-edit is successful then do the following to complete the installation: Execute ELOAMOD to load the portable package. Execute ELOHLPLD to install secondary level HELP. If DB2 RXSQL link-edit is unsuccessful then correct the errors identified in the CMS file ELOLK LKEDIT and do the following to complete the installation: Execute ELOLKED to do the DB2 RXSQL link-edit. Execute ELOAMOD to load the portable package. Execute ELOHLPLD to install secondary level HELP. |
Explanation: The disks have been successfully loaded, but the DB2 RXSQL link-edit completed with warning messages.
System Action: The program ends with the return code of 33 from the |I5697ELO or ELOLKED EXECs, and the user returns to CMS.
User Response: Check the CMS file ELOLK LKEDIT on your work disk. If the file contains only IEW0222 messages, the link-edit was successful. If the file contains other error messages, correct the errors, reexecute the ELOLKED EXEC, and continue the installation steps. If the problem persists, contact the IBM Support Center.
| ELO8530E | Error forwarding over tape file num. RC = rc from the CMS VMFPLC2 FSF command. |
Explanation: An error occurred while forward spacing the tape. There is either a hardware problem or a tape error. The tape position is unknown.
System Action: The program ends with the return code of 20 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: After verifying that your hardware is working properly and your tape is mounted correctly, reexecute the installation EXEC. If the condition persists, call your IBM Customer Service Representative if it is a hardware problem, or contact the IBM Support Center if you suspect the problem is with the tape.
| ELO8536E | ELOHLPLD EXEC invoked with invalid parameters. To install secondary level HELP refer to the section in the DB2 RXSQL manual that describes the ELOHLPLD EXEC and execute the EXEC with correct parameters. |
Explanation: The ELOHLPLD EXEC was not invoked with valid parameters.
System Action: The program ends with the return code of 27 from the ELOHLPLD EXEC, and the user returns to CMS.
User Response: Correct the problem and reexecute the ELOHLPLD EXEC with valid parameters. For information on the ELOHLPLD EXEC, refer to The ELOHLPLD EXEC.
| ELO8537E | Error connecting to the default database. Database is not available or the connect password for SQLDBA is incorrect. Return Code = rcode |
Explanation: The error may have been caused by one of the following:
System Action: The program ends with the return code of 31 from the ELOHLPLD EXEC, and the user returns to CMS.
User Response: Correct the error and reexecute the ELOHLPLD EXEC.
| ELO8538E | Either ELOHELPI EXEC is missing or a DBSU error occurred while installing HELP tables into the database. Return Code = rcode |
Explanation: The ELOHELPI EXEC was not found or a DBS Utility error occurred while:
System Action: The program ends with the return code of 31 from the ELOHLPLD EXEC, and the user returns to CMS.
User Response: Correct the problem and reexecute the ELOHLPLD EXEC. You may have to drop the PUBLIC.RXSQLHELP dbspace before reexecuting ELOHLPLD.
| ELO8539E | This VM execution environment is not supported by this release of DB2 RXSQL. |
Explanation: Incorrect VM level. DB2 RXSQL 7.1.0 supports only VM/ESA Release 2.3 and later.
System Action: The program ends with the return code of 36, and the user returns to CMS.
User Response: Correct the problem and reexecute the installation EXEC. If the problem continues, contact the IBM Support Center.
| ELO8540E | DB2 Server for VM level level is not supported by this release of RXSQL. |
Explanation: DB2 RXSQL does not support the indicated DB2 Server for VM level.
System Action: The program ends with the return code of 48, and the user returns to CMS.
User Response: Contact the IBM Support Center.
| ELO8541E | File RXSQL TEXT fm not found, or RXSQL SERVICE minidisk or directory is not accessed as fm. |
Explanation: The CMS STATE command failed to find the RXSQL TEXT file on the minidisk or directory accessed as the file mode.
System Action: The program ends with the return code of 32 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the STATE command, or make sure that you are accessing the correct minidisk or directory. Correct the problem and reexecute the ELOLKED EXEC.
| ELO8542E | Error while generating RXSQL MODULE. |
Explanation: The RXSQL MODULE could not be generated or the production disk is not accessed as read/write.
System Action: The program ends with the return code of 29 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Access the DB2 RXSQL production disk as read/write and reexecute the ELOLKED EXEC.
| ELO8544E | File ELOLK TEXT fm not found, or DB2 RXSQL SERVICE minidisk is not accessed as fm. |
Explanation: The CMS STATE command failed to find the ELOLK TEXT file on the minidisk or directory accessed as the file mode.
System Action: The program ends with the return code of 32 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the STATE command, or verify that you are accessing the correct minidisk or directory. Correct the problem and reexecute the ELOLKED EXEC.
| ELO8546E | File fn ft * not found. |
Explanation: The CMS STATE command failed to find one of the files required to perform the DB2 RXSQL link-edit.
System Action: The program ends with the return code of 32 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Access the DB2 RXSQL and DB2 Server for VM production and service disks with the required access modes and reexecute the ELOLKED EXEC.
| ELO8547E | The above file should be on the DB2 Server for VM type minidisk/directory or you should have your own DATE or TIME routine on one of the accessed minidisks. |
Explanation: The CMS STATE command failed to find either the ARIUXDT TEXT file or the ARIUXTM TEXT file during the DB2 RXSQL link-edit.
System Action: The program ends with the return code of 32 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Make sure that the default date or time routines (on the DB2 Server for VM disk) or your customized date or time routines are available on one of the accessed disks. Reexecute the ELOLKED EXEC.
| ELO8548E | This file should be on the CMS System Disk. |
Explanation: The CMS STATE command failed to find the DMSCSL TEXT file in the CMS system minidisk or directory.
System Action: The program ends with the return code of 32 from the ELOLKED EXEC, and the user returns to CMS.
User Response: File DMSCSL TEXT is required to perform the DB2 RXSQL link-edit in non-XA environments. Please make sure that the system minidisk or directory is accessed and reexecute the ELOLKED EXEC.
| ELO8551E | Error while generating RXSQL LOADLIB. Check ELOLK LKEDIT file (ignore IEW0222 messages). |
Explanation: The link-edit completed with warning messages.
System Action: The program ends with the return code of 33 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Look at the ELOLK LKEDIT file. Ignore all IEW0222 messages, if they exist. Any other messages indicate unsuccessful link-edit. Correct the problem and reexecute the ELOLKED EXEC.
| ELO8556E | DB2 Server for VM level cannot be determined. |
Explanation: The CMS LISTFILE command failed while trying to find the SQLLEVEL EXEC. This file is needed to determine the current DB2 Server for VM level. DB2 RXSQL Version 7 Release 1 only supports DB2 Server for VM Version 6 Release 1.
System Action: The program ends with the return code of 26, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the LISTFILE command. Contact the IBM Support Center if further problems persist.
| ELO8557E | DIAGNOSE X'00' command failed with RC = rc. |
Explanation: The DIAGNOSE X'00' command failed when trying to determine the VM level.
System Action: The program ends with the return code of 36, and the user returns to CMS.
User Response: Consult your CP programming services manual for details on the DIAGNOSE command. Correct the problem and reexecute the installation EXEC.
| ELO8559E | ELOAMOD EXEC invoked with invalid parameters. To perform the PORTABLE PACKAGE RELOAD, refer to the section in the DB2 RXSQL manual that describes the ELOAMOD EXEC and execute the EXEC with correct parameters. |
Explanation: The ELOAMOD EXEC was not invoked with valid parameters.
System Action: The program ends with the return code of 27 from the ELOAMOD EXEC, and the user returns to CMS.
User Response: Correct the problem and reexecute the ELOAMOD EXEC with valid parameters. For information on the ELOAMOD EXEC, refer to The ELOAMOD EXEC.
| ELO8561E | Error loading the PORTABLE PACKAGE into the database. Return Code = rcode |
Explanation: The error may have been caused by one of the following:
System Action: The program ends with the return code of 31 from the ELOAMOD EXEC, and the user returns to CMS.
User Response: Ensure that the above dependencies are met and reexecute the ELOAMOD EXEC.
| ELO8566E | PORTABLE PACKAGE RELOAD unsuccessful. Please correct the problem identified by the previous error messages and re-execute the ELOAMOD EXEC to complete the PORTABLE PACKAGE RELOAD. Return Code = rcode |
Explanation: The PORTABLE PACKAGE RELOAD failed with the return code of 24, 26, 27, 31, or 48.
System Action: The program ends with the return code of 24, 26, 27, 31, or 48 from the ELOAMOD EXEC, and the user returns to CMS.
User Response: Check the return code and previous error messages for more information. Correct the errors and reexecute the ELOAMOD EXEC.
| ELO8567E | Installation of SECONDARY LEVEL HELP TABLES was unsuccessful. Please correct the problem identified by the previous error messages and re-execute the ELOHLPLD EXEC to complete the SECONDARY LEVEL HELP installation. Return Code = rcode |
Explanation: The secondary-level HELP tables load failed with the return code of 24, 27, or 31.
System Action: The program ends with the return code of 24, 27, or 31 from the ELOHLPLD EXEC, and the user returns to CMS.
User Response: Check the return code and errors identified by previous error messages. Correct the problem and reexecute the ELOHLPLD EXEC.
| ELO8573E | The minidisk or directory accessed as filemode fm is not a DB2 RXSQL type minidisk or directory or it is not accessed as read/write. |
Explanation: A disk accessed as the file mode is not the DB2 RXSQL production or service disk. There may be vital files missing from the disk.
System Action: The program ends with the return code of 29 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Make sure that the DB2 RXSQL production and service disks are accessed as read/write and reexecute the ELOLKED EXEC.
| ELO8574E | DB2 RXSQL link-edit was unsuccessful. Please correct the problem and do the following to complete the link-edit: Execute ELOLKED EXEC. Return Code = rcode. |
Explanation: The DB2 RXSQL link-edit was unsuccessful.
System Action: The program ends with the return code of 24, 26, 29, 32, 36, or 48 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Check the return code and the previous error messages for further details. Correct any errors and reexecute the ELOLKED EXEC.
| ELO8575E | The above file should be on the DB2 Server for VM type minidisk/directory. |
Explanation: The STATE command failed to find the ARIRVSTC TEXT file to perform the DB2 RXSQL link-edit.
System Action: The program ends with the return code of 32 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Access DB2 Server for VM production and service disks in read access mode and reexecute the ELOLKED EXEC.
| ELO8576E | Error occurred while attempting to skip to the end of the 5697ELO tape files. |
Explanation: An error occurred while forwarding the tape to the end of the product.
System Action: The program ends with the return code of 20 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: After verifying that your hardware is working properly and your tape is mounted correctly, reexecute the installation EXEC. If the condition persists, call your IBM customer service representative if it is a hardware problem or contact the IBM Support Center if you suspect the problem is with the tape.
| ELO8579E | FILE EXECSQL TEXT fm not found, or DB2 RXSQL SERVICE minidisk or SFS directory is not accessed as fm. |
Explanation: The CMS STATE command failed to find the EXECSQL TEXT file on the disk accessed as the file mode.
System Action: The program ends with the return code of 32 for the ELOLKED EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the STATE command or make sure that you are accessing the correct disk. Correct the problem and reexecute the ELOLKED EXEC.
| ELO8580E | Error while generating EXECSQL MODULE. |
Explanation: The EXECSQL MODULE could not be generated or the production disk is not accessed with read/write mode.
System Action: The program ends with the return code of 29 from the ELOLKED EXEC, and the user returns to CMS.
User Response: Access the DB2 RXSQL production disk with read/write mode and reexecute the EXEC.
| ELO8584E | You are installing the DB2 RXSQL package on a non-DB2 Server for VM application server, but you are not using the DRDA protocol. To perform the installation of the DB2 RXSQL package on a non-DB2 Server for VM application server you must use the DRDA protocol. |
Explanation: The ELOAMOD EXEC was not invoked with DRDA protocol when trying to install the DB2 RXSQL package onto a non-DB2 Server for VM application server.
System Action: The program ends with the return code of 38 from ELOAMOD EXEC, and the user returns to CMS.
User Response: Ensure that you are using the DRDA protocol and reexecute the ELOAMOD EXEC.
| ELO8586E | The SQLDS(No) parameter that you provided is not supported when you are running in the VM/XA environment. |
Explanation: The DB2 RXSQL package cannot be installed in non-DB2 Server for VM applications servers when running in the VM/XA environment.
System Action: The program ends with the return code of 27 from ELOAMOD EXEC, and the user returns to CMS.
User Response: Change the parameter to SQLDS(Yes) and reexecute the ELOAMOD EXEC.
| ELO8608E | Error loading type directory. RC = rc from the CMS VMFPLC2 command. |
Explanation: The directory may be full or the directory was not accessed in read/write mode.
System Action: The program ends with the return code of 25 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the VMFPLC2 command. Correct the problem and reexecute the installation EXEC.
| ELO8610E | Error accessing directory as fm. RC = rc from the CMS ACCESS command. |
Explanation: An SFS directory could not be accessed.
System Action: The program ends with the return code of 16 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the ACCESS command. Correct the problem and reexecute the installation EXEC.
| ELO8612E | Write authority is required for: directory |
Explanation: The SFS directory is not accessed in read/write mode.
System Action: The program ends with the return code of 45 from the| I5697ELO installation EXEC, and the user returns to CMS.
User Response: Acquire write authority for the SFS directory and reexecute the installation EXEC. If the problem persists, contact your IBM Support Center.
| ELO8701E | The DB2 RXSQL type minidisk or directory is not accessed as Read/Write with filemode fm. |
Explanation: An error occurred when ELOSCOR EXEC tried to verify write access to the DB2 RXSQL type minidisk or SFS directory with filemode fm.
System Action: The program ends with the return code of 16 from the ELOSCOR EXEC, and the user returns to CMS.
User Response: Access the type minidisk or SFS directory as filemode fm with read/write access and reexecute the ELOSCOR EXEC.
| ELO8702E | No DB2 RXSQL corrective service files were found on the Work minidisk accessed as filemode fm. Check to make sure the proper tape was mounted and/or the proper files have been unloaded from the tape. Then re-execute this EXEC. |
Explanation: ELOSCOR EXEC could not find any corrective service files on the work minidisk accessed as filemode fm.
System Action: The program ends and the user returns to CMS.
User Response: Ensure that the proper tape was mounted and/or the proper files have been unloaded from the tape to the work minidisk and reexecute this EXEC.
| ELO8704E | Error copying fn ft fm to the DB2 RXSQL type minidisk or directory. RC = rc from the CMS COPYFILE command. |
Explanation: A CMS COPYFILE error occurred when the ELOSCOR EXEC was copying a file from the work minidisk to the DB2 RXSQL type minidisk or SFS directory.
System Action: The program ends with the return code of 28 from the ELOSCOR EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the return code rc from the CMS COPYFILE command. Correct the problem and reexecute ELOSCOR EXEC.
| ELO8705E | Error erasing the fn ft fm file. RC = rc from the CMS ERASE command. |
Explanation: A CMS ERASE error occurred while the EXEC was erasing a file from the work minidisk.
System Action: The program ends with the return code of 28 from the EXEC, and the user returns to CMS.
User Response: Consult your CMS command reference manual for details on the return code rc from the CMS ERASE command. Correct the problem and reexecute the EXEC.
| ELO8804E | ELOSHLP EXEC was invoked with invalid parameters. To service secondary level help refer to the description of ELOSHLP EXEC in the manual. Re-execute the EXEC with the correct parameters. ELOSHLP LANGkey (langkey) CONnect (SQLDBA/password) |
Explanation: The ELOSHLP EXEC was not invoked with valid parameters.
System Action: The program ends with the return code of 27 from the ELOSHLP EXEC, and the user returns to CMS.
User Response: Correct the problem and reexecute the ELOSHLP EXEC with valid parameters.
| ELO8807E | Invalid language key entered. The langkey format is either Sxxx or Dxxx, where xxx is a number. Check the console listing from the preventive service EXEC for the langkey that is to be used when applying service to the help tables. Rerun the ELOSHLP EXEC with the correct langkey. |
Explanation: The ELOSHLP EXEC was not invoked with a valid language key parameter. The language key parameter langkey must:
System Action: The program ends with the return code of 27 from the ELOSHLP EXEC, and the user returns to CMS.
User Response: Check the console listing from the preventive service EXEC for the langkey that is to be used when applying service to the HELP tables, and reexecute the ELOSHLP EXEC with a valid langkey parameter.
| ELO8808E | A DBSU error occurred while servicing the help tables. The stage in service was stage. rc = rc. Look at the console listing to determine the error. Correct the problem indicated and rerun ELOSHLP EXEC. |
Explanation: The DBS Utility error occurred during one of the following:
System Action: The program ends with the return code of 31 from the ELOSHLP EXEC, and the user returns to CMS.
User Response: Look at the console listing to determine the DBS Utility error. Correct the problem indicated and rerun ELOSHLP EXEC.
| ELO8811E | Servicing of the SECONDARY LEVEL HELP TABLES was unsuccessful. Please correct the problem identified by the previous error messages and re-execute the EXEC ELOSHLP to complete the service of SECONDARY LEVEL HELP TABLES. rc = rc. |
Explanation: Servicing of the secondary-level HELP tables failed with the return code of 24, 26, 27, 31, 40 or 48.
System Action: The program ends with the return code of 24, 26, 27, 31, 40, or 48 from the ELOSHLP EXEC, and the user returns to CMS.
User Response: Check the return code and errors identified by previous error messages. Correct the problem and reexecute the ELOSHLP EXEC.
| ELO8813E | The ELOHNLS EXEC was invoked with invalid parameters. To load NLS help text for the languages installed, refer to the description of the ELOHNLS EXEC in the supplied documentation and re-execute the EXEC with the correct parameters. ELOHNLS LANGkey (langkey) CONnect (SQLDBA/password) |
Explanation: The ELOHNLS EXEC was not invoked with valid parameters.
System Action: The program ends with the return code of 27 from the ELOHNLS EXEC, and the user returns to CMS.
User Response: Correct the problem and reexecute the ELOHNLS EXEC with valid parameters.
| ELO8814E | Invalid language key entered. The langkey format is either Sxxx or Dxxx, where xxx is a number. Check supplied documentation for the appropriate langkey and re-execute the ELOHNLS EXEC with the correct langkey. |
Explanation: The ELOHNLS EXEC was not invoked with a valid language key parameter. The language key parameter langkey must:
System Action: The program ends with the return code of 27 from the ELOHNLS EXEC, and the user returns to CMS.
User Response: Check supplied documentation for the appropriate langkey and reexecute the ELOHNLS EXEC with a valid langkey parameter.
| ELO8815E | DBSU error occurred while loading the NLS help text into the help table. rc = rc. Look at the console listing to determine the error. Correct the problem indicated and rerun the ELOHNLS EXEC. |
Explanation: The DBS Utility error occurred during one of the following:
System Action: The program ends with the return code of 31 from the ELOHNLS EXEC, and the user returns to CMS.
User Response: Look at the console listing to determine the DBS Utility error. Correct the problem indicated and rerun ELOHNLS EXEC.
| ELO8817E | Loading of NLS help text into help tables was unsuccessful. Please correct the problem identified by the previous error messages and re-execute the EXEC ELOHNLS to complete the installation of NLS help text into help tables. Return Code = rc. |
Explanation: The NLS HELP tables load failed with the return code of 24, 26, 27, 31, or 48.
System Action: The program ends with the return code of 24, 26, 27, 31, or 48 from the ELOHNLS EXEC, and the user returns to CMS.
User Response: Check the return code and errors identified by previous error messages. Correct the problem and reexecute the ELOHNLS EXEC.
| ELO8818E | File fn ft was not found. Check if you are using the correct langkey or that the DB2 RXSQL Service minidisk or directory is linked. Correct the problem and rerun exec. |
Explanation: This error can be caused by running one of the following EXECs:
If you used ELOSHLP EXEC, the required file used for servicing the HELP tables was not available. If you used ELOHNLS EXEC, the required file used for installation of NLS HELP tables was not available. Either you used an incorrect language key parameter or the DB2 RXSQL service disk was not accessed.
System Action: The program ends with the return code of 26 from the EXEC, and the user returns to CMS.
User Response: Check whether you are using the correct language key parameter or whether the DB2 RXSQL service disk is accessed. Correct the problem and run the EXEC again.
| ELO8821E | ELODNLS EXEC was invoked with invalid parameters. To delete language(s) refer to the section in the manual that describes the ELODNLS EXEC and execute the EXEC with the correct parameters. |
Explanation: The ELODNLS EXEC was not invoked with valid parameters.
System Action: The program ends with the return code of 27 from the ELODNLS EXEC, and the user returns to CMS.
User Response: Correct the problem and reexecute the ELODNLS EXEC with valid parameters.
| ELO8822E | Error unloading table SQLDBA.ELOLANGUAGE |
Explanation: A DBS Utility error occurred when ELODNLS EXEC tried to unload language key information from the SQLDBA.ELOLANGUAGE table.
System Action: The program ends with the return code of 31 from the ELODNLS EXEC, and the user returns to CMS.
User Response: Check the console listing to determine the DBS Utility error. Correct the problem indicated and rerun ELODNLS EXEC.
| ELO8823E | Error unloading table SQLDBA.ELOOPTIONS |
Explanation: A DBS Utility error occurred when ELODNLS EXEC tried to unload default language information from the SQLDBA.ELOOPTIONS table.
System Action: The program ends with the return code of 31 from the ELODNLS EXEC, and the user returns to CMS.
User Response: Check the console listing to determine the DBS Utility error. Correct the problem indicated and rerun ELODNLS EXEC.
| ELO8834E | DBSU error while deleting rows from SQLDBA.ELOLANGUAGE or SQLDBA.ELOTEXT1 tables, or while updating table SQLDBA.ELOOPTIONS. Please review the console listing to find the DBSU error, correct the problem and re-execute this EXEC. |
Explanation: A DBS Utility error occurred when ELODNLS EXEC tried to delete rows from SQLDBA.ELOLANGUAGE table or SQLDBA.ELOTEXT1 HELP table, or while updating the default language in SQLDBA.ELOOPTIONS table.
System Action: The program ends with the return code of 31 from the ELODNLS EXEC, and the user returns to CMS.
User Response: Check the console listing to determine the DBS Utility error. Correct the problem indicated and run ELODNLS EXEC again.
| ELO8839E | Failed to find DB2 RXSQL CMS HELP files on the NLS PRODUCTION minidisk or SFS directory accessed as filemode fm. |
Explanation: An error occurred when ELODNLS EXEC tried to find DB2 RXSQL CMS HELP file with filename DB2 RXSQL and filetype HELPMENU. It was not found for one of the following reasons:
System Action: The program ends with the return code of 16 from the ELODNLS EXEC, and the user returns to CMS.
User Response: Make sure that the file is on the NLS production disk and rerun ELODNLS EXEC.
| ELO8844E | Deactivation of the language or languages (from database and the corresponding CMS HELP from minidisks or SFS directories) was unsuccessful. Please correct the errors identified by the previous error messages and re-execute the ELODNLS EXEC. rc = rc. |
Explanation: Language deactivation failed with the return code of 16, 24, 26, 27, 28, 31, 36, or 48.
System Action: The program ends with the return code of 16, 24, 26, 27, 28, 31, 36, or 48 from the ELODNLS EXEC, and the user returns to CMS.
User Response: Check the return code and errors identified by previous error messages. Correct the problem and reexecute the ELODNLS EXEC.
| ELO8850E | A DBSU error occurred while searching for the language langkey in the SQLDBA.ELOLANGUAGE table. rc = rc. Look at the console listing to determine the error. Correct the problem indicated and rerun ELOSHLP EXEC |
Explanation: The error occurred when the DBS Utility tried to check if the language langkey was in the SQLDBA.ELOLANGUAGE table.
System Action: The program ends with the return code of 31 from the ELOSHLP EXEC, and the user returns to CMS.
User Response: Look at the console listing to determine the DBS Utility error. Correct the problem indicated and rerun ELOSHLP EXEC.
| ELO8851E | An error occurred while searching for the language langkey in the SQLDBA.ELOLANGUAGE table. Either there were no entries in the output DBSU file, or there was more than 1. Look at the console listing to determine the error. Correct the problem indicated and rerun ELOSHLP EXEC. |
Explanation: The result file from the DBS Utility search for the language in the SQLDBA.ELOLANGUAGE table was empty or contained more than one entry.
System Action: The program ends with the return code of 31 from the ELOSHLP EXEC, and the user returns to CMS.
User Response: Ensure that the language is in the SQLDBA.ELOLANGUAGE table and there are no duplicate rows for the language in the table. Correct the problem and run the ELOSHLP EXEC again.
| ELO8852E | The language langkey was not found in the SQLDBA.ELOLANGUAGE table. As a result, you cannot service this language. Correct the LANGkey parameter and rerun the ELOSHLP EXEC. |
Explanation: There is no entry for the language to be serviced in the SQLDBA.ELOLANGUAGE table. To service a language, it must be in the SQLDBA.ELOLANGUAGE table.
System Action: The program ends with the return code of 31 from the ELOSHLP EXEC, and the user returns to CMS.
User Response: Make sure that the language is in the SQLDBA.ELOLANGUAGE table and run the ELOSHLP EXEC again.
| ELO8853E | The attempt to get number free fm virtual address virtual address for the access or link was unsuccessful. There must be at least number free for this EXEC. Correct the situation and rerun. |
Explanation: This EXEC will try to get enough free file modes, and if necessary, virtual device addresses to link and access disks. number indicates the number of free file modes or virtual device addresses required. The EXEC was unable to get the number required.
System Action: The program ends with the return code of 16 from the |I5697ELO installation EXEC, and the user returns to CMS.
User Response: Ensure that there are at least number free file modes or virtual
device addresses (as indicated in the message) and rerun this EXEC.