Messages

The messages in this chapter are those that can be issued when your HCL ZIETrans application runs in a production environment. Messages in the ZIETrans Toolkit do not have message numbers, and error conditions in the toolkit are displayed at the top of the wizard panels. Some toolkit messages will appear in the task list.

The messages are arranged according to their numeric component.

HAT0001
Loading configuration data from {0}.
Explanation:

{0} is the file name of the configuration data file.

User response:

None.

HAT0002
The message log file is {0}.
Explanation:

{0} is the file name of the message log file.

User response:

None.

HAT0003
The trace log file is {0}.
Explanation:

{0} is the file name of the trace log file.

User response:

None.

HAT0040
A program exception occurred. There may be additional messages in this log which describe the error. The following information may help determine the cause, if this log is requested by HCL service:
{0}
{1}
Explanation:

{0} is the exception message string as received by Java™.

{1} is the exception stack trace.

User response:

Check the log for additional messages.

HAT0060
File {0} was not found.
Explanation:

{0} is the file name of the missing file.

User response:

Contact HCL Service for assistance.

HAT0061
Directory {0} was not found.
Explanation:

{0} is the missing directory.

User response:

Contact HCL Service for assistance.

HAT0062
Archive file {0} could not be created.
Explanation:

{0} is the file name of the archive file.

User response:

Ensure that the application's connection settings, specifically the SSL certificate setting, are correct. Contact HCL service for assistance.

HAT0300
An unexpected exception was received: {0}
Explanation:

{0} is the exception.

User response:

If the exception is issued by code written by a user, such as business logic or custom components or widgets, contact the programmer who wrote the code. Otherwise, Contact HCL Service for assistance.

HAT0350
An error occurred reading the file {0}.
Explanation:

{0} is the file name of the file being read.

User response:

Ensure that the file exists and is a valid file and that the user that is running WebSphere® Application Server has the necessary privileges to read files in that directory. Contact HCL Service for assistance.

HAT0351
An error occurred writing the file {0}.
Explanation:

{0} is the file name of the file being written.

User response:

Ensure that the file name is valid and that the user that is running WebSphere Application Server has the necessary privileges to create and write files in that directory. Contact HCL Service for assistance.

HAT0352
Cannot find the file named {0}.
Explanation:

{0} is the file name of the missing file.

User response:

Restore the missing file. Make sure the file is not marked as read-only and that the user that is running WebSphere Application Server has the necessary privileges to create and write files in that directory.

You might need to rebuild the ZIETrans project before the application is run.

Note:
You can set your Rational® SDP workbench preferences to perform a build automatically when a resource has been modified.
HAT0353
Creating the file {0}.
Explanation:

{0} is the file name of the file being created.

User response:

This is an informational message. No response is required.

HAT0354
Failed to delete the file named {0}.
Explanation:

An error occurred that prevented deleting the named file.

User response:

Ensure the file path is valid and the user ID that is running WebSphere Application Server has the necessary privileges to delete the file.

HAT0400
An exception occurred creating the host configuration. A message containing the exception details follows.
User response:

Use the information in the message that follows to bypass the exception during host configuration.

HAT0401
Cannot connect to the host using the following session properties:
{0}
Explanation:

{0} is a set of session properties.

User response:

Examine the properties to verify that the named server exists and is available.

HAT0402
Session is in CONNECTION_ACTIVE state, but not CONNECTION_READY state. A possible reason could be that the TN server port specified does not support the data stream expected.
Session properties being used:
{0}
Explanation:

{0} is a set of session properties.

User response:

Ensure that the connection type (TN3270, TN3270E, TN5250) is correct.

HAT0403
Cannot load the application {0}.
Explanation:

The application.hap file could not be loaded for the named application.

{0} is the name of the application.

User response:

The required file could not be located or has been corrupted. Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. Server traces will display the expected file name and location.

HAT0405
Session is ready, but no host data was available. Session properties:
{0}
Explanation:

{0} displays the session properties.

The host connection came up, but the host sent no screen data.

User response:

Ensure that the application's connection settings are correct. Contact HCL Service for assistance.

HAT0410
An error occurred while processing this request.
Detailed error information:  {0}
Explanation:

{0} is the exception stack trace or other application programmer information.

This message might be followed by another numbered message with further information.

User response:

If the application is still available, you might be able to continue the application. To determine what caused the error, check the other messages appearing with this message and check the message log or trace file for additional information.

HAT0411
The host connection is inactive.
Explanation:

The host became inactive during the processing of the application.

User response:

If the application is ending normally, no response is necessary. If the application ends abnormally, check the message log for additional information. Also, ensure that the application's connection settings are correct. Additional information might be found at the Telnet server.

HAT0412
An error occurred while processing an application Web page "{0}".
Explanation:

{0} is the name of the Web page (such as a transformation .jsp) being processed.

User response:

Contact HCL Service for assistance.

HAT0413
An exception occurred. {0}
Explanation:

An unexpected error occurred.

User response:

Read the extra message text. Check the log file for preceding or subsequent messages. If the problem persists, turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HAT0414
An error occurred while scanning for screen matches.
Explanation:

An unexpected error occurred while comparing the host screen against the list of configured screen customizations. The following messages describe the problem in greater detail.

User response:

Check the log file for subsequent messages. If the problem persists, turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HAT0415
The wfhats.xml file is malformed.
Explanation:

The wfhats.xml file is malformed.

User response:

See System error log for error details. See product documentation for a sample wfhats.xml file.

HAT0600
An error occurred while retrieving the action list for the screen customization "{0}".
Explanation:

{0} is the name of the screen customization.

User response:

Rebuild the project before the application is run.

Note:
You can set your Rational SDP workbench preferences to perform a build automatically when a resource has been modified.
HAT0601
The action {0} specifies an invalid parameter.
Explanation:

{0} is the name of the action.

User response:

Specify a valid parameter for the action.

HAT0602
Cannot insert null value to the host screen at row {0}, column {1}.
Explanation:

{0} is a row number on the host screen.

{1} is a column number on the host screen.

User response:

Ensure that the variable inserted onto the host screen has a value.

HAT0603
Cannot insert the value {0} to the host screen at row {1}, column {2}, because the host screen size is {3}.
Explanation:

{0} is the value.

{1} is a row number on the host screen.

{2} is a column number on the host screen.

{3} is the host screen size.

User response:

Insert a value at the row and column location that is valid for the host screen size.

HAT0604
An exception occurred while calculating the value for the global variable {0}. The action which failed was {1}. A message containing the exception details follows.
Explanation:

{0} is the name of the global variable.

{1} is the name of the action that failed.

User response:

Use the information in the message that follows to bypass the exception during calculation of the value for the global variable.

HAT0605
An error occurred while processing the actions for the screen customization "{0}".
Explanation:

{0} is the name of the screen customization.

User response:

Contact HCL Service for assistance.

HAT0606
Global variable "{0}" does not exist.
Explanation:

{0} is the name of the global variable.

User response:

Check the message log for additional information. Examine the trace file, if one exists. Check the application's screen customization actions to ensure that all required global variables are created.

HAT0607
The index {0} for global variable "{1}" is out of bounds. The global variable has {2} elements.
Explanation:

{0} is the value of the global variable index.

{1} is the name of the global variable.

{2} is the current size of the global variable.

User response:

Check the message log for additional information. Examine the trace file, if one exists. Check the application's screen customization actions to ensure that all required global variables are created and contain enough elements to complete the failing action.

HAT0608
Cannot insert the value "{0}" to the host screen at row {1}, column {2}, because the location is not contained in an unprotected field.
Explanation:

{0} is the name of the global variable.

{1} is a row number on the host screen.

{2} is a column number on the host screen.

User response:

Choose a valid row and column location for the current screen. Ensure that the global variable is being inserted into an unprotected field.

HAT0700
The attribute "{0}" of widget setting does not exist.
Explanation:

{0} is the attribute in the widget setting that does not exist.

User response:

Specify a valid attribute in the widget setting.

HAT0701
The value of attribute "{0}" in widget setting is empty.
Explanation:

{0} is the attribute of the widget setting that is empty.

User response:

Specify a value for the attribute in the widget setting.

HAT0702
The value of attribute "{0}" in widget setting is invalid.
Explanation:

{0} is the attribute of the widget setting that is invalid.

User response:

Specify a valid value for the attribute in the widget setting.

HAT0703
An error occurred while processing a transformation fragment {0}.
Explanation:

{0} is the name of the transformation fragment file that could not be processed because it is missing or corrupted.

User response:

Check whether the file exists. If it does, open it in the JSP editor and look at the task list for messages.

HAT0800
An exception occurred setting the property of print session. A message containing the exception details follows.
User response:

Use the information in the message that follows to bypass the exception that occurred while setting the property of the print session.

HAT0801
An exception occurred processing PDF I/O to client browser. A message containing the exception details follows.
User response:

Use the information in the message that follows to bypass the exception during processing of the PDF I/O to the client browser.

HAT0910
User credentials could not be retrieved from Web Express Logon.
Explanation:

Credentials were not found for this user.

