The messages in this chapter are those that can be issued when your HATS application runs on the WebSphere Application Server. Messages in HATS Studio do not have message numbers; error conditions in HATS Studio are displayed at the top of the wizard panels.
{0} is the filename of the configuration data file.
None.
{0} is the filename of the message log file.
None.
{0} is the filename 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 filename of the missing file.
Contact IBM service for assistance.
{0} is the missing directory.
Contact IBM service for assistance.
{0} is the filename 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 filename of the file being read.
Ensure that the file exists and is a valid file. Contact IBM service for assistance.
{0} is the filename of the file being written.
Ensure that the filename is valid. Contact IBM service for assistance.
{0} is the filename of the missing file.
{0} is the filename of the file being created.
This is an informational message. No response is required.
{0} is the filename of the file that could not be deleted.
Contact IBM service for assistance.
{0} is the number of licenses used.
{1} is the number of licenses purchased.
Verify that the number of licenses you configured is correct.
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. Republish the application and redeploy the .ear file. Tracelevel.3 runtime traces will display the expected filename 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 your 3270 or 3270E host is configured to drop the connection when the user logs off and the 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.
{0} is the name of the screen customization.
{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 currentl 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.
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.