Data Service Probe Messages

The Data Service generates messages that report errors, warnings, and debugging information when it is queried for data. Each message has a unique prefix and ID number, so that it may be easily identified in the tables in this article. To help with diagnosing problems, the Data Service also returns contextual information for each message, which can include the following information:
uimpga-ga
The Data Service generates messages that report errors, warnings, and debugging information when it is queried for data. Each message has a unique prefix and ID number, so that it may be easily identified in the tables in this article. To help with diagnosing problems, the Data Service also returns contextual information for each message, which can include the following information:
  • Source of the message: This is usually the component that reported the message, in the format 
    host:port.
    If a particular Data Source reported the message, then this will be set to the hostname or IP address and port of the CIM server or z/VM Data Collector in question.
  • Reason for the message: This is an explanation of why the message was generated, or in the case of errors, what potentially caused the message to be generated.
  • Action the user should take in response to the message: This contains the recommended steps the user should perform to further diagnose or resolve the underlying cause of the message.
 
Contents
 
 
 
2
 
2
 
 
Data Service Messages
The following table describes the messages that the Data Service can report.
MessagePrefix
MessageID
Message Type
Message Description
Message Reason
Message Action
DAAS
 
0001
Error
There are no resources available that match the filter.
After applying the request filter, there were no resources found that matched using any of the available connectors.
Verify that all of the related connectors are configured properly, and their associated data sources are functioning correctly. Also, verify that the filter provided is a valid filter and that it is not filtering required data.
DAAS
0002
Error
Invalid filter provided: %s. Correct the filter.
The filter provided with the request is not a valid filter format.
Correct the filter format and retry the request.
DAAS
0003
Error
Unable to find the build number.
The Data Service was unable to read the build number information from the BUILDINFO file.
Contact technical support. Ensure that you attach the Data Service system log to the support ticket.
DAAS
0004
Error
Unable to find the version number.
The Data Service was unable to read the version number information from the BUILDINFO file.
Contact technical support. Ensure that you attach the Data Service system log to the support ticket.
DAAS
0005
Error
Unable to find the build time stamp.
The Data Service engine was unable to read the build time stamp information from the BUILDINFO file.
Contact technical support. Ensure that you attach the Data Service system log to the support ticket.
DAAS
0006
Error
There were no connectors that could satisfy the request for the resource \"%s\".
All of the available connectors were unable to satisfy the request for the resource.
Verify that all of the related connectors are configured properly and their associated data sources are functioning correctly.
DAAS
0015
Error
There are no resources available that match the request for \"%s\".
The request for data from Data Service succeeded, but the resource requested was not found.
Verify that all of the configured data source servers are behaving properly, available, and no other errors appear in the Data Service system log. If there are no other errors, contact technical support.
DAAS
0016
Error
Invalid query parameter \"%s\" (%s).
The query parameter is not valid for the REST query or it has an invalid value.
Specify a valid parameter.
DAAS
0017
Error
Required query parameter \"%s\" is missing.
The REST query has a required parameter that was not specified.
Add the required parameter to the REST query.
DAAS
0018
Error
Invalid path parameter \"%s\" (%s).
The path parameter has an invalid value.
Specify a valid parameter.
DAAS
0019
Error
There was a problem with parameter \"%s\": %s. See the log for details.
An unexpected problem occurred while processing the parameters.
Contact customer support. Be sure to include the data service log file.
DAAS
0020 
 Error
Internal server error, see the log for details.
An unexpected problem occurred while processing the request.
Contact customer support. Be sure to include the data service log file.
DAAS
0001
Debug
%s of the loaded connectors could filter the data per the filter supplied. %d of %d connector(s) filtered results, the rest of the filtering occurred in the Data Service.
This message contains debug information that details the quantity of the filtering (percentage) that took place in the Data Service as compared with the connectors and underlying data sources.
None. This message is for internal debugging purposes.
DAAS
0002
Debug
%s: Connector toggle completed successfully
This message contains debug information that indicates that a successful validation or invalidation of the request connectors occurred.
None. This message is for internal debugging purposes.
DAAS
0003
Debug
%s: Invalid Connector
This message contains debug information that indicates that an invalid connector name was passed when performing a validate or invalidate operation on connectors.
None. This message is for internal debugging purposes.
DAAS
0004 
 Debug
Current locale language is %s
 
This message contains debug information that displays the locale.
None. This message is for internal debugging purposes.
DAAS
 0005
 Debug
Locale language is %s
This message contains debug information that displays the locale.
None. This message is for internal debugging purposes.
DAAS
 0006
 Debug
No language specified; current locale %s is not altered.  
This message contains debug information that displays the locale. 
None. This message is for internal debugging purposes.
DAAS
 0007
 Debug
 You must specify a well-formed language code; current locale %s is not altered. 