User response:

Check your credential source to determine whether it is providing credentials for this user.

HAT0911
Web Express Logon macro could not be initialized.
Explanation:

Internal error.

User response:

Contact HCL Service for assistance.

HAT0912
Web Express Logon cannot retrieve user credentials because the client servlet request was not provided.
Explanation:

You might have tried to use a WEL-enabled macro on a non-WEL connection.

User response:

Verify that the macro and the connection both support Web Express Logon or both do not support Web Express Logon.

HAT0913
Web Express Logon cannot retrieve user credentials because the credential mapper was not initialized.
Explanation:

The Credential Mapper has not been configured.

User response:

Validate your Web Express Logon configuration and check for errors.

HAT0914
Verify that the connection has been configured to support Web Express Logon.
Explanation:

HCL ZIETrans cannot verify that the connection has been configured for Web Express Logon.

User response:

Check your connection configuration in HCL ZIETrans Toolkit. Verify that the check box for Web Express Logon is checked.

HAT0915
The plug-in {0} is not appropriate for the environment it is running in. Be sure to choose the proper plug-in implementation class for each environments.
Explanation:

The plug-in class specified in the zietranswelcfg.xml file used by Web Express Logon is not valid for this type of project.

User response:

Validate your Web Express Logon configuration and choose a proper plug-in for the project.

HPS5001
The value {0} of the attribute {1} in the XML element {2} is not a valid value
Explanation:

In a configuration file, the specified value is not acceptable.

User response:

Rebuild the application in the Toolkit and redeploy it. If the problem continues, review the settings in the Toolkit for this application.

HPS5007
Failed to delete the file named {0}
Explanation:

An error occurred that prevented deleting the named file.

User response:

Ensure the file path is valid and the user ID that is running WebSphere Application Server has the necessary privileges to delete the file.

HPS5008
There was an error reading the file {0}
Explanation:

Some error occurred while reading the specified file.

User response:

Ensure the specified file exists and the user ID that is running WebSphere Application Server has the necessary privileges to read the file. Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. If the problem continues, Contact HCL Service.

HPS5009
There was an error writing the file {0}
Explanation:

Some error occurred while writing the specified file.

User response:

Ensure the directory for the file exists, and the user ID that is running WebSphere Application Server has the necessary privileges to create and write files in that directory.

HPS5010
The installation directory parameter {0} specifies a directory {1} that is not an absolute path
Explanation:

The install directory parameter does not represent a complete unambiguous directory.

User response:

Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. If the problem continues, Contact HCL Service.

HPS5011
The installation directory parameter {0} specifies a path {1} that does not exist
Explanation:

The install directory parameter does not represent a directory that exists.

User response:

Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. If the problem continues, Contact HCL Service.

HPS5012
{0} is not a directory
Explanation:

The named object was expected to be a directory but was not.

User response:

Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. If the problem continues, Contact HCL Service.

HPS5013
The XML element {0} is missing the required attribute {1}
Explanation:

An expected item was not found in a configuration file.

User response:

Look for other messages that identify the application. Install the application again.

HPS5014
The initialization parameter {0} is missing. It should specify the installation directory name
Explanation:

WebSphere Application Server is not correctly configured to provide the application with the name of its installation directory.

User response:

Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. If the problem continues, Contact HCL Service.

HPS5015
The XML element {0} is missing either the attribute {1} or the attribute {2}
Explanation:

One of two expected items is missing in a configuration file.

User response:

Look for other messages that identify the application. Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. If the problem continues, Contact HCL Service.

HPS5016
The XML element {0} is not a valid element in the file {1}
Explanation:

An unexpected item was found in the specified configuration file.

User response:

Look for other messages that identify the application. Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. If the problem continues, Contact HCL Service.

HPS5017
Unexpected error {0} occurred. {1}
Explanation:

An unexpected error occurred.

User response:

Try again. If the problem persists, turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5018
An unexpected exception has occurred.
{0}.
Explanation:

{0} is the exception.

User response:

If the exception is issued by code written by a user, such as business logic or custom components or widgets, contact the programmer who wrote the code. Otherwise, Contact HCL Service for assistance.

HPS5019
There was an XML parse error while reading the file {0} or its DTD file at line {1} in column {2}. The error message is {3}
Explanation:

There was something wrong with a configuration file.

User response:

Look for other messages that identify the application. Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. If the problem continues, Contact HCL Service.

HPS5020
An exception occurred while parsing XML file {0} : {1}.
Explanation:

An unexpected error occurred.

User response:

If the problem persists, turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5021
Invalid value of attribute {0} in object {1}. {0} can only be greater than 0.
Explanation:

An error was found creating the named object. An invalid value has been specified for the named attribute.

User response:

Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.

HPS5022
Invalid value of attribute {0} in object {1}. {0} cannot be equal to 0
Explanation:

An error was found creating the named object. An invalid value has been specified for the named attribute.

User response:

Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.

HPS5023
Invalid value of attribute {0} in object {1}. {0} can only be 0 or higher
Explanation:

An error was found creating the named object. An invalid value has been specified for the named attribute.

User response:

Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.

HPS5024
Invalid value of attribute {0} in object {1}. {0} can only be -1 or higher.
Explanation:

An error was found creating the named object. An invalid value has been specified for the named attribute.

User response:

Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.

HPS5025
Missing mandatory attribute {0} in object {1}
Explanation:

An error was found creating the named object. The mandatory attribute is missing.

User response:

Examine the pool and connection XML files, and ensure you are providing the mandatory attribute for the named object.

HPS5027
Error creating object {0}. Object {1} not defined.
Explanation:

An error was found creating the named object. The second named object did not exist. An error occurred while creating the second named object.

User response:

Examine the log messages before this one and resolve the errors that occurred creating the second named object.

HPS5028
Object {0} already defined
Explanation:

An attempt was made to create an object already defined.

User response:

Examine the pool and connection XML files, and remove the duplicate occurrence of the named object.

HPS5029
The runtime is not started.
Explanation:

The HCL ZIETrans runtime is not started, but an operation was attempted that requires the runtime to have been started.

User response:

Use the WebSphere Application Server Administration program to start the HCL ZIETrans runtime. If this does not resolve the error, stop and restart the WebSphere Application Server, then ensure the HCL ZIETrans runtime is started.

HPS5030
{0} expired. Cannot get a connection from {1}.
Explanation:

The maximum waiting time defined for the named connection pool has expired. No connection is available to satisfy the request.

User response:

If this condition occurs frequently, you might want to increase the maximum number of connections defined for the named connection pool.

HPS5031
Object {0} not defined
Explanation:

The named object is not defined. An Integration Object refers to a connection pool that is not defined on the server. Using HCL ZIETrans Integration Objects in a non-HCL ZIETrans web module, such as a portlet, can cause Object not defined errors (HPS5031) to occur if the display name in web.xml doesn't match the context defined in application.xml.

User response:

Try installing the application again. This will also install the required connection pool definition. If you get this error because you are using HCL ZIETrans Integration Objects in a non-HCL ZIETrans web module, change the display-name tag in web.xml (in .war) to match the context value from application.xml (in .ear) to resolve the problem.

HPS5032
Cannot load Pool Manager {0}
Explanation:

An unexpected error occurred.

User response:

If the problem persists, turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5033
Too little memory. {0} bytes available
Explanation:

There is too little memory left to proceed.

User response:

Free some memory by shutting down applications and freeing disk space. Retry the application request.

HPS5034
No HttpSession available
Explanation:

An Integration Object tried to acquire an existing connection from the Web session, but there is no web connection. Either the Integration Object that requested the connection or the Integration Object that saved the object are miscoded, or the web connection has timed out, and the web connection (HttpSession) has been deleted.

User response:

Examine the Integration Objects for errors, and determine whether or not the timeout value for the web connection (HttpSession) is too short.

HPS5035
HPS5035 There is no data source object {0} in HttpSession. A possible cause is the use of multiple browsers from a single machine to a chained application. See documentation for more information.
Explanation:

A chained Integration Object attempted to retrieve a data source resource from the HttpSession, but the resource is not in the HttpSession object. This may occur for a number of reasons:

User response:

The correct action depends on the cause. Possible actions for the listed causes are, respectively:

HPS5036
Attempt to create user list with invalid type: {0}.
Explanation:

An unexpected error occurred.

User response:

If the problem persists, turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5037
Attempt to create user list with invalid name: {0}.
Explanation:

An attempt was made to create a user list with no name.

User response:

Check the name of the user list in the configuration file (.hco file) for this connection. A valid user list name must be unique and cannot contain:

Caution:

If you have limited experience editing macro files, please call HCL service.

HPS5038
Error creating object {0}. Object is empty
Explanation:

The named object has no contents. Perhaps the XML file that defines the object has been corrupted. For example, a user list object has no users.

User response:

Examine the XML files that define the named object. You may need to republish or repair the XML files.

HPS5039
Cannot get a User from user list {0}
Explanation:

The named user list has no free users available.

User response:

Retry the request later, or enlarge the size of the user list.

HPS5040
Invalid value of attribute {0} in object {1}. {0} can only be -1 or greater than 0
Explanation:

