Filter
Top Products
COPDEX081E The system cannot specify an input
file.
Explanation: No additional information is available
for this message.
COPDEX082E The system cannot find the input file
VALUE_0.
Explanation: No additional information is available
for this message.
COPDEX083E The input file VALUE_0 is empty.
Explanation: No additional information is available
for this message.
COPDEX084E The operation type VALUE_0 is not
identified.
Explanation: No additional information is available
for this message.
COPDEX085E On the second line of the input file,
the system cannot find the query.
Explanation: No additional information is available
for this message.
COPDEX087E The workflow expects a locale that is
different from the one that is specified.
The locale of the device VALUE_0 is set
to VALUE_1. The workflow expects the
locale to be: VALUE_2.
Explanation: No additional information is available
for this message.
COPDEX092E The system cannot find the VALUE_0
workflow. The system cannot export the
execution logs for this workflow.
Explanation: No additional information is available
for this message.
COPDEX093E The system cannot create the VALUE_0
output file. Verify the directory path
and then try again.
Explanation: No additional information is available
for this message.
COPDEX094E The system cannot recognize the
VALUE_0 command option. Valid
options are -n[workflow name] or
-r[request id], -i[input file name] and
-f[output file name].
Explanation: No additional information is available
for this message.
COPDEX096E The property retrieval query VALUE_0
is not valid. Review the documentation
to find the recommended procedures.
Explanation: No additional information is available
for this message.
COPDEX097E The discovery keys file VALUE_0 is
not valid.
Explanation: The system cannot read the
DiscoveryKeys.ini file because the file includes errors.
Operator response: Correct the errors in the
DiscoveryKeys.ini file located in the
TIO_HOME/config subdirectory.
COPDEX098E The system obtained an empty profile
XML file name.
Explanation: The ITM Obtain OS Profiles workflow
generates an XML file that contains the list of profiles
installed in Tivoli Management Agent. This profile
XML file is copied to the IBM Tivoli Provisioning
Manager and then it is parsed by the Profile XML
Parser. The system encountered a problem when the
name of the profile XML file was an empty string.
Operator response: Verify that the ITM Obtain OS
Profiles workflow specifies the correct path to the
ProfileXMLParser Java plug-in.
COPDEX099E An IO error occurred when the SAX
XML parser parsed the profile XML file.
Explanation: The ITM Obtain OS Profiles workflow
generates an XML file that contains the list of profiles
that are installed in the Tivoli Management Agent. This
profile XML file is copied to the IBM Tivoli
Provisioning Manager and then it is parsed by the
Profile XML Parser. The SAX XML parser cannot read
the profile XML file. Because the XML file could not be
read, an IO exception occured.
Operator response: Verify that the ITM Obtain OS
Profiles workflow specifies the correct path to the
ProfileXMLParser Java plug-in. Verify that the system
correctly copied the XML file that contains the list of
profiles to the IBM Tivoli Provisioning Manager server.
Also verify that the parent directory of the XML file
includes the appropriate credentials.
COPDEX100E A parsing error occurred while the
system parsed the profile XML file.
Explanation: The ITM Obtain OS Profiles workflow
generates an XML file that contains the list of profiles
that are installed in Tivoli Management Agent. This
profile XML file is copied to the IBM Tivoli
Provisioning Manager and then it is parsed by the
Profile XML Parser. The XML parser cannot read the
profile XML file because it encountered a parsing error.
Chapter 10. Tivoli Intelligent Orchestrator messages 129