| ARI2900E | Language &1. cannot be accessed. Reason Code = nn. |
Explanation: Either the national language name has been misspelled, or the language specified on the SET LANGUAGE command cannot be accessed because of one of the following reasons:
&1. is the language identifier.
System Action: An attempt to set language &1. failed, because the language specified could not be found.
User Response: Make sure that the language identifier is correct and the requested language is supported on your system.
An INSERT may have been made into table SYSLANGUAGE during a DB2 Server for VM session. You must bring the DB2 Server for VM machine down and bring it up again in order for the inserted language IDs in SYSLANGUAGE to be recognized.
| ARI2901I | Warning: The database manager cannot access the default language &1.. English will be used instead. Reason Code = nn. |
Explanation: The message file for the language currently set in VM could not be loaded and the attempt to set the DB2 Server for VM default language also failed. The English message repository is used instead. Reason codes have the following meaning:
| ARI2902E | There is no message file that the database manager can access. |
Explanation: This message appears when all of the following conditions have been met:
System Action: Subcomponent initialization is cancelled.
User Response: Notify your system programmer.
System Programmer Response: Ensure that the repository corresponding to the current CMS language is available, or that the first entry of the ARISNLSC MACRO Q file has a corresponding available repository, or that the repository for AMENG is available. Finally, verify that you have enough storage to load the message repository. Refer to the DB2 Server for VM Program Directory for more information on installing a language on your system.
| ARI2903E | Error loading Resource Adapter. SQLCODE = &1A |
Explanation: Resource adapter could not be loaded. This message is always issued in English.
System Action: Subcomponent initialization is cancelled.
User Response: Notify your System Programmer.
Programmer Response: Correct the problem indicated by the SQLCODE value. For more information, see Chapter 19, SQLCODEs.
| ARI2905E | The command command is not supported when using the DRDA protocol. |
Explanation: You are accessing a non-DB2 Server for VM application server or you are using the DRDA protocol, and have attempted to use the specified command against this application server. The command is available only against a DB2 Server for VM application server using a non-DRDA protocol.
System Action: Command processing failed.
User Response: Enter another command.
| ARI2906I | The only valid isolation level is CS when the DRDA protocol is used. Isolation level of CS is now in effect. |
Explanation: If the DRDA protocol is used, the isolation level defaults to cursor stability (CS). The SET ISOLATION command cannot be used to change the isolation level.
System Action: The SET ISOLATION command is ignored.
User Response: You may continue with another command.
| ARI2909I | Warning: An error in the conversation has been detected. Please wait for the data capture completion message to appear before taking further action. LUWID = &1. |
Explanation: An error has been detected in either the communication partner's datastream or internally using DRDA protocol processing.
System Action: System information is dumped to a console file. The logical unit of work identifier may be used to correlate this message to the console file.
User Response: Wait until completion message ARI2910I is displayed, then notify your system programmer. DO NOT erase any console files that may exist.
System Programmer Response: This message indicates that an error has occurred during DRDA protocol processing, and diagnostic error information has been dumped to a console file. Save the console file containing the dump identified by the logical unit of work identifier in the message and contact the designated support group for your installation.
| ARI2910I | Data capture process completed successfully. Please notify your system programmer. |
Explanation: The data capture process referred to in message ARI2909I is completed.
| ARI2911E | An internal error has occurred in the data capture process. Notify your system programmer. LUWID = &1. |
Explanation: An error has occurred during the data capture process. This indicates a serious system problem.
System Action: Process of data capture is interrupted. A console file containing partial data may or may not exist.
User Response: Notify your system programmer. Do NOT erase any console files that may exist.
System Programmer Response: This message indicated that a DB2 Server for VM internal error has occurred during data capture. There may or may not be a console file containing a partial dump identified by the logical unit of work identifier in the message. Save this file if it exists. Contact the designated support group for your installation.
| ARI2912E | Error reading NETID from SNA NETID file. |
Explanation: You have specified PROTOCOL=AUTO which requires a NETID value. An error occurred when the SQLSTART EXEC tried to retrieve the NETID value from the SNA NETID file on the production disk.
System Action: Database startup is terminated because the NETID is a required parameter for DRDA protocol.
User Response: Check the existence of the SNA NETID file on the production disk. If it is not found or corrupted, then recreate the file with the correct NETID value and rerun the EXEC.
| ARI2913I | Character translation table for CHARNAME = charname cannot be found. The character translation table for INTERNATIONAL will be used. |
Explanation: The row with the CHARNAME value cannot be found in the CMS file ARISSCR MACRO on the production minidisk, or the file ARISSCR MACRO does not exist. If the CHARNAME value is 'unknown', an error has occurred while retrieving the GLOBAL variable CHARNAME from the LASTING GLOBALV file.
System Action: Processing continues. The character translation table for INTERNATIONAL will be used.
User Response: If the CHARNAME value is 'unknown', re-run SQLINIT with a correct CHARNAME. Contact your system programmer if the specified CHARNAME cannot be found in ARISSCR MACRO on the system production minidisk, or if the file ARISSCR MACRO does not exist.
System Programmer Response: Check that the row corresponding to the CHARNAME in the user's LASTING GLOBALV file exists in the flat file ARISSCR MACRO on the production minidisk. If the row does not exist, or if the flat file does not exist, re-create the flat file ARISSCR MACRO. Refer to the DB2 Server for VM System Administration manual.
| ARI2914E | An error occurred with the CMS MACRO name while accessing the file filename filetype. Return code = rc |
Explanation: An error occurred with the CMS MACRO while accessing the file filename filetype that is required for character translation support or for CCSID support. filename filetype may have one of the following values: ARISCCS MACRO, ARISSTR MACRO or ARISSCR MACRO. The return code value is the CMS MACRO return code.
System Action: Processing terminates.
User Response: Contact your system programmer.
System Programmer Response: Refer to the VM/ESA: CMS Application Development Reference for an explanation of the return code and correct the problem. If the problem cannot be corrected, contact the designated support group for your installation.
| ARI2915E | An error occurred when the application attempted to {get | free} dynamic storage. |
Explanation: The application encountered an error in either getting or freeing storage needed for work areas.
System Action: Processing terminates.
User Response: Contact your system programmer.
System Programmer Response: If this is a get failure, increase the size of the user machine. Otherwise, refer to VM/ESA: CMS Command Reference
| ARI2916E | An error occurred with the CMS command name. Return code = rc. |
Explanation: An error occurred with the CMS command name. The return code rc is the CMS command return code.
System Action: Processing terminates.
User Response: Contact your system programmer.
System Programmer Response: Refer to the appropriate VM/ESA: CMS Command Reference manual for an explanation of the return code, and correct the problem.
If the problem cannot be corrected, contact the designated support group for
your installation.