An error was found creating the named object. An invalid value has been specified for the named attribute.

User response:

Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.

HPS5041
Value of attribute {0} specified, but no file name specified.
Explanation:

A logoff macro, logon macro, or checkin screen name attribute is specified in the .hco file, but the value is not valid.

User response:

Examine the connection XML (.hco) file, and ensure you are providing a valid value for each attribute.

HPS5043
Internal error, attribute {0} in Conn object is null.
Explanation:

This is an internal error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5044
SQL connection is closed.
Explanation:

A JDBC connection has unexpectedly closed.

User response:

Retry the request.

HPS5045
JDBC exception while checking connection state : {0}
Explanation:

{0} is a JDBC exception received while testing the connection before use.

User response:

Examine the exception message for the cause of the problem. Retry the request. If the problem reoccurs, contact HCL support.

HPS5046
JDBC driver {0} not loadable, received exception: {1}
Explanation:

The JDBC driver (Java class) could not be loaded.

User response:

The driver may be missing. The directory where the class resides may not be in WebSphere Application Server or reloadable servlet classpath. Check both.

HPS5047
JDBC getConnection call failed for URL {0}, received exception: {1}
Explanation:

Could not connect to database (URL) specified in the connection specification for this application.

User response:

Verify that the database URL is reachable using DB vendor-supplied tools.

HPS5048
Call to method {0} not expected for JDBC connections.
Explanation:

This is an internal error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5049
The following Session properties are not acceptable to HOD : {0}. Exception received: {1}
Explanation:

Host On-Demand will not accept the current value of the named property. The value is either invalid or is incompatible with the other Session properties for this host connection.

User response:

Specify a valid value for the named property. If this does not correct the error, turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5050
Cannot recover connection if HodLogonSpec is null.
Explanation:

This connection requires recovery because the user ID and password are characterized as being single use only, and when the connection was returned to the connection pool, the screen was not what was expected. However, this application has no connect specification, and thus there is no connect or alternate connect macro that can be run to recover the user ID and password.

User response:

None, if the above scenario is true. If not, you can change the connection specification to define the user IDs to not be single use only, or define connect and alternate connect macros.

HPS5051
Cannot recover connection if logon or alternate logon macros are null
Explanation:

This connection requires recovery because the user ID and password are characterized as being single use only, and when the connection was returned to the connection pool, the screen was not what was expected. However, this application has no connect or alternate connect macro that can be run to recover the user ID and password.

User response:

None, if the above scenario is true. If not, you can change the connection specification to define the user IDs to not be single use only, or define connect and alternate connect macros.

HPS5052
Cannot set up a connection to the host using the following session properties: {0}
Explanation:

Cannot connect to the host (TN server) specified in the connection specification file for this application.

User response:

Examine the host name and port number for the TN server that is in the connection specification file for this application. Check that TCP/IP connectivity to the TN server is available using the ping program. If that succeeds, then use an emulator for the right terminal type and check if the TN server is operational.

HPS5053
Received InterruptedException: {0}
Explanation:

This is an unexpected error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5054
Macro state STATE_EMPTY not reached. Current macro state is {0}
Explanation:

This is an unexpected error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5055
Ran out of time while playing HOD macro: Macro file name = {0} Macro = {1}
Explanation:

While playing a connect (or disconnect) macro, the connect (or disconnect) timeout specified in the connection specification for this application expired. The timeout value could be too small in the context of how busy the TN server or network traffic is. It is also possible that a screen expected while running the macro did not arrive.

User response:

Increase the timeout value and look at the log to identify the screen.

HPS5056
Problem encountered while playing macro in file {0} Current state is {0} Initial fragment of the macro: {1}
Explanation:

This is an unexpected problem.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5057
PropertyVetoException received from HOD: {0}
Explanation:

Host On-Demand will not accept the current value of the named property. The value is either invalid or is incompatible with the other session properties for this host connection

User response:

Specify a valid value for the named property. If this does not correct the error, turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5058
MacroException received from HOD: {0}
Explanation:

The Host On-Demand code threw an exception while executing a connect or disconnect macro. This is an unexpected error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5059
HOD extract event {0} not expected. Extracts are not permitted in logon or logoff macros
Explanation:

The connect or disconnect macro has extract commands, which are unexpected in such macros and are ignored.

User response:

Examine your macros. Extraction of host screens is not supported while running macros to connect to, or disconnect from, a host. If you wish to extract host screens while the main connection is being made, play the macro within the connect event instead.

HPS5060
Both UserPool and BeanRef are null - cannot provide value for prompt {0} to HOD macro
Explanation:

While trying to supply a parameter to a connect or disconnect macro, the connection manager could not get it from the user list, nor was there an Integration Object bean that could be interrogated for the value. This can occur if pooling is enabled and the minimum connections setting for the connection pool is greater than zero. The connection subsystem will be unable to prefill the pool as requested.

User response:

Either disable pooling for this connection definition, or adjust the minimum connections to zero. This will still allow connections to be created on demand, but the connection subsystem will stop trying to prefill the pool without the required information to prime the connection. Alternatively, supply a user list with the needed information.

HPS5061
Ran out of time while supplying prompt values to HOD macro in file {0}. Exception received: {1}
Explanation:

While setting up a connect or disconnect macro for running, the connect (or disconnect) timeout expired. The timeout value could be too small in the context of how busy the TN server or the network traffic is. It is also possible that a screen expected while running the macro did not arrive. The amount of time elapsed in attempting to connect to the host did not allow enough time to run the macro.

User response:

Increase the timeout value and look at the log to identify the screen on which it failed.

HPS5062
Macro prompt value could not be provided. Exception received: {0}
Explanation:

An error was encountered while trying to provide one or more values corresponding to prompt statements in a connect or disconnect macro.

User response:

Examine the prompt statements in the macro (the file name is logged) and check that the value being accessed is in the user list or is available using a getter method in the Integration Object bean.

HPS5063
Received the following MacroErrorEvent while playing HOD macro: {0}
Explanation:

The execution of a connect or disconnect macro resulted in an error.

User response:

Examine the additional information provided in the log for more information on the cause of the error.

HPS5064
No get_userid method (with either 0 or 1 argument) in bean
Explanation:

Expected the Integration Object bean to supply the password using a get_userid method since there was no user list. However, no such method was found.

User response:

Fix the application in the Toolkit.

HPS5065
No get_password method in bean
Explanation:

Expected the Integration Object bean to supply the password using a get_password method since there was no user list. However, no such method was found.

User response:

Fix the application in the HCL ZIETrans Toolkit.

HPS5066
No "getter" method {0} for parameter {1} in bean {2}
Explanation:

A parameter to be supplied to a prompt statement in a connect or disconnect macro was expected to be found using a getter method in the Integration Object bean, since it was not found in the user list entry associated with this connection. However, no getter method was found.

User response:

Re-create the Integration Object in the HCL ZIETrans Toolkit and reinstall the application.

HPS5067
Exception received when calling getter method in bean: {0}
Explanation:

When attempting to get values from the Integration Object bean to supply macro prompt parameters to a connect or disconnect macro, a bean getter method threw a Java exception. This indicates there was a problem with the Integration Object generated by the HCL ZIETrans Toolkit.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5068
Exception received: {0}
Explanation:

Received an unexpected exception while attempting to supply macro prompt values to a connect or disconnect macro by invoking getter methods of the Integration Object bean.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5069
Attempt to set connection state to {0} is not valid.
Explanation:

This is an internal error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5070
Cannot change originating Pool. Old: {0}, New: {1}.
Explanation:

This is an internal error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5071
Cannot change connection specification. Old: {0}, New: {1}
Explanation:

This is an internal error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5072
There is no Pool Manager
Explanation:

An unexpected error occurred.

User response:

Re-export the user list from Host Publisher without encryption.

HPS5073
An encryption key is needed to start the system.
Explanation:

The named user list contains encrypted data that requires an encryption key.

User response:

Supply the required encryption key.

HPS5074
An encryption key is needed because user list {0} is encrypted.
Explanation:

The named user list contains encrypted data that requires an encryption key.

User response:

Supply the required encryption key.

HPS5075
Received STATE_PLAY_ERROR while playing macro in file {0}
Explanation:

An error was encountered by the Host On-Demand code while executing a connect or disconnect macro.

User response:

The log will contain additional information about the host screen that was seen by the macro engine when the macro failed, and the macro screen on which the failure occurred. Examine both to determine if this is the screen the macro expected.

HPS5077
Session is in CONNECTION_ACTIVE state, but not CONNECTION_READY state. A possible reason could be that the TN server port specified does not support the data stream expected. Session properties being used: {0}
Explanation:

This can occur if the port specified for the TN server, in the connection specification for this application, does not support the terminal type expected. There could be other reasons too.

User response:

Verify that the port specified does support the expected terminal type (3270, 5250, or VT). If it does, contact your TN server administrator.

HPS5079
HOD macro {0} has one or more syntax errors
Explanation:

The connect or disconnect macro currently running (identified in the log file) has a syntax error.

