End-to-End Automation Adapter Messages

The following messages are issued by the end-to-end automation adapter.

Note that within NetView an additional * may be appended to the end of the message text.

EEZA0001E Syntax error on line line number

Explanation

A syntax error has occurred in the configuration file, for example, a leading = on a line.

System action

The automation adapter stops.

Operator response

Analyze the configuration file for invalid syntax.

EEZA0002E Wrong datatype in key the key. Expected the desired type, found value "the value that was found"

Explanation

The value of the given key cannot be interpreted as the desired type. For example, the system expected a boolean value but found the string "hello".

System action

The automation adapter stops.

Operator response

Analyze the configuration file for invalid key/value pairs.

EEZA0003E The key "the key that was not found" was not found and no default value was given

Explanation

The system wanted to retrieve from the configuration file a value that did not exist and no default value was given.

System action

The automation adapter stops.

Operator response

Supply a value for the key in the configuration file.

EEZA0004E Integer out of bounds in key "the key". Expected value between the lower bound expected and the upper bound expected, found the value parsed

Explanation

The system expected an integer value between the given bounds (inclusive) for the given key, but found a value outside these bounds.

System action

The automation adapter stops.

Operator response

Supply a value within the given bounds for the key.

EEZA0005I At least one system symbol cannot be resolved: text-line

Explanation

The text line in error contains the system symbol that cannot be resolved. A system symbol is considered unresolved if it is either not defined or empty.

System action

The automation adapter stops.

Operator response

If available, refer to message EEZA0031E that specifies the name of the configuration file in error. Check the text line in error for an invalid system symbol. The system symbol in the corresponding z/OS IEASYMxx parmlib member might not be defined. If you are authorized to do so, enter the z/OS DISPLAY SYMBOLS command to display the system symbols and associated substitution texts that are in effect, and then define the corresponding system symbol if it's missing.

EEZA0006E Cannot create an instance of the class because class not found: class name

Explanation

The automation adapter cannot load the class.

System action

The automation adapter rejects the request.

Operator response

Check whether the class name is valid and is available in the corresponding class path.

EEZA0007E Cannot create an instance of the class because method not found: class name

Explanation

The automation adapter can load the class but cannot create an instance.

System action

The automation adapter rejects the request.

Operator response

Check whether the class is valid.

EEZA0008E Cannot create an instance of the class because of an unknown error: class name

Explanation

The automation adapter cannot load the class or create an instance.

System action

The automation adapter rejects the request.

Operator response

Check whether the class is valid and analyze the attached original exception.

EEZA0009E Invocation of adapter plug-in failed: plug-in=plug-in name, method=method name, internalRetcode=internal return code, taskRetcode=task return code

Explanation

The automation adapter client API was called to execute a task on the remote automation adapter. There are three error categories:

  • The client suffers an error on the connection
  • The execution of the task within the automation adapter backend failed
  • Execution failed in the automation adapter plug-in.
Automation adapter internal return codes:
3
Backend detects that the request expired before it was started.
4
Backend cannot be loaded.
22
Backend cannot load the plug-in Java™ class.
23
An exception occurred in the backend or the plug-in returns a non-zero task return code.
24
Backend rejects the execution of the task. See the automation adapter trace for details.
30
Backend detects invalid input arguments. Cannot execute task. This is an internal error.
40
Authentication failed. The user ID or password has not been specified or an internal error occurred.
41
Authentication failed. The user ID or password is invalid on the automation adapter host.
42
Authentication failed. The user ID has been revoked. JAAS login modules may not provide this information or may also use it if the password has expired.
43
Authentication failed. The password has expired. JAAS login modules may not provide this information.
The automation adapter client connection internal return codes:
101
Connection timed out while open.
102
Connection failed during open/read/write because peer closed.
103
Not all data received. The data was read successfully but the number of bytes is too small. This might be an internal error.
104
Unable to connect to the automation adapter.
105
Unable to close connection. This might be an internal error.
106
Unable to send data. Connection has been aborted due to, for example, SSL mismatch or the automation adapter stopped.
107
Marshal error occurred while sending or receiving data. This is an internal error.
108
Connection is invalid, for example, connection has not been opened or previously failed.
109
Read response failed. Data is zero, for example, the connection has been aborted due to an SSL mismatch.
110
Connection timed out during read/write.
Predefined task return codes from plug-in:
<0
Internally used task return codes have been mapped to one of the automation adapter return codes.
0
The plug-in was successful.
4004
The plug-in connection timed out.
4008
The plug-in authorization is missing to execute the request.
4009
The plug-in authentication failed.
4012
The plug-in failed but might execute the next request successfully. This is the default return code if the plug-in throws an exception but the plug-in return code is zero.
4016
The plug-in failed and might not execute the next request successfully.
4020
The plug-in failed and forces the entire automation adapter to stop.
4024
The plug-in cannot find the policy. For example, this may occur if the policy should be activated.
4028
The plug-in has found an error in the automation policy. For example, a policy rule was violated.

