|
|
|
Reason:
The NetMaster translator initialized using parameter overwrites from either environment variables or java properties. p1 identifies the parameters set. The following list shows the possible parameters:
HOST=xxx
Shows the value of the netmaster.tr.host overwrite. If set, then the primary NetMaster connection is made to the specified host name or address.
PORT=nnn
Shows the value of the netmaster.tr.port overwrite. If set, then the primary NetMaster connection is made to the specified port number on the host name or address that is configured (or set using the run-time parameter).
DEBUG=(xxx)
Shows the debugging options in use for generating trace messages on the translators execution.
System Action:
None.
User Action:
None.
Reason:
The NetMaster translator will use the java system property p1 as a parameter overwrite for controlling the translator. p2 is the value of the property.
System Action:
None.
User Action:
None.
Reason:
The NetMaster translator will use the environment variable p1 as a parameter overwrite for controlling the translator. p2 is the value of the variable.
System Action:
None.
User Action:
None.
Reason:
An error was encountered while attempting to cancel an existing translator request. p1 is the encountered error.
System Action:
The error is ignored and processing continues. The connection in error is recycled.
User Action:
None.
Reason:
The translator attempted to log in to CA NetMaster, but the login failed.
p1 is the protocol return code.
p2 is the feedback code.
p3 is the error message.
System Action:
The request is terminated, and no data is returned for the SQL request.
User Action:
Check the log for messages that identifies the user that was attempting to log in, and ensure that they are authorized to access CA NetMaster data.
Reason:
The translator could not establish a TCP/IP connection to CA NetMaster on host name/address p1 and port p2.
System Action:
The request is terminated, and no data is returned for the SQL request.
User Action:
Check that the correct host name/address and port have been set for the connection. If these values are correct, then ensure that the region is running on the identified z/OS system.
Reason:
A connection was established successfully for user p3 to CA NetMaster on host name/address p1 and port p2. This connection is used to satisfy data requests for this user. p4 indicates the API and connector versions used.
System Action:
None.
User Action:
None.
Reason:
While attempting to read p1 bytes from a TCP/IP socket to CA NetMaster, an end-of-file condition was encountered after only reading p2 bytes.
System Action:
The connection is terminated, and another connection is established to retry the request.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The record length of a response from CA NetMaster is invalid. An additional message is issued, which shows a dump of the data that was received as the record length.
p1 is the record length.
System Action:
The request is terminated.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
This dump message shows data in hexadecimal and character format.
System Action:
None.
User Action:
See the related messages that are issued before this message.
Reason:
A socket I/O error was encountered while attempting to send or receive data on a connection to CA NetMaster. Subsequent messages show the data that was sent.
System Action:
The connection is terminated.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
A socket I/O error was encountered while attempting to read data on a connection to CA NetMaster.
System Action:
The connection is terminated.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The exception p1 was encountered while attempting to decode the BER encoded response from CA NetMaster. Subsequent messages show the data that was in error.
System Action:
The connection is terminated.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator was unable to obtain the required security application identifier to generate PassTickets for logon to CA NetMaster. p1 and p2 are the host name/address and port of the contacted region.
System Action:
The connection is terminated.
User Action:
Review proceeding messages that indicate the cause of the error.
Reason:
The translator was unable to obtain the required security application identifier to generate PassTickets for logon to CA NetMaster. The region responded with the following information:
p1 is the return code.
p2 is the feedback code.
p3 is the error message.
System Action:
The connection is terminated.
User Action:
Check the region for error messages that indicate the cause of the error.
Reason:
A connection is being established to host name/address p1 and port p2 for the CA NetMaster server p3. After the TCP/IP connection has been established, the port sharing protocol is negotiated and a connection to servlet p3 is established.
System Action:
None.
User Action:
None.
Reason:
An exception was encountered while attempting to get more data from CA NetMaster.
System Action:
The request terminates.
User Action:
Review the preceding and associated messages for the reason of the error.
Reason:
The translator attempted to obtain the table metadata from CA NetMaster, but the request failed.
p1 is the return code.
p2 is the feedback code.
p3 is the error message.
System Action:
The request is terminated, and the translator is not able to initialize.
User Action:
Review the log for messages that indicate the cause of the error.
Reason:
The translator has connected successfully to CA NetMaster and is attempting to retrieve the metadata that describes the data that is available. p1 indicates the API, connector and translator versions used.
System Action:
None.
User Action:
None.
Reason:
An error was encountered while attempting to get metadata from CA NetMaster.
System Action:
The request terminates, and the translator does not initialize.
User Action:
Review the associated messages for the reason of the error.
Reason:
The translator has connected successfully to CA NetMaster and retrieved all metadata that describes the data that is available. p1 table definitions were retrieved and cached.
System Action:
None.
User Action:
None.
Reason:
The translator has retrieved successfully the metadata for table p1 which has p2 columns.
System Action:
None.
User Action:
None.
Reason:
The translator received a request that contained a literal class that is not supported. p1 identifies the class.
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator received a request that contained a condition class that is not supported. p1 identifies the class.
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator received a request for an aggregate function to be applied on a streamed table. This action is unsupported.
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator received a request for an aggregate function p1 that is not supported.
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator received a request that contained the LIMIT clause on a streamed table. This action is unsupported.
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator received a request that contained the ORDERBY clause on a streamed table. This action is unsupported.
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator received a request that contained the GROUPBY clause on a streamed table. This action is unsupported.
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator received a request to invoke the stored procedure p2 with the p1 argument type. This action is unsupported.
System Action:
The request terminates.
User Action:
For assistance, contact at http://ca.com/support.
Reason:
The translator received a request to get more responses to a previous request; however, no more responses are waiting to be received.
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator sent a query request to CA NetMaster, but the request failed.
p1 is the response return code.
p2 is the feedback code.
p3 is the error message.
System Action:
The request is terminated, and no data is returned for the sql request.
User Action:
Check the CA NetMaster region for messages that indicate the reason for the error.
Reason:
The translator sent a streamed query notification request for table p1 to CA NetMaster, but the request failed.
p2 is the response return code.
p3 is the feedback code.
p4 is the error message.
System Action:
The request is terminated, and no data is returned for the SQL request.
User Action:
Check the CA NetMaster region for messages that indicate the reason for the error.
Reason:
An exception was encountered while monitoring for data notifications for table p1. The streamed table ends abnormally. No more data is delivered to the stream.
System Action:
The connection is terminated.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
A translator query call to an access method resulted in an error. p1 is the ID of the access method that was processing the request. p2 contains information about the error and can have the following possible values:
XSCAN search error: m
Indicates that the access method encountered an error with a packet analyzer XSCAN search request that finds all records applicable to a query. The error is described in the message m that follows.
XSCAN count error: m
Indicates that the access method encountered an error with a packet analyzer XSCAN count request that counts the number of records that match a query. The error is described in the message m that follows.
System Action:
Error codes and message are sent back to client.
User Action:
Ensure that the query request is formed correctly, and retry the request. For assistance, contact CA Support at http://ca.com/support.
Reason:
Valid values for this field are A through Z, 0 through 9, PROD, or NONE. PROD is equivalent to a TSF suffix of a blank character while NONE disables sending TSF metric data from this region. The value must match the TSF region identifier shown in the CA Chorus TSF startup log message ETJTS106I. For details on the CA Chorus TSF suffix, see CA Chorus Installation Guide.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
Valid values for this field are A through Z, 0 through 9, PROD, or NONE. PROD is equivalent to a TSF suffix of a blank character, while NONE disables sending TSF metric data from this region. The value must match the TSF region identifier shown in the CA Chorus TSF startup log message ETJTS106I.
For details on the CA Chorus TSF suffix, see CA Chorus Installation Guide.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
During the initialization of the CA Chorus interface, product p1 was not found in the NMTSFREG registration load module.
System Action:
Processing terminates.
User Action:
Verify that you are using the NMTSFREG registration module that comes with this release of the product.
Reason:
The value p1 is not a valid TSF data feed interval. Valid values are 15, 30, 60, 300, 900, 1800, 3600, 7200, 14400, 43200, and 86400.
System Action:
Processing terminates.
User Action:
Enter a valid value for the INTERVAL= parameter keyword.
Reason:
The required input data p1 was not provided. p2 indicates the failed function call.
System Action:
The request is rejected.
User Action:
Provide a valid value, and retry the request.
Reason:
The TSF data feed process received a logical record from the server that did not conform to the PD API protocol specification. p1 is the specific error that is found with the received data and has the following possible values:
The direction indicator of the record is invalid.
The sum of the header section and the data section does not add up to the total logical record length.
A record was received with a request code of x that is invalid or that this version of the PD API does not support.
A logical record was received with a request code of x that is not valid currently.
The heartbeat record type is invalid.
The expected heartbeat correlator does not match.
The allowed maximum time for record x to be send expired.
An error condition was detected. x is the record type. y describes the reason for the error.
System Action:
Processing terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The TCP/IP sockets interface is not active, which prevents the TSF data feed process from establishing a TCP connection with the TSF server.
System Action:
Process is terminated.
User Action:
To start the TCP/IP sockets interface:
Reason:
The TSF data feed process failed on a socket.
p1 identifies the socket option.
p2 is the return code.
p3 is the feedback code.
p4 is the socket error number and vendor-specific error code.
p5 (optional) shows a brief description of the error number.
System Action:
Processing terminates.
User Action:
Check the error codes. For assistance, contact CA Support at http://ca.com/support.
Reason:
The TSF data feed process failed to retrieve a valid TSF name/token pair. p1 is the reason for the failure.
System Action:
Process is terminated.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Translator driver encountered an internal logic error. p1 is additional text to describe the specific error.
System Action:
Processing terminates.
User Action:
Review the log for other error messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
A query request resulted in an error. The request could not be completed and was aborted. p1 contains information about the error and can have the following possible values:
Indicates that the server does not know table t, which was being queried.
Indicates that the query resulted in the generation of an invalid BOOLEXPR expression, e, for testing system inclusion. The request MDO is written to the log.
Indicates that the query expression included invalid or unsupported WHERE clause criteria. The invalid criteria was encountered at MDO reference r. The request MDO is written to the log.
Indicates that the access method procedure proc in package pkg abended. The error details are written to the log.
Indicates that the requested query could not be sent to secondary system s and its contribution to the output is not returned. The query continues processing for other eligible systems. Additional message appears in the log of this system or the log of the remote secondary system.
Indicates that the requested query failed on system s on LPAR l. The query continues processing for other eligible systems. Additional messages appear in the log of this system or the log of the remote secondary system.
Indicates that the requested query could not be sent to secondary system s on LPAR l. The process that failed to respond had ID n. The query continues processing for other eligible systems. Additional messages appear in the log of the remote secondary system.
Indicates that the requested query could not be processed successfully because the internal processing queue encountered an error. n is the feedback code that describes the error.
System Action:
Error codes and message are sent back to client.
User Action:
Ensure that the query request is correctly formed, and retry the request. For assistance, contact CA Support at http://ca.com/support.
Reason:
A request for table metadata found no tables matching the requested criteria. p1 is optional criteria that was specified on the request.
System Action:
Error codes and message are sent back to client.
User Action:
Ensure that the filter criteria specified is correct, and retry the request.
Reason:
A request to transfer variable data from one process to another failed. p1 contains information about the error and can have the following possible values:
Indicates that the transfer to process ID n running on system domain t for variable stem v was aborted. The source was from process ID m running on system domain f. The error message returned was msg.
Indicates that the transfer to process ID n running on system domain t for variable stem v was aborted. The target process is no longer running.
Indicates that the transfer to process ID n running on system domain t for variable stem v was aborted. The transfer is unable to obtain lock on the control table. x is the lock return code, and y is the feedback code.
Indicates that the request to accept the transfer of variable data to process ID n failed. The request timed out.
Indicates that the request to accept the transfer of variable data to process ID n failed. An unexpected message arrived on the INTQUEUE. m is the message that arrived.
Indicates that the request to accept the transfer of variable data to process ID n failed. The table key presented was not applicable for the requesting process ID.
System Action:
Error codes and message are sent back to client.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The translator server uses the security application name p1. This name was either found in the SXCTL ddname or defaulted to the job name of the region. p2 indicates where the name was retrieved from.
System Action:
The RAPPL value is used for generating PassTickets for remote users who access the region.
User Action:
None.
Reason:
The Translator servlet encountered an error while receiving data from a TCP socket. The process was in p1 state when the error occurred. p2 is the return code, and p3 is the feedback code. p4 gives the socket error number and vendor-specific error code. If present, p5 gives a brief description of the error number. p6 and p7 are the address and port of the client.
System Action:
The specific connection is closed.
User Action:
Review the error codes. For assistance, contact CA Support at http://ca.com/support.
Reason:
The Translator servlet encountered an error while sending data to a TCP socket. The process was in p1 state when the error occurred. p2 is the return code, and p3 is the feedback code. p4 gives the socket error number and vendor-specific error code. If present, p5 gives a brief description of the error number. p6 and p7 are the address and port of the client.
System Action:
The specific connection is closed.
User Action:
Review the error codes. For assistance, contact CA Support at http://ca.com/support.
Reason:
The Translator servlet received a request encoding prefix that it does not support. The encoding technique indicated by the prefix was p1.
System Action:
The specific connection is closed.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The Translator servlet could not decode the data that is received from the client. The data received was invalid and failed the decoding process. p1 is the return code from the decoding process, and p2 is the feedback code. If present, p3 contains additional information.
System Action:
The specific connection is closed, and data is written to the log.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The Translator servlet received a request that violates the communications protocol between the translator client and server. p1 indicates the specific error and can have the following values:
Indicates that the login request specified an unsupported API version. n was the value that the client specified, and m is the maximum value that this server supports.
Indicates that the login request specified an unsupported character set x.
Indicates that a client requested more responses but there were no more pending to be sent.
Indicates that a client requested a login when the connection was logged in already.
Indicates that a client requested sub-option x for option y, however, the sub-option is not applicable.
Indicates that a client requested option x, which this server does not support.
Indicates that a client sent request option o with sub-option s during the login phase of a connection.
System Action:
The specific connection is closed.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The TCP socket transfer to a servlet process failed.
p1 is the TCP socket ID.
p2 is the NCL ID of the servlet process.
p3 is the return code.
p4 is the feedback code.
p5 is the socket error number and vendor-specific error code.
p6 (optional) is a brief description of the error number.
System Action:
The specific connection is closed.
User Action:
Review the error codes. For assistance, contact CA Support at http://ca.com/support.
Reason:
The Translator servlet could not encode the data to send to the client. The request to be sent was invalid and failed the encoding process.
p1 is the return code from encoding process.
p2 is the feedback code.
p3 (optional) is a message.
System Action:
The specific connection is closed, and data is written to the log.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Translator servlet encountered a fatal processing condition and cannot recover from it. Proceeding and subsequent error messages detail the condition and other diagnostic information.
System Action:
Processing terminates, and the connection is closed.
User Action:
Review the log for other error messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
Translator server encountered an internal logic error. p1 provides additional text to describe the specific error.
System Action:
Processing terminates.
User Action:
Review the log for other error messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
During the initialization of the CA Chorus interface, product p1 was not found in the NMTSFREG registration load module.
System Action:
Processing terminates.
User Action:
Verify that you are using the NMTSFREG registration module that comes with this release of the product.
Reason:
The value p1 is not a valid TSF data feed interval. Valid values are 15, 30, 60, 300, 900, 1800, 3600, 7200, 14400, 43200, and 86400.
System Action:
Processing terminates.
User Action:
Enter a valid value for the INTERVAL= parameter keyword.
Reason:
The required input data p1 was not provided. p2 indicates the failed function call.
System Action:
The request is rejected.
User Action:
Provide a valid value, and retry the request.
Reason:
The TSF data feed process received a logical record from the server that did not conform to the PD API protocol specification. p1 is the specific error that is found with the received data and has the following possible values:
The direction indicator of the record is invalid.
The sum of the header section and the data section does not add up to the total logical record length.
A record was received with a request code of x that is invalid or that this version of the PD API does not support.
A logical record was received with a request code of x that is not valid currently.
The heartbeat record type is invalid.
The expected heartbeat correlator does not match.
The allowed maximum time for record x to be send expired.
An error condition was detected. x is the record type. y describes the reason for the error.
System Action:
Processing terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The TCP/IP sockets interface is not active, which prevents the TSF data feed process from establishing a TCP connection with the TSF server.
System Action:
Process is terminated.
User Action:
To start the TCP/IP sockets interface:
Enter /PARMS and review the SOCKETS parameter group. Verify that all of the details are correct, and then press F6 to action the group.
If actioning the group fails, verify that the associated stack address space is available and initialized, then action the parameter group again.
Reason:
The TSF data feed process failed on a socket.
p1 identifies the socket option.
p2 is the return code.
p3 is the feedback code.
p4 is the socket error number and vendor-specific error code.
p5 (optional) shows a brief description of the error number.
System Action:
Processing terminates.
User Action:
Check the error codes. For assistance, contact CA Support at http://ca.com/support.
Reason:
The TSF data feed process failed to retrieve a valid TSF name/token pair. p1 is the reason for the failure.
System Action:
Process is terminated.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
This debug message is issued when debugging is turned on for the translator. p1 is variable information.
System Action:
None.
User Action:
Gather the log messages, and send them to the CA Support representative who asked for debugging to be turned on.
| Copyright © 2012 CA. All rights reserved. |
|