User response:

This should not occur unless the macro was manually edited. If you have edited the macro, examine the additional information logged in the message log file, for example, messages.txt, to determine the line where an error is being detected, and correct it. If no error can be detected, rerecord the macro using the HCL ZIETrans Toolkit.

HPS5080
Invalid value of attribute {0} in object {1}. {0} can only be -1 or greater than {2}
Explanation:

An error was found creating the named object. An invalid value has been specified for the named attribute.

User response:

Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.

HPS5081
The value {0} assigned to the attribute {1} in the file {2} is not valid. It should be a number. A value of {3} will be used.
Explanation:

A configuration file contains a value that was supposed to be a number but was not. A default value was used.

User response:

Modify the value in the specified configuration file to be a number.

HPS5082
Missing property {0} in user list {1}
Explanation:

The password expected by a prompt statement in a connect or disconnect macro is missing. The password was expected to be in the user list.

User response:

Examine the user list being used by this application. If you do see entries that define values for the property _password, contact HCL service. Otherwise, the user list needs to be rebuilt using the HCL ZIETrans Toolkit.

HPS5083
Failed to find the file named {0}
Explanation:

The specified file does not exist or could not be read.

User response:

Ensure the specified file exists and the user ID that is running WebSphere Application Server has the necessary privileges to read the file. Rebuild the application in HCL ZIETrans Toolkit and reinstall it on WebSphere Application Server. If the problem continues, Contact HCL Service.

HPS5084
Could not set up a connection
Explanation:

The HCL ZIETrans runtime ran out of time while setting up a connection to a back-end data source. The data source may not be currently available, or your connection timeout in the connection specification file may be too low.

User response:

Check the availability of the data source. If it is available, then it is possibly too busy, and consider increasing the timeout value in your connection specification and reinstalling that application.

HPS5086
Invalid value of attribute {0} in object {2}. {0} cannot be greater than attribute {1}. The value of attribute {1} will be used.
Explanation:

An inconsistency was found creating the named object. An invalid value has been specified for the first named attribute. The value of the first named attribute cannot be greater than the value of the second named attribute. The value of the second attribute will be used for the first attribute.

User response:

This message is informational only; no action is required.

HPS5090
System start
Explanation:

This is an informational message.

User response:

The HCL ZIETrans runtime has been started. This message is informational only; no action is required.

HPS5091
System shutdown
Explanation:

This is an informational message.

User response:

The HCL ZIETrans runtime has been stopped. This message is informational only; no action is required.

HPS5092
{0} Security attribute {1} appears to be corrupted, or the encryption key is incorrect. {2}
Explanation:

An attempt to decrypt user list data failed. The supplied encryption key is incorrect or the user list data has been corrupted.

User response:

Republish the user list from Host Publisher without encryption.

HPS5093
{0} Invalid schema value for {1} property. {2}
Explanation:

An encryption level that is not valid is specified for the named property.

User response:

Specify a valid encryption level in the schema for the user list.

HPS5094
{0} User property {1} conflicts with schema. {2}
Explanation:

An unexpected error occurred.

User response:

If the problem persists, turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5095
User {0} not found in user list {1}
Explanation:

The named user was not found in the named user list.

User response:

Respecify the name of the user.

HPS5096
Pool {0} exceeded its capacity. Overflow connection created
Explanation:

The maximum number of connections defined for the named pool has been reached. A non-pooled connection has been created to satisfy the request.

User response:

Based on how often this condition occurs you might want to increase the maximum number of connections defined for the named pool. This message is informational only.

HPS5097
Pool {0} exceeded its capacity. Request failed
Explanation:

The maximum number of connections defined for the named pool has been reached. A new connection could not be created to satisfy the request.

User response:

Based on how often this condition occurs you might want to increase the maximum number of connections defined for the named pool.

HPS5098
Ran out of time while playing HOD macro: Macro file name = {0} Macro = {1} Exception received: {2}
Explanation:

While supplying parameters corresponding to prompt statements in a connect or disconnect macro, the connecttimeout or disconnecttimeout timer expired.

User response:

The timeout value could be too small in the context of how busy the TN server or the network traffic is. It is also possible that a screen expected while running the macro did not arrive, and the connect (or disconnect) timeout expired.

HPS5099
Internal error, the following attribute or result is unexpected {0}
Explanation:

This is an internal error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5100
User ID {0} from UserPool {1} was used to set up a session to host {2}, and must be recovered
Explanation:

During shutdown, a disconnect macro associated with a host connection could not be run because the connection was in use by the Integration Object bean. This message logs which user ID is potentially lost as a result.

User response:

You can manually log on to the host with the above user ID and perform the alternate connect steps to recover the user ID. Otherwise, the HCL ZIETrans runtime will perform that recovery on a per connection basis, on restart. The manual recovery will result in more efficient operation after restart.

HPS5101
The WebSphere servlet engine cannot create an HttpSession object to store the host connection with the key {0}.
Explanation:

This is a Web container error.

User response:

Turn on HCL ZIETrans traces and try to re-create the condition. Contact HCL service and provide the trace information.

HPS5102
Insufficient rights to the file {0}. Please check file owner and permissions
Explanation:

The permissions of the files are not set to values which allow the requested action.

User response:

Ensure that the directory path is valid and the user ID that is running WebSphere Application Server has the necessary privileges to create the directory.

HPS5103
The data source connection has been removed, probably because the maxBusyTime has expired
Explanation:

The connection to the host application or database has already been removed. It is possible that maxBusyTime has been configured in the .poolspec file for this application and time has expired, causing the connection to be terminated before the Integration Object returned the connection. This can occur when an application with chained Integration Objects is running, and the end user pauses between two middle-in-chain Integration Objects for a time longer than the maxBusyTime configured for the connection pool.

User response:

Ensure that maxBusyTime is set to an appropriate value. In Host Access, click the Connection Pools tab in the left pane. In the right pane, click the Connection Pool Configuration tab, then in the Connection Timeouts box, type a new value for Maximum busy time before disconnection.

HPS5107
User list {0} not found
Explanation:

An unexpected error occurred.

User response:

If the problem persists, clear all trace and log files, turn on HCL ZIETrans tracing and tracing for the Integration Objects associated with this application, and try to re-create the condition. Contact HCL service and provide the trace and log file information.

HPS5108
Connection Pool {0} not found
Explanation:

An unexpected error occurred.

User response:

If the problem persists, clear all HCL ZIETrans trace and log files, turn on HCL ZIETrans tracing and tracing for the Integration Objects associated with this application, and try to re-create the condition. Contact HCL service and provide the trace and log file information.

HPS5109
Hostname {0} cannot be resolved
Explanation:

The hostname provided cannot be resolved in the network.

User response:

Verify that the hostname provided exists in the network and is reachable.

HPS5110
RemoteException received when making RMI call:
{0}
Explanation:

When attempting the specified call, a RemoteException was received. This usually indicates a network outage.

User response:

Verify that the runtime being administered is still available.

HPS5111
Integration object {0} has no methods. Check your Java CLASSPATH
Explanation:

While attempting to access the specified Integration object, no methods could be found. This most commonly happens if the Integration Object class is not accessible to WebSphere Application Server.

User response:

Verify that WebSphere Application Server's CLASSPATH correctly reflects accessibility to the Integration Object.

HPS5117
Key {0} not present in message file
Explanation:

The information for the specified message could not be found.

User response:

If the problem persists, clear all HCL ZIETrans trace and log files, turn on HCL ZIETrans tracing and tracing for the Integration Objects associated with this application, and try to re-create the condition. Contact HCL service and provide the trace and log file information.

HPS5136
There is no runtime on host "{0}" named {1}.
Explanation:

The runtime with the specified name does not exist.

User response:

Examine the message log for other messages that may give more details. Verify that the names of the host and runtime are correct and that they are active.

HPS5137
Checkin screen did not match current PS. Connection = {0} ECL error = {1} Screen description = {2} Screen dump = {3}
Explanation:

While verifying the state of the connection, it was found that the current screen of the application does not match the expected screen for the host connection to be returned to the connection pool.

User response:

Examine your macros to see if the screen that is in the log for this error message could have appeared after a normal execution of a data macro of an Integration Object (the last one in a chain, if chained). If so, your checkin screen description defined by the application is incorrect. This can occur if you choose screen recognition criteria which inadequately describe the screen state of the Integration Object when the connection is to be released. The checkin screen is the last screen of the connect macro if one exists, or the first screen of the data macro (of the first Integration Object in a chain, if chained).

HPS5142
License limit has been reached. No further connections are allowed. For more information on licensing enablement, see the InfoCenter at ({0}).
Explanation:

The number of licenses in use has exceeded the number of licenses purchased. No further connections are allowed.

User response:

Be sure you have properly enabled the HCL ZIETrans runtime licenses and have enabled the correct number of licenses. If so, contact your support organization to purchase additional HCL ZIETrans licenses.

For more information see the section, Flexera Licensing integration for ZIETrans Projects, in ZIETrans Getting Started.