System action

Execution of the remote task fails.

Operator response

Analyze the return code description. If it is an internal error, check IBM® Electronic Support for additional information - http://www.ibm.com/support/entry/portal/

EEZA0010E Request expired before the adapter passes it to the adapter plug-in. Timeout period is timeout value seconds

Explanation

All requests have an associated expiration date. The request is scheduled to an execution thread that detected that the expiration time had expired.

System action

The automation adapter rejects the request.

Operator response

Analyze the reason (for example, high working load). Increase the timeout period if necessary.

EEZA0011E The backend program specification is invalid

Explanation

The backend program is not a Java program or the Java program name was not specified.

System action

The automation adapter rejects the request.

Operator response

Check the program that called the automation adapter client API.

EEZA0012E Invalid parameter list

Explanation

The automation adapter detected a request that is associated with an invalid parameter list.

System action

The automation adapter rejects the request.

Operator response

Check the program that called the automation adapter client API.

EEZA0013E Authentication for user ID user name was unsuccessful

Explanation

The request is associated with a user ID and password that have been validated unsuccessfully.

System action

The automation adapter rejects the request.

Operator response

Check whether the user ID is authorized for the system and check the security policy. Also check if you have stored a user ID and password for this domain in the credential store of the Dashboard Application Services Hub.

EEZA0014E The original exception original-class needs to be transported to the remote caller

Explanation

An exception from an underlying component needs to be transported to the remote caller.

System action

None.

Operator response

Analyze the original exception attached with this message.

EEZA0015E Method not supported: name of the missing method

Explanation

The automation adapter detected an unknown method name. The list of all valid method names is defined in the EEZAdapterInteraction interface.

System action

The automation adapter rejects the request.

Operator response

Check IBM Electronic Support for additional information - http://www.ibm.com/support/entry/portal/

EEZA0017E Request not supported: name of the unsupported request

Explanation

The automation adapter plug-in does not support the specified request.

System action

The request might be rejected depending on the behavior of the plug-in.

Operator response

Check whether the automation domain supports this type of request. Check whether you have installed the latest E2E adapter version.

EEZA0022E Adapter client is unable to connect to the adapter at host:port due to exception: the exception that was caught

Explanation

The automation adapter client cannot connect to the server at the given host and port. The original exception text is provided.

System action

The connection is not established.

Operator response

Analyze the original exception. For example, check firewall settings.

EEZA0023E Cache directory is invalid

Explanation

The EIF cache directory is not a directory.

System action

The automation adapter stops.

Operator response

Correct the configuration file.

EEZA0024E EIF sender and receiver must not be equal

Explanation

The EIF configuration parameters are not allowed to point to each other.

System action

The automation adapter stops.

Operator response

Correct the main configuration file. For example, compare parameter eif-receive-send-hostname with eif-receive-from-hostname and compare parameter eif-send-from-port with eif-receive-from-port.

EEZA0025E Cannot find the plug-in configuration file: configuration file name

Explanation

The main configuration file contains the name of a plug-in configuration file that cannot be found.

System action

The automation adapter stops.

Operator response

Correct the configuration file. Check parameter plugin-configfile-xxx, where for example xxx stands for sa4zos.

