| ARI0428E | DB2 Server for VM services were requested but DB2 Server for VM is not available in Virtual Machine &1 .. |
Explanation: An application program requested a DB2 Server for VM service, but the database manager is not available in the virtual machine identified by &1.
System Action: The Resource Adapter returns to the application with an SQLCODE of -940 and the SQLWARN0 and SQLWARN6 flags set to S, indicating a serious error. If another SQL call is issued, the application will abend, and message ARI0439E will be issued.
Operator Response: Retry the application program after logging on the DB2 Server for VM virtual machine and running the SQLSTART EXEC.
| ARI0429I | SQL CANCEL was requested while COMMIT or ROLLBACK was in process. CANCEL of COMMIT or ROLLBACK is not allowed. The database manager is ignoring the CANCEL request. |
Explanation: The terminal operator tried to cancel an SQL request while an SQL COMMIT or ROLLBACK command was processing. Cancellation of COMMIT or ROLLBACK processing is not allowed.
System Action: The SQL CANCEL request is ignored.
| ARI0439E | The application is abending because of a serious system error that occurred on a call to the application server. SQLCODE = &1A .. |
Explanation: The application tried to issue an SQL command after a serious error. (SQLWARN0 and SQLWARN6 were set to S.) The resource adapter prevents further tries to communicate with the database manager by terminating the application.
System Action: The resource adapter abends the application and rolls back the logical-unit-of-work.
Programmer Response: Correct the problem indicated by the SQLCODE value. (See the list of SQLCODEs starting at Chapter 19, SQLCODEs for an explanation.) Notify the operator when the application can be tried again.
Operator Response: The cause of the problem may be due to your database environment. That is, the database manager is not available, or the database manager is accessing a different database than the one expected. If this is the case, correct the environment and try the application again. If you cannot determine the cause of the problem, gather pertinent information and notify the system programmer.
| ARI0440E | The application is abending. An error or warning is encountered and the WHENEVER condition specifies STOP. SQLCODE = nnn. |
Explanation: The application had specified WHENEVER ERROR STOP or WHENEVER WARNING STOP. The SQLCODE satisfied this WHENEVER condition and the resource adapter stopped the application with an operating system abend.
System Action: The transaction ends.
Operator Response: The cause of the problem may be an environmental one. That is, the database manager is not available, or it is accessing a different database than the one expected. If this is the case, correct the environment and try the application again. If you cannot determine the cause of the problem, gather pertinent information and notify the application programmer.
Programmer Response: Correct the problem indicated by the SQLCODE. (See the list of SQLCODEs starting at Chapter 19, SQLCODEs for an explanation.) Notify the operator when the application can be tried again.
| ARI0442E | A non-DB2 Server for VM message has been received. The Resource Adapter has severed the communication path. |
Explanation: The resource adapter received a non-DB2 Server for VM message.
System Action: The resource adapter terminated the communication path.
Operator Response: If you are unable to determine the cause of the problem, retry the application program. If the problem repeats, collect pertinent information and notify the system programmer.
Programmer Response: Make a record of the error and contact the designated support group for your installation.
| ARI0451I | Status of application server conversations on timestamp . |
Explanation: This is the normal DB2 Server for VM response to SQLQRY.
| ARI0452I | EXTNAME = external name.
RDBMS = dbname server version STATUS = status TIME = time LU = luname TPN = tpn LUWID= luwid . |
Explanation: This is the normal DB2 Server for VM response to SQLQRY.
| ARI0470E | Trace file OPEN failed. Reason Code = nn . Return Code = nn . |
Explanation: The Resource Adapter trace is being initialized before application execution. An error occurred when the database manager attempted to open the trace output file on tape unit or CMS minidisk. The Reason Code value is the Primary Error Code. The Return Code value is the Secondary Error Code. For further explanation, look up the displayed error codes under either Chapter 23, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.
System Action: The trace facility remains inactive and the application continues to execute.
Operator Response: For corrective action, look up the displayed error codes under either Chapter 23, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.
System Programmer Response: See the Operator Response.
| ARI0471I | Trace is ON. |
Explanation: The Resource Adapter trace parameters have been successfully processed. The trace is now active with trace output going to a tape unit or a CMS minidisk.
System Action:
| ARI0472E | Trace file CLOSE failed. Reason Code = nn . Return Code = nn . |
Explanation: The Resource Adapter Trace is being turned off during application termination. When the system attempted to close the trace output file on a tape unit or a CMS minidisk, a termination error occurred. The Reason Code value is the Primary Error Code. The Return Code value is the Secondary Error Code. For further explanation, look up the displayed error codes under either Chapter 23, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.
System Action: Trace shutdown is completed. DB2 Server for VM Resource Adapter trace is in the OFF state. Assume that the trace tape or minidisk file was not closed and is not fully processable (see below).
Operator Response: Report the problem (message) to your system programmer. Include any CMS minidisk or tape unit error messages displayed by CMS.
You can run the DB2 Server for VM Trace Formatter Utility Program (ARIMTRA). It will format and output all trace data up to the point of failure. At that point, it may end because of a lack of tape/minidisk CLOSE recording or an unreadable record on the tape/minidisk.
System Programmer Response: For corrective action, look up the displayed error codes under either Chapter 23, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.
| ARI0473I | Trace is OFF. |
Explanation: The Resource Adapter Trace is inactive and the trace output file is closed on a tape unit or a CMS minidisk.
System Action: The trace output file is closed.
Operator Response: None required.
| ARI0474I | Warning: The status shared segment could not be updated. |
Explanation: The Resource Adapter was unable to update the status shared segment. The segment is either no longer available or does not have sufficient space for another entry.
System Action: The Resource Adapter continues without updating the status in the shared segment.
User Response: Make a record of the warning and contact the designated support group for your installation.
System Programmer Response: Check that the status shared segment is still loaded. If this message occurs intermittently, the status shared segment is not large enough to support your installation. Increase the space available for the segment.
| ARI0499I | Warning: The status shared segment is not loaded. Return Code = retcode . |
Explanation: The Resource Adapter was unable to load the status shared segment.
System Action: The Resource Adapter continues without updating the status in the shared segment.
User Response: Make a record of the warning with the return code retcode and contact the designated support group for your installation.
Operator Response: Check that the shared segment exists and can be loaded.