HPS5143
An Exception was caught when creating an HOD screen for connection {0}. This probably is caused by an environment configuration problem. Perhaps the X Window System DISPLAY variable is not set, or RAWT is not configured properly.
Explanation:

A problem occurred while trying to draw a Display Terminal. This is likely an environment configuration problem.

User response:

Verify that WebSphere Application Server is configured properly for displaying graphics. For Windows platforms, you must select Allow service to interact with desktop in Windows Services panel. For other graphics environments, refer to HCL ZIETrans User's and Administrator's Guide for instructions.

HPS5145
Cannot connect to the host using SSL. If importing a certificate is required for this SSL connection, make sure that it has been imported from the Telnet server into a valid PKCS12 file, and that the password (SSLP12Password) and path (SSLP12FilePath) for the PKCS12 file are specified correctly. The session properties are:
{0}
Explanation:

The application was unable to connect to the host using SSL. Possible causes may be that the certificate is incorrect, the application was unable to locate and open the keystore file, or the connection could not be made to the host (Telnet server) specified in the connection specification file. The {0} lists the session properties.

User response:

Check that the application can load the certificate. Verify that the path specified for the PKCS12 file points to a valid PKCS12 file accessible by the application. Verify that the password specified is correct for the PKCS12 file. Also check that the correct certificate is available in the keystore file.

In addition to the checks suggested above, examine the host name and port number for the Telnet server that is in the connection specification file for this application. Check that TCP/IP connectivity to the Telnet server is available using the ping program. If that succeeds, then use an emulator for the right terminal type and check if the Telnet server is operational.

HAT5551
Parameter {0} is missing
Explanation:

Expected parameter {0} was not found.

User response:

Verify your command parameters and retry.

HAT5552
Conflicting parameters {0}
Explanation:

An incorrect combination of parameters was passed.

User response:

Remove one of the parameters as shown by {0} and retry. To see usage syntax , type a question mark (?) as the command's first parameter. For example: apply ?

HAT5556
File has been opened {0}
Explanation:

File {0} has been opened for reading or writing.

User response:

No user action required.

HAT5557
File not found {0}
Explanation:

File {0} is missing or cannot be opened for reading.

User response:

If the name of file {0} contains the CAPAR or APAR number, check to see if you are trying to restore or commit a fix that has not been applied. You cannot restore or commit a fix that has not been applied. Make sure file {0} exists and allows read/write permission by the logged-on user.

HAT5561
A fix for {0} cannot be applied to {1}.
Explanation:

The fix you are trying to apply to {1} cannot be applied to the installed product. The fix you are trying to apply is for product {0} and cannot be applied to the installed product {1}

User response:

Obtain the correct fix for your product as shown by {1} and retry.

HAT5562
{0} fix information for {1} was not found in {2}
Explanation:

The fix {0} you are trying to apply cannot be found in fix file {2}. Fix names are case sensitive. For example, you will see this message if you try to apply, restore or commit a fix named Jr12345 and the actual fix is named JR12345. You will also see this message if the APAR or CAPAR does not contain fix information for your platform {1}.

User response:

Correct the fix name case and retry or obtain the correct fix for your platform as shown by {1} and retry.

HAT5563
{0} cannot be restored because it has not been applied
Explanation:

You are trying to restore a fix that has not been applied. You can only restore fixes that have been applied and not committed.

User response:

Apply and test fix {0} before trying to restore it.

HAT5564
{0} cannot be committed because it has not been applied
Explanation:

You are trying to commit a fix that has not been applied. You can only commit fixes that have been applied.

User response:

Apply and test fix {0} before trying to commit it.

HAT5565
Fix {0} has an unknown type {1}
Explanation:

The fix you are trying to apply cannot be applied to the installed product because the type is not APAR or CAPAR.

User response:

Obtain the correct fix for your product and retry.

HAT5571
CAPAR {0} was applied on {1}
Explanation:

This is an informational message to confirm CAPAR {0} has been applied to the installed product.

User response:

No user action required.

HAT5572
CAPAR {0} was committed on {1}
Explanation:

This is an informational message to confirm CAPAR {0} has been committed to the installed product.

User response:

No user action required.

HAT5573
CAPAR {0} has an unknown state {1}
Explanation:

The report command is unable to determine whether the fix is applied or committed.

User response:

Contact the HCL Software Support Center if the problem persists.

HAT5574
APAR {0} was applied on {1}
Explanation:

This is an informational message to confirm APAR {0} has been applied to the installed product.

User response:

No user action required.

HAT5575
APAR {0} was committed on {1}
Explanation:

This is an informational message to confirm APAR {0} has been committed to the installed product.

User response:

No user action required.

HAT5576
APAR {0} has an unknown state {1}
Explanation:

The report command is unable to determine whether the fix is applied or committed.

User response:

Contact the HCL Software Support Center if the problem persists.

HAT5577
Fix type {0} is a valid type for {1}
Explanation:

This is an informational message to confirm the fix is valid for your platform {1}.

User response:

No user action required.

HAT5578
APAR {0} for build {1} will be applied to build {2}
Explanation:

This is an informational message to confirm APAR {0} will be applied to your product's build level {2}. APARs do not change the build level. Your product's build level will remain {2} after the APAR is applied.

User response:

No user action required.

HAT5579
CAPAR {0} for build {1} will be applied to build {2}
Explanation:

This is an informational message to confirm CAPAR {0} will be applied to your product's build level {2}. CAPARs change the build level. Your product's build level will be {1} after the CAPAR is applied.

User response:

No user action required.

HAT5581
Source file {0} is available
Explanation:

This is an informational message to confirm file {0} is available and has read permission.

User response:

No user action required.

HAT5582
There are no CAPARs applied to this component.
Explanation:

This is an informational message to confirm there are no CAPARs applied to your product.

User response:

No user action required.

HAT5583
There are no APARs applied to this component.
Explanation:

This is an informational message to confirm there are no APARs applied to your product.

User response:

No user action required.

HAT5584
There are no CAPARs or APARs applied to this component
Explanation:

This is an informational message to confirm there are no CAPARs or APARs applied to your product.

User response:

No user action required.

HAT5585
The {0} build level is {1} dated {2}
Explanation:

This is an informational message stating the current build level is {1} for component {0}.

User response:

No user action required.

HAT5586
Report for {0} version {1}
Explanation:

This is an informational message. The messages following this message refer to product {0} version {1}.

User response:

No user action required.

HAT5587
CAPAR {0} includes fix {1}
Explanation:

This is an informational message stating fix {1} is included in applied CAPAR {0}.

User response:

No user action required.

HAT5588
APAR {0} includes fix {1}
Explanation:

This is an informational message stating fix {1} is included in applied APAR {0}.

User response:

No user action required.

HAT5589
{0} is not applied or committed
Explanation:

This is an informational message stating fix {0} is not applied or committed.

User response:

No user action required.

HAT5590
{0} is included in fix {1}
Explanation:

This is an informational message stating fix {0} is included in applied fix {1}.

User response:

No user action required.

HAT5591
{0} cannot be applied because it was superseded by {1}
Explanation:

You are trying to apply fix {0} and fix {0} was already applied as part of fix {1}.

User response:

No user action required. You do not need fix {0}.

HAT5592
{0} cannot be applied until prereq fix {1} is committed
Explanation:

You are trying to apply fix {0} and fix {1} has not been committed. Fix {1} must be committed before fix {0} can be applied.

User response:

If you are satisfied that fix {1} is working correctly, commit fix {1} and then apply fix {0}.

HAT5593
{0} cannot be applied because it requires prereq fix {1}
Explanation:

You are trying to apply fix {0} and fix {0} cannot be applied until fix {1} has been applied, tested, and committed.

User response:

Apply, test and commit fix {1}.

HAT5594
{0} has already been applied
Explanation:

You are trying to apply fix {0} and fix {0} has already been applied.

User response:

Run the report command to see a list of applied and committed fixes.

HAT5595
Write permission is denied for target {0}.
Explanation:

File {0} cannot be opened for writing or the file does not exist.

User response:

Make sure file {0} exists and allows write permission by the logged-on user.

HAT5596
Source file {0} is missing
Explanation:

File {0} cannot be opened for reading or writing or the file does not exist.

User response:

Make sure file {0} exists and allows read/write permission by the logged-on user.

HAT5597
Read permission is denied for {0}
Explanation:

File {0} cannot be opened for reading or the file does not exist.

User response:

Make sure file {0} exists and allows read permission by the logged-on user.

HAT5598
Checking source file {0}
Explanation:

This is an informational message stating file {0} is being tested for read permissions.

User response:

No user action required.

HAT5599
{0} - Checking applied fix {1}
Explanation:

This is an informational message stating fix {0} is being checked to see if it is already installed.

User response:

No user action required.

HAT5602
Checking target file {0}
Explanation:

This is an informational message stating file {0} is being tested for write permissions.

User response:

No user action required.

HAT5603
Target file {0} is missing and cannot be replaced
Explanation:

File {0} cannot be opened for writing or the file does not exist.

User response:

Make sure file {0} exists and allows read/write permission by the logged-on user.