EEZA0026E No plug-in configuration file was specified

Explanation

The main configuration file must contain at least one plug-in configuration file.

System action

The automation adapter stops.

Operator response

Correct the configuration file. Compare parameter plugin-impl-class with the IBM provided settings.

EEZA0027E Cannot load configuration file: configuration file name

Explanation

The specified configuration file cannot be loaded.

System action

The automation adapter stops.

Operator response

Make sure that the configuration file resides in your customized E2E adapter configuration directory.

EEZA0028E Plug-in configuration file does not contain all mandatory parameters: configuration file name

Explanation

The specified configuration file does not contain all mandatory parameters. The plug-in is not used.

System action

The automation adapter does not deploy the plug-in.

Operator response

Compare the configuration file with the IBM provided settings.

EEZA0029E Cannot create the first instance of the plug-in class: class name

Explanation

An attempt was made to create the first instance of the plug-in during initialization. Creation failed.

System action

The automation adapter does not deploy the plug-in.

Operator response

Compare parameter plugin-impl-class with the IBM provided settings.

EEZA0030E Cannot set up event subscription list for plug-in configuration file: plug-in configuration file name

Explanation

The specification of the EIF event classes in the plug-in configuration file is invalid.

System action

The automation adapter does not deploy the plug-in.

Operator response

Compare parameter plugin-event-classes with the IBM provided settings.

EEZA0031E Cannot load configuration file from: plug-in configuration file name

Explanation

The automation adapter cannot load the specified configuration file because either no configuration file or an invalid one was specified.

System action

The automation adapter stops.

Operator response

Check whether the name of the configuration file is correct. Compare parameter plugin-configfile-xxx with the IBM provided settings.

EEZA0032E Initialization of the adapter failed: original exception

Explanation

An error occurred in the initialization step of the automation adapter.

System action

The automation adapter stops.

Operator response

Analyze the associated exception. If there is no exception text for this message, try to find additional messages in the adapter log.

EEZA0033E Unable to create type of factory SocketFactory

Explanation

The automation adapter server or client cannot create a socket factory for the remote contact.

System action

The automation adapter client cannot create a connection or the automation adapter server cannot receive connections.

Operator response

Analyze the reason by using previous messages.

EEZA0036E The adapter suffered an unexpected interruption: original exception

Explanation

The automation adapter waits for a termination command. An unexpected interruption occurred.

System action

The automation adapter stops.

Operator response

Analyze the original exception.

EEZA0037E The adapter stops because no plug-in has been successfully initialized

Explanation

At least one plug-in must have been successfully initialized otherwise the automation adapter stops.

System action

The automation adapter stops.

Operator response

Analyze previous messages and exceptions that are issued by the failing plug-in.

EEZA0038E A (SSL) socket configuration error occurred: exception text

Explanation

An error occurred during the loading or processing of (SSL) socket-related configuration data. An SSL handshake exception will only be reported during initial contact.

System action

The automation adapter client cannot create a connection or the automation adapter server cannot receive connections.

Operator response

Analyze the exceptions text. Check the SSL configuration file, ing.adapter.ssl.properties, if necessary.

EEZA0039E Not all data was read from socket: number of bytes read bytes read, number of bytes expected bytes expected to be read

Explanation

The incoming request has a length in bytes, but not all bytes can be read.

System action

The automation adapter rejects the request.

Operator response

Check why the socket connection was broken while transferring data.

EEZA0040E The adapter client cannot establish connection to the adapter: string representation of the connection

Explanation

Opening the connection failed. A request cannot be sent to the automation adapter. The string representation of the connection contains details about the connection.

System action

The automation adapter frontend failed.

Operator response

Analyze the connection information.

EEZA0041E The adapter client cannot invoke an adapter request: InternalRC=internal return code, TaskRC=task return code

Explanation

A connection to the automation adapter has been successfully established. The automation adapter frontend might have sent a request to the automation adapter but the request failed. If the internal or task return codes are not applicable (n/a), some other unexpected exception occurred.

System action

The automation adapter frontend failed.

