CTGDIK001E
The SAP ABAP Application Server User Registry Connector failed to create an instance of the TDI Function Component ''Function Component Name''. This failure may have been caused by incorrect installation of the Function Component or an incorrect Function Component name.
Explanation:
The SAP ABAP Application Server User Registry Connector internally creates and uses an instance of the named Function Component to enable communication to the SAP ABAP AS system. The Connector was unable to create an instance of this Function Component.
Operator response:
To correct this problem, ensure that the named Function Component has been correctly installed. Ensure the jar file containing the Function Component implementation is located in the jars/functions. Check that the SAP Java Connector has been correctly deployed.
CTGDIK002E
An error has been detected while initializing the Function Component ''Function Component name''.
Explanation:
The SAP ABAP Application Server User Registry Connector internally creates and uses an instance of the named Function Component to enable communication to the SAP ABAP AS system. Before using the Function Component, the Connector needs to call the initialize method of the Function Component. The Connector initializes the Function Component with the configuration parameter information defined for the Connector.
Operator response:
Ensure that the configuration information defined for the Connector is correct. Check that the SAP Java Connector has been correctly deployed.
CTGDIK003E
An XSL transformation has failed. Ensure that a valid XML value has been supplied for the 'sapUserXml' attribute. The source XSL file name is ''file name''.
Explanation:
The XSL transformation defined in the named file has returned an empty XML result document.
Operator response:
If the transform has been applied to an XML request document, check that the XML request value is correct.
CTGDIK005E
The XSL files for the Connectors' putEntry method have not been configured. Ensure these files have been configured. If this error continues, try removing and adding the Connector to the AssemblyLine in the correct mode.
Explanation:
The putEntry method is called by the AssemblyLine when a Connector has been deployed in AddOnly mode. The SAP User Connector requires XSL stylesheets to process RFC requests responses executed against the target SAP system. In this case, the Connector was unable to read the required XSL stylesheets that it uses when deployed in AddOnly mode.
Operator response:
Ensure the XSL stylesheet files associated with Add Mode StyleSheets configuration parameter are correct. Try specifying the fully qualified path name of the XSL stylesheets. Ensure the XSL stylesheets have read permissions set.
CTGDIK006E
The XSL files for the Connectors' modEntry method have not been configured. Ensure these files have been configured. If this error continues, try removing and adding the Connector to the AssemblyLine in the correct mode.
Explanation:
The modEntry method is called by the AssemblyLine when a Connector has been deployed in Update mode. The SAP User Connector requires XSL stylesheets to process RFC requests responses executed against the target SAP system. In this case, the Connector was unable to read the required XSL stylesheets that it uses when deployed in Update mode.
Operator response:
Ensure the XSL stylesheet files associated with Update Mode StyleSheets configuration parameter are correct. Try specifying the fully qualified path name of the XSL stylesheets. Ensure the XSL stylesheets have read permissions set.
CTGDIK007E
The XSL files for the Connectors' deleteEntry method have not been configured. Ensure these files have been configured. If this error continues, try removing and adding the Connector to the AssemblyLine in the correct mode.
Explanation:
The deleteEntry method is called by the AssemblyLine when a Connector has been deployed in Delete mode. The SAP User Connector requires XSL stylesheets to process RFC requests responses executed against the target SAP system. In this case, the Connector was unable to read the required XSL stylesheets that it uses when deployed in Delete mode.
Operator response:
Ensure the XSL stylesheet files associated with Delete Mode StyleSheets configuration parameter are correct. Try specifying the fully qualified path name of the XSL stylesheets. Ensure the XSL stylesheets have read permissions set.
CTGDIK008E
The configured XSL file named ''file name'' does not exist.
Explanation:
The Connector has attempted to read the named XSL stylesheet file. This file does not exist in the specified location on the file system.
Operator response:
Ensure the XSL stylesheet file name is correct and exists. XSL stylesheet file names are specified using Connector parameters and differ based on the Connector mode.
CTGDIK009E
The configured XSL file named ''file name'' is not a valid file. A possible cause of this error might be that the configured name is actually a directory.
Explanation:
The Connector has attempted to read the named XSL stylesheet file. This file does not exist in the specified location on the file system or is not a valid file.
Operator response:
Ensure the XSL stylesheet file name is correct and exists. XSL stylesheet file names are specified using Connector parameters and differ based on the Connector mode.
CTGDIK010E
The configured XSL file named ''file name'' is not readable.
Explanation:
The Connector has attempted to read the named XSL stylesheet file. This file is not readable.
Operator response:
Ensure the file has read permissions set.
CTGDIK011E
The configuration parameter named ''file name'' is missing. The configured Connector mode requires additonal configuration of this parameter. Ensure these values have been configured. If this error continues, try removing and adding the Connector to the AssemblyLine in the correct mode. See the IBM TDI Users Guide for specific details.
Explanation:
The named Connector configuration parameter is missing.
Operator response:
Supply a value for the Connector configuration parameter. Refer to the IBM TDI Users Guide for details.
CTGDIK012E
The Attribute named ''attribute name'' is not present, or does not have a value, in the Entry supplied. This attribute must be present in the Connector entry.
Explanation:
See message.
Operator response:
Modify the Connector attribute mappings or client code. See the IBM TDI Users Guide for details regarding supported Connector attributes and values.
CTGDIK013W
No search criteria have been defined for the Connectors'' findEntry method. This method will return null to indicate no objects found.
Explanation:
Link criteria a typically needed for Connectors in Update, Delete, and Lookup mode. The Link Criteria is used to obtain the current details of a given object instance in the target system.
Operator response:
If the Connector is not behaving as expected, try specifying the Link Criteria. See the IBM TDI Users Guide for details.
CTGDIK014W
An XSL transform was performed before calling an SAP RFC. The result of the XSL transform was an empty document. An empty transform result typically occurs when mandatory XPath or Parameters are missing; for example, sapUserName. The RFC call will not be performed.
Explanation:
See message.
Operator response:
If the Connector is not behaving an expected, ensure the Connector entry contains the necessary attributes with associated XML values.
CTGDIK015W
The XSL transform defined in file ''file name'' resulted in an empty XML document. An empty transform result typically occurs when mandatory XPath or Parameters are missing, e.g. sapUserName. The RFC call was not performed.
Explanation:
See message.
Operator response:
If the Connector is not behaving an expected, ensure the Connector entry contains the necessary attributes with associated XML values.
CTGDIK016W
Some application level errors and warnings have been detected while creating the SAP ABAP AS user. The operation may be incomplete.
Explanation:
The Connector has received a response from the SAP system which indicates that some request data or application state might be incorrect. This status is typically indicated in the RFC parameter named RETURN.
Operator response:
Ensure the target SAP system and target application are functioning correctly. Ensure the request data values mapped onto the Connector are valid with respect to SAP business logic.
CTGDIK017W
Some application level errors and warnings have been detected while deleting the SAP ABAP AS user. The operation may be incomplete.
Explanation:
The Connector has received a response from the SAP system which indicates that some request data or application state might be incorrect. This status is typically indicated in the RFC parameter named RETURN.
Operator response:
Ensure the target SAP system and target application are functioning correctly. Ensure the request data values mapped onto the Connector are valid with respect to SAP business logic.
CTGDIK018W
Some application level errors and warnings have been detected while updating the SAP ABAP AS user. The operation may be incomplete.
Explanation:
The Connector has received a response from the SAP system which indicates that some request data or application state might be incorrect. This status is typically indicated in the RFC parameter named RETURN.
Operator response:
Ensure the target SAP system and target application are functioning correctly. Ensure the request data values mapped onto the Connector are valid with respect to SAP business logic.
CTGDIK019E
The Connector detected an exception during initialization. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK020E
The Connector detected an exception while performing a schema query. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK021E
The Connector detected an exception while adding an entry. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK022E
The Connector detected an exception while deleting an entry. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK023E
The Connector detected an exception while modifying an entry. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK024E
The Connector detected an exception while attempting to find an entry. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK025E
The Connector detected an exception while selecting entries in preparation for iterator mode processing. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK026E
The Connector detected an exception while iterating through the known entries. The number of entries successfully processed before the exception was number of entries. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK027E
No XSL style sheet files have been configured for the Connector running in ''Connector mode'' mode. This mode requires XSL style sheets to be defined. See the IBM Tivoli Directory Integrator Users Guide for specific details.
Explanation:
See message.
Operator response:
Correct the Connector configuration parameters related to XSL stylesheet specifications.
CTGDIK028I
The findEntry method is returning null.
Explanation:
This is an informational message only.
CTGDIK029I
The findEntry method is returning the initialized entry.
Explanation:
This is an informational message only.
CTGDIK030I
The findEntry method is returning null.
Explanation:
This is an informational message only.
CTGDIK031I
Adding message to error list: ''message''.
Explanation:
This is an informational message only.
CTGDIK032I
Adding message to warning list: ''message''.
Explanation:
This is an informational message only.
CTGDIK033I
Extracting the return data from element named ''tag name''.
Explanation:
This is an informational message only.
CTGDIK034I
Creating AbapErrorInfo object: message=''message'', error number=''error number'', error flag=''error flag''.
Explanation:
This is an informational message only.
CTGDIK035I
The XML element to return is a table style element: ''boolean''.
Explanation:
This is an informational message only.
CTGDIK036I
The result of pre RFC XSL call is: ''string''.
Explanation:
This is an informational message only.
CTGDIK037I
The result of RFC call is: ''string''.
Explanation:
This is an informational message only.
CTGDIK038I
Executing function for XSL file: ''file''.
Explanation:
This is an informational message only.
CTGDIK101E
The SAP ABAP AS BOR Connector has failed to create an instance of the IBM TDI Function Component named ''Function Component name''. This failure may have been caused by incorrect installation of the Function Component or incorrect Function Component name.
Explanation:
The SAP ABAP AS BOR Connector internally creates and uses an instance of the named Function Component to enable communication to the SAP ABAP AS system. The Connector was unable to create an instance of this Function Component.
Operator response:
To correct this problem, ensure that the named Function Component has been correctly installed. Ensure the jar file containing the Function Component implementation is located in the jars/functions. Check that the SAP Java Connector has been correctly deployed.
CTGDIK102E
An error has been detected while initializing the Function Component named ''Function Component name''.
Explanation:
The SAP ABAP AS BOR Connector internally creates and uses an instance of the named Function Component to enable communication to the SAP ABAP AS system. Before using the function component, the Connector needs to call the initalize method of the Function Component. The Connector initializes the Function Component with the configuration parameter information defined for the Connector.
Operator response:
Ensure that the configuration information defined for the Connector is correct. Check that the SAP Java Connector has been correctly deployed.
CTGDIK103E
An XSL transformation has failed. Ensure that a valid XML value has been supplied for the 'sapXml' attribute. The source XSL file name is ''file name''.
Explanation:
The XSL transformation defined in the named file has returned an empty XML result document.
Operator response:
If the transform has been applied to an XML request document, check that the XML request value is correct.
CTGDIK105E
The XSL files for the Connector's putEntry method have not been configured. Ensure these files have been configured. If this error continues, try removing and adding the Connector to the AssemblyLine in the correct mode.
Explanation:
The putEntry method is called by the AssemblyLine when a Connector has been deployed in AddOnly mode. The SAP User Connector requires XSL stylesheets to process RFC requests and responses executed against the target SAP system. In this case, the Connector was unable to read the required XSL stylesheets that it uses when deployed in AddOnly mode.
Operator response:
Ensure the XSL stylesheet files associated with Add Mode StyleSheets configuration parameter are correct. Try specifying the fully qualified path name of the XSL stylesheets. Ensure the XSL stylesheets have read permissions set.
CTGDIK106E
The XSL files for the Connectors' modEntry method have not been configured. Ensure these files have been configured. If this error continues, try removing and adding the Connector to the AssemblyLine in the correct mode.
Explanation:
The modEntry method is called by the AssemblyLine when a Connector has been deployed in Update mode. The SAP User Connector requires XSL stylesheets to process RFC requests and responses executed against the target SAP system. In this case, the Connector was unable to read the required XSL stylesheets that it uses when deployed in Update mode.
Operator response:
Ensure the XSL stylesheet files associated with Update Mode StyleSheets configuration parameter are correct. Try specifying the fully qualified path name of the XSL stylesheets. Ensure the XSL stylesheets have read permissions set.
CTGDIK107E
The XSL files for the Connectors' deleteEntry method have not been configured. Ensure these files have been configured. If this error continues, try removing and adding the Connector to the AssemblyLine in the correct mode.
Explanation:
The deleteEntry method is called by the AssemblyLine when a Connector has been deployed in Delete mode. The SAP User Connector requires XSL stylesheets to process RFC requests and responses executed against the target SAP system. In this case, the Connector was unable to read the required XSL stylesheets that it uses when deployed in Delete mode.
Operator response:
Ensure the XSL stylesheet files associated with Delete Mode StyleSheets configuration parameter are correct. Try specifying the fully qualified path name of the XSL stylesheets. Ensure the XSL stylesheets have read permissions set.
CTGDIK108E
The configured XSL file named ''file name'' does not exist.
Explanation:
The Connector has attempted to read the named XSL stylesheet file. This file does not exist in the specified location on the file system.
Operator response:
Ensure the XSL stylesheet file name is correct and exists. XSL stylesheet file names are specified using Connector parameters and differ based on the Connector mode.
CTGDIK109E
The configured XSL file named ''file name'' is not a valid file. A possible cause of this error might be that the configured name is actually a directory.
Explanation:
The Connector has attempted to read the named XSL stylesheet file. This file does not exist in the specified location on the file system or is not a valid file.
Operator response:
Ensure the XSL stylesheet file name is correct and exists. XSL stylesheet file names are specified using Connector parameters and differ based on the Connector mode.
CTGDIK110E
The configured XSL file named ''file name'' is not readable.
Explanation:
The Connector has attempted to read the named XSL stylesheet file. This file is not readable.
Operator response:
Ensure the file has read permissions set.
CTGDIK111E
The configuration parameter named ''parameter name'' is missing
Explanation:
The named Connector configuration parameter is missing.
Operator response:
The configured Connector mode requires additional configuration of this parameter. Ensure these values have been configured. If this error continues, try removing and adding the Connector to the AssemblyLine in the correct mode. See the the IBM TDI Users Guide for specific details.
CTGDIK112E
The Attribute named ''file name'' is not present, or does not have a value in the Entry supplied. This attribute must be present in the Connector entry.
Explanation:
The named Connector configuration parameter is missing.
Operator response:
Supply a value for the Connector configuration parameter. Refer to the IBM Tivoli Directory Integrator Users Guide for details.
CTGDIK113W
No search criteria have been defined for the Connectors' findEntry method. This method will return null to indicate no objects found.
Explanation:
Link criteria are typically needed for Connectors in Update, Delete, and Lookup mode. The Link Criteria is used to obtain the current details of a given object instance in the target system.
Operator response:
If the Connector is not behaving as expected, try specifying the Link Criteria. See the IBM TDI Users Guide for details.
CTGDIK114W
An XSL transform was performed before calling an SAP RFC. The result of the XSL transform was an empty document. An empty transform result typically occurs when mandatory XPath or Parameters are missing. The RFC call will not be performed.
Explanation:
See message.
Operator response:
If the Connector is not behaving an expected, ensure the Connector entry contains the necessary attributes with associated XML values.
CTGDIK115W
The XSL transform defined in file ''file name'' resulted in an empty XML document. An empty transform result typically occurs when mandatory XPath or Parameters are missing. The RFC call was not performed.
Explanation:
See message.
Operator response:
If the Connector is not behaving an expected, ensure the Connector entry contains the necessary attributes with associated XML values.
CTGDIK116W
Some application level errors and warnings have been detected while creating the ABAP AS user. The operation may be incomplete.
Explanation:
The Connector has received a response from the SAP system which indicates that some request data or application state might be incorrect. This status is typically indicated in the RFC parameter named RETURN.
Operator response:
Ensure the target SAP system and target application are functioning correctly. Ensure the request data values mapped onto the Connector are valid with respect to SAP business logic.
CTGDIK117W
Some application level errors and warnings have been detected while deleting the ABAP AS user. The operation may be incomplete.
Explanation:
The Connector has received a response from the SAP system which indicates that some request data or application state might be incorrect. This status is typically indicated in the RFC parameter named RETURN.
Operator response:
Ensure the target SAP system and target application are functioning correctly. Ensure the request data values mapped onto the Connector are valid with respect to SAP business logic.
CTGDIK118W
Some application level errors and warnings have been detected while updating the ABAP AS user. The operation may be incomplete.
Explanation:
The Connector has received a response from the SAP system which indicates that some request data or application state might be incorrect. This status is typically indicated in the RFC parameter named RETURN.
Operator response:
Ensure the target SAP system and target application are functioning correctly. Ensure the request data values mapped onto the Connector are valid with respect to SAP business logic.
CTGDIK119E
The Connector detected an exception during initialization. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK120E
The Connector detected an exception while performing a schema query. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK121E
The Connector detected an exception while adding an entry. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK122E
The Connector detected an exception while deleting an entry. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK123E
The Connector detected an exception while modifying an entry. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK124E
The Connector detected an exception while attempting to find an entry. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK125E
The Connector detected an exception while selecting entries in preparation for iterator mode processing. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK126E
The Connector detected an exception while iterating through the known entries. The number of entries successfully processed before the exception was number of entries. The message is: ''exception''.
Explanation:
See message.
Operator response:
See exception stack trace. Check for earlier errors or warnings in the log.
CTGDIK127E
No XSL style sheet files have been configured for the Connector running in ''Connector mode'' mode. This mode requires XSL style sheets to be defined. See the IBM Tivoli Directory Integrator Users Guide for specific details.
Explanation:
See message.
Operator response:
Correct the Connector configuration parameters related to XSL stylesheet specifications.
CTGDIK128E
Delete mode requires the attribute named 'sapXml' to present if no Link Criteria have been defined.
Explanation:
When deleting an object instance from the target system, the Connector performs a lookup of the object attributes. Link Criteria are needed to find the given object instance.
Operator response:
Specify the Link Criteria for the Connector.
CTGDIK129I
Adding message to error list: ''message''.
Explanation:
This is an informational message only.
CTGDIK130I
Adding message to warning list: ''message''.
Explanation:
This is an informational message only.
CTGDIK131I
Extracting the return data from element named ''tag name''.
Explanation:
This is an informational message only.
CTGDIK132I
Creating AbapErrorInfo object: message=''message'', error number=''error number'', error flag=''error flag''.
Explanation:
This is an informational message only.
CTGDIK133I
The XML element to return is a table style element: ''boolean''.
Explanation:
This is an informational message only.
CTGDIK134I
The result of pre RFC XSL call is: ''string''.
Explanation:
This is an informational message only.
CTGDIK135I
The result of RFC call is: ''string''.
Explanation:
This is an informational message only.
CTGDIK136I
Executing function for XSL file:: ''file''.
Explanation:
This is an informational message only.
CTGDIK137I
The findEntry method is returning the initialized entry.
Explanation:
This is an informational message only.
CTGDIK138I
The findEntry method is returning null.
Explanation:
This is an informational message only.
CTGDIK201E
Must call the initialize method first!
Explanation:
An attempt to use an uninitialized Function Component has been detected. This error may occur if the initialize method has not be successfully called before calling other Function Component methods. This may also occur if a Function Component method has been called after calling terminate.
Operator response:
Correct the calling code so that initialize method has been successfully called before calling other Function Component methods.
CTGDIK202E
Entry Attribute ''attribute name'' missing value.
Explanation:
A mandatory attribute is missing or is missing a value.
Operator response:
Correct the AssemblyLine mapping or client code so that the named attribute has a value.
CTGDIK203E
Entry Attribute ''attribute name'' missing value or value does not match expected type. Expected type: ''document type''.
Explanation:
A mandatory attribute is missing or is missing a value of the correct type.
Operator response:
Correct the AssemblyLine mapping or client code so that the named attribute has a value and its type is as expected. See Users Guide for details.
CTGDIK204E
Entry attribute ''attribute name'' must be one of 'xmlDomDocument', 'xmlString', or 'multiValuedAttributes'.
Explanation:
See message.
Operator response:
Correct the AssemblyLine mapping or client code.
CTGDIK205E
Entry object expected.
Explanation:
The object type passed the Function Components perform method was not a IBM TDI Entry.
Operator response:
Correct the client code.
CTGDIK206E
Must call initialize() first.
Explanation:
An attempt has been made to use an uninitialized Function Component.
Operator response:
Correct the client code. Ensure the initialize method is called before using the Function Component. Ensure the Function Component is not use after calling its terminate method.
CTGDIK207E
Function cannot be reused once terminate() has been called.
Explanation:
An attempt has been made to use the Function Component after its terminate method has been called.
Operator response:
Correct the client code. Ensure the initialize method is called before using the Function Component. Ensure the Function Component is not use after calling its terminate method.
CTGDIK208E
''class name'' != ''class name''.
Explanation:
The classname does not match the expected classname.
Operator response:
Correct the AssemblyLine attribute mapping or client code.
CTGDIK209E
Mandatory RFC parameter named ''field name'' has not been supplied.
Explanation:
RFC modules in SAP often define mandatory import and table parameters. The parameters must be present when calling the RFC.
Operator response:
For the RFC being called, use transaction SE37 in the target SAP system to determine the mandatory RFC parameters. Correct the AssemblyLine attribute mapping or client code.
CTGDIK210E
Length of supplied value for field ''field name'' exceeds maximum length ''field length''.
Explanation:
The length of the value supplied for the named RFC parameters or table parameter field exceeds the maximum length defined by the RFC in the target SAP system.
Operator response:
For the RFC being called, use transaction SE37 in the target SAP system to determine the length of the given RFC parameter or table parameter field. Correct the AssemblyLine attribute mapping or client code.
CTGDIK211E
''class name'' does not equal ''class name''.
Explanation:
The classname does not match the expected classname.
Operator response:
Correct the AssemblyLine attribute mapping or client code.
CTGDIK212E
Mandatory RFC parameter named ''field name'' has not been supplied.
Explanation:
RFC modules in SAP often define mandatory import and table parameters. The parameters must be present when calling the RFC.
Operator response:
For the RFC being called, use transaction SE37 in the target SAP system to determine the mandatory RFC parameters. Correct the AssemblyLine attribute mapping or client code.
CTGDIK213E
No such function named ''function name''.
Explanation:
The entry attributes and values represent an RFC request for an RFC module that does not exist in the target SAP system, or has not been released.
Operator response:
Ensure the RFC exists on the target SAP system. Ensure the RFC name is correctly specified in the entry.
CTGDIK214E
The remove method is not implemented.
Explanation:
See message.
Operator response:
See the Users Guide.
CTGDIK215E
The Function Component detected an exception while attempting to disconnect. The message is: ''exception''.
Explanation:
See message.
Operator response:
Ensure the network between the Function Component and SAP is available.
CTGDIK216E
Connection pool ''pool name'' already exists. The message is: ''exception''.
Explanation:
See message.
Operator response:
Restart the AssemblyLine.
CTGDIK217E
No more connections available in ''pool name''. The message is: ''exception''.
Explanation:
See message.
Operator response:
Restart the AssemblyLine.
CTGDIK218E
Unable to establish a connection using ''pool name''. The message is: ''exception''.
Explanation:
See message.
Operator response:
Ensure the network is available. Ensure the target SAP system is available.
CTGDIK219E
Unable to execute RFC ''function name''. The message is: ''exception''.
Explanation:
See message.
Operator response:
Ensure the RFC on the target SAP system is functioning correctly.
CTGDIK220E
Communication error with SAP ABAP Application Server. The message is: ''exception''.
Explanation:
See message.
Operator response:
Ensure the network is available. Ensure the target SAP system is available.
CTGDIK221W
Trouble invoking ''function name''. The function has been retried apos;'number of retries'' times.
Explanation:
See message.
Operator response:
Ensure the network is available. Ensure the target SAP system is available.
CTGDIK222E
Trouble invoking ''function name''. The function has been retried apos;'number of retries'' times. The message is: ''exception''.
Explanation:
See message.
Operator response:
Ensure the network is available. Ensure the target SAP system is available.
CTGDIK223E
Unable to create DOM parser. The message is: ''exception''.
Explanation:
See message.
Operator response:
Ensure IBM TDI has been correctly installed.
CTGDIK224E
Unable to parse DOM parser. The message is: ''exception''.
Explanation:
See message.
Operator response:
Ensure IBM TDI has been correctly installed.
CTGDIK225E
Unable to read DOM parser. The message is: ''exception''.
Explanation:
See message.
Operator response:
Ensure TDI has been correctly installed.
CTGDIK226E
Failed to prepare parameters for RFC. The message is: ''exception''.
Explanation:
See message.
Operator response:
Ensure the AssemblyLine attribute mapping or client code has correctly initialized the entry for the Function Component.
CTGDIK227I
Executing function for XSL file:: ''file''. Multiple elements with name ''element name'' are present in the structure type. Using the element in first position following the preorder traversal.
Explanation:
This is an informational message only.
CTGDIK228I
DOM: Connecting to SAP ABAP Application Server...
Explanation:
This is an informational message only.
CTGDIK229I
DOM: Connecting to SAP ABAP Application Server...
Explanation:
This is an informational message only.
CTGDIK230I
DOM: Getting the dynamic proxy.
Explanation:
This is an informational message only.
CTGDIK231I
DOM: Getting the importer.
Explanation:
This is an informational message only.
CTGDIK232I
DOM: Populating the request with data values.
Explanation:
This is an informational message only.
CTGDIK233I
DOM: Executing RFC: ''function name''.
Explanation:
This is an informational message only.
CTGDIK234I
DOM: Exporting RFC results.
Explanation:
This is an informational message only.
CTGDIK235I
DOM: Disconnecting...
Explanation:
This is an informational message only.
CTGDIK236I
XSchema: Connecting to the SAP system.
Explanation:
This is an informational message only.
CTGDIK237I
XSchema: Getting the dynamic proxy.
Explanation:
This is an informational message only.
CTGDIK238I
XSchema: Creating the importer.
Explanation:
This is an informational message only.
CTGDIK239I
XSchema: Populating the request with data values.
Explanation:
This is an informational message only.
CTGDIK240I
XSchema: Disconnecting...
Explanation:
This is an informational message only.
CTGDIK241I
XSchema: Getting the importer.
Explanation:
This is an informational message only.
CTGDIK242I
Entry: Connecting to SAP system...
Explanation:
This is an informational message only.
CTGDIK243I
Entry: Getting the dynamic proxy.
Explanation:
This is an informational message only.
CTGDIK244I
Entry: Disconnecting...
Explanation:
This is an informational message only.
CTGDIK245I
The input entry is: ''entry''.
Explanation:
This is an informational message only.
CTGDIK246I
Obtaining RFC request from DOM Document.
Explanation:
This is an informational message only.
CTGDIK247I
Invoking RFC from DOM Document.
Explanation:
This is an informational message only.
CTGDIK248I
Obtaining RFC request from XML string.
Explanation:
This is an informational message only.
CTGDIK249I
Invoking RFC from XML string.
Explanation:
This is an informational message only.
CTGDIK250I
Invoking RFC using MVA parameter.
Explanation:
This is an informational message only.
CTGDIK251I
Using JCo config option ''option name'': ''option value''.
Explanation:
This is an informational message only.
CTGDIK252I
The supplied options are not supported or were incomplete.
Usage: java -cp (SAP_JCO_HOME)/sapjaco.jar;(TDI_HOME)/jars/functions/SapR3RfcFC.jar -Djava.library.path=(SAP_JCO_HOME) com.ibm.di.fc.sapr3rfc.RfcXmlInvoker-f [input XML file] -o [output XML file] -p [JCO Connection properties file]
-f The name of the file containing the input RFC request as XML.
-o The name of the file to be produced containing RFC response as XML.
-p The JCO Connection properties file.
Explanation:
This is an informational message only.
CTGDIK253I
Input entry value: ''entry value''.
Explanation:
This is an informational message only.
CTGDIK301I
Started JCo IDoc Server and listening for requests.
Explanation:
This is an informational message only.
CTGDIK302E
Unable to initialize the Connector. Exception occurred: exception
Explanation:
See message.
Operator response:
See the exception message for additional information on how to respond. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK303E
The ''parameter name'' parameter must be set to use the SAP IDocs Connector.
Explanation:
A value is required for this RFC Connection parameter for either the RFC Server or RFC Client connection.
Operator response:
Specify the required parameter in the Connector.
CTGDIK304I
Optional RFC Connection parameter ''parameter name'' set with the value ''parameter value''.
Explanation:
This is an informational message only.
CTGDIK305I
Connector configuration parameter ''parameter name'' set with the value ''parameter value''.
Explanation:
This is an informational message only.
CTGDIK306I
Checking if TID Manager for TID ''TID'' is available for processing.
Explanation:
This is an informational message only.
CTGDIK307E
No TID Manager found for TID ''TID''.
Explanation:
The Connector IDoc Inbound queue has a key of the given transaction identifier but has not had a TID Manager object created.
Operator response:
An internal error occurred. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK308I
TID Manager for TID ''TID'' is available for processing.
Explanation:
This is an informational message only.
CTGDIK309W
Provided poll time value is 0 or less. Single request will be processed only.
Explanation:
The Connector will operate in standard Iterator mode. Only one IDoc request will be processed by the Connector. After all the IDocs have been place in the AssemblyLine as IBM TDI entries, the Connector will return null to exit Iterator mode.
Operator response:
Check that this was an intentional action. If not the poll time must be greater then zero.
CTGDIK310I
Polling for next the IDoc request in getNextEntry method.
Explanation:
This is an informational message only.
CTGDIK311E
Exception generated while polling.
Explanation:
Unexpected error has occurred in Thread.sleep(pollTime).
Operator response:
Restart the AssemblyLine of the Connector.
CTGDIK312E
Null Entry found in the Entry list of the TID Manager for TID ''TID''.
Explanation:
Unexpected error has occurred. Null entries should not be possible in a TID Manager.
Operator response:
An internal error occurred. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK313W
No TID provided with this RFM call. Manually removing the TID Manager to complete the TID Management cycle.
Explanation:
An RFM request has been processed by the Connector, where no transaction identifier was provided.
Operator response:
No response required. RFM Entry will be place on AssemblyLine the same as is done for IDoc entries.
CTGDIK314I
No Parser Attached to the Connector.
Explanation:
This is an informational message only.
CTGDIK315I
Finished processing TID Manager for TID ''TID'' . TID ready for confirmation.
Explanation:
This is an informational message only.
CTGDIK316E
The getNextEntry method returned null in Iterator mode with a valid poll time.
Explanation:
The modified Iterator mode to act as a Server has failed. Exception has been thrown to prevent standard Iterator mode taking place.
Operator response:
An internal error occurred. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK317W
Entry contains no XML attributes to parse.
Explanation:
An XML Parser has been attached but there are no XML valued attributes available.
Operator response:
An internal error occurred. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK318I
Attempting to parse XML content with attached Parser.
Explanation:
This is an informational message only.
CTGDIK319W
The attached Parser returned a null Entry.
Explanation:
A Parser has been attached but no entry with parsed attributes was produced.
Operator response:
Check that an XML Parser was used, and that the parser was configured correctly.
CTGDIK320E
Unable to parse the XML. Exception occurred: exception
Explanation:
See message.
Operator response:
See the exception message for additional information on how to respond. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK321W
Exception occurred while generating schema: exception
Explanation:
See message.
Operator response:
See the exception message for additional information on how to respond. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK322E
Unable to start the JCo IDoc Server.
Explanation:
The Connector was not able to start the internal JCo IDoc Server.
Operator response:
The problem may be caused by invalid Config parameters. Verify the Config parameters of the Connector are set properly. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK323I
Polling for next IDoc request in getNextClient method.
Explanation:
This is an informational message only.
CTGDIK324I
The onCheckTID method was called for TID ''TID''. . TID Management already in progress for this TID.
Explanation:
This is an informational message only.
CTGDIK325I
The onCheckTID method was called for TID ''TID''. TID Management beginning now for this TID. Next handleRequest method call will begin the inbound processing.
Explanation:
This is an informational message only.
CTGDIK326I
TID Manager for TID ''TID'' is not yet confirmed. Current status is ''status''.
Explanation:
This is an informational message only.
CTGDIK327I
TID Manager for TID ''TID'' is now confirmed.
Explanation:
This is an informational message only.
CTGDIK328I
The handleRequest method was invoked. Current TID value is ''TID'' . Incoming IDoc list request contains ''number of IDocs'' IDocs.
Explanation:
This is an informational message only.
CTGDIK329E
Unable to convert IDoc request into a IBM TDI entry. The writeIDocToTDIEntry method returned null IDoc Entry.
Explanation:
The functionality in the Connector that converts a JCoIDoc.Document object to a IBM TDI Entry object has failed.
Operator response:
The problem may be an issue with the JCo middleware. Verify the JCo middleware is installed properly with all dependent libaries. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK330E
No value provided for current transaction identifier. This list of IDocs will not be processed.
Explanation:
The Connector received a handleRequest method callback without a prior onCheckTID method call.
Operator response:
The problem may be an issue with the JCo middleware. Verify the JCo middleware is installed properly with all dependent libaries. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK331E
Current TID ''TID'' already has a TID Manager and is being processed. Ignoring this request.
Explanation:
The Connector received a second handleRequest method callback for a particular transaction identifier.
Operator response:
The problem may be an issue with the JCo middleware. Verify the JCo middleware is installed properly with all dependent libaries. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK332E
No IDoc Entries available. Ignoring request for TID ''TID''.
Explanation:
The Connector received a handleRequest method callback for a particular transaction identifier but no IDocs were contained in that request.
Operator response:
The problem may be an issue with the JCo middleware. Verify the JCo middleware is installed properly with all dependent libaries. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK333I
Created TID Manager for TID ''TID'' with ''number of IDoc entries'' IDoc entries for processing.
Explanation:
This is an informational message only.
CTGDIK334E
Unable to convert IDoc request into a IBM TDI entry. The Connector received a null JCoIDoc.Document object.
Explanation:
The Connector encountered a null IDoc object.
Operator response:
The problem may be an issue with the JCo middleware. Verify the JCo middleware is installed properly with all dependent libaries. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK335I
The handleRequest method was invoked. Current TID value is ''TID value''. Incoming RFM request is ''RFM name''.
Explanation:
This is an informational message only.
CTGDIK336W
No TID received with this RFM request. Defaulting for TID Management processing.
Explanation:
The Connector has received a request that contains a SAP client Remote Function Call. No transaction identifier has been provided with the request so the Connector will use a dummy value for the purposes of TID Management.
Operator response:
No response required.
CTGDIK337I
RFM as XML: [''TID''].
Explanation:
This is an informational message only.
CTGDIK338E
Unable to convert RFM request into a IBM TDI entry. No RFMs provided in request.
Explanation:
The Connector has received a request that should contain a SAP client Remote Function Call, but the Connector was not able to produce a IBM TDI Entry for the RFM.
Operator response:
The problem may be an issue with the JCo middleware. Verify the JCo middleware is installed properly with all dependent libaries. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK339E
Unable to convert RFM request into a IBM TDI entry. The JCO.Function object received was null.
Explanation:
The Connector has received a request that contained a null JCO.Function object. This should not happen a may indicate a problem in the JCo middleware or the Connector configuration.
Operator response:
The problem may be an issue with the JCo middleware. Verify the JCo middleware is installed properly with all dependent libaries. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK340I
Storing RFM request as XML file ''file name''.
Explanation:
This is an informational message only.
CTGDIK341E
Failed to read RFM request XML file ''file name'' into IBM TDI Entry. No contents found in file.
Explanation:
The Connector stores RFM as a file that contains their XML form as part of RFM processing. This message indicates that no XML content was available from the file.
Operator response:
An internal error occurred. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK342E
Failed to process RFM XML file. Exception occurred: exception
Explanation:
The Connector stores RFM as a file that contains their XML form as part of RFM processing. This message indicates an exception occurred while handling the file.
Operator response:
See the exception message for additional information on how to respond. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK343E
An exception occurred. Exception trapped from JCo Server with Program ID of ''Program ID'': exception
Explanation:
The Connector uses an exception listener to trap internal JCo exceptions. The exception message indicates the type of exception trapped.
Operator response:
See the exception message from the JCo Server in the message for additional information on how to respond. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK344E
An error was encountered. An error message was trapped from JCo Server with Program ID of ''Program ID'': error message.
Explanation:
The Connector uses an error message listener to trap internal JCo error messages when an error is encountered.
Operator response:
See the error message from the JCo Server in the message for additional information on how to respond. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK345I
State Change occurred for JCo Server with Program ID of ''Program ID''. Previous State: ''old state'' New State: ''new state''.
Explanation:
This is an informational message only.
CTGDIK346I
Trace message trapped from JCo Server. Trace Level: ''trace level'' Trace Message: ''trace message''.
Explanation:
This is an informational message only.
CTGDIK347W
File was not able to be deleted: ''file name''.
Explanation:
This is an informational message only.
CTGDIK348I
Import parameter: ''value''.
Explanation:
This is an informational message only.
CTGDIK349I
The import parameter is a structure.
Explanation:
This is an informational message only.
CTGDIK350I
The import parameter is a table.
Explanation:
This is an informational message only.
CTGDIK351I
The import parameter is a simple field.
Explanation:
This is an informational message only.
CTGDIK352I
No Input Fields required for this RFM.
Explanation:
This is an informational message only.
CTGDIK353I
RFM export Paramters:
--------------------
Explanation:
This is an informational message only.
CTGDIK354I
The export parameter is a structure.
Explanation:
This is an informational message only.
CTGDIK355I
The export parameter is a simple field.
Explanation:
This is an informational message only.
CTGDIK356I
No Export Fields returned for this RFM.
Explanation:
This is an informational message only.
CTGDIK357I
RFM table Paramters:
--------------------
Explanation:
This is an informational message only.
CTGDIK358I
Rows found for table: ''table name''.
Explanation:
This is an informational message only.
CTGDIK359I
No rows found for table: ''table name''.
Explanation:
This is an informational message only.
CTGDIK360I
Field ''field name'' has string value ''value''.
Explanation:
This is an informational message only.
CTGDIK362I
Field ''field name'' has raw value ''value''.
Explanation:
This is an informational message only.
CTGDIK364I
A bad field value passed.
Explanation:
This is an informational message only.
CTGDIK365I
Input is a Record. Record fields are as follows:
Explanation:
This is an informational message only.
CTGDIK366I
Record field: ''value''.
Explanation:
This is an informational message only.
CTGDIK367I
Input is a table. Table records are as follows:
Explanation:
This is an informational message only.
CTGDIK368I
Input is a structure. Structure records are as follows:
Explanation:
This is an informational message only.
CTGDIK401E
Invalid ENTRY type: Entry Type.
Explanation:
The Connector was configured to use an Entry Type that is not supported.
Operator response:
Reconfigure the Connector to use a valid Entry Type.
CTGDIK402E
Missing ENTRY type. Entry type is null.
Explanation:
The Connector was configured to use no Entry Type.
Operator response:
Set the Entry Type in the Connector.
CTGDIK403E
Invalid TAM configuration file: file name.
Explanation:
The Connector was configured to use an invalid TAM Configuration File.
Operator response:
Reconfigure the Connector to use a valid TAM Configuration File.
CTGDIK404E
Could not log on to TAM.
Explanation:
The Connector was configured to use invalid TAM credentials.
Operator response:
Ensure the TAM ID and TAM Password configuration parameters of the Connector are set to valid values.
CTGDIK405E
Could not query TAM Domains.
Explanation:
The Connector was unable to query TAM for a list of valid Domains.
Operator response:
Ensure we have configured the TAM JRTE correctly, and that all Configuration parameters are correct. If the problem persists, contact IBM support.
CTGDIK406E
Could not shutdown TAM object name.
Explanation:
The Connector was unable to shutdown TAM.
Operator response:
Ensure we have configured the TAM JRTE correctly, and that all Configuration parameters are correct. Ensure your TAM Server is operational and available. If the problem persists, contact IBM support.
CTGDIK407E
Could not retrieve entries for: object name.
Explanation:
The Connector was unable to retrieve entries for the target object.
Operator response:
Ensure the Connector to is configured to use the correct Entry Type. If the problem persists, contact IBM support.
CTGDIK408E
Could not retrieve next entry for: object name.
Explanation:
The Connector was unable to retrieve the next entry for the target object.
Operator response:
Ensure the Connector to is configured to use the correct Entry Type. If the problem persists, contact IBM support.
CTGDIK409E
Could not find entries for: object name.
Explanation:
The Connector was unable to find entries for the target object.
Operator response:
Ensure the Connector to is configured to use the correct Entry Type. If the problem persists, contact IBM support.
CTGDIK410E
There was an error while creating: object name.
Explanation:
The Connector was unable to create an entry of the configured Entry Type.
Operator response:
Check the HashMap object returned from the TAMConnectorException.getFailed method for more details on the error. Ensure the Connector is configured to use the correct Entry Type. If the problem persists, contact IBM support.
CTGDIK411E
There was an error while updating: entry name.
Explanation:
The Connector was unable to modify an entry of the configured Entry Type.
Operator response:
Check the HashMap object returned from the TAMConnectorException.getFailed method for more details on the error. Ensure the Connector is configured to use the correct Entry Type. If the problem persists, contact IBM support.
CTGDIK412E
Could not delete entry for: entry name.
Explanation:
The Connector was unable to delete an entry of the configured Entry Type.
Operator response:
Ensure the Connector is configured to use the correct Entry Type. If the problem persists, contact IBM support.
CTGDIK413E
Unable to interface with the TAM server. The following invalid message was retrieved by TAM while processing an exception thrown by TAM: invalid message.
Explanation:
The Connector has tapped a TAM exception while interfacing with TAM. The message type attached to the exception message is invalid message.
Operator response:
See the logs for additional information on how to respond. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK414E
Unable to interface with the TAM server. The following error message was retrieved by TAM while processing an exception thrown by TAM: error message.
Explanation:
The Connector has tapped a TAM exception while interfacing with TAM. The message type attached to the exception message is error message.
Operator response:
Ensure the Connector to is configured correctly, and that the TAM Server is operational. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK415E
Unable to interface with the TAM server. While retrieving the cause of an exception thrown by TAM, an internal exception has occured.
Explanation:
The Connector has trapped an underlying Java Exception while attempting to find the cause for a previous TAM exception.
Operator response:
Check the logs for details. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK416E
Unable to complete the operation. The attribute attribute name was missing.
Explanation:
The Connector was attempting an operation for a specific Entry Type and was missing an attribute.
Operator response:
Make sure that the required attribute for the respective Entry Type is available. If the problem persists, contact IBM support.
CTGDIK417E
Connector search failed. An unsupported search criteria was specified.
Explanation:
The Connector was attempting to search/find with unsupported search criteria.
Operator response:
Verify the search criteria for the respective Entry Type is valid.
CTGDIK418E
Deleting policy failed. User name is not specified.
Explanation:
The Connector was attempting to delete a Policy without a valid User Name.
Operator response:
Make sure that the User Name is valid for the Policy being deleted. If the problem persists, contact IBM support.
CTGDIK419E
Invalid Resource Type: resource type.
Explanation:
The Connector was attempting an operation with an invalid resource type.
Operator response:
Ensure the resource type is valid for the Entry Type. If the problem persists, contact IBM support.
CTGDIK420E
Admin Group group name is reserved and cannot be deleted.
Explanation:
The Connector was attempting to delete a Group that is reserved.
Operator response:
Unreserve the Group before attempting to delete it.
CTGDIK421E
Admin User user name is reserved and cannot be deleted.
Explanation:
The Connector was attempting to delete a User that is reserved.
Operator response:
Unreserve the User before attempting to delete it.
CTGDIK422E
Error while loading the group group name.
Explanation:
The Connector could not load the Group specified.
Operator response:
Confirm the Group exists in TAM. If the problem persists, contact IBM support.
CTGDIK423E
No Credentials Exist for User: user name.
Explanation:
The Connector could not find credentials for the User specified.
Operator response:
Confirm the User credentials exist in TAM.
CTGDIK424E
Operation Code operation code not supported.
Explanation:
The Connector does not support the operation code specified.
Operator response:
Change to a supported operation code.
CTGDIK425I
Shutting down connection to TAM.
Explanation:
This is an informational message only.
CTGDIK426I
Initializing PDAdmin for application: TAM program ID.
Explanation:
This is an informational message only.
CTGDIK427I
Creating a TAM Context: context name.
Explanation:
This is an informational message only.
CTGDIK428I
Retrieving data for entries with the entry type entry type and the attribute value attribute value.
Explanation:
This is an informational message only.
CTGDIK429I
The groups for the user: group names.
Explanation:
This is an informational message only.
CTGDIK430I
Importing User: user name.
Explanation:
This is an informational message only.
CTGDIK431I
Adding User: user name.
Explanation:
This is an informational message only.
CTGDIK432I
The groups to add: group names.
Explanation:
This is an informational message only.
CTGDIK433I
The groups to delete: group names.
Explanation:
This is an informational message only.
CTGDIK434I
Removing User: user name.
Explanation:
This is an informational message only.
CTGDIK435I
The users to add: user names.
Explanation:
This is an informational message only.
CTGDIK436I
The users to delete: user names.
Explanation:
This is an informational message only.
CTGDIK437I
Removing members from Group: group name.
Explanation:
This is an informational message only.
CTGDIK438I
Adding members to Group: group name.
Explanation:
This is an informational message only.
CTGDIK439I
Removing Group: group name.
Explanation:
This is an informational message only.
CTGDIK440I
Removing User: user name.
Explanation:
This is an informational message only.
CTGDIK441I
Creating Policy for User: user name.
Explanation:
This is an informational message only.
CTGDIK442I
Removing Policy for User: user name.
Explanation:
This is an informational message only.
CTGDIK443I
Creating Domain: domain name.
Explanation:
This is an informational message only.
CTGDIK444I
Removing Domain: domain name.
Explanation:
This is an informational message only.
CTGDIK445I
Creating SSO Credential: credential name.
Explanation:
This is an informational message only.
CTGDIK446I
Deleteing SSO Credential: credential name.
Explanation:
This is an informational message only.
CTGDIK447I
Refer to Users Guide, or initialize the Connector first.
Explanation:
This is an informational message only.
CTGDIK448E
No valid value found for the following Connector Configuration Parameter: Config Param Name.
Explanation:
The Connector was configured with a Configuation Parameter that either had no value, or the value specified was invalid.
Operator response:
Reconfigure the Connector to use valid values for all required Configuration Parameters.
CTGDIK449E
Unable to interface with the TAM server. The following invalid context message was retrieved by TAM while processing an exception thrown by TAM: invalid context message.
Explanation:
The Connector has tapped a TAM exception while interfacing with TAM. The message type attached to the exception message is invalid context.
Operator response:
See the logs for additional information on how to respond. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.
CTGDIK450E
Unable to interface with the TAM server. The following unknown message type was retrieved by TAM while processing an exception thrown by TAM: unknown message.
Explanation:
The Connector has tapped a TAM exception while interfacing with TAM. The message type attached to the exception message is unknown.
Operator response:
See the logs for additional information on how to respond. Attempt to restart the AssemblyLine containing this Connector. If the problem persists, contact IBM support.