IBM Host Access Transformation Services. Messages SC

Transcription

1 IBM Host Access Transformation Services Messages Version 9.5 SC

2

3 IBM Host Access Transformation Services Messages Version 9.5 SC

4 Note Before using this information and the product it supports, be sure to read the general information under Notices, on page 29. Eleventh Edition (November 2015) Copyright IBM Corporation 2003, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Messages Appendix. Notices Trademarks Copyright IBM Corp. 2003, 2015 iii

6 iv IBM Host Access Transformation Services: Messages

7 Messages 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. HAT0001 Loading configuration data from {0}. data file. {0} is the file name of the configuration None. HAT0002 The message log file is {0}. file. {0} is the file name of the message log None. HAT0003 The trace log file is {0}. HAT0040 {0} is the file name of the trace log file. None. 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 IBM service: {0} {1} {0} is the exception message string as received by Java. {1} is the exception stack trace. HAT0060 HAT0061 HAT0062 Check the log for additional messages. File {0} was not found. {0} is the file name of the missing file. Contact IBM service for assistance. Directory {0} was not found. {0} is the missing directory. Contact IBM service for assistance. Archive file {0} could not be created. {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. HAT0300 An unexpected exception was received: {0} {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. HAT0350 An error occurred reading the file {0}. {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. HAT0351 An error occurred writing the file {0}. written. {0} is the file name of the file being 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. HAT0352 Cannot find the file named {0}. {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. Copyright IBM Corp. 2003,

8 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}. created. {0} is the file name of the file being This is an informational message. No response is required. HAT0354 Failed to delete the file named {0}. 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. HAT0360 Licenses used ({0}) exceeding licenses purchased ({1}). For more information on licensing enablement, see the InfoCenter at ({2}). 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. HAT0361 HATS License key is corrupt. Default assigned. For more information on licensing enablement, see the InfoCenter at ({0}). 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. HAT0362 HATS License key is missing. Default assigned. For more information on licensing enablement, see the InfoCenter at ({0}). 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: v The EAR project created in your HATS Toolkit workspace contains a copy of the runtime.properties file that should contain the correct value for licensehardlimit. The location of the runtime.properties file is shared_install_directory\ plugins\com.ibm.hats_nnn\predefined\projects\ earproject\runtime.properties, where shared_install_directory is the shared resources directory where you installed the HATS offering using IBM Installation Manager and nnn is the version and build level of HATS. v If you have other HATS.ear files deployed to your server, each has a runtime.properties file, which should contain the correct value for licensehardlimit. 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. HAT0363 HATS Error reading HATS License key. Default assigned. For more information on licensing enablement, see the InfoCenter at ({0}). 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 HAT IBM Host Access Transformation Services: Messages

9 HAT0400 An exception occurred creating the host configuration. A message containing the exception details follows. 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} {0} is a set of session properties. 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} {0} is a set of session properties. Ensure that the connection type (TN3270, TN3270E, TN5250) is correct. HAT0403 Cannot load the application {0}. 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. HAT0405 Session is ready, but no host data was available. Session properties: {0} {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. HAT0410 An error occurred while processing this request. Detailed error information: {0} {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. HAT0411 The host connection is inactive. 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. HAT0412 An error occurred while processing an application Web page "{0}". {0} is the name of the Web page (such as a transformation.jsp) being processed. Contact IBM service for assistance. HAT0413 An exception occurred. {0} 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. HAT0414 An error occurred while scanning for screen matches. 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. Messages 3

10 HAT0415 The wfhats.xml file is malformed. The wfhats.xml file is malformed. See System error log for error details. See product documentation for a sample wfhats.xml file. HAT0416 An error occurred while forwarding control to WebFacing. An error occurred while forwarding control to WebFacing. Check that wfcontextroot in wfhats.xml matches the context root of your WebFacing application. HAT0600 An error occurred while retrieving the action list for the screen customization "{0}". {0} is the name of the screen customization. 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 action. HAT0602 The action {0} specifies an invalid parameter. {0} is the name of the action. Specify a valid parameter for the Cannot insert null value to the host screen at row {0}, column {1}. {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. HAT0603 Cannot insert the value {0} to the host screen at row {1}, column {2}, because the host screen size is {3}. {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. 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. {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. HAT0605 An error occurred while processing the actions for the screen customization "{0}". {0} is the name of the screen customization. HAT0606 Contact IBM service for assistance. Global variable "{0}" does not exist. {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. HAT0607 index. The index {0} for global variable "{1}" is out of bounds. The global variable has {2} elements. {0} is the value of the global variable {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. 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. {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. 4 IBM Host Access Transformation Services: Messages

11 HAT0700 The attribute "{0}" of widget setting does not exist. {0} is the attribute in the widget setting that does not exist. setting. HAT0701 Specify a valid attribute in the widget The value of attribute "{0}" in widget setting is empty. {0} is the attribute of the widget setting that is empty. widget setting. Specify a value for the attribute in the HAT0911 HAT0912 Web Express Logon macro could not be initialized. Internal error. Contact IBM Service for assistance. Web Express Logon cannot retrieve user credentials because the client servlet request was not provided. 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. HAT0702 The value of attribute "{0}" in widget setting is invalid. {0} is the attribute of the widget setting that is invalid. Specify a valid value for the attribute in the widget setting. HAT0703 An error occurred while processing a transformation fragment {0}. {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. HAT0800 An exception occurred setting the property of print session. A message containing the exception details follows. 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. 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. Credentials were not found for this user. Check your credential source to determine whether it is providing credentials for this user. HAT0913 configured. Web Express Logon cannot retrieve user credentials because the credential mapper was not initialized. The Credential Mapper has not been Validate your Web Express Logon configuration and check for errors. HAT0914 Verify that the connection has been configured to support Web Express Logon. 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. 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 IBM or Standard portlet environments. 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. HAT1300 Event payload type must be serializable. 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. Messages 5

12 HPS5001 The value {0} of the attribute {1} in the XML element {2} is not a valid value 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. HPS5007 Failed to delete the file named {0} 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. HPS5008 There was an error reading the file {0} 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. HPS5009 There was an error writing the file {0} 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. HPS5012 {0} is not a directory 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. HPS5013 The XML element {0} is missing the required attribute {1} An expected item was not found in a configuration file. 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 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. HPS5015 The XML element {0} is missing either the attribute {1} or the attribute {2} 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. HPS5010 The installation directory parameter {0} specifies a directory {1} that is not an absolute path 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. HPS5016 The XML element {0} is not a valid element in the file {1} 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. HPS5011 The installation directory parameter {0} specifies a path {1} that does not exist 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. HPS5017 Unexpected error {0} occurred. {1} 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. 6 IBM Host Access Transformation Services: Messages

13 HPS5018 An unexpected exception has occurred. {0}. {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. 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} 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. 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. 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. HPS5025 Missing mandatory attribute {0} in object {1} 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. HPS5020 An exception occurred while parsing XML file {0} : {1}. 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. HPS5021 Invalid value of attribute {0} in object {1}. {0} can only be greater than 0. 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. HPS5027 Error creating object {0}. Object {1} not defined. 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. HPS5028 Object {0} already defined 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. HPS5022 Invalid value of attribute {0} in object {1}. {0} cannot be equal to 0 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. HPS5023 Invalid value of attribute {0} in object {1}. {0} can only be 0 or higher An error was found creating the named object. An invalid value has been specified for the named attribute. Examine the pool and connection XML HPS5029 The runtime is not started. 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. HPS5030 {0} expired. Cannot get a connection from {1}. The maximum waiting time defined for the named connection pool has expired. No connection is available to satisfy the request. Messages 7

14 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 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. HPS5032 Cannot load Pool Manager {0} 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. HPS5033 proceed. Too little memory. {0} bytes available There is too little memory left to Free some memory by shutting down applications and freeing disk space. Retry the application request. HPS5034 No HttpSession available 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. 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. 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: v v v v When you double-click the Internet Explorer icon to open the Internet Explorer browser, this problem does not occur; however, if you use any method other than double-clicking the icon to open the Internet Explorer browser, the problem will occur because the Internet Explorer browser windows will then share a single HttpSession. A single JSP or servlet runs multiple Integration Objects without checking for an error in a previous Integration Object and stopping the next Integration Object from executing. The previous Integration Object will not have placed the data source resource back in the HttpSession if it encountered an error. A user clicks Submit or clicks a link twice before the first button press or link click can be completely processed at the server. If processing is taking longer than expected, a user might click on a link to the next page of a chained Integration Object application twice rather than wait for the next page to process its Integration Object and send the output page back to the client. The second click causes the next page to be processed again, while the Integration Object still has ownership of the data source resource. During this processing, a second instance of the Integration Object cannot find the resource in the HttpSession, and causes a HPS5035 error to be logged and the output of the first Integration Object processing is lost. A very long-running Integration Object (usually more than a minute) might cause the Web server to time out while the Integration Object is still processing. If this occurs, the Web server may destroy the HTTP connection to the browser client. Internet Explorer sometimes reacts to this by immediately requesting the same page again without user intervention. This second request is just like a second Submit or link click, causing a second instance of the Integration Object to run. This second instance fails to find the 8 IBM Host Access Transformation Services: Messages

15 v v data source resource in the HttpSession, which causes a HPS5035 error. Additionally, the output of the first Integration Object processing is lost. If the maximum busy time before disconnection specified for the connection expires because a chained Integration Object application was left idle between Integration Objects executing (for example, the Integration Objects are on different pages), then the next Integration Object in the chain will log an HPS5035 if a user continues with the application after the expiration time. If the HttpSession Activity Timeout, set in WebSphere Application Server, occurs because a chained Integration Object application is left idle between Integration Objects executing (for example, the Integration Objects are on different pages), then the next Integration Object in the chain logs a HPS5035 if a user continues with the application after the expiration time. The correct action depends on the cause. Possible actions for the listed causes are, respectively: v v If you are running multiple applications containing chained Integration Objects, be sure to double-click the Internet Explorer icon to open the Internet Explorer browser. JSPs or servlets should not attempt to continue running subsequent chained Integration Objects after an error has occurred in a previous Integration Object in the chain. Instead, subsequent Integration Objects should not be executed if an error occurred in a previous Integration Object, and the Integration Object in error should redirect the client to an error page. You might avoid this problem by using servlet or JSP code like this: v v // 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. } You might avoid this problem by using a JavaScript snippet like this one: <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> The simplest way to prevent this is to have no Integration Object run for a very long time. Alternatively, you may be able to adjust the Web server timeout value. Messages 9

16 v v If this is not what you want, you can lengthen or disable the maximum busy time before disconnection on your connection. If this is still not what you want, you can lengthen or disable the HttpSession Activity Timeout. HPS5036 Attempt to create user list with invalid type: {0}. 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. HPS5037 Attempt to create user list with invalid name: {0}. 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: v Front or back slash (/ \) v Colon (:) v Asterisk (*) v Question mark (?) v Quotation mark (") v Less than or greater than brackets (< >) v System device names: con, com, lpt, prn, or nul Caution: If you have limited experience editing macro files, please call IBM service. HPS5038 Error creating object {0}. Object is empty 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. HPS5039 Cannot get a User from user list {0} available. The named user list has no free users 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 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. HPS5041 Value of attribute {0} specified, but no file name specified. 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. HPS5043 Internal error, attribute {0} in Conn object is null. This is an internal error. Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information. HPS5044 closed. HPS5045 SQL connection is closed. A JDBC connection has unexpectedly Retry the request. JDBC exception while checking connection state : {0} {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. HPS5046 be loaded. JDBC driver {0} not loadable, received exception: {1} The JDBC driver (Java class) could not 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} Could not connect to database (URL) specified in the connection specification for this application. 10 IBM Host Access Transformation Services: Messages

17 Verify that the database URL is reachable using DB vendor-supplied tools. HPS5048 Call to method {0} not expected for JDBC connections. This is an internal error. Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information. HPS5049 The following Session properties are not acceptable to HOD : {0}. Exception received: {1} 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. HPS5050 Cannot recover connection if HodLogonSpec is null. 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. HPS5051 Cannot recover connection if logon or alternate logon macros are null 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. HPS5052 Cannot set up a connection to the host using the following session properties: {0} 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. HPS5053 Received InterruptedException: {0} This is an unexpected error. Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information. HPS5054 Macro state STATE_EMPTY not reached. Current macro state is {0} This is an unexpected error. Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information. HPS5055 Ran out of time while playing HOD macro: Macro file name = {0} Macro = {1} 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. HPS5056 Problem encountered while playing macro in file {0} Current state is {0} Initial fragment of the macro: {1} This is an unexpected problem. Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information. HPS5057 PropertyVetoException received from HOD: {0} 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 Messages 11

18 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. HPS5058 MacroException received from HOD: {0} 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. allow enough time to run the macro. 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} 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. HPS5059 HOD extract event {0} not expected. Extracts are not permitted in logon or logoff macros 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. HPS5060 Both UserPool and BeanRef are null - cannot provide value for prompt {0} to HOD macro 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. HPS5061 Ran out of time while supplying prompt values to HOD macro in file {0}. Exception received: {1} 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 HPS5063 Received the following MacroErrorEvent while playing HOD macro: {0} 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. HPS5064 No get_userid method (with either 0 or 1 argument) in bean 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. HPS5065 Fix the application in the Toolkit. No get_password method in bean 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. Toolkit. Fix the application in the HATS HPS5066 No "getter" method {0} for parameter {1} in bean {2} 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. 12 IBM Host Access Transformation Services: Messages

19 HPS5067 Exception received when calling getter method in bean: {0} 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. HPS5068 Exception received: {0} 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. HPS5069 Attempt to set connection state to {0} is not valid. This is an internal error. Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information. HPS5070 Cannot change originating Pool. Old: {0}, New: {1}. This is an internal error. Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information. HPS5071 Cannot change connection specification. Old: {0}, New: {1} This is an internal error. Turn on HATS traces and try to re-create the condition. Contact IBM service and provide the trace information. HPS5072 There is no Pool Manager An unexpected error occurred. Re-export the user list from Host Publisher without encryption. HPS5073 An encryption key is needed to start the system. The named user list contains encrypted data that requires an encryption key. HPS5074 Supply the required encryption key. An encryption key is needed because user list {0} is encrypted. The named user list contains encrypted data that requires an encryption key. HPS5075 Supply the required encryption key. Received STATE_PLAY_ERROR while playing macro in file {0} 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. 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} 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. HPS5079 HOD macro {0} has one or more syntax errors 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. Messages 13

20 HPS5080 Invalid value of attribute {0} in object {1}. {0} can only be -1 or greater than {2} 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. 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. 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. HPS5082 Missing property {0} in user list {1} 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. HPS5085 Licenses used ({0}) exceeding licenses purchased ({1}). For more information on licensing enablement, see the InfoCenter at ({2}). 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. HPS5086 Invalid value of attribute {0} in object {2}. {0} cannot be greater than attribute {1}. The value of attribute {1} will be used. 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. HPS5090 System start This is an informational message. The HATS runtime has been started. This message is informational only; no action is required. HPS5083 Failed to find the file named {0} not be read. The specified file does not exist or could 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. HPS5084 Could not set up a connection 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. HPS5091 System shutdown This is an informational message. The HATS 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} 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. HPS5093 {0} Invalid schema value for {1} property. {2} 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. 14 IBM Host Access Transformation Services: Messages

21 HPS5094 {0} User property {1} conflicts with schema. {2} 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. HPS5095 User {0} not found in user list {1} The named user was not found in the named user list. HPS5096 Respecify the name of the user. Pool {0} exceeded its capacity. Overflow connection created 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. HPS5097 Pool {0} exceeded its capacity. Request failed 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. HPS5098 Ran out of time while playing HOD macro: Macro file name = {0} Macro = {1} Exception received: {2} 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. HPS5099 Internal error, the following attribute or result is unexpected {0} This is an internal error. Turn on HATS traces and try to re-create the condition. Contact IBM 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 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. HPS5101 The WebSphere servlet engine cannot create an HttpSession object to store the host connection with the key {0}. 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. HPS5102 Insufficient rights to the file {0}. Please check file owner and permissions 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. HPS5103 The data source connection has been removed, probably because the maxbusytime has expired 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. Messages 15