HAT5604
Directory {0} is missing
Explanation:

The APAR or CAPAR is trying to run a process from directory {0} and directory {0} is missing.

User response:

Create directory {0} and retry the apply command. Contact the HCL Software Support Center if the problem persists.

HAT5605
Existing file {0} will be replaced
Explanation:

This is an informational message stating expected missing file {0} already exists. File {0} will be backed up. If you have to restore the fix, file {0} will be restored.

User response:

No user action required.

HAT5606
Target file {0} is missing and cannot be removed
Explanation:

The APAR or CAPAR is trying to remove file {0} but file {0} does not exist. The file might have been manually removed or removed as part of a previous fix.

User response:

No user action required.

HAT5607
Target file {0} is missing and cannot be restored
Explanation:

File {0} does not exist and cannot be restored. No files will be restored and the applied fix is still installed.

User response:

Use the report command to see a list of applied fixes. Because you are trying to restore a fix, you can create a dummy file {0} and rerun the restore command. See the fixes.log file for the fully qualified file name.

HAT5611
File {0} was previously backed up
Explanation:

File {0} is shared between two components and was previously backed up while backing up the same fix to the other shared component.

User response:

No user action required.

HAT5612
Checking backup file {0}
Explanation:

This is an informational message stating file {0} is being tested for read permissions.

User response:

No user action required.

HAT5613
Backup file {0} is missing
Explanation:

File {0} was backed up and is expected to exist but does not exist. This could be the result of insufficient disk space.

User response:

Check to make sure your system is not low on disk space.

HAT5614
Target file {0} is missing and will be created.
Explanation:

File {0} was expected to exist but does not exist. The apply command will create file {0}. After the fix is applied, and you use the restore command to remove the fix, the restore command will delete file {0}.

User response:

No user action required.

HAT5615
Write access is permitted for target {0}.
Explanation:

This is an informational message to confirm file {0} is available and has write permission.

User response:

No user action required.

HAT5616
Read access is permitted for {0}
Explanation:

This is an informational message to confirm file {0} is available and has read permission.

User response:

No user action required.

HAT5617
Source file {0}
Explanation:

This is an informational message stating the name of a source file. Fixes.log will contain the fully qualified file name.

User response:

No user action required.

HAT5618
Target file {0}
Explanation:

This is an informational message stating the name of a target file. Fixes.log will contain the fully qualified file name.

User response:

No user action required.

HAT5619
Creating directory {0}
Explanation:

This is an informational message stating directory {0} does not exist and will be created.

User response:

No user action required.

HAT5620
Existing target file {0} will be backed up
Explanation:

This is an informational message stating product file {0} will be saved. The restore command will use the saved file to restore the product to the previous state. The commit command will delete the saved file {0}.

User response:

No user action required.

HAT5621
Backing up file {0}
Explanation:

This is an informational message confirming file {0} is being saved. The restore command will use the saved file to restore the product to the previous state. The commit command will delete the saved file {0}. Fixes.log will contain the fully qualified file name.

User response:

No user action required.

HAT5623
Applying new file {0}
Explanation:

This is an informational message confirming file {0} is being applied. Fixes.log will contain the fully qualified file name.

User response:

No user action required.

HAT5624
Removing old file {0}
Explanation:

This is an informational message confirming file {0} is being deleted. The restore command will use a saved copy of file {0} to restore the product to the previous state. Fixes.log will contain the fully qualified file name.

User response:

No user action required.

HAT5627
File {0} was previously restored
Explanation:

File {0} is shared between two components and was previously restored while restoring the same fix to the other shared component.

User response:

No user action required.

HAT5628
Restoring original file {0}
Explanation:

This is an informational message confirming file {0} is being restored from a saved copy. Fixes.log will contain the fully qualified file name.

User response:

No user action required.

HAT5629
{0} cannot be restored because it has been committed
Explanation:

You are trying to restore fix {0} and fix {1} has already been committed. You cannot restore a fix that has been committed.

User response:

Use the report command to see a list of applied and committed fixes. Reevaluate the need to remove fix {0}. If you really need to remove the fix you will have to reinstall the product. Reinstalling the product will remove all CAPARs and APARs.

HAT5630
{0} cannot be restored because it has not been applied
Explanation:

You are trying to restore fix {0} and fix {0} has not been applied.

User response:

Run the report command to see a list of applied and committed fixes.

HAT5635
{0} has concurrent {1} fix requirements - see the readme file
Explanation:

The fix you have applied may require a concurrent fix or fixes to product {1}.

User response:

Review the readme file packaged with the CAPAR or APAR. The readme file name will be same name as the fix number with the .TXT extension. For example, the readme file for fix JR12345 is named JR12345.txt.

HAT5641
{0} has already been committed
Explanation:

You are trying to commit fix {0} and fix {0} has already been committed.

User response:

Run the report command to see a list of applied and committed fixes.

HAT5642
{0} must be committed before a new fix can be applied
Explanation:

You are trying to apply fix {0} and fix {0} cannot be applied because other fixes have been applied and not committed. You must commit all applied fixes before you can apply new fixes.

User response:

Run the report command to see a list of applied and committed fixes. Test and commit fix {0}.

HAT5643
{0} for build {1} cannot be applied to build {2}
Explanation:

The fix you are trying to apply cannot be applied to the installed product. The most common reason for this is you are trying to apply an APAR that is not required for your product build level. For example, you applied and committed CAPAR-1 followed by CAPAR-2 and then tried to apply an APAR that was written for CAPAR-1.

User response:

Obtain the correct fix for your product and retry.

HAT5644
{0} for build {1} cannot be applied to build {2}
Explanation:

The fix you are trying to apply cannot be applied to the installed product. The most common reason for this is you are trying to apply a CAPAR that is not required for your product build level. For example, you applied and committed CAPAR-1 followed by CAPAR-3 and then tried to apply CAPAR-2. Another reason for this message is you are trying to apply a CAPAR to a beta version of the product.

User response:

Obtain the correct fix for your product and retry.

HAT5645
The request was successful
Explanation:

The apply, commit or restore command was able to successfully complete your request. If the request was apply, the fix has been applied and is ready to be tested. If the request was commit, the fix has been made permanent. If the request was restore, the fix has been removed.

User response:

No user action required.

HAT5646
The request was not successful
Explanation:

The apply, commit or restore command was not able to successfully complete your request.

User response:

See the previous messages for more information. See messages HAT5648 and HAT5649.

HAT5647
The final return code is {0}
Explanation:

This is an informational message used by the HCL Software Support Center.

User response:

No user action required.

HAT5648
Log file {0} contains 1 additional message.
Explanation:

A problem has occurred and the log file {0} contains an additional message.

User response:

Review the log file {0} for the additional message.

HAT5649
Log file {0} contains {1} additional messages.
Explanation:

A problem has occurred and the log file {0} contains additional messages.

User response:

Review the log file {0} for additional messages.

HAT5653
System Information {0} {1}
Explanation:

This is an informational message used by the HCL Software Support Center.

User response:

No user action required.

HAT5654
Today is {0}
Explanation:

This is an informational message showing the time and date.

User response:

No user action required.

HAT5655
Fix type {0} is not a CAPAR or APAR
Explanation:

No user action required.

User response:

Contact the HCL Software Support Center.

HAT5656
Unable to construct the XML image {0}
Explanation:

No user action required.

User response:

Contact the HCL Software Support Center.

HAT5657
Unexpected xerces exception {0}
Explanation:

No user action required.

User response:

Contact the HCL Software Support Center.

HAT5658
Unexpected exception {0}
Explanation:

An unexpected exception occurred. No user action required.

User response:

Contact the HCL Software Support Center.

HAT5659
Internal program problem {0}
Explanation:

No user action required.

User response:

Contact the HCL Software Support Center.

HAT5700
User Parameter {0} {1}
Explanation:

This is an informational message listing the APAR installation utility parameter number {0} and value {1}.

User response:

No user action required.

HAT5703
Checking {0} root {1}
Explanation:

This is an informational message stating that the APAR installation utility will try to locate {0} at {1}.

User response:

No user action required.

HAT5704
Unable to locate {0} root {1}
Explanation:

The APAR Installation utility was unable to locate {0} at {1}.

User response:

Ensure that HCL ZIETrans Toolkit is installed at {1}. If the problem persists, contact the HCL Software Support Center.

HAT5705
{0} root located {1}
Explanation:

This is an information message stating that {0} was successfully located at {1}.

User response:

No user action required.

HAT5706
{0} product not found
Explanation:

Product {0} was not found. The only valid product name is HCL ZIETrans Toolkit.

User response:

Correct the spelling of {0} and retry the command.

HAT5708
{0} not found.
Explanation:

A required file {0} was not found.

User response:

Ensure that Rational SDP is installed correctly. If the problem persists, contact the HCL Software Support Center.

HAT5710
{0} located {1}
Explanation:

This is an informational message stating that {0} was located at {1}.

User response:

No user action required.

HAT5711
Fix file not found {0}
Explanation:

