|
|
|
The disconnect process has completed successfully.
|
Service svcname not found.
|
The requested service was not found in the inbound service name file.
|
Client has already logged in.
|
A client process has attempted to establish a connection when a connection already existed. (The connection request protocol was resent.)
|
Client has not logged in.
|
A client process has made a request to the TMA TCP for CICS gateway but has not yet established a login connection. (The connection request protocol was never sent.)
|
|
The password specified in the TMA TCP gateway configuration file does not match the password specified when the CICS supplied listener was configured.
|
|
The account code specified in the TMA TCP gateway configuration file does not match the account code specified when the CICS supplied listener was configured.
|
Data too long, please check message header.
|
A message received is larger than the maximum allowable message length.
|
Application Handler abnormally terminated.
|
The Application Handler terminated prior to completing the service request. This message usually occurs when a service has timed out. Verify that you are not expecting a reply from a service that does not send one.
|
Requested Service timed out.
|
The requested service did not complete within the time provided in the message header from the remote Tuxedo gateway.
|
Unable to start another session.
|
The Handler is already processing the maximum number of service requests configured as the multiplex count.
|
Unable to start transaction.
|
A CICS error occurred attempting to start the transaction.
|
Error occurred in Application Handler.
|
The Application Handler encountered a CICS error.
|
Security error occurred in Application Handler.
|
The Application Handler encountered a CICS security error.
|
DNS Lookup Failed for HOST(host) ERRNO(errno)
|
The DNS lookup function failed for the given host name.
|
Dotted IP address (address) malformed.
|
There was an erroneous IP address passed into the ConvertAddress function.
|
Invalid data pointer (pointer).
|
There was an invalid data buffer pointer passed into the BufferHeader function.
|
Socket CONNECT Failed. ERRNO=errno
|
The Socket CONNECT function failed.
|
fcntl(F_SETFL) Failed. ERRNO=errno FLAGS=hexcode
|
The file control function with the F_SETFL option failed in the connect socket function.
|
fcntl (F_GETFL) Failed. ERRNO=errno
|
The file control function with the F_GETFL option failed in the connect socket function.
|
Socket CREATE Failed. ERRNO=errno
|
The Socket CREATE function failed.
|
WRITE on Socket Failed. ERRNO=errno
|
The Socket WRITE function failed.
|
initapi Failed. ERRNO=errno
|
The Socket initialization function failed.
|
RETRIEVE Failed. RESP=hexcode RESP2=hexcode
|
The CICS RETRIEVE command failed when it tried to access the buffer passed to the TMA TCP gateway Handler from the Sockets for CICS Listener.
|
Load Control Failed. RESP=hexcode RESP2=hexcode
|
A CICS LOAD PROGRAM command failed. The Handler was unable to load the control programs OTPCICS01 or OTPCICS02 .
|
Start Task Failed. RESP=hexcode RESP2=hexcode
|
A CICS START command failed when the Handler tried to issue a START on the specified user program.
|
Link Program Failed. RESP=hexcode RESP2=hexcode
|
A CICS LINK command failed. The Handler was unable to LINK to the specified user program.
|
GETMAIN Failed. RESP=hexcode RESP2=hexcode
|
The CICS GETMAIN command failed.
|
Take Socket Failed. ERRNO=errno
|
The TMA TCP Handler was unable to take control of the TCP/IP socket.
|
Error on Select. ERRNO=errno
|
The Sockets SELECT function failed.
|
Read on Socket Failed. ERRNO=errno
|
An error was encountered while attempting to read from the active socket.
|
Socket SEND Failed. RC=rc ERRNO=errno
|
An error was encountered while issuing a send over the active socket.
|
Handler connected successfully.
|
The client request is allowed because the account and password codes are authorized to use the TMA TCP gateway.
|
BEA TMA TCP Server CTOS is shutting down.
|
The TMA TCP gateway Handler is shutting down.
|
|
The Handler is verifying that the account and password codes supplied by TMA TCP gateway on the remote Tuxedo gateway are valid.
|
Handler initialization complete.
|
The TMA TCP Handler has successfully initialized.
|
Normal shutdown requested, x requests pending.
|
The TMA TCP Handler shuts down after the currently pending requests complete.
|
Handler exceeded maximum idle time.
|
The TMA TCPHandler has exceeded the configured IDLE TIME .
|
BEA TMA TCP Handler is shutting down.
|
The TMA TCP Handler is shutting down.
|
|
The client has been disconnected from the TMA TCP Handler.
|
Read of file failed, resp(hexcode)
|
A CICS READ command failed.
|
Freemain did not work, resp(hexcode)
|
A CICS FREEMAIN command failed.
|
Getmain shared failed: resp(hexcode)
|
A CICS GETMAIN(SHARED) command failed.
|
Delete from file failed, resp(hexcode)
|
A CICS DELETE command failed.
|
Write to file failed, resp(hexcode)
|
A CICS WRITE command failed.
|
Rewrite of file failed, resp(hexcode)
|
A CICS REWRITE command failed.
|
Read(update) of file failed, resp(hexcode)
|
A CICS READ(UPDATE) command failed.
|
Unauthorized Client Rejected.
|
The client request are not allowed because the account and/or password codes are not authorized.
|
deleteq ts did not work, resp(hexcode)
|
A CICS DELETEQ TS command failed.
|
Unable to start transaction
|
A CICS error occurred attempting to start the transaction.
|
Security Violation: Invalid user for this transaction
|
The user ID sent with a request by the client does not match the user ID set in the mainframe security for this transaction.
|
The Handler is designed to run in the background.
|
A user has attempted to start the Handler from a terminal.
|
The appHandler is designed to run in the background.
|
A user, from a terminal, has attempted to start the transaction that initiates the Application Handler.
|
App Handler received corrupted header, exiting.
|
The Application Handler is terminating on initialization because there is a problem with the header it received. This would occur, for example, if the transaction for the Application Handler was given in the Inbound Service Information screen as the transaction to start a service with no reply.
|
opcode is not CONNECT on connection.
|
The Requester has received a reply that should be the acknowledgment of a connection request; however, the message does not contain the correct opcode.
|
Trying connection, but already connected.
|
The Requester has received a reply containing an opcode indicating a response to a connection request; however, the connection already exists.
|
Read on sockets failed. Connection closed by other side.
|
The Handler terminated because the socket status indicated that the client side had closed the connection.
|
LMID is disabled. Auto enabling LMID ,LMID name>
|
The pre-requester is dynamically enabling an LMID which is disabled. This message will be displayed only when the AUTO ENABLE option is set to E.
|