This message contains debug information that displays the locale.
None. This message is for internal debugging purposes. 
z/OS Plug-in Messages
The following table describes the messages that the z/OS Plug-in can report.
MessagePrefix
MessageID
Message Type
Message Description
Message Reason
Message Action
ZOSPLG
0007
Error
You must supply a filter for %s to query %s metrics.
The Data Service requires the request to provide a filter for the metrics.
Add the filter to the request.
ZOSPLG
0008
Error
Invalid Range: The start and end ranges should be specified.
The Data Service engine requires the request to specify the range.
Specify a valid range.
ZOSPLG
0009
Error
Invalid Range: The start range should be specified.
The request did not specify the start range.
Specify the start range.
ZOSPLG
0010
Error
Invalid Range: The end range should be specified.
The request did not specify the end range.
Specify the end range.
ZOSPLG
0011
Error
Invalid Range: The start range should be a higher index than the end range.
The request contained a start range that was greater than the end range.
Specify a valid range.
ZOSPLG
0012
Error
Invalid Range: range limit is 2000 instances, inclusive.
The range was greater than 2000 instances.
Specify a valid range.
ZOSPLG
0013
Error
Invalid Range: the range cannot start with an index less than 1.
The start range was less than 1.
Specify a valid range.
ZOSPLG
0014
Error
Invalid Range: the range must be numeric.
The data format for the start range, end range, or both was not valid.
Specify a valid range.
CIM Connector Messages
The following table describes the messages that the CIM Connector can report.
MessagePrefix
MessageID
Message Type
Message Description
Message Reason
Message Action
CIM
 
0001
Error
Internal Server Error: %s
An internal server error occurred. Check the logs for details.
Contact technical support. Ensure that you attach the Data Service system log to the support ticket.
CIM
 
0002
Error
Error: The CIM configuration failed to load.
The Data Service could not load the CIM connector configuration file.
Ensure that the CIM configuration file exists and that it has a proper YAML syntax. See the Data Service system log file for additional details.
CIM
0003
Error
CIM Server Error: %s
A general error occurred on the CIM server. Examine the log files for further details.
If neither the message or log files contain enough information to diagnose the problem, contact technical support. Ensure that you attach the Data Service system log to the support ticket.
CIM
0004
Error
CIM Server Error: Invalid port.
The Data Service could not connect to the CIM server due to an invalid port.
See the messageSource for the hostname and port of the CIM server. Verify that the hostname and port have the correct values, and that the CIM server is running and reachable from the Data Service. If the values are determined invalid, check the CIM configuration file and adjust the port value.
CIM
0005
Error
CIM Server Error: Invalid CIM namespace.
An error occurred while trying to access the namespace supplied for the CIM server.
Verify that the user can access the CIM namespace provided, and that the namespace provided in the CIM configuration file is correct. By default, CIM uses "root/cimv2" as the namespace.
CIM
0006
Error
CIM Server Error: Unauthorized; unable to authenticate or authorize the user at the CIM server.
An error occurred while trying to authenticate or authorize the user at the CIM server.
Verify that the username and password that were provided are correct and can access the CIM server and the namespace provided.
CIM
0007
Error
CIM Server Error: Server Limit Exceeded. The CIM server is unable to handle any more requests.
An error occurred while trying to get data from the CIM server; there are too many active requests.
Verify that the CIM STC is behaving properly and does not require a restart. Examine the limit of the CIM server request limit and increase it if necessary. If CIM is functioning and configured properly, reduce the polling period of the Data Service clients (UIM probes). If errors persist, contact technical support.
CIM
0008
Error
CIM Connection Timeout: %s
The connection or request to CIM timed out. See the log for details.
Verify that the CIM STC is behaving properly and does not require a restart. Examine the timeout setting on the CIM configuration file, and try to increase that. If errors persist, contact technical support.
CIM
0009
Error
Missing parameters in request for CIM data: %s
The request for CIM data from Data Service was missing required parameters.
Contact technical support.
CIM
0010
Error
An unknown resource type was queued for execution. 
The request for CIM data from Data Service was using an unknown resource type.
Contact technical support.
CIM
0011
Error
Resource not available: The requested resource \"%s\" was not found.
The request for CIM data from Data Service succeeded, but the resource requested was not found.
Verify that all of the configured CIM servers are behaving properly, available, and no other error appear in the Data Service system log. If there are no other errors, contact technical support.
CIM
0012
Error
CIM Server Error: Invalid protocol.
The Data Service could not connect to the CIM server due to an invalid protocol.
Verify that the CIM server configuration file contains the correct protocol.
CIM
 0001
 Warn
