Messages

The messages in this chapter are those that can be issued when your HATS application runs on the IBM WebSphere Application Server. Messages in the Studio do not have message numbers; error conditions in the Studio are displayed at the top of the wizard panels. Some Studio messages will appear in the task list.

HAT0001

HAT0002

HAT0003

HAT0040

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

HAT0060

HAT0061

HAT0062

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

HAT0300

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

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

Ensure that the filename 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

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.

Note: Set your WebSphere Studio workbench preferences to perform a build automatically when a resource has been modified.

HAT0353

Create the file {0}.

Explanation:

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

User Response:

This is an informational message. No response is required.

HAT0354

Failed to delete the file named {0}.

Explanation:

An error occurred that prevented deleting the named file.

User Response:

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

HAT0360

Licenses used ({0}) exceeding licenses purchased ({1}).

Explanation:

{0} is the number of licenses used.

{1} is the number of licenses purchased.

You cannot create connections beyond the number of licenses you have purchased.

User Response:

Cannot load the application {0}.

Explanation:

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

{0} is the name of the application.

User Response:

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

HAT0405

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

Explanation:

{0} displays the session properties.

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

User Response:

Ensure that the application's connection settings are correct. Contact IBM service for assistance.

HAT0410

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

Explanation:

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

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

User Response:

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

HAT0411

The host connection is inactive.

Explanation:

The host became inactive during the processing of the application.

User Response:

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

HAT0412

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

HAT0604

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

Explanation:

{0} is the name of the global variable.

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

User Response:

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

HAT0605

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

Explanation:

{0} is the name of the screen customization.

User Response:

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

Explanation:

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

User Response:

Specify a valid attribute in the widget setting.

HAT0701

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

Explanation:

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

User Response:

Specify a value for the attribute in the widget setting.

HAT0702

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

Explanation:

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

User Response:

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

HAT0703

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

Explanation:

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

User Response:

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

HAT0800

An exception occurred setting the property of print session. A message containing the exception details follows.

User Response:

No HttpSession available

Explanation:

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

User Response:

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

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

Explanation

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

Netscape browsers use a single HttpSession for Web access, even when accessing from different browser windows. The multiple windows request the same data source resource, when the multiple windows should be using different resources.

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 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.

User Action

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

To avoid this problem, do not attempt to run multiple applications containing chained Integration Objects concurrently from the same client machine running Netscape.

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:
// 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 time-out value.

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}.

Explanation:

An unexpected error occurred.

User Response:

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}.

Explanation:

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

User Response:

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

Front or back slash (/ \)

Colon ( : )

Asterisk ( * )

Question mark ( ? )

Quotation mark ( " )

Less than or greater than brackets ( < > )

System device names: con, com, lpt, prn, or nul

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

Explanation:

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

User Response:

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

Unable to copy {0}

Explanation:

The named file or directory cannot be copied.

User Response:

If WebSphere Application Server has been uninstalled, the file or directory may no longer exist. Environment variables may be set incorrectly. Check that the file

server\common\service\lib\hpserverevn.bat

or the equivalent .sh file exists and has appropriate values.

HPS5747E

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.

HPS5955

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

Explanation:

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

User Response:

Internal processing error

Explanation:

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

The hPubStartType in the Integration Object contained an unexpected value.

The runtime could not find the macro specified by the Integration Object.

An unexpected error occurred during macro play.

User Response:

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

HPS6006

Introspection exception

Explanation:

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

User Response:

Contact application vendor if problem persists.

HPS6007

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

Explanation:

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

User Response:

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

Internal macro processing error, macro empty

Explanation:

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

User Response:

Check whether the macro file is empty. If it is, go back to HATS Studio and attempt to recover or record the macro again.

If the problem persists, contact IBM service.

HPS7001

Unexpected exception {0}.

Explanation:

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

User Response:

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

Home

Messages

Overview

HAT0001

HAT0002

HAT0003

HAT0040

HAT0060

HAT0061

HAT0062

HAT0300

HAT0350

HAT0351

HAT0352

HAT0353

HAT0354

HAT0360

HAT0400

HAT0401

HAT0402

HAT0403

HAT0405

HAT0410

HAT0411

HAT0412

HAT0413

HAT0600

HAT0601

HAT0602

HAT0603

HAT0604

HAT0605

HAT0606

HAT0607

HAT0608

HAT0700

HAT0701

HAT0702

HAT0703

HAT0800

HAT0801

HAT0910

HAT0911

HAT0912

HAT0913

HAT0914

HPS5001

HPS5007

HPS5008

HPS5009

HPS5010

HPS5011

HPS5012

HPS5013

HPS5014

HPS5015

HPS5016

HPS5017

HPS5018

HPS5019

HPS5020

HPS5021

HPS5022

HPS5023

HPS5024

HPS5025

HPS5027

HPS5028

HPS5029

HPS5030

HPS5031

HPS5032

HPS5033

HPS5034

HPS5036

HPS5037

HPS5038

HPS5039

HPS5040

HPS5041

HPS5043