| ARI4021E | The length{s} contained in a data stream sent by CRR recovery server at TPN tpn does not match the length of the data received. Length in Exchange Log Names: length1 Length in Compare States: length2 Length of data received: length3 |
Explanation: One of the following has occurred:
tpn indicates the transaction program name for the CRR recovery server with which the database manager is communicating.
length1 indicates the length, in decimal, found in the Exchange Log Names reply or request sent by the CRR recovery server.
length2 is only present in Resynchronization recovery processing and indicates the length found in the Compare States request sent by the CRR recovery server.
length3 indicates the length of data, in decimal, that was actually received.
System Action: The SYNCPNT parameter is reset from "Y" to "N" and the database manager is unable to use VM/CRR for handling DRDA sync point operations. As a result, this database may not be a participant in DRDA logical units of work that update multiple remote databases. However, the database manager is still able to process SQLDS protocol requests and DRDA requests that do not involve a sync point manager (for example, DRDA logical units of work that only update a single remote database).
System Programmer Response: Make a record of what went wrong and contact the designated support group for your installation.
| ARI4022E | A data stream sent by CRR recovery server at TPN tpn has an invalid GDSID. GDSID expected: gdsid1 GDSID received: gdsid2 |
Explanation: One of the following has occurred:
gdsid1 indicates the GDS identifier that was expected by the database manager. This is a four digit hexadecimal value.
gdsid2 indicates the GDS identifier that was sent by the CRR recovery server. This is a four digit hexadecimal value.
System Action: The SYNCPNT parameter is reset from "Y" to "N" and the database manager is unable to use VM/CRR for handling DRDA sync point operations. As a result, this database may not be a participant in DRDA logical units of work that update multiple remote databases. However, the database manager is still able to process SQLDS protocol requests and DRDA requests that do not involve a sync point manager (for example, DRDA logical units of work that only update a single remote database).
System Programmer Response: Make a record of what went wrong and contact the designated support group for your installation.
| ARI4023I | The CRR recovery server has completed resynchronizing work with the database manager. Date: date Time: time |
Explanation: Message ARI4023I is a signal to the database manager operator that the CRR recovery server has completed resynchronization recovery with the database manager at the date and time indicated. This message is followed by message ARI0182I which identifies the transaction id and LUW id for the unit of work being recovered.
System Action: Database manager processing continues.
Database Administrator Action: If errors occurred during resynchronization recovery, then an error message will have been displayed that indicated the error. See the explanation for that message and resolve the error.
| ARI4100I | TCP/IP service initialized from {ETC SERVICES|TCPPORT}. Service name is service-name. TCP/IP Port is port-number. |
Explanation: The TCP/IP service was successfully initialized by the application server.
TCP/IP service can be initialized from the ETC SERVICES file or TCPPORT. If it is ETC SERVICES, then the service name and port number were determined by doing a look up in the ETC SERVICES file. If it is TCPPORT, then the port number was taken from the TCPPORT parameter specified on the SQLSTART command.
service-name is the service name that was used to do the look up in the ETC SERVICES file. If service-name is N/A, then there is no service name. This will only happen if TCP/IP support was initialized by specifying the TCPPORT parameter.
port-number is the port number that the application server will listen to for connect requests. It is determined by the value in the ETC SERVICES file or from the TCPPORT parameter.
System Action: The application server listens for TCP/IP connect requests on the port identified in port-number. The application server is able to handle both SNA connections and TCP/IP connections.
| ARI4101I | Unable to find service-name in ETC SERVICES. |
Explanation: The application server attempted to search the ETC SERVICES file for the value identified by service-name.
System Action: The system continues. If service-name is the same value as the RESID, the application server will attempt to use the default service name of ddm-rdb. If service-name is ddm-rdb, the application server will discontinue TCP/IP initialization. The application server will only be able to accept SNA connections.
Operator Response: Report this message to your system programmer.
System Programmer Response: Determine if an entry for service-name should be added to the ETC SERVICES file. Add the entry if it is required. If TCP/IP services are not required, ignore this message or start the application server with the TCPPORT=0 parameter to bypass the TCP/IP initialization.
| ARI4102I | Unable to initialize TCP/IP service. |
Explanation: The application was unable to initialize TCP/IP services because access to TCP/IP for VM was not available.
System Action: The application server continues, but it can only accept SNA connections.
Operator Response: Report this error to your system programmer.
System Programmer Response: If TCP/IP services are required, make sure that TCP/IP for VM is available and running, and the ETC SERVICES file or the TCPPORT parameter is correct. Shut down and restart the application server when TCP/IP for VM is available. If TCP/IP services are not required, ignore this message or start the application server with the TCPPORT=0 parameter to bypass the TCP/IP initialization.
| ARI4103I | TCP/IP service service-name failed. Return code = n. |
Explanation: A TCP/IP function was performed but an error occurred during the execution of the function. service-name identifies the function and n is the return code that was received.
System Action: The system continues.
Operator Response: Report this error to your system programmer.
System Programmer Response: Take corrective action, if necessary, based on the function and return code received.
The description of the function reported by this message can be found in the IBM Transmission Control Protocol/Internet Protocol for VM: Programmer's Reference Version 2 Release 4 manual.
The explanation for this return code can be found in the IBM Transmission Control Protocol/Internet Protocol for VM: Programmer's Reference Version 2 Release 4 manual.
| ARI4106I | The connection with the TCP/IP machine has been severed.
TCP/IP service = servicename. Sever Reason = reasoncode. |
Explanation: The IUCV connection between the application requester and the TCP/IP VM machine has been severed.
System Action: The logical unit of work is rolled back.
Operator Response: Report this error to your system programmer.
System Programmer Response: Report this error to the designated support group for your installation.
| ARI4107I | Error while communicating with the TCP/IP machine.
TCP/IP service = servicename. IPRCODE = reasoncode. |
Explanation: A communications error occurred between the application requester and the TCP/IP VM machine.
System Action: The communications path is severed and the logical unit of work is rolled back.
Operator Response: Report this error to your system programmer.
System Programmer Response: Report this error to the designated support group for your installation.
| ARI4108E | Unable to initialize the external security manager. SECTYPE has been changed to DB2. |
Explanation: The application server issued the external security manager initialization command "RPIUCMS INIT" and it failed. The command was issued because the initialization parameter SECTYPE=ESM was specifed.
System Action: SECTYPE is switched to DB2 and processing continues.
System Programmer Response: Correct the problem with the external security manager.
| ARI4109E | While trying to process an external security manager request through
the RACROUTE macro, an error occurred.
Function = function SAF Return Code = X'return code' RACF Return Code = X'return code' RACF Reason Code = X'reason code' |
Explanation: The application server issued the RACROUTE macro to authenticate a userid. The RACROUTE macro responded with the information described in the message.
System Action: Authentication of the userid failed. SECTYPE remains at ESM and processing continues.
System Programmer Response: Correct the problem with the external security manager. For more information about the return codes and reason codes, see External Security Interface (RACROUTE) Macro Reference for MVS and VM manual.
| ARI4110E | ESM function ESM function failed. Return code = return code |
Explanation: The application server was performing function ESM function and encountered an error. return code indicates the error that occurred.
System Action: Processing continues.
System Programmer Response: Report this error to the designated support group for your installation.
|
| ARI4112I | TCPPORT nnnnn is invalid. It must be in the range from n1 to n2. |
Explanation: An invalid port number was specified in the START TCPIP TCPPORT operator |command, nnnnn is the port number specified. |
n1 is the lower limit (or minimum) for the correct parameter |value.
n2 is the upper limit (or maximum) for the correct parameter |value. |
|System Action: The system continues, the application server ignores the restart TCP/IP |request. The application server will only be able to accept SNA |connections.
|Operator Response: Retry the command by specifying a valid port number.
|
| ARI4113I | TCP/IP support for the database manager was never enabled. Start request is ignored. |
Explanation: The START TCPIP operator command was issued while the TCP/IP support |initialization process was never invoked during application server |startup. The restart process is relying on the TCP/IP agent structure |previously created during application server initialization. Without |the agent structure, restart process cannot be performed. This is the |case where either TCPPORT = 0 was specified or RMTUSERS = 0 was |specified.
|System Action: The system continues, the application server ignores the restart TCP/IP |request. The application server will only be able to accept SNA |connections.
|Operator Response: Report this error to your system programmer.
|System Programmer Response: Restart the application server by specifying a valid TCPPORT parameter if |TCP/IP support is desired.
|
| ARI4114I | TCP/IP support for the database manager is still active. Start request is ignored. |
Explanation: The START TCPIP operator command was issued, but the TCP/IP support for the |application server is still active.
|System Action: The system continues, the application server ignores the restart TCP/IP |request.
|Operator Response: Issue the START TCPIP command only after TCP/IP support for the application |server went down abnormally.
|
| ARI4115I | TCP/IP support for the database server is disabled. |
Explanation: TCP/IP support for the application server is disabled. This could be |the result of a severe error detected during the execution of a TCP/IP |function. The listener socket of the application server is closed and |no new TCP/IP connect request can be accepted. The application server |will only be able to accept SNA connections.
|For the error situation encountered, there should be a preceding message |that describes the error. Refer to the corresponding message and take |action accordingly.
|System Action: The system continues, but no TCP/IP support is available.
|Operator Response: Report this error to your system programmer.
|System Programmer Response: Take correction action, if necessary, based on the function and return code |received in the preceding error message. Once the error condition is |resolved, issue the START TCPIP operator command to restart TCP/IP support if |TCP/IP communication for the application server is desired.
| ARI4151I | FORMAT 1
START PROC successful for proc-name. FORMAT 2 START PROC successful for proc-name for AUTHID authid. |
Explanation: The stored procedure referenced has been started successfully.
System Action: Processing of the operator command has completed.
| ARI4152E | FORMAT 1
START PROC failed for proc-name. Reason Code reason-code. FORMAT 2 START PROC failed for proc-name for AUTHID authid. Reason Code reason-code. |
Explanation: Processing of the command failed. Possible reason codes are:
System Action: The operator command is not processed.
Operator Response: Correct the error and issue the command again.
| ARI4153I | FORMAT 1
Stored procedure proc-name is already started. FORMAT 2 Stored procedure proc-name for AUTHID authid is already started. |
Explanation: The stored procedure referenced was started by a previous START PROC command.
System Action: Processing of the operator command has ended.
Explanation: This message provides information about an error that occurred when an operator command was issued. It indicates that either
System Action: Processing of the operator command has ended.
Operator Response: Correct the source of the error and issue the command again.
| ARI4155I | FORMAT 1
STOP PROC successful for proc-name. FORMAT 2 STOP PROC successful for proc-name for AUTHID authid. |
Explanation: The stored procedure referenced has been stopped successfully.
System Action: Processing of the operator command has completed.
| ARI4156I | FORMAT 1
New calls to stored procedure proc-name will be action-code. FORMAT 2 New calls to stored procedure proc-name with AUTHID authid will be action-code. |
Explanation: This message is displayed when a stored procedure is stopped. It indicates how subsequent CALLs to that procedure will be handled.
System Action: The STOP PROC command has completed successfully for the procedure indicated.
| ARI4157E | FORMAT 1
STOP PROC failed for proc-name. Reason code reason-code. FORMAT 2 STOP PROC failed for proc-name for AUTHID authid. Reason code reason-code. |
Explanation: Processing of the command failed. Possible reason codes are:
System Action: Processing of the operator command has ended.
Operator Response: Correct the error and issue the command again.
| ARI4158E | Error in operator command oper-cmd. Reason code reason-code. |
Explanation: Processing of the command failed. Possible reason codes are:
System Action: Processing of the operator command has ended.
Operator Response: Correct the error and issue the command again.
| ARI4159I | FORMAT 1
Stored procedure proc-name is already stopped. FORMAT 2 Stored procedure proc-name for AUTHID authid is already stopped. |
Explanation: The stored procedure referenced was stopped by a previous STOP PROC command.
System Action: Processing of the operator command continues.
| ARI4160E | Operator command oper-cmd has insufficient number of input parameters. |
Explanation: The command entered did not use the correct syntax.
oper-cmd The operator command issued.
Operator Response: Refer to the DB2 Server for VSE & VM Operation manual for the syntax diagram for the command.
| ARI4161E | Operator command oper-cmd has too many input parameters. |
Explanation: The command entered did not use the correct syntax.
oper-cmd The operator command issued.
System Action: Processing of the operator command has terminated.
Operator Response: Refer to the DB2 Server for VSE & VM Operation manual for the syntax diagram for the command.
| ARI4162I | Stored procedure server serv-name has been started. |
Explanation: The stored procedure server serv-name is able to accept SQL CALL statements to run stored procedures associated with this server.
System Action: Operator command complete successfully. Processing continues.
| ARI4163I | FORMAT 1
Stored procedure server serv-name is not defined. FORMAT 2 Stored procedure server group serv-group-name is not defined. FORMAT 3 Wildcard is used improperly in stored procedure server name serv-name. FORMAT 4 Wildcard is used improperly in stored procedure server group name serv-group-name. FORMAT 5 Stored procedure server name serv-name is a keyword. FORMAT 6 Stored procedure server group name serv-group-name is a keyword. |
Explanation: This message provides information about an error that occurred when an operator command was issued. It indicates that either
System Action: Processing of the operator command terminates.
Operator Response: Correct the error and issue the command again.
| ARI4164I | Stored procedure server serv-name is already started. |
Explanation: The stored procedure server serv-name was started by a previous START PSERVER command.
System Action: Processing of the operator command has ended.
| ARI4165I | START PSERVER cannot be processed for server-name because it has a status of status. |
Explanation: Only a stored procedure server that is currently stopped can be started. Possible values for status are:
System Action: Processing of the operator command terminates.
Operator Response:
If you need to stop and start the stored procedure immediately, you can use the STOP PSERVER command with the QUICK option, and then issue the START PSERVER command.
| ARI4166I | FORMAT 1
Unable to acquire storage for a pseudoagent for server server-name. FORMAT 2 Unable to acquire storage for an XPCC control block for server server-name. |
Explanation: In VM, when START PSERVER is issued, the database manager allocates the pseudoagent structure to be used for the connection between the database manager and the stored procedure server. In VSE, when START PSERVER is issued, the database manager allocates an XPCC control block to be used for the connection between the database manager and the stored procedure server. In either case, if storage for the structure is not available, the START PSERVER command cannot complete.
System Action: Processing of the operator command terminates.
Operator Response: Try the command again later. Since storage utilization on the database manager varies depending on the number of active agents and their activities, storage may become available, enabling the command to complete.
Database Administrator Action:
Consider whether the amount of storage available to the database manager needs to be increased.
| ARI4167E | FORMAT 1
START PSERVER for serv-name failed. Reason code reason-code. FORMAT 2 START PSERVER GROUP for serv-group-name failed. Reason code reason-code. |
Explanation: Processing of the command failed. Possible reason codes are:
System Action: Processing of the operator command has ended.
Operator Response: This message is preceded by an informational message that indicates the reason for the error. Follow the instructions given in the Operator Response for the informational message.
| ARI4168I | START PSERVER operator command timed out. |
Explanation: The START PSERVER command did not complete in the amount of time specified by the initialization parameter PTIMEOUT. Either:
System Action: Processing of the operator command terminates.
System Programmer Response: If the connection failed, use the diagnostic information displayed to determine the source of the problem and correct the error.
Database Administrator Action:
If no error occurred during the attempt to connect to the stored procedure server, consider whether the PTIMEOUT value should be increased.
Explanation: A stored procedure has exceeded the number of allowed abnormal terminations as defined by PROCMXAB init parameter.
System Action: Processing of the SQL statement has ended.
Operator Response: Issue START PROC command to restart the procedure.
Programmer Response: Determine the reason for stored procedure abend.
Explanation: The cache structure is currently being updated by another agent.
System Action: Processing of the operator command has ended.
Operator Response: Issue the command again at a later time
| ARI4171I | FORMAT 1
Stored procedure server serv-name has been stopped. It can be implicitly started. FORMAT 2 Stored procedure server serv-name has been stopped. It cannot be implicitly started. |
Explanation: Stored procedure server serv-name has been deactivated as requested by a STOP PSERVER or SQLEND command.
System Action: Processing of the operator command is complete.
| ARI4172I | Stored procedure server serv-name is already stopped. |
Explanation: The stored procedure server serv-name was stopped by a previous STOP PSERVER command.
System Action: Processing of the operator command terminates.
Explanation: The STOP PSERVER command was issued for a stored procedure server that is currently running a stored procedure.
System Action: When the stored procedure finishes, the database manager will stop the stored procedure server.
Operator Response: If you must stop the stored procedure server immediately, issue the STOP PSERVER command again, specifying the QUICK option.
| ARI4174E | FORMAT 1
STOP PSERVER for serv-name failed. Reason code reason-code. FORMAT 2 STOP PSERVER GROUP for serv-group-name failed. Reason code reason-code. |
Explanation: Processing of the command failed. Possible reason codes are:
System Action: Processing of the operator command has ended.
Operator Response: Correct the error and issue the command again.
| ARI4175I | The cach-name cache is loaded at load-address. |
Explanation: cach-name is the name of the cache loaded by the database manager.
load-address is the storage address (expressed in hexadecimal) where the cache was loaded.
System Action: Processing continues.
System Programmer Response: You may want to note the address for use in any potential problem
determination.