Operator response

Analyze the internal and task return codes (see EEZA0009E for an explanation of the return codes).

EEZA0042E The adapter has thrown a remote exception: InternalRC=internal return code, TaskRC=task return code. The original message was: message text

Explanation

A connection to the automation adapter has been successfully established. The automation adapter frontend has sent a request to the automation adapter but the plug-in has thrown an exception.

System action

None.

Operator response

Analyze the internal and task return codes (see EEZA0009E for an explanation of the return codes).

EEZA0043E A required command line parameter is missing

Explanation

One of the required command line parameters is missing (such as -start,-stop or -terminate).

System action

The automation adapter frontend failed.

Operator response

Specify the required command-line parameters and try again.

EEZA0045E The adapter cannot establish a server socket due to illegal arguments: exception text

Explanation

The automation adapter cannot establish a receiver thread and cannot accept incoming connections.

System action

The automation adapter stops.

Operator response

Analyze the configuration file for an invalid IP address.

EEZA0047E The adapter is unable to accept connections due to socket exception "exception"

Explanation

An exception occurred as the automation adapter was about to accept an incoming connection.

System action

The automation adapter stops.

Operator response

Analyze the exception text.

EEZA0051W Termination of the adapter failed due to exception: error message

Explanation

The attempt to stop the receiver thread failed because an exception occurred.

System action

None.

Operator response

Analyze the exception text.

EEZA0052E Cannot create an in-storage EIF configuration file: exception text

Explanation

An instance of the Java class ByteArrayInputStream cannot be created or written.

System action

The automation adapter stops.

Operator response

This is probably an internal error. The exception text might give the reason for the problem.

EEZA0053E Missing argument for command line parameter "the parameter"

Explanation

A required argument for a command line parameter (such as -start) is missing. For example, AdapterCmd -start would be incorrect because -start requires an argument. A correct example would be: AdapterCmd -start com.ibm.ing.saplugin.INGXPluginInvocation

System action

Processing of this command ends.

Operator response

Check the documentation for information about valid command line arguments and their parameters.

EEZA0055E Remote Contact inactivity threshold exceeded: elapsed seconds=elapsed seconds threshold=threshold

Explanation

The automation adapter calculates the elapsed time since the last synchronous request was received. The automation adapter stops itself if this time exceeds the number specified in the parameter eez-remote-contact-activity-interval-seconds. Any incoming event is used as a trigger for the calculation.

System action

The automation adapter stops.

Operator response

You might want to increase the number of seconds specified by the parameter eez-remote-contact-activity-interval-seconds. Setting this parameter to 0 (zero) means it never expires.

EEZA0056I Initial contact was enabled and the connection to the management server has been established

Explanation

The parameter eez-initial-contact was set to true and the automation adapter attempted to connect the management server. The handshake to the management server was successful.

System action

None.

Operator response

No action required.

EEZA0057E The connection to the management server cannot be established

Explanation

The automation adapter stops attempting to connect to the management server because the timeout interval is over.

System action

The automation adapter stops.

Operator response

You might want to increase the number of minutes specified by the parameter eez-initial-contact-retry-interval-minutes. Specify the value 0 (zero) in order to retry forever.

EEZA0058E The plug-in has not been deployed or not yet started: name of the Java plug-in class

Explanation

An attempt was made to issue a request against a non-deployed plug-in or a plug-in that has not been started.

System action

The automation adapter rejects the request.

Operator response

Check the plug-in configuration file and deploy the missing plug-in class. Search for message EEZA0115I.

EEZA0059E An internal error occurred

Explanation

The automation adapter detected an internal error.

System action

None.

Operator response

Contact your IBM Electronic Support for additional information - http://www.ibm.com/support/entry/portal/

EEZA0060I The termination of the adapter is delayed for duration of the delay in seconds seconds

Explanation

Stopping the automation adapter is delayed for a short while until it has sent the appropriate domain leave events. You can configure the duration of this delay with the eez-stop-delay-seconds parameter.

System action

The automation adapter attempts to send domain leave events.

Operator response

No action required.

