|
|
jobname BEA TMA vv.rr TCP For IMS has ended - RC = rc
|
| |
|
This message is issued during termination just before Oracle TMA TCP for IMS returns to z/OS.
jobname is the z/OS job name assigned to Oracle TMA TCP for IMS.
vv is the product version number.
rr is the product release number.
rc is a return code indicating the reason for termination. The most common return code is 24, indicating that termination occurred in response to a SHUTDOWN request.
|
| |
|
Oracle TMA TCP for IMS normally terminates in response to a SHUTDOWN request, in which case the return code is 24 and no special response is required.
If Oracle TMA TCP for IMS terminates with a return code other than 24, termination is the result of an abnormal condition. In that case, there should be other messages that provide additional information about the reason for the termination.
|
|
|
jobname BEA TMA vv.rr TCP For IMS starting
|
| |
|
This message is issued when Oracle TMA TCP for IMS begins execution.
jobname is the z/OS job name assigned to Oracle TMA TCP for IMS.
vv is the product version number.
rr is the product release number.
|
| |
|
|
|
|
jobname BEA TMA vv.rr TCP For IMS initialization complete
|
| |
|
This message is issued when Oracle TMA TCP for IMS has successfully completed initialization and is ready to begin normal processing.
jobname is the z/OS job name assigned to Oracle TMA TCP for IMS.
vv is the product version number.
rr is the product release number.
|
| |
|
|
|
|
BEA TMA vv.rr TCP For IMS is terminating (RSN= rc)
|
| |
|
This message is issued when Oracle TMA TCP for IMS begins the termination process (for example, in response to an operator SHUTDOWN command).
vv is the product version number.
rr is the product release number.
rc is a reason code indicating the reason for termination.
|
| |
|
Oracle TMA TCP for IMS normally terminates in response to a SHUTDOWN request, in which case the return code is 24 and no special response is required.
If Oracle TMA TCP for IMS terminates with a return code other than 24, termination is the result of an abnormal condition. In that case, there should be other messages that provide additional information about the reason for the termination.
|
|
|
Invalid IMS Client Request: description, Error( error-code), Reason( reason-code)
|
| |
|
An IMS client transaction has issued a request that is invalid.
description is a text description of the error detected.
error-code is the error code. For a description of error codes issued by Oracle TMA TCP for IMS, refer to the
Error and Reason Codes section.
reason-code is the reason code. For a description of reason codes issued by Oracle TMA TCP for IMS, refer to the
Error and Reason Codes section.
|
| |
|
Identify and correct the indicated problem.
|
|
|
IMS Client Request for Service( service) failed: Requested service not defined
|
| |
|
The requested service is not defined to Oracle TMA TCP for IMS.
service is the specified service name.
|
| |
|
The specified service is not defined in the Oracle TMA TCP for IMS configuration file. Ensure that the correct local service name is being specified, and that the service is properly defined in the configuration file with the specified local service name.
|
|
|
IMS Client Request for Service( service) failed: All outbound sessions busy
|
| |
|
All available outbound sessions with remote systems offering the service are currently in use (and no additional sessions can be started due to session limits).
service is the specified service name.
|
| |
|
Retry the request later. Increase the maximum number of outbound sessions defined for remote systems that offer the specified service.
|
|
|
Client Request routing error: Service( service-name), RC( rc)
|
| |
|
An internal error occurred while attempting to select a remote system and outbound session to process an IMS client request.
service-name is the specified service name.
rc is the return code returned by the GetServiceInfo() function.
|
| |
|
Report the error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Operator command unrecognized - rejected
|
| |
|
An operator command has been entered that is syntactically invalid.
|
| |
|
Correct and re-enter the command.
|
|
|
Operator request for SHUTDOWN accepted
|
| |
|
Oracle TMA TCP for IMS has recognized and accepted an operator request to initiate shutdown processing.
|
| |
|
Oracle TMA TCP for IMS begins the process of terminating.
|
| |
|
|
|
|
Initializing IMS interface
|
| |
|
This message is issued during initialization to indicate that the interface with IMS (i.e., via the IMS message queue) is being initialized.
|
| |
|
|
|
|
Abnormal return from IMS function request - Status = ss
|
| |
|
An IMS API call has returned an abnormal or unexpected status code.
function is the IMS function code: GU (Get Unique) GN (Get Next) CHNG (Change) ISRT (Insert) PURG (Purge) CHKP (Checkpoint).
ss is the status code from the program control block (PCB).
|
| |
|
Identify the type of error and determine the reason for it. For example, the error may be the result of a temporary change in the IMS configuration.
|
|
|
Open failed for Message Log: DDNAME( ddname)
|
| |
|
Oracle TMA TCP for IMS was unable to open the message log.
ddname is the DDNAME of the message log dataset.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Verify that the correct DDNAME is coded in the JCL for Oracle TMA TCP for IMS and that the message log dataset has the correct attributes.
|
|
|
Initializing network (TCP/IP) interface
|
| |
|
This message is issued during initialization to indicate that the TCP/IP network interface is being initialized. This includes starting a Listener session for each local gateway defined in the Oracle TMA TCP for IMS configuration file.
|
| |
|
|
|
|
Terminating network (TCP/IP) interface
|
| |
|
This message is issued during termination to indicate that the TCP/IP network interface is being terminated. This involves: - terminating active inbound sessions - terminating active outbound sessions - terminating Listener sessions
|
| |
|
|
|
|
ssss Inbound Sessions are no longer being accepted by LMID( lmid,L)
|
| |
|
The Listener for the specified logical machine ID is being stopped; inbound TCP/IP connection requests are no longer accepted by this LMID.
ssss is the socket ID assigned to the Listener by TCP/IP.
lmid is the logical machine ID of the local gateway.
|
| |
|
|
|
|
Starting Listener for LMID( lmid,L), IP( ip-address), Port( port-number)
|
| |
|
A Listener is being started for the local gateway to accept TCP/IP connection requests from remote systems.
lmid is the logical machine ID of the local gateway.
ip-address is the IP address at which TCP/IP connection requests are accepted. If an asterisk (*) appears, connection requests are accepted through any available network interface on the machine.
port-number is the port number at which TCP/IP connection requests are accepted.
|
| |
|
|
|
|
Unable to allocate Session Control Block for Listener
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage for an internal control block used to manage a Listener session.
|
| |
|
This is an abnormal condition indicating a severe storage shortage or corruption of the storage allocation control blocks. It may be necessary to terminate Oracle TMA TCP for IMS (preferably with a dump) to identify and correct the problem.
|
|
|
ssss LMID( lmid,L) is accepting TCP/IP connection requests at IP( ip-address), Port( port-number)
|
| |
|
A Listener was successfully started for a local gateway and is ready to accept inbound TCP/IP connection requests from remote systems.
ssss is the socket ID assigned to the Listener by TCP/IP.
lmid is the logical machine ID of the local gateway.
ip-address is the IP address at which TCP/IP connection requests are accepted. If an asterisk (*) appears, connection requests are accepted through any available network interface.
port-number is the port number on which TCP/IP connection requests are accepted.
|
| |
|
|
|
|
ssss Inbound TCP/IP connection request received for LMID( lmid,L) from IP( ip-address: host-name)
|
| |
|
A TCP/IP connection request was received from a remote system for a local gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway receiving the request.
ip-address is the IP address of the remote system making the request.
host-name is the network name of the remote system making the request. TCP/IP obtains this information from a domain name server or from a local /etc/hosts file. If the name of the remote host cannot be determined, "Unknown" is displayed.
|
| |
|
|
|
|
ssss Inbound TCP/IP connection request rejected: Session limit ( max-sessions) exceeded
|
| |
|
A TCP/IP connection request from a remote system was rejected because the local gateway is already operating at the specified maximum number of concurrent, inbound sessions.
ssss is the socket ID assigned to the connection by TCP/IP.
max-sessions is the maximum number of concurrent, active inbound sessions supported by the local gateway.
|
| |
|
If necessary, increase the maximum number of inbound sessions for the local gateway (defined by the SESSIONS parameter in the GATEWAY TYPE=LOCAL statement).
|
|
|
ssss Unable to allocate Session Control Block for Inbound Session
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage for an internal control block used to manage an inbound session.
ssss is the socket ID assigned to the connection by TCP/IP.
|
| |
|
This is an abnormal condition indicating a severe storage shortage or corruption of the storage allocation control blocks. It may be necessary to terminate Oracle TMA TCP for IMS (preferably with a dump) to identify and correct the problem.
|
|
|
ssss Inbound TCP/IP connection accepted by LMID( lmid,L( port)) from R( ip-address: port)
|
| |
|
An inbound TCP/IP connection from a remote system has been accepted by a local gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the port for logical machine ID of the local gateway accepting the connection.
port is the port for the local gateway accepting the connection.
ip-address: port is the IP address and port for the remote system making the connection.
|
| |
|
|
|
|
Requesting outbound TCP/IP connection with LMID( lmid,R) at IP( ip-address), Port( port-number)
|
| |
|
The local gateway is attempting to establish an outbound TCP/IP connection with a remote system.
lmid is the logical machine ID of the remote gateway.
ip-address is the IP address of the remote gateway.
port-number is the port number of the remote gateway.
|
| |
|
|
|
|
ssss Unable to establish TCP/IP connection with LMID( lmid,R)
|
| |
|
The local gateway failed to establish an outbound TCP/IP connection with a remote system.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
|
| |
|
|
|
|
ssss Received message length ( rcvd-length) exceeds maximum allowed on session ( max-length)
|
| |
|
The local gateway received a gateway message whose length exceeds the maximum allowed for the session.
ssss is the socket ID assigned to the connection by TCP/IP.
rcvd-length is the length of the message received.
max-length is the maximum message length allowed on the session.
|
| |
|
The session is terminated.
|
| |
|
This error can be caused by any of the following:
- The configurations of the local and/or remote gateways may be incorrect or inconsistent with respect to the maximum message length allowed. The maximum message length of the local gateway is specified by the MAXMSGLEN parameter on the GATEWAY TYPE=LOCAL statement.
- The remote gateway may not be properly configured to connect to an IMS gateway. In particular, the remote gateway may be configured incorrectly to connect to a CICS gateway.
- Some other TCP/IP application (i.e., not a Oracle Tuxedo Mainframe Adapter gateway) may be attempting to connect to the IP address and port number used by Oracle TMA TCP for IMS. Check the configuration and verify that Oracle TMA TCP for IMS is not using an IP address and port number which are also being used by another TCP/IP application.
|
|
|
ssss Message header length ( length) is not valid
|
| |
|
The local gateway received a gateway message containing an invalid header length.
ssss is the socket ID assigned to the connection by TCP/IP.
length is the length of the message header received.
|
| |
|
The session is terminated.
|
| |
|
This error may be caused by any of the following:
- The versions of the local and remote gateways may be incompatible.
- Some other TCP/IP application (i.e., not a Oracle Tuxedo Mainframe Adapter gateway) may be attempting to connect to the IP address and port number used by Oracle TMA TCP for IMS. Check the configuration and verify that Oracle TMA TCP for IMS is not using an IP address and port number which is also being used by another TCP/IP application.
|
|
|
ssss Message length ( length) is not valid
|
| |
|
The local gateway received a gateway message whose overall length is invalid (the total length is less than the length of the message header).
ssss is the socket ID assigned to the connection by TCP/IP.
length is the length of the gateway message received.
|
| |
|
The session is terminated.
|
| |
|
Contact your Oracle TMA TCP for IMS system programmer.
|
|
|
ssss IMS Client Request timed out: LMID( lmid,R), Service( service)
|
| |
|
An IMS client request was sent to a remote system for processing, but no response was received within a specified period of time.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
service is the remote name of the service requested (i.e., the name of the service as defined on the remote system).
|
| |
|
Oracle TMA TCP for IMS aborts the request and schedules the specified IMS response transaction with the appropriate return codes.
|
| |
|
The remote system may be experiencing problems, or may be extremely busy. An adjustment to the time out value may resolve this problem.
|
|
|
ssss Allocation failed for buffer (size = buffer-size)
|
| |
|
Oracle TMA TCP for IMS is unable to allocate a buffer of the specified size for a gateway message.
ssss is the socket ID assigned to the connection by TCP/IP (this field is blank if there is no associated connection).
buffer-size is the size of the requested buffer.
|
| |
|
The session is terminated.
|
| |
|
Assuming a reasonable buffer size, this is an abnormal condition indicating a severe storage shortage or corruption of the storage allocation control blocks. It may be necessary to terminate Oracle TMA TCP for IMS (preferably with a dump) to identify and correct the problem.
|
|
|
ssss IMS Server Request failed - Invalid IMS transaction code: Service( service-name)
|
| |
|
Oracle TMA TCP for IMS received an abnormal return from IMS (PCB Status Code = "A1") while attempting to insert a server request message into the IMS message queue.
ssss is the socket ID assigned to the connection by TCP/IP.
service-name is the name of the requested service (i.e., the IMS transaction code for the server transaction).
|
| |
|
The request fails. This message is also returned to the remote gateway as part of a negative response to the request.
|
| |
|
The requested service name must be the (correct) IMS transaction code for the server transaction that processes the request. Check the remote configuration and verify that a valid IMS transaction name is specified as the remote service name.
|
|
|
ssss Shutdown requested by client transaction: Type( type)
|
| |
|
A client transaction requested a shutdown of the IMS gateway. Note that this request can be made either by a remote (e.g., Oracle TUXEDO) client or an IMS server transaction if CLIENTSHUTDOWN is set to Yes.
ssss is the socket ID assigned to the connection by TCP/IP.
type is the type of shutdown requested: STOP - Normal shutdown DUMP - User 3166 abend with dump
|
| |
|
Oracle TMA TCP for IMS initiates shutdown processing.
|
| |
|
Assuming that this is a valid request, no response is required.
|
|
|
ssss IMS Server Request (size= size) exceeds maximum supported IMS message length ( max-length)
|
| |
|
Oracle TMA TCP for IMS received a server request which is too large to be formatted into a single IMS message segment for insertion into the IMS message queue.
ssss is the socket ID assigned to the connection by TCP/IP.
size is the length of the request message received.
max-length is the maximum supported length of an IMS message segment.
|
| |
|
|
| |
|
Server requests are limited by the maximum supported IMS message segment length.
|
|
|
Logging IMS Server Response: mmddyyyy.hhmmss.nnnnnn ( reason)
|
| |
|
Oracle TMA TCP for IMS is unable to correlate a response message returned by an IMS server transaction with a pending, active request. Each server request and response message is identified by a timestamp consisting of the date and time that Oracle TMA TCP for IMS was started and a unique serial number:
mm month (1-12) dd day (1-31) yyyy year hh hour (0-23) mm minute (0-59) ss second (0-59) nnnnnn serial number reason specifies the reason that the response is being logged.
|
| |
|
The response message is logged in the server response log dataset.
|
| |
|
If the reason is "Server Request not found", one of the following occurred:
- Oracle TMA TCP for IMS was restarted after the server request was sent to IMS but before the response was received. This message may be issued following a restart of Oracle TMA TCP for IMS if server requests were in progress at the time Oracle TMA TCP for IMS was terminated.
- The TCP/IP connection with the remote gateway was lost after the server request was sent to IMS but before the response was received.
- A server request timed out and was aborted (either by the local or the remote gateway) before the response was received from IMS.
|
| |
|
If the reason is "No response was expected", it indicates that an IMS server transaction issued a response to a request for which a response was not required. Correct the IMS server transaction. One other possible cause for this error is that Oracle TMA TCP for IMS was unable to identify an IMS client request and processed it as if it were an IMS server response. This can happen if an IMS client transaction improperly initializes the Oracle Client request header by failing to initialize the BEA-RESERVED1 field (BEA_Reserved1 in the C header file) to binary zero (low values).
|
|
|
ssss Invalid or unsupported request received by LMID( lmid,L): Opcode( opcode)
|
| |
|
Oracle TMA TCP for IMS received a gateway message from a remote gateway containing an invalid or unsupported request type.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is theological machine ID of the local gateway receiving the request.
opcode is a numeric value identifying the request type.
|
| |
|
The session is terminated. This message is also sent to the remote gateway as part of a negative response to the request.
|
| |
|
The local and remote gateways may be incompatible (different versions).
|
|
|
Unable to add service service-name, maximum service count reached.
|
| |
|
The maximum number of dynamically added services has been reached.
|
| |
|
The ADD SERVICE operator command is rejected.
|
| |
|
The service cannot be added dynamically. The Oracle TMA TCP for IMS gateway must be stopped and restarted before additional services can be added dynamically.
|
|
|
ssss CONNECT request received by LMID( lmid,L)
|
| |
|
Oracle TMA TCP for IMS received a CONNECT request from a remote gateway. A CONNECT request is issued to establish an inbound session with the local gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway receiving the request.
|
| |
|
|
|
|
ssss CONNECT request accepted by LMID( lmid,L)
|
| |
|
Oracle TMA TCP for IMS accepted a CONNECT request from a remote gateway. An inbound session has been established.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway receiving the request.
|
| |
|
|
|
|
Reserved for future use by Oracle TMA TCP for IMS.
|
|
|
ssss CONNECT request rejected by LMID( lmid,L): Not Authorized
|
| |
|
The local gateway rejected a CONNECT request from a remote gateway because the account ID and/or password presented is not correct.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway.
|
| |
|
The session is terminated. This message is also returned to the remote gateway as part of a negative response to the CONNECT request.
|
| |
|
Check the respective configurations of the local and remote gateways to verify that they are consistent with respect to account ID and/or password. If the local gateway definition specifies that no account ID and/or password are to be used (by coding an asterisk for the account ID and/or password), the remote gateway must present a blank (i.e., spaces) account ID and/or password.
|
|
|
ssss SHUTDOWN request received by LMID( lmid,L)
|
| |
|
Oracle TMA TCP for IMS received a SHUTDOWN request from a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway receiving the request.
|
| |
|
Oracle TMA TCP for IMS initiates termination processing.
|
| |
|
|
|
|
ssss DISCONNECT request received by LMID( lmid,L)
|
| |
|
Oracle TMA TCP for IMS received a DISCONNECT request from a remote gateway. A DISCONNECT request may be sent by a remote gateway to logically terminate a session.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway receiving the request.
|
| |
|
Oracle TMA TCP for IMS terminates the inbound session with the remote gateway. Note, however, that the TCP/IP connection is not affected and remains open. The remote gateway may issue a subsequent CONNECT request to establish a new inbound session, or it may close the TCP/IP connection at its option.
|
| |
|
|
|
|
ssss DISCONNECT request accepted by LMID( lmid,L)
|
| |
|
Oracle TMA TCP for IMS accepted a DISCONNECT request received from a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway receiving the request.
|
| |
|
This message is also returned to the remote gateway as part of a positive response to the DISCONNECT request.
|
| |
|
|
|
|
Inbound ( request/response) for LMID( lmid,L)
|
| |
|
A network message was received.
lmid is the logical machine ID of the local gateway receiving the request.
|
| |
|
|
| |
|
None required. This message is used only when MSGLEVEL is set to DEBUG(10).
|
|
|
ssss PING request received by LMID( lmid,L)
|
| |
|
Oracle TMA TCP for IMS received a PING request from a remote gateway. A PING request may be sent by a remote gateway to verify that a logical session exists and that the partner gateway is operative.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway receiving the request.
|
| |
|
|
|
|
PING response: jobname BEA TMA vv.rr TCP For IMS
|
| |
|
This message is returned to the remote gateway by Oracle TMA TCP for IMS in response to a PING request. This message is not logged.
jobname is the z/OS job name assigned to Oracle TMA TCP for IMS.
vv is the product version number.
rr is the product release number.
|
| |
|
|
|
|
ssss COMMAND received by LMID( lmid,L)
|
| |
|
Oracle TMA TCP for IMS has received a command from a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway receiving the request.
|
| |
|
The COMMAND request is not currently supported by Oracle TMA TCP for IMS and should not be sent by a remote gateway. (See ID: BEA2047E).
|
|
|
ssss Command rejected by LMID( lmid,L): Remote commands are not supported
|
| |
|
Oracle TMA TCP for IMS does not currently support commands sent by remote gateways.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway.
|
| |
|
Oracle TMA TCP for IMS ignores the request. This message is also returned to the remote gateway as part of a negative response to the COMMAND request.
|
| |
|
The remote gateway should not be sending commands. Check the configuration and version of the remote gateway to determine why this is occurring.
|
|
|
Allocating Buffer (size= n)
|
| |
|
An internal storage buffer was allocated.
|
| |
|
|
| |
|
None required. This message is used only when MSGLEVEL is set to DEBUG(10).
|
|
|
ssss Protocol error detected by LMID( lmid,L) on Inbound Session: Request( request), State( state)
|
| |
|
Oracle TMA TCP for IMS received a request from a remote gateway, but the session is currently in a state which is inconsistent with the request.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the local gateway receiving the request.
request is the type of request received: CONNECT, DISCONNECT, etc.
state is a numeric value corresponding to the current state of the session, as viewed by Oracle TMA TCP for IMS.
|
| |
|
Oracle TMA TCP for IMS takes no specific action. However, subsequent errors (including additional protocol errors) can occur, which likely leads to termination of the session. This message is also returned to the remote gateway as part of a negative response to the request.
|
| |
|
This error can occur if two gateways become "out of sync" on a session with respect to their respective states. If this error occurs frequently or persistently, notify the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
IMS Host hostname has been added.
|
| |
|
The ADD HOST operator command has completed successfully.
|
| |
|
|
| |
|
|
|
|
ssss Invalid or unsupported response received from LMID( lmid,R): Opcode( opcode)
|
| |
|
Oracle TMA TCP for IMS received a response message from a remote gateway on an outbound session that cannot be identified (that is, the Opcode in the Oracle Tuxedo Mainframe Adapter message header is not valid).
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
opcode is the numeric value of the Opcode in the Message Header.
|
| |
|
The session is terminated.
|
| |
|
If this error occurs, notify the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
ssss Issuing CONNECT request for LMID( lmid,R)
|
| |
|
Oracle TMA TCP for IMS is requesting an outbound session with a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
|
| |
|
|
|
|
ssss CONNECT request rejected by LMID( lmid,R): GWError( gwerror), GWMsg( gwmsg)
|
| |
|
Oracle TMA TCP for IMS received a negative response to a CONNECT request to establish an outbound session with a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
gwerror is the gateway error code returned by the remote gateway.
gwmsg is the gateway error message returned by the remote gateway.
|
| |
|
The CONNECT request fails and the TCP/IP connection with the remote gateway is terminated.
|
| |
|
Refer to the documentation for the remote gateway for information about the reason for the error. Also, consult the remote gateway's log file for additional information.
|
|
|
ssss CONNECT request accepted by LMID( lmid,R)
|
| |
|
Oracle TMA TCP for IMS has received a positive response to a CONNECT request to establish an outbound session with a remote gateway. The session is established and is ready to process requests.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
|
| |
|
|
|
|
ssss Issuing DISCONNECT for LMID( lmid,R)
|
| |
|
Oracle TMA TCP for IMS is ending an outbound session with a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
|
| |
|
|
|
|
ssss DISCONNECT rejected by LMID( lmid,R): GWError( gwerror), GWMsg( gwmsg)
|
| |
|
Oracle TMA TCP for IMS received a negative response to a DISCONNECT request to end an outbound session with a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
gwerror is the gateway error code returned by the remote gateway.
gwmsg is the gateway error message returned by the remote gateway.
|
| |
|
The session is terminated.
|
| |
|
Refer to the documentation for the remote gateway for information about the reason for the error. Also, consult the remote gateway's log file for additional information.
|
|
|
ssss DISCONNECT accepted by LMID( lmid,R)
|
| |
|
Oracle TMA TCP for IMS received a positive response to a DISCONNECT request to end an outbound session with a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
|
| |
|
|
|
|
ssss Sending PING request to LMID( lmid,R)
|
| |
|
Oracle TMA TCP for IMS is sending a PING request to a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
|
| |
|
|
|
|
ssss PING request rejected by LMID( lmid,R): GWError( gwerror), GWMsg( gwmsg)
|
| |
|
Oracle TMA TCP for IMS received a negative response to a PING request sent to a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
gwerror is the gateway error code returned by the remote gateway.
gwmsg is the gateway error message returned by the remote gateway.
|
| |
|
The session is terminated.
|
| |
|
Refer to the documentation for the remote gateway for information about the reason for the error. Also, consult the remote gateway's log file for additional information.
|
|
|
ssss PING response from LMID( lmid,R): response
|
| |
|
Oracle TMA TCP for IMS received a positive response to a PING request sent to a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway. response is the text of the response message returned by the remote gateway.
|
| |
|
|
|
|
ssss Sending command to LMID( lmid,R)
|
| |
|
Oracle TMA TCP for IMS is sending a command to a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
|
| |
|
|
|
|
ssss COMMAND rejected by LMID( lmid,R): GWError( gwerror), GWMsg( gwmsg)
|
| |
|
Oracle TMA TCP for IMS received a negative response to a command sent to a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
gwerror is the gateway error code returned by the remote gateway.
gwmsg is the gateway error message returned by the remote gateway.
|
| |
|
The session is terminated.
|
| |
|
Refer to the documentation for the remote gateway for information about the reason for the error. Also, consult the remote gateway's log file for additional information.
|
|
|
ssss Unable to allocate buffer for IMS Client Request (size= buffer-size)
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage for an internal buffer required to process an IMS client request.
ssss is the socket ID assigned to the connection by TCP/IP.
buffer-size is the size of the required buffer.
|
| |
|
This is an abnormal condition indicating a severe storage shortage or corruption of the storage allocation control blocks. It may be necessary to terminate Oracle TMA TCP for IMS (preferably with a dump) to identify and correct the problem.
|
|
|
ssss IMS Client Request sent to LMID( lmid,R) failed: GWError( gwerror), GWMsg( gwmsg)
|
| |
|
Oracle TMA TCP for IMS received a negative response to an IMS client request sent to a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the remote gateway.
gwerror is the gateway error code returned by the remote gateway.
gwmsg is the gateway error message returned by the remote gateway.
|
| |
|
The specified IMS client response transaction is scheduled with the appropriate return codes.
|
| |
|
Refer to the documentation for the remote gateway for information about the reason for the error. Also, consult the remote gateway's log file for additional information.
|
|
|
ssss State error on inout Session: LMID( lmid, type), Request( request), State( state)
|
| |
|
Oracle TMA TCP for IMS attempted to execute an operation against a session which is not currently in a state consistent with the requested operation.
ssss is the socket ID assigned to the connection by TCP/IP.
inout session type: inbound or outbound.
lmid is the logical machine ID of the gateway.
type is the gateway type: L (local) or R (remote).
request is the request type: CONNECT, DISCONNECT, etc.
state describes the current state of the session.
|
| |
|
The session is terminated.
|
| |
|
Refer this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Unable to allocate Session Control Block for Outbound Session
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage for an internal control block required to manage an outbound session.
|
| |
|
This is an abnormal condition indicating a severe storage shortage or corruption of the storage allocation control blocks. It may be necessary to terminate Oracle TMA TCP for IMS (preferably with a dump) to identify and correct the problem.
|
|
|
ssss TCP/IP connection closed by session partner
|
| |
|
Oracle TMA TCP for IMS was notified that a TCP/IP connection with a remote system was closed by the session partner.
ssss is the socket ID assigned to the connection by TCP/IP.
|
| |
|
The session is terminated.
|
| |
|
|
|
|
ssss TCP/IP connection reset
|
| |
|
Oracle TMA TCP for IMS was notified that a connection with a remote system was reset. A reset occurs when the connection is hard-closed (i.e., closed without first issuing a TCP/IP shutdown request).
ssss is the socket ID assigned to the connection by TCP/IP.
|
| |
|
The session is terminated.
|
| |
|
|
|
|
ssss Length error on socket read
|
| |
|
TCP/IP reported an illogical length read from a connection; for example, the length reported was greater than the actual length requested.
ssss is the socket ID assigned to the connection by TCP/IP.
|
| |
|
The session is terminated.
|
| |
|
This error may indicate a problem with TCP/IP for z/OS.
|
|
|
ssss Abnormal return from TCP/IP API request: fcn( function), rc( rc), errno( errno)
|
| |
|
Oracle TMA TCP for IMS received an abnormal return from a TCP/IP socket operation.
ssss is the socket ID assigned to the connection by TCP/IP.
function is the TCP/IP API function called: read, write, etc.
rc is the TCP/IP return code (usually -1).
errno is the TCP/IP errno value returned.
|
| |
|
The session is terminated.
|
| |
|
Consult the IBM TCP/IP for z/OS documentation for a description of possible errno values and their meanings.
|
|
|
ssss Session termination in progress (RSN= reason)
|
| |
|
Oracle TMA TCP for IMS has initiated termination of a session with a remote gateway.
ssss is the socket ID assigned to the connection by TCP/IP.
reason is a numeric value indicating the reason the session is being terminated. Some typical reason codes are: 12 A socket error occurred.
16 The connection was closed by the session partner. 20 An internal gateway request (such as CONNECT) timed out. 24 BEA TMA TCP for IMS is terminating in response to a SHUTDOWN request. 28 Session limit exceeded (a new session cannot be started). 60 A session protocol error occurred.
|
| |
|
This action typically occurs as the result of a session-related error condition (identified by the reason code), or in conjunction with a SHUTDOWN request. If a reason code other than one of those previously listed is given, the error should be reported to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
ssss TCP/IP connection closed
|
| |
|
As part of the session termination process, Oracle TMA TCP for IMS successfully closed the TCP/IP connection. ssss is the socket ID assigned to the connection by TCP/IP.
|
| |
|
|
|
|
ssss Session termination complete
|
| |
|
A session was successfully terminated by Oracle TMA TCP for IMS.
ssss is the socket ID assigned to the connection by TCP/IP.
|
| |
|
|
|
|
Error writing to Server Response Log File
|
| |
|
Oracle TMA TCP for IMS received an abnormal return attempting to write a record to the server response log file.
|
| |
|
Check the server response log file to ensure that it is allocated with the correct dataset attributes, allocated using the correct DDNAME, and is not full or experiencing I/O errors.
|
|
|
Open failed for server response log file: DDNAME( ddname)
|
| |
|
Oracle TMA TCP for IMS is not able to open the Server Response Log File.
ddname is the DDNAME used by Oracle TMA TCP for IMS to open the dataset.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Check the server response log file to ensure that it is allocated with the correct dataset attributes and is allocated using the correct DDNAME as shown.
|
|
|
ssss IMS Server Request received with previous request pending (timeout assumed)
|
| |
|
Oracle TMA TCP for IMS received an IMS server request from a remote gateway, but a prior request is still pending (i.e., currently being serviced by IMS).
ssss is the socket ID assigned to the connection by TCP/IP.
|
| |
|
Oracle TMA TCP assumes that the remote gateway timed out while waiting for a response to the previous request. Therefore, the previous request (currently being serviced by IMS) is aborted (discarded) and Oracle TMA TCP for IMS begins processing the new request.
|
| |
|
This error can occur when a remote gateway cancels a previously sent request (i.e., due to timeout) and immediately sends another request.
|
|
|
ssss Pending IMS Server Request for Service( service) aborted
|
| |
|
Oracle TMA TCP for IMS aborted processing of the current server request.
ssss is the socket ID assigned to the connection by TCP/IP.
service is the name of the IMS server transaction scheduled to process the current request.
|
| |
|
The current request is discarded and the session is ready to accept a new request.
|
| |
|
|
|
|
ssss IMS Server Request timed out: Service( service)
|
| |
|
An IMS server request requiring a response was being processed by IMS, but no response was received within a specified period of time.
ssss is the socket ID assigned to the connection by TCP/IP.
service is the name of the IMS server transaction scheduled to process the request.
|
| |
|
The request is aborted. This message is also returned to the remote gateway as part of a negative response to the request.
|
| |
|
Check the IMS server transaction (service) that processes the request to make sure that it is not stopped or has an unusually high backlog.
|
|
|
Client Response failed: Sense Code= sc Reason= reason
|
| |
|
A response to a client request was rejected by OTMA.
reason is a numeric value indicating the reason for the response failure.
|
| |
|
|
| |
|
Consult the IMS Open Transaction Manager Access Guide to determine the cause of the error.
|
|
|
Malloc failed for parse work area
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage for an internal work area used to parse the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Report this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
|
| |
|
Displays the contents of the IOPCB after a CHKP DLI call.
|
| |
|
|
| |
|
None required. This message is used only when MSGLEVEL is set to DEBUG(10).
|
|
|
Missing LMID option for REMOTE GATEWAY
|
| |
|
A required keyword parameter (LMID) was omitted from a GATEWAY TYPE=REMOTE statement in the configuration File.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Missing HOSTADDR option for REMOTE GATEWAY
|
| |
|
A required keyword parameter (HOSTADDR) was omitted from a GATEWAY TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Missing PORT option for REMOTE GATEWAY
|
| |
|
A required keyword parameter (PORT) was omitted from a GATEWAY TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
NAME option is invalid for REMOTE GATEWAY
|
| |
|
An invalid keyword parameter (NAME) was specified on a GATEWAY TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
TIMEOUT option is invalid for REMOTE GATEWAY
|
| |
|
An invalid keyword parameter (TIMEOUT) was specified on a GATEWAY TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Cannot malloc for Remote Host
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage for an internal control block used to manage a remote gateway.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Report this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Missing LMID option for LOCAL GATEWAY
|
| |
|
A required keyword parameter (LMID) was omitted from a GATEWAY TYPE=LOCAL statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Missing HOSTADDR option for LOCAL GATEWAY
|
| |
|
A required keyword parameter (HOSTADDR) was omitted from a GATEWAY TYPE=LOCAL statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Missing PORT option for LOCAL GATEWAY
|
| |
|
A required keyword parameter (PORT) was omitted from a GATEWAY TYPE=LOCAL statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Missing ACCOUNT option for LOCAL GATEWAY
|
| |
|
A required keyword parameter (ACCOUNT) was omitted from a GATEWAY TYPE=LOCAL statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Missing PASSWORD option for LOCAL GATEWAY
|
| |
|
A required keyword parameter (PASSWORD) was omitted from a GATEWAY TYPE=LOCAL statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
NAME option is invalid for LOCAL GATEWAY
|
| |
|
An invalid keyword parameter (NAME) was specified on a GATEWAY TYPE=LOCAL statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
TIMEOUT option is invalid for LOCAL GATEWAY
|
| |
|
An invalid keyword parameter (TIMEOUT) was specified on a GATEWAY TYPE=LOCAL statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Cannot malloc for Local Host
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage for an internal control block used to manage the local gateway.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Report this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Missing LMID option for REMOTE SERVICE
|
| |
|
A required keyword parameter (LMID) was omitted from a SERVICE TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
HOSTADDR option is invalid for REMOTE SERVICE
|
| |
|
An invalid keyword parameter (HOSTADDR) was specified on a SERVICE TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
PORT option is invalid for REMOTE SERVICE
|
| |
|
An invalid keyword parameter (PORT) was specified on a SERVICE TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
ACCOUNT option is invalid for REMOTE SERVICE
|
| |
|
An invalid keyword parameter (ACCOUNT) was specified on a SERVICE TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
PASSWORD option is invalid for REMOTE SERVICE
|
| |
|
An invalid keyword parameter (PASSWORD) was specified on a SERVICE TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
MAXMSGLEN option is invalid for REMOTE SERVICE
|
| |
|
An invalid keyword parameter (MAXMSGLEN) was specified on a SERVICE TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
SESSIONS option is invalid for REMOTE SERVICE
|
| |
|
An invalid keyword parameter (SESSIONS) was specified on a SERVICE TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Missing NAME option for REMOTE SERVICE
|
| |
|
A required keyword parameter (NAME) was omitted from a SERVICE TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Missing TIMEOUT option for REMOTE SERVICE
|
| |
|
A required keyword parameter (TIMEOUT) was omitted from a SERVICE TYPE=REMOTE statement in the configuration file.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the problem and restart Oracle TMA TCP for IMS.
|
|
|
Cannot malloc for Work Service
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage used to process remote service definitions.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Report this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Cannot malloc for CurrWorkSer Info
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage used to process remote service definitions.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Report this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
The command lines which are in error are: text
|
| |
|
When a syntax error is detected during processing of the configuration file, Oracle TMA TCP for IMS displays the lines containing the error.
text is the line containing the text in error.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the error and restart Oracle TMA TCP for IMS.
|
|
|
Cannot malloc for ServiceKeys
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage used to process remote service definitions.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Report this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Could not find LMID [ lmid] for Service [ service]
|
| |
|
The logical machine ID (LMID) specified on a SERVICE TYPE=REMOTE statement could not be matched with a GATEWAY TYPE=REMOTE statement specifying the same (matching) LMID in the configuration file.
lmid is the logical machine ID specified in the SERVICE TYPE=REMOTE statement.
service is the local service name specified in the SERVICE TYPE=REMOTE statement.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Each Remote Service must be associated with a particular remote gateway (identified by a unique logical machine ID) that provides the service. Check the GATEWAY TYPE=REMOTE and SERVICE TYPE=REMOTE statements to verify that they specify the same logical machine ID. Correct any errors and restart Oracle TMA TCP for IMS.
|
|
|
Syntax error in configuration file, line line-no
|
| |
|
A syntax error was detected during processing of the configuration file.
line-no is the line number of the line containing the syntax error.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the error and restart Oracle TMA TCP for IMS.
|
|
|
|
| |
|
This message is displayed in conjunction with message BEA2110E.
text is the line containing the text in error.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Correct the error and restart Oracle TMA TCP for IMS.
|
|
|
Open failed for configuration file: DDNAME( ddname)
|
| |
|
Oracle TMA TCP for IMS was unable to open the configuration file.
ddname is the logical dataset name of the configuration file dataset.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Verify that the correct DDNAME is coded in the JCL for Oracle TMA TCP for IMS and that the configuration file dataset has the correct attributes.
|
|
|
jobname BEA TMA vv.rr TCP For IMS ready
|
| |
|
This message is issued by Oracle TMA TCP for IMS in conjunction with an outstanding WTOR which can be used to enter operator commands.
jobname is the z/OS job name assigned to Oracle TMA TCP for IMS.
vv is the product version number.
rr is the product release number.
|
| |
|
None required. You can reply to the associated WTOR to enter an operator command for Oracle TMA TCP for IMS.
|
|
|
ssss Session TIMEOUT detected on LMID( lmid, type)
|
| |
|
This message is issued by Oracle TMA TCP for IMS when an IDLE TIMEOUT has occurred.
ssss is the socket ID assigned to the connection by TCP/IP.
lmid is the logical machine ID of the gateway.
type is the gateway type: L (local) or R (remote).
|
| |
|
Refer this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Service service-name for IMSID logical-IMS-identifier has been added.
|
| |
|
The ADD SERVICE operator command for a local service has completed successfully.
service-name is the local service name which is passed to IMS as the transaction name.
logical-IMSID-identifier is a symbolic name that uniquely identifies an IMS system definition. This name must match a logical IMS ID (IMSID) specified in a HOST, TYPE=IMS statement.
|
| |
|
|
| |
|
|
|
|
|
|
|
IMS Host IMSID has been modified.
|
| |
|
The MOD HOST operator command has completed successfully. IMSID is a symbolic name that uniquely identifies the IMS system definition.
|
| |
|
|
| |
|
|
|
|
IMS Host IMSID has been modified.
|
| |
|
The MOD HOST operator command has completed successfully.
IMSID is a symbolic name that uniquely identifies the IMS system definition.
|
| |
|
|
| |
|
|
|
|
IMS Host must be stopped prior to modifying.
|
| |
|
The STOP HOST command must be issued before entering the MOD HOST command.
|
| |
|
The MOD HOST command is aborted.
|
| |
|
Enter the STOP HOST command and then retry the MOD HOST command.
|
|
|
Missing IMSID option for MOD HOST.
|
| |
|
The IMSID parameter was omitted and is required.
|
| |
|
The MOD HOST command is aborted.
|
| |
|
Enter the IMSID parameter and then retry the MOD HOST command.
|
|
|
Allocation failed for OTMA Work Area
|
| |
|
Upon initialization of the OTMA interface, Oracle TMA TCP for IMS was unable to allocate storage used to interface with OTMA.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Refer this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Terminating OTMA interface
|
| |
|
During shutdown, Oracle TMA TCP for IMS prepares to close its connection with OTMA.
|
| |
|
The OTMA interface is closed and its associated resources are returned to the system.
|
| |
|
|
|
|
|
| |
|
During configuration file processing, a hostname for a local or remote gateway could not be resolved by the domain name server or the local host file.
|
| |
|
If the error occurs during initialization, Oracle TMA TCP for IMS terminates. If the error occurs during the dynamic addition of a gateway, the gateway is not added.
|
| |
|
Check the hostname to verify spelling. Contact your network administrator to verify the hostname or change the hostname if necessary.
|
|
|
Host address for hostname is IP-address
|
| |
|
A hostname in the configuration file has been resolved to the following IP address.
|
| |
|
|
| |
|
|
|
|
|
| |
|
The initial communication between Oracle TMA TCP for IMS and the IMS OTMA interface failed.
|
| |
|
Initialization of the OTMA interface fails.
|
| |
|
Verify that the OTMA interface for the IMS system you want to access is enabled and that the OTMAGROUP parameter defined for Oracle TMA TCP for IMS matches the XCF group defined to IMS.
|
|
|
|
| |
|
Informational message only displayed when message level is set to DEBUG(10).
|
| |
|
|
| |
|
|
|
|
|
| |
|
Informational message only displayed when message level is set to DEBUG(10).
|
| |
|
|
| |
|
|
|
|
|
| |
|
Informational message only displayed when message level is set to DEBUG(10).
|
| |
|
|
| |
|
|
|
|
XCF Status with IMS Client OTMANAME= status
|
| |
|
Response message to the STATUS operator command.
status is one of the following: ACTIVE, UNKNOWN, ERROR, RESET, or BID SENT
|
| |
|
|
| |
|
|
|
|
Processing input from file filename
|
| |
|
Response message to the INFILE operator command.
|
| |
|
|
| |
|
|
|
|
Writing Configuration to file filename
|
| |
|
Response message to the CHKPT CONFIG operator command.
|
| |
|
|
| |
|
|
|
|
Open failed for Checkpoint File: filename
|
| |
|
The filename given in the CHKPT CONFIG operator command was not a valid file name or the file could not be created.
|
| |
|
The configuration checkpoint is aborted.
|
| |
|
Check the file name and re-enter the command. Contact the system programmer responsible for Oracle TMA TCP for IMS to check for availability of DASD resources.
|
|
|
Configuration checkpoint complete
|
| |
|
Normal response to a CHKPT CONFIG operator command.
|
| |
|
|
| |
|
|
|
|
Error opening file filename
|
| |
|
The file name entered with the INFILE operator command could not be opened.
|
| |
|
The INFILE command processing is aborted.
|
| |
|
Check the file name and retry if it is correct. Resolve any contention issues with other processes needing exclusive access to the file.
|
|
|
|
| |
|
The LMID for a gateway definition is not a unique name. No two gateways can share the same LMID.
|
| |
|
If the error occurs during Oracle TMA TCP for IMS startup, initialization aborts. If the error occurs while dynamically adding a gateway, the gateway is not added.
|
| |
|
Change the LMID to a unique name.
|
|
|
Gateway lmid has been added
|
| |
|
This is the normal response to an ADD GATEWAY operator command.
lmid is the logical machine ID specified for the ADD GATEWAY command.
|
| |
|
|
| |
|
|
|
|
Missing LMID option for MOD GATEWAY
|
| |
|
The LMID option is required for a MOD GATEWAY operator command.
|
| |
|
The command action is aborted.
|
| |
|
Add the LMID parameter to the command and retry.
|
|
|
|
| |
|
The LMID parameter entered in a MOD GATEWAY or MOD SERVICE command is not a currently defined gateway.
lmid is the logical machine ID specified for the MOD command.
|
| |
|
The MOD command is aborted.
|
| |
|
Change the LMID to match the name of the defined gateway to be modified.
|
|
|
Gateway must be stopped prior to modifying
|
| |
|
A MOD GATEWAY operator command was issued prior to stopping the gateway with a STOP GATEWAY command.
|
| |
|
The MOD command processing is aborted.
|
| |
|
Issue a STOP GATEWAY command and retry the MOD GATEWAY command.
|
|
|
Gateway lmid has been modified
|
| |
|
This is the normal response to a MOD GATEWAY operator command.
lmid is the logical machine ID specified for the MOD GATEWAY command.
|
| |
|
|
| |
|
|
|
|
Gateway lmid has been started
|
| |
|
This is the normal response to a START GATEWAY command.
lmid is the logical machine ID specified for the START GATEWAY command.
|
| |
|
|
| |
|
|
|
|
Gateway lmid is being stopped
|
| |
|
This is the initial response to a STOP GATEWAY operator command.
lmid is the logical machine ID specified for the STOP GATEWAY command.
|
| |
|
All outstanding messages are allowed to continue processing unless the IMMED=YES option was specified. All sessions for the gateway are then closed.
|
| |
|
|
|
|
Gateway lmid has been stopped
|
| |
|
The STOP GATEWAY command has completed stopping the gateway.
lmid is the logical machine ID specified for the STOP GATEWAY command.
|
| |
|
|
| |
|
|
|
|
Local Service Name not Unique
|
| |
|
A service of the same name exists for the LMID associated with this service.
|
| |
|
If the error occurs during Oracle TMA TCP for IMS startup, initialization aborts and the program terminates. If the error occurs during processing of an ADD SERVICE operator command, command processing aborts.
|
| |
|
Choose a unique name for the service and retry the command.
|
|
|
Service service-name for LMID lmid has been added
|
| |
|
This is the normal response to an ADD SERVICE operator command.
service is the local service name specified in the SERVICE TYPE=REMOTE statement.
lmid is the logical machine ID specified for the ADD SERVICE command.
|
| |
|
|
| |
|
|
|
|
Service service-name for LMID lmid is invalid
|
| |
|
The service name specified in the MOD SERVICE operator command does not exist, or the LMID is incorrect.
service is the local service name specified in the SERVICE TYPE=REMOTE statement.
lmid is the logical machine ID specified for the MOD SERVICE command.
|
| |
|
The MOD SERVICE command processing aborts.
|
| |
|
Correct the error and retry the command.
|
|
|
Service must be stopped prior to modifying
|
| |
|
A MOD SERVICE operator command was entered prior to stopping the service with a STOP SERVICE command.
|
| |
|
The MOD SERVICE command processing aborts.
|
| |
|
Issue a STOP SERVICE command and retry the MOD SERVICE command.
|
|
|
Service service-name for LMID lmid has been modified
|
| |
|
This is the normal response for a MOD SERVICE operator command.
service is the local service name specified in the SERVICE TYPE=REMOTE statement.
lmid is the logical machine ID specified for the MOD SERVICE command.
|
| |
|
|
| |
|
|
|
|
System parameters have been modified
|
| |
|
This is the normal response to a MOD SYSTEM operator command.
|
| |
|
|
| |
|
|
|
|
Inbound TCP/IP connection refused: MCB Error
|
| |
|
A connection attempt from a remote gateway was rejected because of a shortage of message control blocks probably due to an allocation of system resource failure.
|
| |
|
The connection is refused.
|
| |
|
Refer this error to the system programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Security Violation: Tran= tran-id, UserID= userid, GroupID= groupid, TermID= terminalid
|
| |
|
A request to execute a transaction on behalf of the given userid failed authorization.
|
| |
|
A security error response is returned to the requestor.
|
| |
|
None required. The message is given for auditing purposes only.
|
|
|
XCF Send Failed Ret= return-code Rsn= reason-code
|
| |
|
An attempt to send a message to OTMA failed.
|
| |
|
A system error response is sent back to the requestor.
|
| |
|
Verify the OTMA system parameters, correct any errors, and retry. If the error persists, refer this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Message rejected by LMID( lmid,L) on Inbound Session - Gateway Stopped
|
| |
|
A new request was received by a gateway in a stopping condition.
lmid is the logical machine ID specified for the MOD SERVICE command.
|
| |
|
A system error response is sent to the requestor.
|
| |
|
|
|
|
Service service-name for LMID lmid has been started
|
| |
|
This is the normal response for a START SERVICE operator command.
service-name is the name of the requested service (i.e., the IMS transaction code for the server transaction).
lmid is the logical machine ID specified for the gateway.
|
| |
|
|
| |
|
|
|
|
Service service-name for LMID lmid is being stopped
|
| |
|
This is the initial response to a STOP SERVICE operator command.
service-name is the name of the requested service (i.e., the IMS transaction code for the server transaction).
lmid is the logical machine ID specified for the gateway.
|
| |
|
All outstanding requests are allowed to continue processing unless the IMMED=YES option was specified.
|
| |
|
|
|
|
Service service-name for LMID lmid has been stopped
|
| |
|
This is the normal response to a STOP SERVICE operator command.
service-name is the name of the requested service (i.e., the IMS transaction code for the server transaction).
lmid is the logical machine ID specified for the gateway.
|
| |
|
|
| |
|
|
|
|
Response received for previously timed out request
|
| |
|
A response was received for a request for which timeout processing had already initiated.
|
| |
|
|
| |
|
|
|
|
Hostname maximum length (256) exceeded.
|
| |
|
The hostname string used in the HOSTADDR gateway parameter is too long.
|
| |
|
If the error occurs during Oracle TMA TCP for IMS startup, initialization aborts. If the error occurs while dynamically adding a gateway, the gateway is not added.
|
| |
|
Contact your network administrator to provide a new hostname less than 256 characters, or use the IP address in dotted decimal format.
|
|
|
Maximum number of hostnames (256) exceeded.
|
| |
|
More than 256 gateways were defined in the configuration using the hostname option of the HOSTADDR parameter.
|
| |
|
If the error occurs during Oracle TMA TCP for IMS startup, initialization aborts. If the error occurs while dynamically adding a gateway, the gateway is not added.
|
| |
|
Refer this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
Inbound TCP/IP connection request rejected: Gateway Stopped
|
| |
|
A remote gateway connection attempt to a stopped gateway was rejected.
|
| |
|
A connection error response was returned to the remote gateway.
|
| |
|
|
|
|
IMS Error Message received
|
| |
|
IMS rejected a service request for a variety of reasons.
|
| |
|
An IMS DFS Error message was returned to the gateway on behalf of a client request.
|
| |
|
Examine the text of the message to determine the nature of the error and take corrective action.
|
|
|
IMS Server Request failed - IMS Unavailable
|
| |
|
The IMS host system required to service this request is not available.
|
| |
|
An error message is returned to the client with the appropriate error and reason codes set.
|
| |
|
Determine why the IMS Host is unavailable and change the configuration to reroute the request to another available Host, if possible.
|
|
|
OTMA Status change detected with status: Old= oldstatus New= newstatus
|
| |
|
The Tuxedo Mainframe Adapter gateway detected a status change with an IMS Host.
|
| |
|
The message is logged and displayed to the console.
|
| |
|
Determine why the status of the IMS Host has changed.
|
|
|
OTMAINPIPE maximum length n exceeded.
|
| |
|
An IMS Host was configured with an OTMAINPIPE parameter.
|
| |
|
The message is logged and displayed to the console.
|
| |
|
Correct the configuration information and retry.
|
|
|
Multi-Segment Message Reconstructed
|
| |
|
A multi-segment client response was received.
|
| |
|
|
| |
|
None required. This message is used only when MSGLEVEL is set to DEBUG(10).
|
|
|
Not enough spare sockets available.
|
| |
|
A dynamic configuration change was attempted that required the use of additional TCP/IP socket resources and not enough were available. Message BEA2166E should follow with additional details.
|
| |
|
The configuration change was rejected.
|
| |
|
The TMA TCP for IMS gateway must be shut down to accomplish the change. Consider increasing the value of the SPARESOCKETS parameter for future dynamic updates.
|
|
|
Requested: n, Available: n
|
| |
|
A follow on message to BEA2165E. This message details the TCP/IP socket resources requested and available.
|
| |
|
The configuration change was rejected.
|
| |
|
The TMA TCP for IMS gateway must be shut down to accomplish the change. Consider increasing the value of the SPARESOCKETS parameter for future dynamic updates.
|
|
|
|
| |
|
The command was entered incorrectly.
|
| |
|
The command was rejected.
|
| |
|
For correct command syntax, refer to the
Configuring Oracle TMA TCP for IMS section.
|
|
|
IMS Server Request for Service( service-name) failed: Requested Service not defined
|
| |
|
The service request from a remote client was for an undefined service.
|
| |
|
The client request is rejected with an appropriate error and reason code.
|
| |
|
Update the remote client to request the correct service name or define a new local service with the name requested.
|
|
|
IMS Server Request for Service ( service-name) failed:Requested Service not available
|
| |
|
The service request from a remote client was for a service that is temporarily unavailable.
|
| |
|
The client request is rejected with an appropriate error and reason code.
|
| |
|
Determine why the service is currently unavailable and take corrective action, if necessary.
|
|
|
IMS Server Request for Service ( service-name) failed: Buffer Size Error
|
| |
|
The service request from a remote client failed due to an internal buffer size error. Typically, this is caused by exceeding the maximum message size of 64K, including internal header data.
|
| |
|
The client request is rejected with an appropriate error and reason code.
|
| |
|
Contact Oracle Support to report the error.
|
|
|
Multiplex Count must be greater than zero (0)
|
| |
|
A GATEWAY configuration statement contained a MULTIPLEX parameter set to zero.
|
| |
|
The configuration is rejected. If the error occurred on initial startup, the TMA TCP for IMS gateway exits.
|
| |
|
Change the MULTIPLEX parameter to a number greater than zero or remove the parameter and use the default (1).
|
|
|
Missing IMSID option for IMS HOST
|
| |
|
A HOST configuration statement was missing an IMSID parameter which is required.
|
| |
|
The configuration is rejected. If the error occurred on initial startup, the TMA TCP for IMS gateway exits.
|
| |
|
Correct the configuration information and retry.
|
|
|
Missing OTMANAME option for IMS HOST
|
| |
|
A HOST configuration statement was missing an OTMANAME parameter which is required.
|
| |
|
The configuration is rejected. If the error occurred on initial startup, the TMA TCP for IMS gateway exits.
|
| |
|
Correct the configuration information and retry.
|
|
|
Missing OTMAINPIPE option for IMS HOST
|
| |
|
A HOST configuration statement was missing an OTMAINPIPE parameter which is required.
|
| |
|
The configuration is rejected. If the error occurred on initial startup, the TMA TCP for IMS gateway exits.
|
| |
|
Correct the configuration information and retry.
|
|
|
Missing OTMAOUTPIPE option for IMS HOST
|
| |
|
A HOST configuration statement was missing an OTMAOUTPIPE parameter which is required.
|
| |
|
The configuration is rejected. If the error occurred on initial startup, the TMA TCP for IMS gateway exits.
|
| |
|
Correct the configuration information and retry.
|
|
|
Cannot malloc for IMS HOST
|
| |
|
Oracle TMA TCP for IMS was unable to allocate storage used to process IMS HOST definitions.
|
| |
|
Initialization fails and Oracle TMA TCP for IMS terminates.
|
| |
|
Report this error to the systems programmer responsible for Oracle TMA TCP for IMS.
|
|
|
|
| |
|
A HOST configuration with the same IMSID already exists.
|
| |
|
If the error occurs during Oracle TMA TCP for IMS startup, initialization is aborted and the program terminates. If the error occurs during processing of an ADD HOST operator command, command processing is aborted.
|
| |
|
Choose a unique name for the HOST and retry the command.
|
|
|
Missing IMSID option for Service
|
| |
|
A local service definition is missing an IMSID parameter which is required.
|
| |
|
If the error occurs during Oracle TMA TCP for IMS startup, initialization is aborted and the program terminates. If the error occurs during processing of an ADD SERVICE operator command, command processing is aborted.
|
| |
|
Change the SERVICE, TYPE=LOCAL statement to include an IMSID parameter.
|
|
|
Local Service service-name for IMSID IMS-logical-identifier is invalid
|
| |
|
A dynamic configuration operator command (MOD, START, or STOP SERVICE) was entered for a local service that does not exist.
|
| |
|
Command processing is aborted.
|
| |
|
Enter the correct remote name of the local service in the NAME parameter of the dynamic configuration command.
|
|
|
Service service-name for IMSID IMS-logical-identifier is being stopped
|
| |
|
A STOP SERVICE operator command for a local service is being processed.
|
| |
|
The STOP processing continues for the local service.
|
| |
|
None Required. Informational message only.
|
|
|
Service service-name for IMSID IMS-logical-identifier has been stopped
|
| |
|
A STOP SERVICE operator command for a local service has completed processing.
|
| |
|
The STOP processing has completed.
|
| |
|
None Required. Informational message only.
|
|
|
Could not find IMSID IMS-logical-identifier for service service-name
|
| |
|
A dynamic configuration operator command was entered for a local service which did not contain a valid IMSID parameter.
|
| |
|
Command processing is aborted.
|
| |
|
Enter the correct IMSID of the local service in the IMSID parameter of the dynamic configuration command.
|
|
|
|
| |
|
Part of the STATUS display showing the number of service requests processed.
|
| |
|
|
| |
|
None Required. Informational message only.
|
|
|
XCF Messages Received = n
|
| |
|
Part of the STATUS display showing the number of XCF messages received by the gateway.
|
| |
|
|
| |
|
None Required. Informational message only.
|
|
|
MCBs: Allocated = number of MCBs Assigned = number of MCBs
|
| |
|
Part of the STATUS display showing the number of message control blocks defined and currently in use.
|
| |
|
|
| |
|
None Required. Informational message only.
|
|
|
Services: Remote = number of remote services Local = number of local services
|
| |
|
Part of the STATUS display showing the number of services currently defined.
|
| |
|
|
| |
|
None Required. Informational message only.
|
|
|
IMS HOST IMS-logical-identifier is invalid
|
| |
|
A dynamic configuration operator command ( MOD, START, or STOP was entered for an IMSID that does not exist.
|
| |
|
Operator command processing is aborted.
|
| |
|
Retry the command with a valid IMSID.
|
|
|
IMS HOST IMS-logical-identifier has been started
|
| |
|
A START HOST operator command for an IMS host has completed processing.
|
| |
|
|
| |
|
None Required. Informational message only.
|
|
|
IMS HOST IMS-logical-identifier is being stopped
|
| |
|
A STOP HOST operator command for an IMS host is being processed.
|
| |
|
The STOP HOST processing continues for the host.
|
| |
|
None Required. Informational message only.
|
|
|
IMS HOST IMS-logical-identifier has been stopped
|
| |
|
A STOP SERVICE operator command for an IMS host has completed processing.
|
| |
|
The STOP SERVICE processing has completed.
|
| |
|
None Required. Informational message only.
|
|
|
Service service-name for IMSID IMS-logical-identifier already exists.
|
| |
|
An ADD SERVICE operator command for a local service has been attempted but the service has been previously defined.
|
| |
|
The ADD SERVICE processing has been aborted.
|
| |
|
Change the service name and retry, if necessary,
|
|
|
Missing LMID option for START GATEWAY
|
| |
|
A START GATEWAY operator command has been attempted but the LMID parameter, which is required, has been omitted.
|
| |
|
The START GATEWAY processing has been aborted.
|
| |
|
Add the LMID parameter to the command and retry.
|
|
|
Missing LMID option for STOP GATEWAY
|
| |
|
A STOP GATEWAY operator command has been attempted but the LMID parameter, which is required, has been omitted.
|
| |
|
The STOP GATEWAY processing has been aborted.
|
| |
|
Add the LMID parameter to the command and retry.
|
|
|
Missing IMSID option for START HOST
|
| |
|
A START HOST operator command has been attempted but the IMSID parameter, which is required, has been omitted.
|
| |
|
The START HOST processing has been aborted.
|
| |
|
Add the IMSID parameter to the command and retry.
|
|
|
Missing IMSID option for STOP HOST
|
| |
|
A STOP HOST operator command has been attempted but the IMSID parameter, which is required has, been omitted.
|
| |
|
The STOP HOST processing has been aborted.
|
| |
|
Add the IMSID parameter to the command and retry.
|
|
|
OTMANAME for IMSID IMS-logical-identifier not unique
|
| |
|
A HOST statement contains an OTMANAME parameter value that already is used in another HOST statement.
|
| |
|
If the error occurs during Oracle TMA TCP for IMS startup, initialization is aborted and the program terminates. If the error occurs during processing of an ADD HOST operator command, command processing is aborted.
|
| |
|
Change the OTMANAME parameter to match the unique OTMA client name of the IMS system and retry.
|
|
|
Reserved for internal trace messages used only when debugging is enabled.
|
|
|
Response Service remote-service-name for Service local-service-name is invalid.
|
| |
|
The specified RESPONSE service on a SERVICE, TYPE=LOCAL statement was not a valid remote service.
|
| |
|
If the error occurs during Oracle TMA TCP for IMS startup, initialization is aborted and the program terminates. If the error occurs during processing of an ADD SERVICE operator command, command processing is aborted.
|
| |
|
Change the service name and retry.
|
|
|
Response Transaction remote-service-name from IMS Client is invalid.
|
| |
|
The response transaction specified in the Oracle client request/response header is not defined as a local service.
|
| |
|
The client request is aborted.
|
| |
|
Define the response transaction as a local service.
|
|
|
Client request for Service remote-service-name timed out on queue.
|
| |
|
A service request from an IMS client timed out while waiting for an available session on a remote host.
|
| |
|
A timeout error is returned to the response transaction.
|
| |
|
Reconfigure the SESSIONS or MULTIPLEX count for the desired remote gateway, if necessary.
|
|
|
Service local-service-name for IMSID IMS-logical-identifier has been started.
|
| |
|
This is the normal response for a START SERVICE operator command for a local service.
|
| |
|
|
| |
|
|
|
|
Required SYSTEM parameter missing.
|
| |
|
The SYSTEM parameter is missing in the configuration file.
|
| |
|
Make sure the SYSTEM parameter is in the configuration file.
|
| |
|
|
|
|
Response Message length (nnnn) for Server < server_name> exceeds maximum length allowed (nnnn).
|
| |
|
IMS Server response exceeds the maximum permissible length given in the MAXRSPLEN parameter. THe response is discarded and the request fails.
|
| |
|
Change the MAXRSPLEN value to the response length required. The acceptable value range for the parameter is 1024-8,192,000.
|
| |
|
|
|
|
Allocation failed for Message Buffer (Size = <requested size>, SP= <storage pool>, RC = <return code>, RSN = <reason code>)
|
| |
|
OS GETMAIN fails to allocate the requested buffer size. The session is terminated.
|
| |
|
Assuming a reasonable buffer size, this is an abnormal condition indicating a severe storage shortage or corruption of the storage allocation control blocks.
|
| |
|
Contact Oracle Support to report the error.
|
|
|
Deallocation failed for Message Buffer (Size = <requested size>, SP= <storage pool>, RC = <return code>, RSN = <reason code>)
|
| |
|
OS FREEMAIN fails to deallocate the buffer. The session is terminated.
|
| |
|
Assuming a valid buffer point is passed for deallocation, this is an abnormal condition that indicates a corruption of the storage allocation control block.
|
| |
|
Contact Oracle Support to report the error.
|
|
|
|
| |
|
Indicates the end of the snap dump request.
|
| |
|
|
| |
|
|
|
|
|
| |
|
Displays the current message level.
|
| |
|
|
| |
|
|
|
|
Reserved for future use by Oracle TMA TCP for IMS.
|
|
|
Unable to locate message number <number>.
|
| |
|
An undefined error code has been generated.
|
| |
|
The gateway is unable to describe an error which has occurred.
|
| |
|
Contact Oracle Support to report the error. Be sure to note the error number listed.
|