The file containing the fix was not found. Fix file names are the same as the fix number. For example, fix JR12345 is contained in a file named JR12345.jar. When specifying fix names, do not specify the .jar extension. Fix files must exist in the service directory of the com.ibm.hats plugin

User response:

Correct the spelling of {0} and retry the command or copy fix file {0}.jar to the service directory of the com.ibm.hats plugin and retry the command.

HAT5712
Unknown action {0}
Explanation:

The command action was not apply, commit, restore or report.

User response:

Contact the HCL Software Support Center.

HAT5713
Extracting fix {0} ...
Explanation:

This is an informational message stating fix {0} is being extracted from file {0}.jar.

User response:

No user action required.

HAT5714
Extracting the fix control file {0}
Explanation:

This is an informational message stating file {0}.xml is being extracted from file {0}.jar.

User response:

No user action required.

HAT5715
Fix control file {0} is missing
Explanation:

Fix control file {0}.xml is missing from file {0}.jar. The most common reason for this error is a mismatch in fix name letter case. Fix names are case sensitive.

User response:

Correct the spelling of {0} and retry.

HAT5716
Extracting the fix data files
Explanation:

This is an informational message confirming the specified fix was located in the fix file and updated product files are being extracted.

User response:

No user action required.

HAT5745
{0} can not be applied until previous maintenance is applied to your HCL ZIETrans projects. See the readme for information on applying maintenance to your HCL ZIETrans projects.
Explanation:

Previous maintenance must be applied to your HCL ZIETrans projects before {0} can be applied.

User response:

Apply the previous maintenance to your HCL ZIETrans projects. To apply maintenance to your HCL ZIETrans projects you must open Rational SDP and switch to the HCL ZIETrans perspective. This will automatically apply maintenance to your HCL ZIETrans projects. If there is a problem applying maintenance to your HCL ZIETrans projects, contact the HCL Software Support Center.

HPS5747E
Unable to copy application configuration files
Explanation:

This message appears with message HPS5604. An application directory WebSphere Application Server configuration list contains no files.

User response:

No user action required.

HPS5748E
Security Exception {0}
Explanation:

A security exception occurred while trying to create a directory.

User response:

Ensure you are authorized to create directories on this server. Check WebSphere Application Server security settings.

HPS5750E
Arguments are {0}
Explanation:

This message appears with message HPS5749E and lists the arguments that were received.

User response:

Contact HCL Service and provide the argument information.

HPS5905
Exception occurred attempting to invoke ConnMgr to cleanup a connection
Explanation:

An exception occurred when the HCL ZIETrans EJB attempted to clean up the connection assigned to the processing of an Integration Object chain.

User response:

Check the following related messages or refer to the message log for other messages that provide more details about this problem.

HPS5950
{0}: {1}: {2}: HPubEJB2_Reference={3}, JNDI_NAME={4}, PROVIDER_URL={5}, INITIAL_CONTEXT_FACTORY={6}
Explanation:

The EJB Access bean was unable to locate or connect to the HCL ZIETrans EJB with the specified JNDI_NAME.

User response:

Check the following related messages for additional detail on the problem. Verify that the HPubEJB2_Reference, JNDI_NAME and PROVIDER_URL of the HCL ZIETrans EJB are correct, and modify the .war module's deployment descriptor or Access bean .jar .properties file with the correct values. Verify that the module containing the HCL ZIETrans EJB is installed and started on the target application server with the same JNDI name; correct if necessary.

HPS5951
{0}: accessHandle==null || hPubLinkKey==null
Explanation:

An Integration Object chain is being processed and the EJB Access bean is unable to retrieve the handle of the HCL ZIETrans EJB or the key used to access the connection for the chain.

User response:

Check the following related messages for additional detail on the problem. If this EJB Access Bean is being processed by a servlet or JSP, see the Explanation and User Action for message HPS5035 on page *** for possible causes. If this EJB Access bean is being processed from a Java program, verify that the program is setting the accessHandle and hPubLinkKey properties prior to invoking the middle or last Integration Objects in the chain. Refer to the HCL ZIETrans Programmer's Guide for information on hPubLinkKey.

HPS5952
{0}: getEJBObject(): {2}: {3}
Explanation:

An exception occurred during an attempt to retrieve the EJB object for an Integration Object chain.

User response:

Retry the request. If this problem persists, turn on all WebSphere Application Server traces if the EJB Access bean is running in a WebSphere Application Server environment, and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5953
{0}: processIO({1}): {2}: {3}
Explanation:

An exception occurred while processing the execution method of the HCL ZIETrans EJB.

User response:

Check the following related messages for additional detail on the problem.

HPS5954
{0}: HPubEJB.remove(), ejb={1}: {2}: {3}
Explanation:

An exception occurred while removing an instance of the HCL ZIETrans EJB.

User response:

Check the following related messages for additional detail on the problem. If the following messages indicate the remove failed because the EJB had timed out, then this is an informational message. If this problem persists and the messages indicate a java.rmi.RemoteException occurred, turn on the WebSphere Application Server traces and HCL ZIETrans traces, and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5955
{0}: ejb.getHandle(), ejb={1}: {2}: {3}
Explanation:

An exception occurred during an attempt to get a handle for the HCL ZIETrans EJB object.

User response:

Retry the request. If this problem persists, turn on all WebSphere Application Server traces if the EJB Access bean is running in a WebSphere Application Server environment, and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS5956
{0}: HttpServletRequest.getSession(true), hPubLinkKey={2}
Explanation:

An Integration Object chain is being processed and an error occurred with the linkKey preventing further processing of the chain.

User response:

Retry the request. If this problem persists, turn on all WebSphere Application Server traces if the EJB Access bean is running in a WebSphere Application Server environment, and try to re-create the condition. Contact HCL Service and provide the trace information.

HPS6002
Conn exception while releasing session to the Session Manager
Explanation:

A connection resource could not be appropriately freed. This may cause resources to accumulate and therefore degrade performance.

User response:

Use a resource-usage monitoring tool to check memory, threads, and handle usage. Use HCL ZIETrans Administration to disconnect unused connections. Increasing use of these resources indicates the server may run out of resources. Check preceding error messages for more information.

HPS6003
Unable to acquire connection from the Session Manager
Explanation:

A connection to the data resource could not be acquired. This could mean either that the data resource is inactive or unreachable, or that the pool has been exhausted.

User response:

Examine the message log for other messages that should give more details about this problem.

HPS6004
Exception while invoking a property's read method
Explanation:

An exception occurred when trying to access a routine that returns the value of a program variable.

User response:

Contact application vendor if problem persists.

HPS6005
Internal processing error
Explanation:

An unexpected error occurred during program execution. One of the following conditions could have occurred:

User response:

Examine the message log for other messages that should give more details about this problem.

HPS6006
Introspection exception
Explanation:

An Exception occurred while the Integration Object was performing internal introspection.

User response:

Contact application vendor if problem persists.

HPS6007
Connection Link Key is null when trying to acquire a chained non-web connection
Explanation:

A chain of Integration Objects is attempting to run, and the identification of this sequence has been lost.

User response:

Ensure that you have retrieved hPubLinkKey from the first Integration Object in the chain, and set it properly for all subsequent Integration Objects in the chain. If the request continues to fail, contact the application vendor.

HPS6008
Connection Link Key is null when trying to release a chained non-web connection
Explanation:

A sequence of Integration Objects is attempting to run, and the identification of this sequence has been lost.

User response:

Ensure that you have retrieved hPubLinkKey from the first Integration Object in the chain, and set it properly for all subsequent Integration Objects in the chain. If the request continues to fail, contact the application vendor.

HPS6009
Unexpected exception: {exception text}
Explanation:

An unexpected exception has occurred during execution of the Integration Object. The exception text is included in the message.

User response:

Correct the error identified in the exception text, then retry your request. If you do not know how to correct the error, contact the application vendor.

HPS6100
Unable to acquire session from the Session Manager
Explanation:

A connection to the data source, using a configured pool or connection, could not be established. This could mean either that the data source is inactive or unreachable, or that the pool has been exhausted.

User response:

Examine the message log for other messages that should give more details about this problem.

HPS6101
Internal HOD macro processing error
Explanation:

An error occurred during execution of the host macro. The host macro is a step-by-step, predefined interaction between the terminal connection and the host.

User response:

Examine the message log for other messages that should give more details about this problem. Typically, the failing macro screen is contained in the log. Examine the screen to determine whether the macro needs to be modified. Perhaps a new screen has been added to the host application, or something has changed on the host screen that is being used as screen recognition criteria. Contact the application vendor if the problem persists.

HPS6102
Internal macro processing error, extraction coordinates out of bounds
Explanation:

An error occurred during execution of the host macro. An attempt was made to extract data from the terminal screen, but the terminal screen coordinates of this data are not defined within this terminal screen.

User response:

Examine the failing screen contained in the log. Use it determine whether the macro needs to be modified. Contact the application vendor if the problem persists.

HPS6103
Internal macro processing error, macro empty
Explanation:

An error occurred during execution of the host macro. The host macro that was to be executed was either not found, or was empty.