Warning: duplicate CIM server found in configuration.
Multiple CIM servers with the same information were supplied in the CIM configuration file.
The duplicate server will be automatically ignored and the Data Service will operate normally. Remove the duplicate CIM server from the CIM configuration file at your earliest convenience.
Data Collector Connector Messages
The following table describes the messages that the Data Collector Connector can report.
MessagePrefix
MessageID
Message Type
Message Description
Message Reason
Message Action
DCSDK 
0001
Error
An internal server error occurred. See the log file for details.
An internal server error occurred. This problem should not occur during normal operation.
Contact technical support. Ensure that you attach the Data Service system log to the support ticket.
DCSDK
0002
Error
Failed to connect to the Data Collector: %s
The Data Service could not connect to the Data Collector.
See the messageSource for the hostname and port of the Data Collector. Verify that the hostname and port have the correct values and that the Data Collector is running and reachable from the Data Service. The message may have additional details about the reason for the connection failure.
DCSDK
0003
Error
Failed to parse JSON response from the Data Collector. See the log file for details.
The response from the Data Collector for z/VM does not contain valid JSON data.
See the messageSource for the hostname and port of the Data Collector. Verify that the hostname and port have the correct values. If the response did in fact come from a Data Collector contact technical support.
DCSDK
0004
Error
Unauthorized: unable to authenticate or authorize the user at the Data Collector.
The credentials provided with the request are not valid for the mentioned Data Collector.
See the messageSource for the hostname and port of the Data Collector. Verify that the credentials provided are valid for that particular Data Collector.
z/VM Connector Messages
The following table describes the messages z/VM Connector can report.
MessagePrefix
MessageID
Message Type
Message Description
Message Reason
Message Action
 ZVM
 0001
 Error
There are no resources available that match the request for \"%s\".
The request for data from Data Service succeeded, but the resource requested was not found. 
Verify that all of the configured data source servers are behaving properly, available, and no other errors appear in the Data Service system log. If there are no other errors, contact technical support. 
Data Collector for z/VM Messages
The following table describes the messages that the Data Collector for z/VM can report.
MessagePrefix
MessageID
Message Type
Message Description
Message Reason
Message Action
ZVMDSS
 
0001
Error
The process of collecting monitor records has not started.
The process of collecting monitor records has not started.
Repeat the request. The Monitor record collection process starts immediately after the Data Collector for z/VM server initializes.
ZVMDSS
0002
Error
The process of collecting monitor records stopped. See the log file for details.
The Data Collector for z/VM could not obtain z/VM monitor records.
Contact your z/VM system administrator and verify that the z/VM monitoring is activated. 
ZVMDSS
0003
Error
System name \"%s\" specified in the URI does not match this system name: \"%s\"
The Data Collector for z/VM collects data from a single z/VM system. This message is returned when there was no Data Collector for z/VM that collects data about the z/VM system specified in the URI.
Verify that all Data Collectors for z/VM are running. Query all z/VM systems to ensure that the name used is correct.
ZVMDSS
0004
Error
An internal server error occurred. See the log file for details.
Internal server error occurred. This problem should not occur during normal operation.
Contact technical support. Ensure that you attach the Data Collector for z/VM system log to the support ticket.
Data Collector for z/OS Messages
The following table describes the messages that the Data Collector for z/OS can report.
MessagePrefix
MessageID
Message Type
Message Description
Message Reason
Message Action
DISCOVERYDSS
0001
Error
Error in the execution of the script that is collecting data.
The error occurred during the execution of the REXX script that handles the collection of data.
Restart the Data Collector. If problem persists contact technical support. Ensure that you attach the Discovery Collector log to the support ticket.
DISCOVERYDSS
0002
Error
Script execution has timed out.
The request timed out. The execution of the REXX script took longer than expected.
Make sure your system is not under load. If problem persists contact technical support. Ensure that you attach the Discovery Collector log to the support ticket.
DISCOVERYDSS
0003
Error
Error occurred when reading the REXX script.
The Data Service was unable to read the REXX script.
Verify that the Data Service can find and has permission to execute the REXX script.
DISCOVERYDSS
0004
Error
An internal server error occurred. See the log file for details.
This error occurs when an internal server error occurs. This problem should not occur during normal operation.
Contact technical support. Ensure that you attach the Discovery Collector log to the support ticket.
DISCOVERYDSS
0005
Error
System identity check failed: parameter %s=%s is different from the value for this system: %s.
This error occurs when the data service asks the data collector for data about a particular system, but the data collector runs on a different system. This error should not be visible during normal operation of the data service.
Contact technical support. Ensure that you attach the Discovery Collector log to the support ticket.