The messages in this chapter are those that can be issued when your HATS application runs in a production environment. Messages in the HATS 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.
{0} is the file name of the configuration data file.
None.
{0} is the file name of the message log file.
None.
{0} is the file name of the trace log file.
None.
{0} is the exception message string as received by Java™.
{1} is the exception stack trace.
Check the log for additional messages.
{0} is the file name of the missing file.
Contact IBM® service for assistance.
{0} is the missing directory.
Contact IBM service for assistance.
{0} is the file name of the archive file.
Ensure that the application's connection settings, specifically the SSL certificate setting, are correct. Contact IBM service for assistance.
{0} is the exception.
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 IBM service for assistance.
{0} is the file name of the file being read.
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 IBM service for assistance.
{0} is the file name of the file being written.
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 IBM service for assistance.
{0} is the file name of the missing file.
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 HATS project before the application is run.
{0} is the file name of the file being created.
This is an informational message. No response is required.
An error occurred that prevented deleting the named file.
Ensure the file path is valid and the user ID that is running WebSphere Application Server has the necessary privileges to delete the file.
You cannot create connections beyond the number of licenses you have purchased.
{0} is the number of licenses used.
{1} is the number of licenses purchased.
{2} is the address of the Information Center.
Verify that the number of licenses you configured is correct. The value is specified in the numLicenses parameter in the runtime.properties file.
For more information see the section, Enabling HATS runtime and license settings, in HATS Getting Started.
The value for licenseHardLimit in the runtime.properties file appears to be corrupted. Due to this license corruption, only two connections can be established.
{0} is the address of the Information Center.
Correct the license information as directed in message HAT0362.
If the licenseHardLimit value in runtime.properties is missing, the message HAT0362 is issued, and the HATS server only allows two connections to be established.
{0} is the address of the Information Center.
To resolve this condition and allow more than two users to access the HATS application, you must restore the licenseHardLimit value in the runtime.properties file and restart your application. The value for licenseHardLimit is a case-sensitive string placed into the runtime.properties file when you enable the HATS runtime licenses. You can obtain the correct value for licenseHardLimit from one of the following places:
Copy the licenseHardLimit value to the runtime.properties file in the .ear file causing the problem and restart the HATS application.
For more information see the section, Enabling HATS runtime and license settings, in HATS Getting Started.
If your HATS application is running in a vertically clustered environment, verify that you have followed the instructions for configuring HATS in this type of environment. Failure to follow the instructions could make worse the conditions that cause the HAT0362 message to be issued. Refer to Configuring HATS applications in a clustered environment in the HATS User's and Administrator's Guide.
The value for licenseHardLimit in the runtime.properties file could not be read. Due to this problem, only two connections can be established.
{0} is the address of the Information Center.
Correct the license information as directed in message HAT0362.
Use the information in the message that follows to bypass the exception during host configuration.
{0} is a set of session properties.
Examine the properties to verify that the named server exists and is available.
{0} is a set of session properties.
Ensure that the connection type (TN3270, TN3270E, TN5250) is correct.
The application.hap file could not be loaded for the named application.
{0} is the name of the application.
The required file could not be located or has been corrupted. Rebuild the application in HATS Toolkit and reinstall it on WebSphere Application Server. Server traces will display the expected file name and location.
{0} displays the session properties.
The host connection came up, but the host sent no screen data.
Ensure that the application's connection settings are correct. Contact IBM service for assistance.
{0} is the exception stack trace or other application programmer information.
This message might be followed by another numbered message with further information.
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.
The host became inactive during the processing of the application.
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.
{0} is the name of the Web page (such as a transformation .jsp) being processed.
Contact IBM service for assistance.
An unexpected error occurred.
Read the extra message text. Check the log file for preceding or subsequent messages. If the problem persists, turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
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.
Check the log file for subsequent messages. If the problem persists, turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
The wfhats.xml file is malformed.
See System error log for error details. See product documentation for a sample wfhats.xml file.
An error occurred while forwarding control to WebFacing.
Check that wfContextRoot in wfhats.xml matches the context root of your WebFacing application.
{0} is the name of the screen customization.
Rebuild the project before the application is run.
{0} is the name of the action.
Specify a valid parameter for the action.
{0} is a row number on the host screen.
{1} is a column number on the host screen.
Ensure that the variable inserted onto the host screen has a value.
{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.
Insert a value at the row and column location that is valid for the host screen size.
{0} is the name of the global variable.
{1} is the name of the action that failed.
Use the information in the message that follows to bypass the exception during calculation of the value for the global variable.
{0} is the name of the screen customization.
Contact IBM service for assistance.
{0} is the name of the global variable.
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.
{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.
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.
{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.
Choose a valid row and column location for the current screen. Ensure that the global variable is being inserted into an unprotected field.
{0} is the attribute in the widget setting that does not exist.
Specify a valid attribute in the widget setting.
{0} is the attribute of the widget setting that is empty.
Specify a value for the attribute in the widget setting.
{0} is the attribute of the widget setting that is invalid.
Specify a valid value for the attribute in the widget setting.
{0} is the name of the transformation fragment file that could not be processed because it is missing or corrupted.
Check whether the file exists. If it does, open it in the JSP editor and look at the task list for messages.
Use the information in the message that follows to bypass the exception that occurred while setting the property of the print session.
Use the information in the message that follows to bypass the exception during processing of the PDF I/O to the client browser.
Credentials were not found for this user.
Check your credential source to determine whether it is providing credentials for this user.
Internal error.
Contact IBM Service for assistance.
You might have tried to use a WEL-enabled macro on a non-WEL connection.
Verify that the macro and the connection both support Web Express Logon or both do not support Web Express Logon.
The Credential Mapper has not been configured.
Validate your Web Express Logon configuration and check for errors.
HATS cannot verify that the connection has been configured for Web Express Logon.
Check your connection configuration in HATS Toolkit. Verify that the check box for Web Express Logon is checked.
The plug-in class specified in the hatswelcfg.xml file used by Web Express Logon is not valid for this type of project.
Validate your Web Express Logon configuration and choose a proper plug-in for the project.
A JSR 286 portlet can only send an object that is serializable. An object is serializable if its class implements the Serializable interface.
Ensure the global variable being sent contains a serializable object. A serializable object is an instance of a class that implements the Serializable interface. The problem must be fixed in the toolkit.
In a configuration file, the specified value is not acceptable.
Rebuild the application in the Toolkit and redeploy it. If the problem continues, review the settings in the Toolkit for this application.
An error occurred that prevented deleting the named file.
Ensure the file path is valid and the user ID that is running WebSphere Application Server has the necessary privileges to delete the file.
Some error occurred while reading the specified file.
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 HATS Toolkit and reinstall it on WebSphere Application Server. If the problem continues, contact IBM Service.
Some error occurred while writing the specified file.
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.
The install directory parameter does not represent a complete unambiguous directory.
Rebuild the application in HATS Toolkit and reinstall it on WebSphere Application Server. If the problem continues, contact IBM Service.
The install directory parameter does not represent a directory that exists.
Rebuild the application in HATS Toolkit and reinstall it on WebSphere Application Server. If the problem continues, contact IBM Service.
The named object was expected to be a directory but was not.
Rebuild the application in HATS Toolkit and reinstall it on WebSphere Application Server. If the problem continues, contact IBM Service.
An expected item was not found in a configuration file.
Look for other messages that identify the application. Install the application again.
WebSphere Application Server is not correctly configured to provide the application with the name of its installation directory.
Rebuild the application in HATS Toolkit and reinstall it on WebSphere Application Server. If the problem continues, contact IBM Service.
One of two expected items is missing in a configuration file.
Look for other messages that identify the application. Rebuild the application in HATS Toolkit and reinstall it on WebSphere Application Server. If the problem continues, contact IBM Service.
An unexpected item was found in the specified configuration file.
Look for other messages that identify the application. Rebuild the application in HATS Toolkit and reinstall it on WebSphere Application Server. If the problem continues, contact IBM Service.
An unexpected error occurred.
Try again. If the problem persists, turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
{0} is the exception.
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 IBM service for assistance.
There was something wrong with a configuration file.
Look for other messages that identify the application. Rebuild the application in HATS Toolkit and reinstall it on WebSphere Application Server. If the problem continues, contact IBM Service.
An unexpected error occurred.
If the problem persists, turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
An error was found creating the named object. An invalid value has been specified for the named attribute.
Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.
An error was found creating the named object. An invalid value has been specified for the named attribute.
Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.
An error was found creating the named object. An invalid value has been specified for the named attribute.
Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.
An error was found creating the named object. An invalid value has been specified for the named attribute.
Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.
An error was found creating the named object. The mandatory attribute is missing.
Examine the pool and connection XML files, and ensure you are providing the mandatory attribute for the named object.
An error was found creating the named object. The second named object did not exist. An error occurred while creating the second named object.
Examine the log messages before this one and resolve the errors that occurred creating the second named object.
An attempt was made to create an object already defined.
Examine the pool and connection XML files, and remove the duplicate occurrence of the named object.
The HATS runtime is not started, but an operation was attempted that requires the runtime to have been started.
Use the WebSphere Application Server Administration program to start the HATS runtime. If this does not resolve the error, stop and restart the WebSphere Application Server, then ensure the HATS runtime is started.
The maximum waiting time defined for the named connection pool has expired. No connection is available to satisfy the request.
If this condition occurs frequently, you might want to increase the maximum number of connections defined for the named connection pool.
The named object is not defined. An Integration Object refers to a connection pool that is not defined on the server. Using HATS Integration Objects in a non-HATS 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.
Try installing the application again. This will also install the required connection pool definition. If you get this error because you are using HATS Integration Objects in a non-HATS 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.
An unexpected error occurred.
If the problem persists, turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
There is too little memory left to proceed.
Free some memory by shutting down applications and freeing disk space. Retry the application request.
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.
Examine the Integration Objects for errors, and determine whether or not the timeout value for the web connection (HttpSession) is too short.
You might avoid this problem by using servlet or JSP code like this:
// Run the Integration Object transaction. Does a sendRedirect() on error.
myBean.doHPTransaction(request, response);
if (myBean.getHPubErrorOccurred() != 0)
{ // Do not call another Integration Object's doHPTransaction()
or produce output.
return;
// Instead, we allow the sendRedirect() to answer the client.
} <SCRIPT Language="Javascript">
/**********************************************************************
* Prevent multiple Submit or href click invocations from this page. *
* The 'submitFlag' variable is the switch. When the function is *
* called and the flag is zero, 'true' is returned to the onSubmit *
* parameter of the form. Otherwise a 'false' is returned, preventing *
* additional submit buttons/links from being reselected. *
**********************************************************************/
var submitFlag = 0;
function chkSubForm()
{
if (submitFlag == 0)
{ submitFlag = 1; // first time a button has been clicked
return true;
}
else
{ return false; // submit has already been clicked
}
}
</SCRIPT>
<a href="<%= response.encodeUrl("TheNextPage.jsp") %>"
onClick="return chkSubForm()">Next</a>An unexpected error occurred.
If the problem persists, turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
An attempt was made to create a user list with no name.
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:
If you have limited experience editing macro files, please call IBM service.
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.
Examine the XML files that define the named object. You may need to republish or repair the XML files.
The named user list has no free users available.
Retry the request later, or enlarge the size of the user list.
An error was found creating the named object. An invalid value has been specified for the named attribute.
Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.
A logoff macro, logon macro, or checkin screen name attribute is specified in the .hco file, but the value is not valid.
Examine the connection XML (.hco) file, and ensure you are providing a valid value for each attribute.
This is an internal error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
A JDBC connection has unexpectedly closed.
Retry the request.
{0} is a JDBC exception received while testing the connection before use.
Examine the exception message for the cause of the problem. Retry the request. If the problem reoccurs, contact IBM support.
The JDBC driver (Java class) could not be loaded.
The driver may be missing. The directory where the class resides may not be in WebSphere Application Server or reloadable servlet classpath. Check both.
Could not connect to database (URL) specified in the connection specification for this application.
Verify that the database URL is reachable using DB vendor-supplied tools.
This is an internal error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
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.
Specify a valid value for the named property. If this does not correct the error, turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
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.
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.
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.
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.
Cannot connect to the host (TN server) specified in the connection specification file for this application.
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.
This is an unexpected error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
This is an unexpected error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
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.
Increase the timeout value and look at the log to identify the screen.
This is an unexpected problem.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
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
Specify a valid value for the named property. If this does not correct the error, turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
The Host On-Demand code threw an exception while executing a connect or disconnect macro. This is an unexpected error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
The connect or disconnect macro has extract commands, which are unexpected in such macros and are ignored.
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.
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.
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.
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.
Increase the timeout value and look at the log to identify the screen on which it failed.
An error was encountered while trying to provide one or more values corresponding to prompt statements in a connect or disconnect macro.
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.
The execution of a connect or disconnect macro resulted in an error.
Examine the additional information provided in the log for more information on the cause of the error.
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.
Fix the application in the Toolkit.
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.
Fix the application in the HATS Toolkit.
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.
Re-create the Integration Object in the HATS Toolkit and reinstall the application.
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 HATS Toolkit.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
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.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
This is an internal error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
This is an internal error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
This is an internal error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
An unexpected error occurred.
Re-export the user list from Host Publisher without encryption.
The named user list contains encrypted data that requires an encryption key.
Supply the required encryption key.
The named user list contains encrypted data that requires an encryption key.
Supply the required encryption key.
An error was encountered by the Host On-Demand code while executing a connect or disconnect macro.
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.
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.
Verify that the port specified does support the expected terminal type (3270, 5250, or VT). If it does, contact your TN server administrator.
The connect or disconnect macro currently running (identified in the log file) has a syntax error.
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 HATS Toolkit.
An error was found creating the named object. An invalid value has been specified for the named attribute.
Examine the pool and connection XML files, and ensure you are providing a valid value for the named attribute.
A configuration file contains a value that was supposed to be a number but was not. A default value was used.
Modify the value in the specified configuration file to be a number.
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.
Examine the user list being used by this application. If you do see entries that define values for the property _password, contact IBM service. Otherwise, the user list needs to be rebuilt using the HATS Toolkit.
The specified file does not exist or could not be read.
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 HATS Toolkit and reinstall it on WebSphere Application Server. If the problem continues, contact IBM Service.
The HATS 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.
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.
The number of licenses in use has exceeded the number of licenses purchased.
Be sure you have properly enabled the HATS runtime licenses. If so, contact your support organization to purchase more licenses.
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.
This message is informational only; no action is required.
This is an informational message.
The HATS runtime has been started. This message is informational only; no action is required.
This is an informational message.
The HATS runtime has been stopped. This message is informational only; no action is required.
An attempt to decrypt user list data failed. The supplied encryption key is incorrect or the user list data has been corrupted.
Republish the user list from Host Publisher without encryption.
An encryption level that is not valid is specified for the named property.
Specify a valid encryption level in the schema for the user list.
An unexpected error occurred.
If the problem persists, turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
The named user was not found in the named user list.
Respecify the name of the user.
The maximum number of connections defined for the named pool has been reached. A non-pooled connection has been created to satisfy the request.
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.
The maximum number of connections defined for the named pool has been reached. A new connection could not be created to satisfy the request.
Based on how often this condition occurs you might want to increase the maximum number of connections defined for the named pool.
While supplying parameters corresponding to prompt statements in a connect or disconnect macro, the connecttimeout or disconnecttimeout timer 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, and the connect (or disconnect) timeout expired.
This is an internal error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
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.
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 HATS runtime will perform that recovery on a per connection basis, on restart. The manual recovery will result in more efficient operation after restart.
This is a Web container error.
Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information.
The permissions of the files are not set to values which allow the requested action.
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.
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.
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.
An unexpected error occurred.
If the problem persists, clear all trace and log files, turn on HATS tracing and tracing for the Integration Objects associated with this application, and try to re-create the condition. Contact IBM service and provide the trace and log file information.
An unexpected error occurred.
If the problem persists, clear all HATS trace and log files, turn on HATS tracing and tracing for the Integration Objects associated with this application, and try to re-create the condition. Contact IBM service and provide the trace and log file information.
The hostname provided cannot be resolved in the network.
Verify that the hostname provided exists in the network and is reachable.
When attempting the specified call, a RemoteException was received. This usually indicates a network outage.
Verify that the runtime being administered is still available.
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.
Verify that WebSphere Application Server's CLASSPATH correctly reflects accessibility to the Integration Object.
The information for the specified message could not be found.
If the problem persists, clear all HATS trace and log files, turn on HATS tracing and tracing for the Integration Objects associated with this application, and try to re-create the condition. Contact IBM service and provide the trace and log file information.
The runtime with the specified name does not exist.
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.
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.
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).
The number of licenses in use has exceeded the number of licenses purchased. No further connections are allowed.
Be sure you have properly enabled the HATS runtime licenses and have enabled the correct number of licenses. If so, contact your support organization to purchase additional HATS licenses.
For more information see the section, Enabling HATS runtime and license settings, in HATS Getting Started.
A problem occurred while trying to draw a Display Terminal. This is likely an environment configuration problem.
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 HATS User's and Administrator's Guide for instructions.
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.
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.
Expected parameter {0} was not found.
Verify your command parameters and retry.
An incorrect combination of parameters was passed.
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 ?
File {0} has been opened for reading or writing.
No user action required.
File {0} is missing or cannot be opened for reading.
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.
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}
Obtain the correct fix for your product as shown by {1} and retry.
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}.
Correct the fix name case and retry or obtain the correct fix for your platform as shown by {1} and retry.
You are trying to restore a fix that has not been applied. You can only restore fixes that have been applied and not committed.
Apply and test fix {0} before trying to restore it.
You are trying to commit a fix that has not been applied. You can only commit fixes that have been applied.
Apply and test fix {0} before trying to commit it.
The fix you are trying to apply cannot be applied to the installed product because the type is not APAR or CAPAR.
Obtain the correct fix for your product and retry.
This is an informational message to confirm CAPAR {0} has been applied to the installed product.
No user action required.
This is an informational message to confirm CAPAR {0} has been committed to the installed product.
No user action required.
The report command is unable to determine whether the fix is applied or committed.
Contact the IBM Software Support Center if the problem persists.
This is an informational message to confirm APAR {0} has been applied to the installed product.
No user action required.
This is an informational message to confirm APAR {0} has been committed to the installed product.
No user action required.
The report command is unable to determine whether the fix is applied or committed.
Contact the IBM Software Support Center if the problem persists.
This is an informational message to confirm the fix is valid for your platform {1}.
No user action required.
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.
No user action required.
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.
No user action required.
This is an informational message to confirm file {0} is available and has read permission.
No user action required.
This is an informational message to confirm there are no CAPARs applied to your product.
No user action required.
This is an informational message to confirm there are no APARs applied to your product.
No user action required.
This is an informational message to confirm there are no CAPARs or APARs applied to your product.
No user action required.
This is an informational message stating the current build level is {1} for component {0}.
No user action required.
This is an informational message. The messages following this message refer to product {0} version {1}.
No user action required.
This is an informational message stating fix {1} is included in applied CAPAR {0}.
No user action required.
This is an informational message stating fix {1} is included in applied APAR {0}.
No user action required.
This is an informational message stating fix {0} is not applied or committed.
No user action required.
This is an informational message stating fix {0} is included in applied fix {1}.
No user action required.
You are trying to apply fix {0} and fix {0} was already applied as part of fix {1}.
No user action required. You do not need fix {0}.
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.
If you are satisfied that fix {1} is working correctly, commit fix {1} and then apply fix {0}.
You are trying to apply fix {0} and fix {0} cannot be applied until fix {1} has been applied, tested, and committed.
Apply, test and commit fix {1}.
You are trying to apply fix {0} and fix {0} has already been applied.
Run the report command to see a list of applied and committed fixes.
File {0} cannot be opened for writing or the file does not exist.
Make sure file {0} exists and allows write permission by the logged-on user.
File {0} cannot be opened for reading or writing or the file does not exist.
Make sure file {0} exists and allows read/write permission by the logged-on user.
File {0} cannot be opened for reading or the file does not exist.
Make sure file {0} exists and allows read permission by the logged-on user.
This is an informational message stating file {0} is being tested for read permissions.
No user action required.
This is an informational message stating fix {0} is being checked to see if it is already installed.
No user action required.
This is an informational message stating file {0} is being tested for write permissions.
No user action required.
File {0} cannot be opened for writing or the file does not exist.
Make sure file {0} exists and allows read/write permission by the logged-on user.
The APAR or CAPAR is trying to run a process from directory {0} and directory {0} is missing.
Create directory {0} and retry the apply command. Contact the IBM Software Support Center if the problem persists.
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.
No user action required.
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.
No user action required.
File {0} does not exist and cannot be restored. No files will be restored and the applied fix is still installed.
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.
File {0} is shared between two components and was previously backed up while backing up the same fix to the other shared component.
No user action required.
This is an informational message stating file {0} is being tested for read permissions.
No user action required.
File {0} was backed up and is expected to exist but does not exist. This could be the result of insufficient disk space.
Check to make sure your system is not low on disk space.
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}.
No user action required.
This is an informational message to confirm file {0} is available and has write permission.
No user action required.
This is an informational message to confirm file {0} is available and has read permission.
No user action required.
This is an informational message stating the name of a source file. Fixes.log will contain the fully qualified file name.
No user action required.
This is an informational message stating the name of a target file. Fixes.log will contain the fully qualified file name.
No user action required.
This is an informational message stating directory {0} does not exist and will be created.
No user action required.
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}.
No user action required.
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.
No user action required.
This is an informational message confirming file {0} is being applied. Fixes.log will contain the fully qualified file name.
No user action required.
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.
No user action required.
File {0} is shared between two components and was previously restored while restoring the same fix to the other shared component.
No user action required.
This is an informational message confirming file {0} is being restored from a saved copy. Fixes.log will contain the fully qualified file name.
No user action required.
You are trying to restore fix {0} and fix {1} has already been committed. You cannot restore a fix that has been committed.
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.
You are trying to restore fix {0} and fix {0} has not been applied.
Run the report command to see a list of applied and committed fixes.
The fix you have applied may require a concurrent fix or fixes to product {1}.
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.
You are trying to commit fix {0} and fix {0} has already been committed.
Run the report command to see a list of applied and committed fixes.
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.
Run the report command to see a list of applied and committed fixes. Test and commit fix {0}.
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.
Obtain the correct fix for your product and retry.
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.
Obtain the correct fix for your product and retry.
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.
No user action required.
The apply, commit or restore command was not able to successfully complete your request.
See the previous messages for more information. See messages HAT5648 and HAT5649.
This is an informational message used by the IBM Software Support Center.
No user action required.
A problem has occurred and the log file {0} contains an additional message.
Review the log file {0} for the additional message.
A problem has occurred and the log file {0} contains additional messages.
Review the log file {0} for additional messages.
This is an informational message used by the IBM Software Support Center.
No user action required.
This is an informational message showing the time and date.
No user action required.
No user action required.
Contact the IBM Software Support Center.
No user action required.
Contact the IBM Software Support Center.
No user action required.
Contact the IBM Software Support Center.
An unexpected exception occurred. No user action required.
Contact the IBM Software Support Center.
No user action required.
Contact the IBM Software Support Center.
This is an informational message listing the APAR installation utility parameter number {0} and value {1}.
No user action required.
This is an informational message stating that the APAR installation utility will try to locate {0} at {1}.
No user action required.
The APAR Installation utility was unable to locate {0} at {1}.
Ensure that HATS Toolkit is installed at {1}. If the problem persists, contact the IBM Software Support Center.
This is an information message stating that {0} was successfully located at {1}.
No user action required.
Product {0} was not found. The only valid product name is HATS Toolkit.
Correct the spelling of {0} and retry the command.
A required file {0} was not found.
Ensure that Rational SDP is installed correctly. If the problem persists, contact the IBM Software Support Center.
This is an informational message stating that {0} was located at {1}.
No user action required.
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
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.
The command action was not apply, commit, restore or report.
Contact the IBM Software Support Center.
This is an informational message stating fix {0} is being extracted from file {0}.jar.
No user action required.
This is an informational message stating file {0}.xml is being extracted from file {0}.jar.
No user action required.
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.
Correct the spelling of {0} and retry.
This is an informational message confirming the specified fix was located in the fix file and updated product files are being extracted.
No user action required.
Previous maintenance must be applied to your HATS projects before {0} can be applied.
Apply the previous maintenance to your HATS projects. To apply maintenance to your HATS projects you must open Rational SDP and switch to the HATS perspective. This will automatically apply maintenance to your HATS projects. If there is a problem applying maintenance to your HATS projects, contact the IBM Software Support Center.
This message appears with message HPS5604. An application directory WebSphere Application Server configuration list contains no files.
No user action required.
A security exception occurred while trying to create a directory.
Ensure you are authorized to create directories on this server. Check WebSphere Application Server security settings.
This message appears with message HPS5749E and lists the arguments that were received.
Contact IBM service and provide the argument information.
An exception occurred while attempting to create or activate the HATS EJB.
Check the following related messages or refer to the message log for other messages that provide more details about this problem.
An exception occurred while the HATS EJB was processing the input argument received from an EJB Access bean.
Check the following related messages or refer to the message log for other messages that provide more details about this problem.
An exception occurred while the HATS EJB was processing the Helper object name received from an EJB Access bean.
Check the following related messages or refer to the message log for other messages that provide more details about this problem. Check the EJB .jar file to verify that the Integration Object Helper class exists.
An exception occurred when the HATS EJB invoked the Helper object to process the EJB Access bean request.
Check the following related messages or refer to the message log for other messages that provide more details about this problem.
An exception occurred when the HATS EJB attempted to clean up the connection assigned to the processing of an Integration Object chain.
Check the following related messages or refer to the message log for other messages that provide more details about this problem.
The EJB Access bean was unable to locate or connect to the HATS EJB with the specified JNDI_NAME.
Check the following related messages for additional detail on the problem. Verify that the HPubEJB2_Reference, JNDI_NAME and PROVIDER_URL of the HATS 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 HATS EJB is installed and started on the target application server with the same JNDI name; correct if necessary.
An Integration Object chain is being processed and the EJB Access bean is unable to retrieve the handle of the HATS EJB or the key used to access the connection for the chain.
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 HATS Programmer's Guide for information on hPubLinkKey.
An exception occurred during an attempt to retrieve the EJB object for an Integration Object chain.
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 IBM service and provide the trace information.
An exception occurred while processing the execution method of the HATS EJB.
Check the following related messages for additional detail on the problem.
An exception occurred while removing an instance of the HATS EJB.
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 HATS traces, and try to re-create the condition. Contact IBM service and provide the trace information.
An exception occurred during an attempt to get a handle for the HATS EJB object.
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 IBM service and provide the trace information.
An Integration Object chain is being processed and an error occurred with the linkKey preventing further processing of the chain.
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 IBM service and provide the trace information.
A connection resource could not be appropriately freed. This may cause resources to accumulate and therefore degrade performance.
Use a resource-usage monitoring tool to check memory, threads, and handle usage. Use HATS 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.
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.
Examine the message log for other messages that should give more details about this problem.
An exception occurred when trying to access a routine that returns the value of a program variable.
Contact application vendor if problem persists.
An unexpected error occurred during program execution. One of the following conditions could have occurred:
Examine the message log for other messages that should give more details about this problem.
An Exception occurred while the Integration Object was performing internal introspection.
Contact application vendor if problem persists.
A chain of Integration Objects is attempting to run, and the identification of this sequence has been lost.
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.
A sequence of Integration Objects is attempting to run, and the identification of this sequence has been lost.
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.
An unexpected exception has occurred during execution of the Integration Object. The exception text is included in the message.
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.
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.
Examine the message log for other messages that should give more details about this problem.
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.
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.
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.
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.
An error occurred during execution of the host macro. The host macro that was to be executed was either not found, or was empty.
The synchronization logic of the application received an unexpected error.
Contact application vendor if problem persists.
The application was not able to establish communications with the program that is responsible for maintaining connections to the data sources.
Contact application vendor if problem persists.
An exception occurred when trying to access a routine that returns the value of a program variable.
Contact application vendor if problem persists.
An exception occurred when trying to access a routine that returns the value of a program variable.
Contact application vendor if problem persists.
An exception occurred while attempting to gather information about a prior error condition.
This message can be ignored. Examine the message log for messages about the original error condition.
Host On-Demand returned the specified MacroErrorEvent during while attempting to play a macro.
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 IBM service.
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.
The application is in error or a problem is present in the Java Virtual Machine environment. If the problem persists, contact the application vendor.
Unable to parse the internally generated SQL statement.
The application is in error or a problem is present in the Java Virtual Machine environment. If the problem persists, contact the application vendor.
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.
The application is in error or a problem is present in the Java Virtual Machine environment. If the problem persists, contact the application vendor.
An error was received for the SQL call: createStatement.
Investigate the cause of the SQL error. A more detailed description of the SQL exception should be in message log file.
An error was received for the SQL call: executeUpdate.
Investigate the cause of the SQL error. A more detailed description of the SQL exception should be in message log file.
At least one of the entry fields on the Web page is blank. All numeric fields must have a value.
Enter a value for all numeric entry fields on the Web page.
An unexpected exception {0} has been logged during the XML Legacy Gateway (XLGW) session migration process. None of your XLGW sessions were migrated.
Review the text of the exception condition {0}. Correct the problem and rerun the migration utility.