User response:

  1. Check whether the macro file is empty. If it is, go back to HCL ZIETrans Toolkit and attempt to recover or record the macro again.
  2. If the problem persists, Contact HCL Service.
HPS6105
Received unexpected interrupted exception while waiting
Explanation:

The synchronization logic of the application received an unexpected error.

User response:

Contact application vendor if problem persists.

HPS6106
Unable to communicate with the Session Manager
Explanation:

The application was not able to establish communications with the program that is responsible for maintaining connections to the data sources.

User response:

Contact application vendor if problem persists.

HPS6107
Illegal access exception while invoking a property's read method
Explanation:

An exception occurred when trying to access a routine that returns the value of a program variable.

User response:

Contact application vendor if problem persists.

HPS6108
Invocation target exception while invoking a property's read method
Explanation:

An exception occurred when trying to access a routine that returns the value of a program variable.

User response:

Contact application vendor if problem persists.

HPS6109
Exception occurred, cannot retrieve current screen
Explanation:

An exception occurred while attempting to gather information about a prior error condition.

User response:

This message can be ignored. Examine the message log for messages about the original error condition.

HPS6112
Received the following MacroErrorEvent while playing Host On-Demand macro: {0}
Explanation:

Host On-Demand returned the specified MacroErrorEvent during while attempting to play a macro.

User response:

Examine the MacroErrorEvent to determine whether the condition is temporary or must be resolved by a macro modification. Refer to Host On-Demand documentation for more details on MacroErrorEvents. If the problem persists, Contact HCL Service.

HPS6202
Internal error: Unable to locate read method for property
Explanation:

An attempt was made to access a method that returns a value for a user or application program defined variable. This method does not exist.

User response:

The application is in error or a problem is present in the Java Virtual Machine environment. If the problem persists, contact the application vendor.

HPS6203
Internal error: Unable to locate marker for end-of-input-variable in SQL statement
Explanation:

Unable to parse the internally generated SQL statement.

User response:

The application is in error or a problem is present in the Java Virtual Machine environment. If the problem persists, contact the application vendor.

HPS6204
Internal error: Unable to locate ForSQL read method for property
Explanation:

An attempt was made to access a method that returns a value for a user or application program defined variable. This method does not exist.

User response:

The application is in error or a problem is present in the Java Virtual Machine environment. If the problem persists, contact the application vendor.

HPS6205
SQL error while opening statement
Explanation:

An error was received for the SQL call: createStatement.

User response:

Investigate the cause of the SQL error. A more detailed description of the SQL exception should be in message log file.

HPS6209
SQL error while executing SQL statement: {0}
Explanation:

An error was received for the SQL call: executeUpdate.

User response:

Investigate the cause of the SQL error. A more detailed description of the SQL exception should be in message log file.

HPS6210
Numeric input values cannot be blank. Enter a value for all numeric input fields
Explanation:

At least one of the entry fields on the Web page is blank. All numeric fields must have a value.

User response:

Enter a value for all numeric entry fields on the Web page.

HPS6211
License unavailable for completing the service request
Explanation:

License is unavailable to run the Integration Object.

User response:

Increase the license count. Contact HCL support for further help.

For more information see the section, Flexera Licensing integration for ZIETrans Projects, in 'ZIETrans Getting Started'.

HPS7001
Unexpected exception {0}.
Explanation:

An unexpected exception {0} has been logged during the XML Legacy Gateway (XLGW) session migration process. None of your XLGW sessions were migrated.

User response:

Review the text of the exception condition {0}. Correct the problem and rerun the migration utility.

ZTR0001
ZIETrans License server connection fails. Default assigned. For more information on licensing enablement, see the InfoCenter at ({0}).
Explanation:

Connection to the license server appears to fail with the configuration provided in theruntime.properties file. Due to the incorrect or missing configuration, only two connections can be established.

{0} is the address of the Information Center.

User response:

Correct the license information as explained in Flexera Licensing integration for ZIETrans Projects. Contact HCL Service for further assistance..

ZTR0002
Licenses used exceed licenses purchased. For more information on licensing enablement, see the InfoCenter at ({0}) .
Explanation:

You cannot create sessions beyond the number of licenses that you have purchased. Incase of default licenses, maximum licenses allowed is 2.

{0} is the address of the Information Center.

User response:

Verify that the license server details you configured is correct. Contact HCL Service for further assistance.

For more information see the section, Flexera Licensing integration for ZIETrans Projects, in 'ZIETrans Getting Started'.

ZTR0003
Failure processing the borrow interval {0}. Default 30m assigned. Verify the value entered for {1} in runtime properties. For more information on licensing enablement, see the InfoCenter at ({2}).
Explanation:

Borrow-interval has to be a numeric with unit-suffix letter s, m, h, d, or w indicating seconds, minutes, hours, days, or weeks.

{0}- Value of the flx_BorrowInterval parameter in runtime.properties file.

{1} - flx_BorrowInterval - name of the runtime properties parameter which is incorrect

{2} - The address of the Information Center.

User response:

Assign the right value to flx_BorrowInterval in runtime.properties if you do not want the default 30m.

ZTR0004
Failure in loading private key specified in the path {0}. Verify the valid private key file exists in the path given for {1} in runtime properties. For more information on licensing enablement, see the InfoCenter at ({2}).\nError message : {3}.
Explanation:

Private key may not be present in the path or key is corrupted. If the value is not provided for<user.home>//PrivateKey.pem, the default value is assigned.

{0} Value of the flx_PrivateKey_Absolute_Path parameter in runtime.properties file.

{1} flx_PrivateKey_Absolute_Path - name of the runtime properties parameter which is incorrect.

{2} is the address of the Information Center.

{3} error message in detail

User response:

Configure the right PrivateKey file path for flx_PrivateKey_Absolute_Path in runtime.properties.

ZTR0005
Failure processing the license server response for session {0}. Refer to the following error message for details. \n {1}.
Explanation:

Response from the license server is not as expected.

{0} license unique id which represents the session id.

{1} error message which explains the cause of the failure.

User response:

Contact HCL ZIETrans Support.

ZTR0006
Failure processing the license server response for session {0}. The given feature {1} {2} is unavailable in the license server.
Explanation:

The requested License feature is not available in the license server.

{0} - License unique id which represents the session id.

{1} - HCL ZIETrans license feature name.

{2} - HCL ZIETrans license feature version.

{0} - is the address of the Information Center.

User response:

Contact HCL ZIETrans Support.

ZTR0007
Failure during license server request preparation/processing for session {0}. Refer to the following error message for details. \n {1}.
Explanation:

A Failure occurred either due to the incorrect configuration of licensing runtime properties or due to an application error.

{0} license unique id which represents the session id.

{1} error message which explains about cause of the failure.

User response:

Verify the license parameters are configured correctly in runtime.properties file. Contact HCL ZIETrans support.

ZTR0008
Licenses used exceeding licenses purchased.
Explanation:

You cannot create sessions beyond the number of licenses you have purchased or incase default licenses, maximum licenses allowed exceeds 2.

User response:

Verify that the license server details you configured is correct. Contact HCL Service for further assistance.

For more information see the section, Flexera Licensing integration for ZIETrans Projects, in 'ZIETrans Getting Started'.

ZTR0009
License server not found. Response code returned is {0} for the server URL {1}.
Explanation:

The configure license server URL configured for flx_ServerURL may be incorrect or the server id does not exist in the license server.

{0} Error code returned from license server.

{1} URL of the license server.

User response:

Verify that the license server URL you configured is correct. Contact HCL Service for further assistance.

ZTR0010
License server response received with no payload for the session {0}.
Explanation:

Incorrect license server response returned with no payload data.

{0} - L:icense unique id which represents the session id.

User response:

Contact HCL Service for further assistance.

ZTR0011
License unavailable for session {0}. Error occurred while forwarding to error page jsp. Refer below error for details.\n {1}.
Explanation:

Error message explains the cause of the failure while forwarding to error page.

{0} - L:icense unique id which represents the session id.

User response:

Contact HCL Service for further assistance.

ZTR0012
License unavailable for reissue of the session {0}.
Explanation:

This occurs when the license is unavailable during the reissue of a license, when a borrow-interval returns the license.

{0} - License unique id which represents the session id.

User response:

Increase licenses. Contact HCL Service for further assistance.

ZTR0013
License unavailable for the session {0}.
Explanation:

This occurs when a license is unavailable for acquiring the license when session is created newly.

{0} - License unique id which represents the session id.

User response:

Increase licenses. Contact HCL Service for further assistance.

ZTR0014
Path value of {0} found to be empty in runtime properties configuration. Default path value {1} assigned. For more information on licensing enablement, see the InfoCenter at ({2}).
Explanation:

{0} flx_PrivateKey_Absolute_Path - name of the runtime properties parameter which is incorrect.

{1} default path value assigned.

{2} is the address of the Information Center.

User response:

By default, <user_home>/PrivateKey.pem is assigned internally, if the private key path is different, configure it in runtime.properties.

For more information see the section, Flexera Licensing integration for ZIETrans Projects, in 'ZIETrans Getting Started'.