An internal DB2 collection service failed.
A successful connection was made to XNet agent <agt> using director ID <dir> on port CA Portal with socket number <socket>
The director <dir> connection to XNet agent <agt> was disconnected from socket number <socket>
A request <req> was sent to agent <agt> and the request failed with an agent return code of <rc> and reason code of <rsn>. The <agtmsg> is message data returned from the agent.
A request <req> was sent to agent <agt> and the request failed. No data was returned indicating that the socket was closed by the XNet server.
A request <req> was sent to agent <agt> and the request failed with XNet reason <code>. If the reason code is known <desc> will describe the reason code, otherwise, it is blank.
If this particular reason code has been given, this indicates that the a valid PassTicket has been generated, but it has not been accepted during User ID/Password validation processing.
Two possible reasons for this are:
XNet request failed. <xmsg> is a message that was returned as part of the reply status.
A request <req> was sent to agent <agt> and the request response contained a column <col> that could not be processed because the target control block field length <len> was not correct.
A request <req> was sent to agent <agt> and the request response contained a column <col> that had an unknown column type code of <type>. The request could not be processed.
A request <req> was sent to agent <Id> and the request response contained a column <col> that had column type of <type> that has not been implemented.
A request was started for director <dir> to agent <agt>
The request for director <dir> to agent <agt> has completed.
This is the total external and internal elapsed CPU time used by the request. External time measures time attributable to the XNet agent.
This is the total external and internal CPU time used by the request. External time measures time attributable to the XNet agent.
A request <req> was sent to agent <Id> and the request response header was invalid because the length <len> was too small or large.
A request <req> was sent to agent <Id> and the request response header contained an unknown response ID <resp_id>
A request <req> was sent to agent <Id> and the request response header contained an unexpected response ID <resp_id>
A request <req> was sent to agent <Id> and the request response sequence number <seqret> does not match the sequence number sent <seqsend>.
A request <req> was sent to agent <Id> and the request response is too small to contain a valid response structure. The length is <len>
A request <req> was sent to agent <Id> and the request response field revision number <rev> is not supported.
A request <req> was sent to agent <Id> and the request response field type code <type> was unexpected.
A request <req> was sent to agent <Id> and the request response field length <len> is too small to contain a response packet header.
A request <req> was sent to agent <Id> and the request response packet header indicates there are zero segments in the packet.
A request <req> was sent to agent <Id> and the request response packet type of <type> is unknown.
A request <req> was sent to agent <Id> and the request response packet query ID <idret> does not match the sent query ID <idsend>.
This message indicates that the selected DB2 subsystem is now the current target subsystem. DB2 commands are always directed to the CA Insight agent managing the current target DB2 subsystem.
No DB2 subsystems were found.
While attempting to select a DB2 subsystem, no active DB2 subsystem was found that was being monitored by a CA Insight agent.
While attempting to select a DB2 subsystem, the DB2 subsystem was not found, not active, or not being monitored by a CA Insight agent.
An attempt to verify the target DB2's asid failed. This can occur if the target DB2 was stopped or restarted before a data collection request was completed.
This message indicates that the target DB2 subsystem is not being monitored by a CA Insight agent. It is possible that XNET is not currently running.
A request <req> was sent to agent <agt> and the request response contained a column <col> of type code <type> that did not match the expected type of <etype>. The column could not be converted, but conversion continues with the next column.
The XNET port was not defined using the DB2-XNET-Port parameter in the OPTIONS parmlib member. CA Insight for DB2 agent status and information cannot be determined.
A request <req> was sent to agent <agt> and the request response buffer length of <len> could not be obtained to receive the response.
The director <dir> connection to XNet agent <agt> on socket number <socket> was tested and is in error. The connection will be disconnected and a reconnect will be attempted.
An agent notify error message was received from the agent <agt> for director ID <dir>. Check for additional messages that follow for specific reason codes.
This is a debug informational message, showing the columns that were found and the <action> taken.
This is a debug informational message,
Either the Passticket facility is not available or there is a definition problem. Review Passticket setup.
The XNET-PassTicketApplId parameter in the DB2 PARMLIB member is the application name to be used to generate user passtickets to connect to the CA Database Management Solutions for DB2 for z/OS Xnet address space.
This XNET-PassTicketApplId name must match the Xnet PASSNAME parameter in the INITPARM data set for the Xnet address space.
|
Copyright © 2013 CA.
All rights reserved.
|
|