EEZA0061E Unable to bind a socket to address eez-remote-contact-hostname at port eez-remote-contact-port. Reason: message of the exception

Explanation

The automation adapter was unable to use this address or port. Possible causes of the problem are:

  • The port is already in use by another program.
  • The address could not be assigned.

System action

The automation adapter stops.

Operator response

Make sure that no program is using this port (that is, an automation adapter that is already running). If another program needs this port configure the automation adapter to use another port (with the eez-remote-contact-port parameter in the main configuration file). Ensure that the address is valid.

EEZA0062I The start command of the automation plug-in name of the Java plug-in class was successful

Explanation

The selected automation plug-in was successfully started.

System action

The automation adapter has started the automation plug-in.

Operator response

No action required.

EEZA0063I The stop command of the automation plug-in name of the Java plug-in class was successful

Explanation

The selected automation plug-in was successfully stopped.

System action

The automation adapter has stopped the automation plug-in.

Operator response

No action required.

EEZA0064I The termination command for the adapter was successful

Explanation

The automation adapter was successfully stopped.

System action

The automation adapter stops.

Operator response

No action required.

EEZA0070E The host name eez-remote-contact-hostname is unknown

Explanation

The automation adapter was unable to resolve the host name.

System action

The automation adapter stops.

Operator response

Specify a host name in parameter eez-remote-contact-hostname.

EEZA0071E The domain name is either null or empty

Explanation

The plug-in returned an invalid domain name since it is either null or empty.

System action

The plug-in cannot be started.

Operator response

Specify a domain name in the plug-in configuration file. Use parameter plugin-domain-name or comment it out and use the default.

EEZA0100I The adapter has been started

Explanation

This is the first of a sequence of three messages until the automation adapter is ready. The automation adapter starts initialization and will try to connect to the management server if eez-initial-contact=true.

System action

None.

Operator response

No action required.

EEZA0101I The adapter is active

Explanation

The automation adapter becomes active after a connection has been successfully established to the management server. The automation adapter continues initialization, finds and starts up all plug-ins.

System action

None.

Operator response

No action required.

EEZA0102I The adapter is ready

Explanation

The automation adapter startup sequence is complete.

System action

None.

Operator response

No action required.

EEZA0103I The adapter is stopping

Explanation

An internal or an external stop command has been received.

System action

The automation adapter is about to stop.

Operator response

No action required.

EEZA0104I The adapter has been stopped

Explanation

The automation adapter termination is complete. All possible stop delay periods are over. The process stops immediately.

System action

The automation adapter has stopped.

Operator response

No action required.

EEZA0105I The adapter has been stopped due to a failure, rc=return code

Explanation

The automation adapter stopped because an error occurred. All possible stop delay periods are over. The process stops immediately. The return code might be:
12
if initial contact failed
13
if the remote contact activity threshold is exceeded
16
if a plug-in forced termination of the automation adapter
20
if initialization failed
24
if an error occurred after initialization was successful
28
if an unsupported environment is detected

System action

The automation adapter stops.

Operator response

Search for error messages that were issued previously. On z/OS return code 28 might be caused by the 64-bit JVM. You should use the 32-bit JVM instead.

EEZA0111I The plug-in is starting: name of the Java plug-in class

Explanation

The automation adapter has already successfully created an instance of the plug-in class and will now call function INIT_DOMAIN.

System action

None.

Operator response

No action required.

EEZA0112I The plug-in has been started: name of the Java plug-in class

Explanation

The automation adapter plug-in has successfully initialized the domain (INIT_DOMAIN).

System action

None.

Operator response

No action required.

EEZA0113I The plug-in is stopping: name of the Java plug-in class

Explanation

The automation adapter will call plug-in function TERM_DOMAIN.

System action

None.

Operator response

No action required.

EEZA0114I The plug-in has been stopped: name of the Java plug-in class

Explanation

The automation adapter plug-in has successfully stopped the domain (TERM_DOMAIN).

System action

None.

Operator response

No action required.

EEZA0115I The plug-in startup failed: name of the Java plug-in class

Explanation

This message might follow after EEZA0111I, but the attempt to start the plug-in via function INIT_DOMAIN failed. The automation adapter plug-in will not be started automatically.

System action

The plug-in will be disabled. A join event was not sent.

Operator response

You might want to restart the plug-in using the automation adapter start command. Analyze further plug-in messages.

EEZA0116I The status of the event sender changed: Address=Address, Port=Port, Status=Status

Explanation

This message occurs if the status of the EIF connection changed. The reason could be that a new EIF connection is created or an existing EIF connection is lost. The reason can be found in the status. A status='connection timed out' is expected if the management server is stopped, for example if the management server moves to another system and therefore the adapter needs to change the EIF sender destination. The status can be:
1
connection created
2
connection changed
4
connection closed
8
connection timed out

System action

None.

Operator response

No action required.

EEZA9991E The message file is not installed

Explanation

The English message file must be available.

System action

The automation adapter stops.

Operator response

Make sure that the message file is in the class path

EEZA9992E EEZAdapterLogger is not available

Explanation

The automation adapter logging component has not been initialized.

System action

The automation adapter stops. Other processes using the automation adapter client API will be unable to write messages to log and trace files.

Operator response

Check IBM Electronic Support for additional support - http://www.ibm.com/support/entry/portal/

EEZC0001I Setting up Tivoli® Common Directory at location where Tivoli Common Directory is being set up.

Explanation

The Tivoli Common Directory path was set to its default value, as shown in the message text.

System action

No system action required.

Operator response

No operator action required.

EEZC0002I Unable to determine Tivoli Common Directory. Diverting serviceability related output to alternative location.

Explanation

The system was not able to determine the Tivoli Common Directory.

System action

Processing continues. The application will attempt to divert serviceability related output to another location for this session.

Operator response

In order to manage its serviceability related output, the application should be granted read/write permission to the location /etc/ibm/tivoli/common (UNIX) or <Program_Files_Dir>\ibm\tivoli\common (Windows).

EEZC0003I Base output directory for serviceability related files (for example, message log files and trace files) has been set to new output directory.

Explanation

The output directory for serviceability related files was set to its default value, as shown in the message text.

System action

From now on the application will write serviceability related information to the directory that is contained in the message text.

Operator response

No action is required if the base output directory for serviceability related files is acceptable. Otherwise, if it is required to relocate the base output directory, modify the entry in log.properties, which should be located at <Program_Files_dir>\ibm\tivoli\common\cfg (Windows) or /etc/ibm/tivoli/common/cfg/log.properties (UNIX). Changes to this file will take effect once the corresponding component is restarted.

EEZC0004I Changing base output directory for serviceability related files of name of logger from old output directory to new output directory.

Explanation

Due to changes in configuration settings the output directory of serviceability related files has been relocated.

System action

From now on the system will write serviceability related information to the new location.

Operator response

No action is required if the base output directory for serviceability related files is acceptable. Otherwise, if it is required to relocate the base output directory, modify the entry in log.properties, which should be located at <Program_Files_dir>\ibm\tivoli\common\cfg (Windows) or /etc/ibm/tivoli/common/cfg/log.properties (UNIX). Changes to this file will take effect once the corresponding component is restarted.

EEZK0003E String someString is too long: the maximum length of nameOfTheString Strings is maxLength.

Explanation

Setting the String to the specified value did not succeed due to string length.

System action

The current task ends.

Operator response

Verify the input parameters. If the problem persists, supply the trace file and this message text to your IBM Support Center.

EEZK0004E String named someStringName must not be null and must not exceed the maximum length of maxLength.

Explanation

Setting the String to null is not allowed.

System action

The current task ends.

Operator response

Verify the input parameters. If the problem persists, supply the trace file and this message text to your IBM Support Center.

EEZK0005E An exception, which is not an instance of EEZApplicationException has been passed to the EEZApplicationTransientException. The type of the message is exceptionType. The exception message is: exceptionMessage.

Explanation

This is an unexpected behavior.

System action

The current task will continue. The exception will be processed.

Operator response

Provide the logs and traces for more details, if any other error occurs.