ibm rational host access transformation services: … an error occurred while processing this...

IBM Rational Host Access Transformation Services

MessagesVersion 9.0

SC27-5901-00

��

NoteBefore using this information and the product it supports, be sure to read the general information under “Notices,” on page29.

Tenth Edition (August 2013)

© Copyright IBM Corporation 2003, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Messages . . . . . . . . . . . . . . 1

Appendix. Notices . . . . . . . . . . 29Trademarks . . . . . . . . . . . . . . 30

© Copyright IBM Corp. 2003, 2013 iii

iv IBM Rational Host Access Transformation Services: Messages

Messages

The messages in this chapter are those that can be issued when your HATSapplication runs in a production environment. Messages in the HATS Toolkit donot have message numbers, and error conditions in the toolkit are displayed at thetop of the wizard panels. Some toolkit messages will appear in the task list.

The messages are arranged according to their numeric component.

HAT0001 Loading configuration data from {0}.

Explanation: {0} is the file name of the configurationdata file.

User response: None.

HAT0002 The message log file is {0}.

Explanation: {0} is the file name of the message logfile.


HAT0003 The trace log file is {0}.

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


HAT0040 A program exception occurred. Theremay be additional messages in this logwhich describe the error. The followinginformation may help determine thecause, if this log is requested by IBMservice:

{0}{1}

Explanation: {0} is the exception message string asreceived by Java™.

{1} is the exception stack trace.

User response: Check the log for additional messages.

HAT0060 File {0} was not found.

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

User response: Contact IBM® service for assistance.

HAT0061 Directory {0} was not found.

Explanation: {0} is the missing directory.

User response: Contact IBM service for assistance.

HAT0062 Archive file {0} could not be created.

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

User response: Ensure that the application'sconnection settings, specifically the SSL certificatesetting, are correct. Contact IBM service for assistance.

HAT0300 An unexpected exception was received:{0}

Explanation: {0} is the exception.

User response: If the exception is issued by codewritten by a user, such as business logic or customcomponents or widgets, contact the programmer whowrote the code. Otherwise, contact IBM service forassistance.

HAT0350 An error occurred reading the file {0}.

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

User response: Ensure that the file exists and is avalid file and that the user that is running WebSphere®

Application Server has the necessary privileges to readfiles in that directory. Contact IBM service forassistance.

HAT0351 An error occurred writing the file {0}.

Explanation: {0} is the file name of the file beingwritten.

User response: Ensure that the file name is valid andthat the user that is running WebSphere ApplicationServer has the necessary privileges to create and writefiles in that directory. Contact IBM service forassistance.

HAT0352 Cannot find the file named {0}.

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

User response: Restore the missing file. Make sure thefile is not marked as read-only and that the user that isrunning WebSphere Application Server has thenecessary privileges to create and write files in thatdirectory.

You might need to rebuild the HATS project before theapplication is run.

© Copyright IBM Corp. 2003, 2013 1

Note: You can set your Rational® SDP workbenchpreferences to perform a build automaticallywhen a resource has been modified.

HAT0353 Creating the file {0}.

Explanation: {0} is the file name of the file beingcreated.

User response: This is an informational message. Noresponse is required.

HAT0354 Failed to delete the file named {0}.

Explanation: An error occurred that preventeddeleting the named file.

User response: Ensure the file path is valid and theuser ID that is running WebSphere Application Serverhas the necessary privileges to delete the file.

HAT0360 Licenses used ({0}) exceeding licensespurchased ({1}). For more information onlicensing enablement, see theInfoCenter at ({2}).

Explanation: You cannot create connections beyondthe 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.

User response: Verify that the number of licenses youconfigured is correct. The value is specified in thenumLicenses parameter in the runtime.properties file.

For more information see the section, Enabling HATSruntime and license settings, in HATS Getting Started.

HAT0361 HATS License key is corrupt. Defaultassigned. For more information onlicensing enablement, see theInfoCenter at ({0}).

Explanation: The value for licenseHardLimit in theruntime.properties file appears to be corrupted. Due tothis license corruption, only two connections can beestablished.


User response: Correct the license information asdirected in message HAT0362.

HAT0362 HATS License key is missing. Defaultassigned. For more information onlicensing enablement, see theInfoCenter at ({0}).

Explanation: If the licenseHardLimit value inruntime.properties is missing, the message HAT0362 isissued, and the HATS server only allows two

connections to be established.


User response: To resolve this condition and allowmore than two users to access the HATS application,you must restore the licenseHardLimit value in theruntime.properties file and restart your application. Thevalue for licenseHardLimit is a case-sensitive stringplaced into the runtime.properties file when you enablethe HATS runtime licenses. You can obtain the correctvalue for licenseHardLimit from one of the followingplaces:

v The EAR project created in your HATS Toolkitworkspace contains a copy of the runtime.propertiesfile that should contain the correct value forlicenseHardLimit. The location of theruntime.properties file is shared_install_directory\plugins\com.ibm.hats_nnn\predefined\projects\earProject\runtime.properties, whereshared_install_directory is the shared resourcesdirectory where you installed the HATS offeringusing IBM Installation Manager and nnn is theversion and build level of HATS.

v If you have other HATS .ear files deployed to yourserver, each has a runtime.properties file, whichshould contain the correct value forlicenseHardLimit.

Copy the licenseHardLimit value to theruntime.properties file in the .ear file causing theproblem and restart the HATS application.


If your HATS application is running in a verticallyclustered environment, verify that you have followedthe instructions for configuring HATS in this type ofenvironment. Failure to follow the instructions couldmake worse the conditions that cause the HAT0362message to be issued. Refer to Configuring HATSapplications in a clustered environment in the HATSUser's and Administrator's Guide.

HAT0363 HATS Error reading HATS License key.Default assigned. For more informationon licensing enablement, see theInfoCenter at ({0}).

Explanation: The value for licenseHardLimit in theruntime.properties file could not be read. Due to thisproblem, only two connections can be established.


User response: Correct the license information asdirected in message HAT0362.

2 IBM Rational Host Access Transformation Services: Messages

gslicense.htm

gslicense.htm

gslicense.htm

gslicense.htm

ugcreorg.htm#cluster

ugcreorg.htm#cluster

HAT0400 An exception occurred creating the hostconfiguration. A message containing theexception details follows.

User response: Use the information in the messagethat follows to bypass the exception during hostconfiguration.

HAT0401 Cannot connect to the host using thefollowing session properties:

{0}

Explanation: {0} is a set of session properties.

User response: Examine the properties to verify thatthe named server exists and is available.

HAT0402 Session is in CONNECTION_ACTIVEstate, but not CONNECTION_READYstate. A possible reason could be thatthe TN server port specified does notsupport the data stream expected.

Session properties being used:{0}

Explanation: {0} is a set of session properties.

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

HAT0403 Cannot load the application {0}.

Explanation: The application.hap file could not beloaded for the named application.

{0} is the name of the application.

User response: The required file could not be locatedor has been corrupted. Rebuild the application in HATSToolkit and reinstall it on WebSphere ApplicationServer. Server traces will display the expected file nameand location.

HAT0405 Session is ready, but no host data wasavailable. Session properties:

{0}

Explanation: {0} displays the session properties.

The host connection came up, but the host sent noscreen data.

User response: Ensure that the application'sconnection settings are correct. Contact IBM service forassistance.

HAT0410 An error occurred while processing thisrequest.

Detailed error information: {0}

Explanation: {0} is the exception stack trace or otherapplication programmer information.

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

User response: If the application is still available, youmight be able to continue the application. To determinewhat caused the error, check the other messagesappearing with this message and check the message logor trace file for additional information.

HAT0411 The host connection is inactive.

Explanation: The host became inactive during theprocessing of the application.

User response: If the application is ending normally,no response is necessary. If the application endsabnormally, check the message log for additionalinformation. Also, ensure that the application'sconnection settings are correct. Additional informationmight be found at the Telnet server.

HAT0412 An error occurred while processing anapplication Web page "{0}".

Explanation: {0} is the name of the Web page (such asa transformation .jsp) being processed.


HAT0413 An exception occurred. {0}

Explanation: An unexpected error occurred.

User response: Read the extra message text. Check thelog file for preceding or subsequent messages. If theproblem persists, turn on HATS traces and try tore-create the condition. Contact IBM service andprovide the trace information.

HAT0414 An error occurred while scanning forscreen matches.

Explanation: An unexpected error occurred whilecomparing the host screen against the list of configuredscreen customizations. The following messages describethe problem in greater detail.

User response: Check the log file for subsequentmessages. If the problem persists, turn on HATS tracesand try to re-create the condition. Contact IBM serviceand provide the trace information.

Messages 3

HAT0415 The wfhats.xml file is malformed.

Explanation: The wfhats.xml file is malformed.

User response: See System error log for error details.See product documentation for a sample wfhats.xmlfile.

HAT0416 An error occurred while forwardingcontrol to WebFacing.

Explanation: An error occurred while forwardingcontrol to WebFacing.

User response: Check that wfContextRoot inwfhats.xml matches the context root of your WebFacingapplication.

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

Explanation: {0} is the name of the screencustomization.

User response: Rebuild the project before theapplication is run.

Note: You can set your Rational SDP workbenchpreferences to perform a build automaticallywhen a resource has been modified.

HAT0601 The action {0} specifies an invalidparameter.

Explanation: {0} is the name of the action.

User response: Specify a valid parameter for theaction.

HAT0602 Cannot insert null value to the hostscreen at row {0}, column {1}.

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

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

User response: Ensure that the variable inserted ontothe host screen has a value.

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

Explanation: {0} is the value.

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


{3} is the host screen size.

User response: Insert a value at the row and columnlocation that is valid for the host screen size.

HAT0604 An exception occurred while calculatingthe value for the global variable {0}. Theaction which failed was {1}. A messagecontaining 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 messagethat follows to bypass the exception during calculationof the value for the global variable.

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

Explanation: {0} is the name of the screencustomization.


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


User response: Check the message log for additionalinformation. Examine the trace file, if one exists. Checkthe application's screen customization actions to ensurethat all required global variables are created.

HAT0607 The index {0} for global variable "{1}" isout of bounds. The global variable has{2} elements.

Explanation: {0} is the value of the global variableindex.

{1} is the name of the global variable.

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

User response: Check the message log for additionalinformation. Examine the trace file, if one exists. Checkthe application's screen customization actions to ensurethat all required global variables are created andcontain enough elements to complete the failing action.

HAT0608 Cannot insert the value "{0}" to the hostscreen at row {1}, column {2}, becausethe location is not contained in anunprotected field.


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


User response: Choose a valid row and columnlocation for the current screen. Ensure that the globalvariable is being inserted into an unprotected field.


HAT0700 The attribute "{0}" of widget setting doesnot exist.

Explanation: {0} is the attribute in the widget settingthat does not exist.

User response: Specify a valid attribute in the widgetsetting.

HAT0701 The value of attribute "{0}" in widgetsetting is empty.

Explanation: {0} is the attribute of the widget settingthat is empty.

User response: Specify a value for the attribute in thewidget setting.

HAT0702 The value of attribute "{0}" in widgetsetting is invalid.

Explanation: {0} is the attribute of the widget settingthat is invalid.

User response: Specify a valid value for the attributein the widget setting.

HAT0703 An error occurred while processing atransformation fragment {0}.

Explanation: {0} is the name of the transformationfragment file that could not be processed because it ismissing or corrupted.

User response: Check whether the file exists. If itdoes, open it in the JSP editor and look at the task listfor messages.

HAT0800 An exception occurred setting theproperty of print session. A messagecontaining the exception details follows.

User response: Use the information in the messagethat follows to bypass the exception that occurredwhile setting the property of the print session.

HAT0801 An exception occurred processing PDFI/O to client browser. A messagecontaining the exception details follows.

User response: Use the information in the messagethat follows to bypass the exception during processingof the PDF I/O to the client browser.

HAT0910 User credentials could not be retrievedfrom Web Express Logon.

Explanation: Credentials were not found for this user.

User response: Check your credential source todetermine whether it is providing credentials for thisuser.

HAT0911 Web Express Logon macro could not beinitialized.

Explanation: Internal error.

User response: Contact IBM Service for assistance.

HAT0912 Web Express Logon cannot retrieve usercredentials because the client servletrequest was not provided.

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

User response: Verify that the macro and theconnection both support Web Express Logon or both donot support Web Express Logon.

HAT0913 Web Express Logon cannot retrieve usercredentials because the credentialmapper was not initialized.

Explanation: The Credential Mapper has not beenconfigured.

User response: Validate your Web Express Logonconfiguration and check for errors.

HAT0914 Verify that the connection has beenconfigured to support Web ExpressLogon.

Explanation: HATS cannot verify that the connectionhas been configured for Web Express Logon.

User response: Check your connection configurationin HATS Toolkit. Verify that the check box for WebExpress Logon is checked.

HAT0915 The plug-in {0} is not appropriate for theenvironment it is running in. Be sure tochoose the proper plug-inimplementation class for IBM orStandard portlet environments.

Explanation: The plug-in class specified in thehatswelcfg.xml file used by Web Express Logon is notvalid for this type of project.

User response: Validate your Web Express Logonconfiguration and choose a proper plug-in for theproject.

HAT1300 Event payload type must be serializable.

Explanation: A JSR 286 portlet can only send an objectthat is serializable. An object is serializable if its classimplements the Serializable interface.

User response: Ensure the global variable being sentcontains a serializable object. A serializable object is aninstance of a class that implements the Serializableinterface. The problem must be fixed in the toolkit.

Messages 5

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

Explanation: In a configuration file, the specifiedvalue is not acceptable.

User response: Rebuild the application in the Toolkitand redeploy it. If the problem continues, review thesettings in the Toolkit for this application.

HPS5007 Failed to delete the file named {0}

Explanation: An error occurred that preventeddeleting the named file.

User response: Ensure the file path is valid and theuser ID that is running WebSphere Application Serverhas the necessary privileges to delete the file.

HPS5008 There was an error reading the file {0}

Explanation: Some error occurred while reading thespecified file.

User response: Ensure the specified file exists and theuser ID that is running WebSphere Application Serverhas the necessary privileges to read the file. Rebuild theapplication in HATS Toolkit and reinstall it onWebSphere Application Server. If the problemcontinues, contact IBM Service.

HPS5009 There was an error writing the file {0}

Explanation: Some error occurred while writing thespecified file.

User response: Ensure the directory for the file exists,and the user ID that is running WebSphere ApplicationServer has the necessary privileges to create and writefiles in that directory.

HPS5010 The installation directory parameter {0}specifies a directory {1} that is not anabsolute path

Explanation: The install directory parameter does notrepresent a complete unambiguous directory.

User response: Rebuild the application in HATSToolkit and reinstall it on WebSphere ApplicationServer. If the problem continues, contact IBM Service.

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

Explanation: The install directory parameter does notrepresent a directory that exists.


HPS5012 {0} is not a directory

Explanation: The named object was expected to be adirectory but was not.


HPS5013 The XML element {0} is missing therequired attribute {1}

Explanation: An expected item was not found in aconfiguration file.

User response: Look for other messages that identifythe application. Install the application again.

HPS5014 The initialization parameter {0} ismissing. It should specify theinstallation directory name

Explanation: WebSphere Application Server is notcorrectly configured to provide the application with thename of its installation directory.


HPS5015 The XML element {0} is missing eitherthe attribute {1} or the attribute {2}

Explanation: One of two expected items is missing ina configuration file.

User response: Look for other messages that identifythe application. Rebuild the application in HATSToolkit and reinstall it on WebSphere ApplicationServer. If the problem continues, contact IBM Service.

HPS5016 The XML element {0} is not a validelement in the file {1}

Explanation: An unexpected item was found in thespecified configuration file.


HPS5017 Unexpected error {0} occurred. {1}


User response: Try again. If the problem persists, turnon HATS traces and try to re-create the condition.Contact IBM service and provide the trace information.


HPS5018 An unexpected exception has occurred.{0}.

Explanation: {0} is the exception.

User response: If the exception is issued by codewritten by a user, such as business logic or customcomponents or widgets, contact the programmer whowrote the code. Otherwise, contact IBM service forassistance.

HPS5019 There was an XML parse error whilereading the file {0} or its DTD file atline {1} in column {2}. The error messageis {3}

Explanation: There was something wrong with aconfiguration file.


HPS5020 An exception occurred while parsingXML file {0} : {1}.


User response: If the problem persists, turn on HATStraces and try to re-create the condition. Contact IBMservice and provide the trace information.

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

Explanation: An error was found creating the namedobject. An invalid value has been specified for thenamed attribute.

User response: Examine the pool and connection XMLfiles, and ensure you are providing a valid value forthe named attribute.

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



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


User response: Examine the pool and connection XML

files, and ensure you are providing a valid value forthe named attribute.

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



HPS5025 Missing mandatory attribute {0} inobject {1}

Explanation: An error was found creating the namedobject. The mandatory attribute is missing.

User response: Examine the pool and connection XMLfiles, and ensure you are providing the mandatoryattribute for the named object.

HPS5027 Error creating object {0}. Object {1} notdefined.

Explanation: An error was found creating the namedobject. The second named object did not exist. An erroroccurred while creating the second named object.

User response: Examine the log messages before thisone and resolve the errors that occurred creating thesecond named object.

HPS5028 Object {0} already defined

Explanation: An attempt was made to create an objectalready defined.

User response: Examine the pool and connection XMLfiles, and remove the duplicate occurrence of thenamed object.

HPS5029 The runtime is not started.

Explanation: The HATS runtime is not started, but anoperation was attempted that requires the runtime tohave been started.

User response: Use the WebSphere Application ServerAdministration program to start the HATS runtime. Ifthis does not resolve the error, stop and restart theWebSphere Application Server, then ensure the HATSruntime is started.

HPS5030 {0} expired. Cannot get a connectionfrom {1}.

Explanation: The maximum waiting time defined forthe named connection pool has expired. No connectionis available to satisfy the request.

Messages 7

User response: If this condition occurs frequently, youmight want to increase the maximum number ofconnections defined for the named connection pool.

HPS5031 Object {0} not defined

Explanation: The named object is not defined. AnIntegration Object refers to a connection pool that is notdefined on the server. Using HATS Integration Objectsin a non-HATS web module, such as a portlet, cancause Object not defined errors (HPS5031) to occur ifthe display name in web.xml doesn't match the contextdefined in application.xml.

User response: Try installing the application again.This will also install the required connection pooldefinition. If you get this error because you are usingHATS Integration Objects in a non-HATS web module,change the display-name tag in web.xml (in .war) tomatch the context value from application.xml (in .ear)to resolve the problem.

HPS5032 Cannot load Pool Manager {0}


User response: If the problem persists, turn on HATS

traces and try to re-create the condition. Contact IBMservice and provide the trace information.

HPS5033 Too little memory. {0} bytes available

Explanation: There is too little memory left toproceed.

User response: Free some memory by shutting downapplications and freeing disk space. Retry theapplication request.

HPS5034 No HttpSession available

Explanation: An Integration Object tried to acquire anexisting connection from the Web session, but there isno web connection. Either the Integration Object thatrequested the connection or the Integration Object thatsaved the object are miscoded, or the web connectionhas timed out, and the web connection (HttpSession)has been deleted.

User response: Examine the Integration Objects forerrors, and determine whether or not the timeout valuefor the web connection (HttpSession) is too short.

HPS5035 There is no data source object {0} in HttpSession. A possible cause is the use of multiplebrowsers 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 theHttpSession, but the resource is not in the HttpSession object. This may occur for anumber of reasons: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 thandouble-clicking the icon to open the Internet Explorer browser, the problem will occurbecause the Internet Explorer browser windows will then share a single HttpSession.

v A single JSP or servlet runs multiple Integration Objects without checking for an errorin a previous Integration Object and stopping the next Integration Object fromexecuting. The previous Integration Object will not have placed the data sourceresource back in the HttpSession if it encountered an error.

v A user clicks Submit or clicks a link twice before the first button press or link click canbe completely processed at the server. If processing is taking longer than expected, auser might click on a link to the next page of a chained Integration Object applicationtwice rather than wait for the next page to process its Integration Object and send theoutput page back to the client. The second click causes the next page to be processedagain, while the Integration Object still has ownership of the data source resource.During this processing, a second instance of the Integration Object cannot find theresource in the HttpSession, and causes a HPS5035 error to be logged and the output ofthe first Integration Object processing is lost.

v A very long-running Integration Object (usually more than a minute) might cause theWeb server to time out while the Integration Object is still processing. If this occurs, theWeb server may destroy the HTTP connection to the browser client. Internet Explorersometimes reacts to this by immediately requesting the same page again without userintervention. This second request is just like a second Submit or link click, causing asecond 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.

v If the maximum busy time before disconnection specified for the connection expiresbecause a chained Integration Object application was left idle between IntegrationObjects executing (for example, the Integration Objects are on different pages), then thenext Integration Object in the chain will log an HPS5035 if a user continues with theapplication after the expiration time.

v If the HttpSession Activity Timeout, set in WebSphere Application Server, occursbecause a chained Integration Object application is left idle between Integration Objectsexecuting (for example, the Integration Objects are on different pages), then the nextIntegration Object in the chain logs a HPS5035 if a user continues with the applicationafter the expiration time.

User response:The correct action depends on the cause. Possible actions for the listed causes are,respectively: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.v 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 aprevious Integration Object, and the Integration Object in error should redirect theclient 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.}

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

v The simplest way to prevent this is to have no Integration Object run for a very longtime. Alternatively, you may be able to adjust the Web server timeout value.

Messages 9

v If this is not what you want, you can lengthen or disable the maximum busy timebefore disconnection on your connection.

v If this is still not what you want, you can lengthen or disable the HttpSession ActivityTimeout.

HPS5036 Attempt to create user list with invalidtype: {0}.



HPS5037 Attempt to create user list with invalidname: {0}.

Explanation: An attempt was made to create a userlist with no name.

User response: Check the name of the user list in theconfiguration file (.hco file) for this connection. A validuser 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 macrofiles, please call IBM service.

HPS5038 Error creating object {0}. Object is empty

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

User response: Examine the XML files that define thenamed object. You may need to republish or repair theXML files.

HPS5039 Cannot get a User from user list {0}

Explanation: The named user list has no free usersavailable.

User response: Retry the request later, or enlarge thesize of the user list.

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


User response: Examine the pool and connection XML

files, and ensure you are providing a valid value forthe named attribute.

HPS5041 Value of attribute {0} specified, but nofile name specified.

Explanation: A logoff macro, logon macro, or checkinscreen name attribute is specified in the .hco file, butthe value is not valid.

User response: Examine the connection XML (.hco)file, and ensure you are providing a valid value foreach attribute.

HPS5043 Internal error, attribute {0} in Connobject is null.

Explanation: This is an internal error.

User response: Turn on HATS traces and try tore-create the condition. Contact IBM service andprovide the trace information.

HPS5044 SQL connection is closed.

Explanation: A JDBC connection has unexpectedlyclosed.

User response: Retry the request.

HPS5045 JDBC exception while checkingconnection state : {0}

Explanation: {0} is a JDBC exception received whiletesting the connection before use.

User response: Examine the exception message for thecause of the problem. Retry the request. If the problemreoccurs, contact IBM support.

HPS5046 JDBC driver {0} not loadable, receivedexception: {1}

Explanation: The JDBC driver (Java class) could notbe loaded.

User response: The driver may be missing. Thedirectory where the class resides may not be inWebSphere Application Server or reloadable servletclasspath. Check both.

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

Explanation: Could not connect to database (URL)specified in the connection specification for thisapplication.


User response: Verify that the database URL isreachable using DB vendor-supplied tools.

HPS5048 Call to method {0} not expected forJDBC connections.



HPS5049 The following Session properties are notacceptable to HOD : {0}. Exceptionreceived: {1}

Explanation: Host On-Demand will not accept thecurrent value of the named property. The value iseither invalid or is incompatible with the other Sessionproperties for this host connection.

User response: Specify a valid value for the namedproperty. If this does not correct the error, turn onHATS traces and try to re-create the condition. ContactIBM service and provide the trace information.

HPS5050 Cannot recover connection ifHodLogonSpec is null.

Explanation: This connection requires recoverybecause the user ID and password are characterized asbeing single use only, and when the connection wasreturned to the connection pool, the screen was notwhat was expected. However, this application has noconnect specification, and thus there is no connect oralternate connect macro that can be run to recover theuser ID and password.

User response: None, if the above scenario is true. Ifnot, you can change the connection specification todefine the user IDs to not be single use only, or defineconnect and alternate connect macros.

HPS5051 Cannot recover connection if logon oralternate logon macros are null

Explanation: This connection requires recoverybecause the user ID and password are characterized asbeing single use only, and when the connection wasreturned to the connection pool, the screen was notwhat was expected. However, this application has noconnect or alternate connect macro that can be run torecover the user ID and password.

User response: None, if the above scenario is true. Ifnot, you can change the connection specification todefine the user IDs to not be single use only, or defineconnect and alternate connect macros.

HPS5052 Cannot set up a connection to the hostusing the following session properties:{0}

Explanation: Cannot connect to the host (TN server)specified in the connection specification file for thisapplication.

User response: Examine the host name and portnumber for the TN server that is in the connectionspecification file for this application. Check thatTCP/IP connectivity to the TN server is available usingthe ping program. If that succeeds, then use anemulator for the right terminal type and check if theTN server is operational.

HPS5053 Received InterruptedException: {0}

Explanation: This is an unexpected error.


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

Explanation: This is an unexpected error.


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

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

User response: Increase the timeout value and look atthe log to identify the screen.

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

Explanation: This is an unexpected problem.


HPS5057 PropertyVetoException received fromHOD: {0}

Explanation: Host On-Demand will not accept thecurrent value of the named property. The value iseither invalid or is incompatible with the other session

Messages 11

properties for this host connection

User response: Specify a valid value for the namedproperty. If this does not correct the error, turn onHATS traces and try to re-create the condition. ContactIBM service and provide the trace information.

HPS5058 MacroException received from HOD: {0}

Explanation: The Host On-Demand code threw anexception while executing a connect or disconnectmacro. This is an unexpected error.


HPS5059 HOD extract event {0} not expected.Extracts are not permitted in logon orlogoff macros

Explanation: The connect or disconnect macro hasextract commands, which are unexpected in suchmacros and are ignored.

User response: Examine your macros. Extraction ofhost screens is not supported while running macros toconnect to, or disconnect from, a host. If you wish toextract host screens while the main connection is beingmade, play the macro within the connect event instead.

HPS5060 Both UserPool and BeanRef are null -cannot provide value for prompt {0} toHOD macro

Explanation: While trying to supply a parameter to aconnect or disconnect macro, the connection managercould not get it from the user list, nor was there anIntegration Object bean that could be interrogated forthe value. This can occur if pooling is enabled and theminimum connections setting for the connection pool isgreater than zero. The connection subsystem will beunable to prefill the pool as requested.

User response: Either disable pooling for thisconnection definition, or adjust the minimumconnections to zero. This will still allow connections tobe created on demand, but the connection subsystemwill stop trying to prefill the pool without the requiredinformation to prime the connection. Alternatively,supply a user list with the needed information.

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

Explanation: While setting up a connect or disconnectmacro for running, the connect (or disconnect) timeoutexpired. The timeout value could be too small in thecontext of how busy the TN server or the networktraffic is. It is also possible that a screen expected whilerunning the macro did not arrive. The amount of timeelapsed in attempting to connect to the host did not

allow enough time to run the macro.

User response: Increase the timeout value and look atthe log to identify the screen on which it failed.

HPS5062 Macro prompt value could not beprovided. Exception received: {0}

Explanation: An error was encountered while tryingto provide one or more values corresponding to promptstatements in a connect or disconnect macro.

User response: Examine the prompt statements in themacro (the file name is logged) and check that thevalue being accessed is in the user list or is availableusing a getter method in the Integration Object bean.

HPS5063 Received the following MacroErrorEventwhile playing HOD macro: {0}

Explanation: The execution of a connect or disconnectmacro resulted in an error.

User response: Examine the additional informationprovided in the log for more information on the causeof the error.

HPS5064 No get_userid method (with either 0 or1 argument) in bean

Explanation: Expected the Integration Object bean tosupply the password using a get_userid method sincethere was no user list. However, no such method wasfound.

User response: Fix the application in the Toolkit.

HPS5065 No get_password method in bean

Explanation: Expected the Integration Object bean tosupply the password using a get_password methodsince there was no user list. However, no such methodwas found.

User response: Fix the application in the HATSToolkit.

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

Explanation: A parameter to be supplied to a promptstatement in a connect or disconnect macro wasexpected to be found using a getter method in theIntegration Object bean, since it was not found in theuser list entry associated with this connection.However, no getter method was found.

User response: Re-create the Integration Object in theHATS Toolkit and reinstall the application.


HPS5067 Exception received when calling gettermethod in bean: {0}

Explanation: When attempting to get values from theIntegration Object bean to supply macro promptparameters to a connect or disconnect macro, a beangetter method threw a Java exception. This indicatesthere was a problem with the Integration Objectgenerated by the HATS Toolkit.


HPS5068 Exception received: {0}

Explanation: Received an unexpected exception whileattempting to supply macro prompt values to a connector disconnect macro by invoking getter methods of theIntegration Object bean.


HPS5069 Attempt to set connection state to {0} isnot valid.



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



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



HPS5072 There is no Pool Manager


User response: Re-export the user list from HostPublisher without encryption.

HPS5073 An encryption key is needed to start thesystem.

Explanation: The named user list contains encrypteddata that requires an encryption key.

User response: Supply the required encryption key.

HPS5074 An encryption key is needed becauseuser list {0} is encrypted.

Explanation: The named user list contains encrypteddata that requires an encryption key.

User response: Supply the required encryption key.

HPS5075 Received STATE_PLAY_ERROR whileplaying macro in file {0}

Explanation: An error was encountered by the HostOn-Demand code while executing a connect ordisconnect macro.

User response: The log will contain additionalinformation about the host screen that was seen by themacro engine when the macro failed, and the macroscreen on which the failure occurred. Examine both todetermine if this is the screen the macro expected.

HPS5077 Session is in CONNECTION_ACTIVEstate, but not CONNECTION_READYstate. A possible reason could be thatthe TN server port specified does notsupport the data stream expected.Session properties being used: {0}

Explanation: This can occur if the port specified forthe TN server, in the connection specification for thisapplication, does not support the terminal typeexpected. There could be other reasons too.

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

HPS5079 HOD macro {0} has one or more syntaxerrors

Explanation: The connect or disconnect macrocurrently running (identified in the log file) has asyntax error.

User response: This should not occur unless themacro was manually edited. If you have edited themacro, examine the additional information logged inthe message log file, for example, messages.txt, todetermine the line where an error is being detected,and correct it. If no error can be detected, rerecord themacro using the HATS Toolkit.

Messages 13

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



HPS5081 The value {0} assigned to the attribute{1} in the file {2} is not valid. It shouldbe a number. A value of {3} will beused.

Explanation: A configuration file contains a value thatwas supposed to be a number but was not. A defaultvalue was used.

User response: Modify the value in the specifiedconfiguration file to be a number.

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

Explanation: The password expected by a promptstatement in a connect or disconnect macro is missing.The password was expected to be in the user list.

User response: Examine the user list being used bythis application. If you do see entries that define valuesfor the property _password, contact IBM service.Otherwise, the user list needs to be rebuilt using theHATS Toolkit.

HPS5083 Failed to find the file named {0}

Explanation: The specified file does not exist or couldnot be read.

User response: Ensure the specified file exists and theuser ID that is running WebSphere Application Serverhas the necessary privileges to read the file. Rebuild theapplication in HATS Toolkit and reinstall it onWebSphere Application Server. If the problemcontinues, contact IBM Service.

HPS5084 Could not set up a connection

Explanation: The HATS runtime ran out of time whilesetting up a connection to a back-end data source. Thedata source may not be currently available, or yourconnection timeout in the connection specification filemay be too low.

User response: Check the availability of the datasource. If it is available, then it is possibly too busy,and consider increasing the timeout value in yourconnection specification and reinstalling thatapplication.

HPS5085 Licenses used ({0}) exceeding licensespurchased ({1}). For more information onlicensing enablement, see theInfoCenter at ({2}).

Explanation: The number of licenses in use hasexceeded the number of licenses purchased.

User response: Be sure you have properly enabled theHATS runtime licenses. If so, contact your supportorganization 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 beused.

Explanation: An inconsistency was found creating thenamed object. An invalid value has been specified forthe first named attribute. The value of the first namedattribute cannot be greater than the value of the secondnamed attribute. The value of the second attribute willbe used for the first attribute.

User response: This message is informational only; noaction is required.

HPS5090 System start

Explanation: This is an informational message.

User response: The HATS runtime has been started.This message is informational only; no action isrequired.

HPS5091 System shutdown

Explanation: This is an informational message.

User response: The HATS runtime has been stopped.This message is informational only; no action isrequired.

HPS5092 {0} Security attribute {1} appears to becorrupted, or the encryption key isincorrect. {2}

Explanation: An attempt to decrypt user list datafailed. The supplied encryption key is incorrect or theuser list data has been corrupted.

User response: Republish the user list from HostPublisher without encryption.

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

Explanation: An encryption level that is not valid isspecified for the named property.

User response: Specify a valid encryption level in theschema for the user list.


HPS5094 {0} User property {1} conflicts withschema. {2}



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

Explanation: The named user was not found in thenamed user list.

User response: Respecify the name of the user.

HPS5096 Pool {0} exceeded its capacity. Overflowconnection created

Explanation: The maximum number of connectionsdefined for the named pool has been reached. Anon-pooled connection has been created to satisfy therequest.

User response: Based on how often this conditionoccurs you might want to increase the maximumnumber of connections defined for the named pool.This message is informational only.

HPS5097 Pool {0} exceeded its capacity. Requestfailed

Explanation: The maximum number of connectionsdefined for the named pool has been reached. A newconnection could not be created to satisfy the request.

User response: Based on how often this conditionoccurs you might want to increase the maximumnumber of connections defined for the named pool.

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

Explanation: While supplying parameterscorresponding to prompt statements in a connect ordisconnect macro, the connecttimeout ordisconnecttimeout timer expired.

User response: The timeout value could be too smallin the context of how busy the TN server or thenetwork traffic is. It is also possible that a screenexpected while running the macro did not arrive, andthe connect (or disconnect) timeout expired.

HPS5099 Internal error, the following attribute orresult is unexpected {0}



HPS5100 User ID {0} from UserPool {1} was usedto set up a session to host {2}, and mustbe recovered

Explanation: During shutdown, a disconnect macroassociated with a host connection could not be runbecause the connection was in use by the IntegrationObject bean. This message logs which user ID ispotentially lost as a result.

User response: You can manually log on to the hostwith the above user ID and perform the alternateconnect steps to recover the user ID. Otherwise, theHATS runtime will perform that recovery on a perconnection basis, on restart. The manual recovery willresult in more efficient operation after restart.

HPS5101 The WebSphere servlet engine cannotcreate an HttpSession object to store thehost connection with the key {0}.

Explanation: This is a Web container error.


HPS5102 Insufficient rights to the file {0}. Pleasecheck file owner and permissions

Explanation: The permissions of the files are not set tovalues which allow the requested action.

User response: Ensure that the directory path is validand the user ID that is running WebSphere ApplicationServer has the necessary privileges to create thedirectory.

HPS5103 The data source connection has beenremoved, probably because themaxBusyTime has expired

Explanation: The connection to the host application ordatabase has already been removed. It is possible thatmaxBusyTime has been configured in the .poolspec filefor this application and time has expired, causing theconnection to be terminated before the IntegrationObject returned the connection. This can occur when anapplication with chained Integration Objects is running,and the end user pauses between two middle-in-chainIntegration Objects for a time longer than themaxBusyTime configured for the connection pool.

User response: Ensure that maxBusyTime is set to anappropriate value. In Host Access, click the ConnectionPools tab in the left pane. In the right pane, click theConnection Pool Configuration tab, then in theConnection Timeouts box, type a new value forMaximum busy time before disconnection.

Messages 15

HPS5107 User list {0} not found


User response: If the problem persists, clear all traceand log files, turn on HATS tracing and tracing for theIntegration Objects associated with this application, andtry to re-create the condition. Contact IBM service andprovide the trace and log file information.

HPS5108 Connection Pool {0} not found


User response: If the problem persists, clear all HATStrace and log files, turn on HATS tracing and tracingfor the Integration Objects associated with thisapplication, and try to re-create the condition. ContactIBM service and provide the trace and log fileinformation.

HPS5109 Hostname {0} cannot be resolved

Explanation: The hostname provided cannot beresolved in the network.

User response: Verify that the hostname providedexists in the network and is reachable.

HPS5110 RemoteException received when makingRMI call:{0}

Explanation: When attempting the specified call, aRemoteException was received. This usually indicates anetwork outage.

User response: Verify that the runtime beingadministered is still available.

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

Explanation: While attempting to access the specifiedIntegration object, no methods could be found. Thismost commonly happens if the Integration Object classis not accessible to WebSphere Application Server.

User response: Verify that WebSphere ApplicationServer's CLASSPATH correctly reflects accessibility tothe Integration Object.

HPS5117 Key {0} not present in message file

Explanation: The information for the specifiedmessage could not be found.

User response: If the problem persists, clear all HATStrace and log files, turn on HATS tracing and tracingfor the Integration Objects associated with thisapplication, and try to re-create the condition. ContactIBM service and provide the trace and log fileinformation.

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

Explanation: The runtime with the specified namedoes not exist.

User response: Examine the message log for othermessages that may give more details. Verify that thenames of the host and runtime are correct and that theyare active.

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

Explanation: While verifying the state of theconnection, it was found that the current screen of theapplication does not match the expected screen for thehost connection to be returned to the connection pool.

User response: Examine your macros to see if thescreen that is in the log for this error message couldhave appeared after a normal execution of a data macroof an Integration Object (the last one in a chain, ifchained). If so, your checkin screen description definedby the application is incorrect. This can occur if youchoose screen recognition criteria which inadequatelydescribe the screen state of the Integration Object whenthe connection is to be released. The checkin screen isthe last screen of the connect macro if one exists, or thefirst screen of the data macro (of the first IntegrationObject in a chain, if chained).

HPS5142 License limit has been reached. Nofurther connections are allowed. Formore information on licensingenablement, see the InfoCenter at ({0}).

Explanation: The number of licenses in use hasexceeded the number of licenses purchased. No furtherconnections are allowed.

User response: Be sure you have properly enabled theHATS runtime licenses and have enabled the correctnumber of licenses. If so, contact your supportorganization to purchase additional HATS licenses.


HPS5143 An Exception was caught when creatingan HOD screen for connection {0}. Thisprobably is caused by an environmentconfiguration problem. Perhaps the XWindow System DISPLAY variable isnot set, or RAWT is not configuredproperly.

Explanation: A problem occurred while trying to drawa Display Terminal. This is likely an environmentconfiguration problem.


gslicense.htm

gslicense.htm

User response: Verify that WebSphere ApplicationServer is configured properly for displaying graphics.For Windows platforms, you must select Allow serviceto interact with desktop in Windows Services panel.For other graphics environments, refer to HATS User'sand Administrator's Guide for instructions.

HPS5145 Cannot connect to the host using SSL. Ifimporting a certificate is required forthis SSL connection, make sure that ithas been imported from the Telnetserver into a valid PKCS12 file, and thatthe password (SSLP12Password) andpath (SSLP12FilePath) for the PKCS12file are specified correctly. The sessionproperties are:{0}

Explanation: The application was unable to connect tothe host using SSL. Possible causes may be that thecertificate is incorrect, the application was unable tolocate and open the keystore file, or the connectioncould not be made to the host (Telnet server) specifiedin the connection specification file. The {0} lists thesession properties.

User response: Check that the application can load thecertificate. Verify that the path specified for the PKCS12file points to a valid PKCS12 file accessible by theapplication. Verify that the password specified is correctfor the PKCS12 file. Also check that the correctcertificate is available in the keystore file.

In addition to the checks suggested above, examine thehost name and port number for the Telnet server that isin the connection specification file for this application.Check that TCP/IP connectivity to the Telnet server isavailable using the ping program. If that succeeds, thenuse an emulator for the right terminal type and check ifthe Telnet server is operational.

HAT5551 Parameter {0} is missing

Explanation: Expected parameter {0} was not found.

User response: Verify your command parameters andretry.

HAT5552 Conflicting parameters {0}

Explanation: An incorrect combination of parameterswas passed.

User response: Remove one of the parameters asshown by {0} and retry. To see usage syntax , type aquestion mark (?) as the command's first parameter. Forexample: apply ?

HAT5556 File has been opened {0}

Explanation: File {0} has been opened for reading orwriting.

User response: No user action required.

HAT5557 File not found {0}

Explanation: File {0} is missing or cannot be openedfor reading.

User response: If the name of file {0} contains theCAPAR or APAR number, check to see if you are tryingto restore or commit a fix that has not been applied.You cannot restore or commit a fix that has not beenapplied. Make sure file {0} exists and allows read/writepermission by the logged-on user.

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

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

User response: Obtain the correct fix for your productas shown by {1} and retry.

HAT5562 {0} fix information for {1} was not foundin {2}

Explanation: The fix {0} you are trying to applycannot be found in fix file {2}. Fix names are casesensitive. For example, you will see this message if youtry to apply, restore or commit a fix named Jr12345 andthe actual fix is named JR12345. You will also see thismessage if the APAR or CAPAR does not contain fixinformation for your platform {1}.

User response: Correct the fix name case and retry orobtain the correct fix for your platform as shown by {1}and retry.

HAT5563 {0} cannot be restored because it has notbeen applied

Explanation: You are trying to restore a fix that hasnot been applied. You can only restore fixes that havebeen applied and not committed.

User response: Apply and test fix {0} before trying torestore it.

HAT5564 {0} cannot be committed because it hasnot been applied

Explanation: You are trying to commit a fix that hasnot been applied. You can only commit fixes that havebeen applied.

User response: Apply and test fix {0} before trying tocommit it.

Messages 17

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

Explanation: The fix you are trying to apply cannot beapplied to the installed product because the type is notAPAR or CAPAR.

User response: Obtain the correct fix for your productand retry.

HAT5571 CAPAR {0} was applied on {1}

Explanation: This is an informational message toconfirm CAPAR {0} has been applied to the installedproduct.


HAT5572 CAPAR {0} was committed on {1}

Explanation: This is an informational message toconfirm CAPAR {0} has been committed to the installedproduct.


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

Explanation: The report command is unable todetermine whether the fix is applied or committed.

User response: Contact the IBM Software SupportCenter if the problem persists.

HAT5574 APAR {0} was applied on {1}

Explanation: This is an informational message toconfirm APAR {0} has been applied to the installedproduct.


HAT5575 APAR {0} was committed on {1}

Explanation: This is an informational message toconfirm APAR {0} has been committed to the installedproduct.


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

Explanation: The report command is unable todetermine whether the fix is applied or committed.

User response: Contact the IBM Software SupportCenter if the problem persists.

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

Explanation: This is an informational message toconfirm the fix is valid for your platform {1}.


HAT5578 APAR {0} for build {1} will be applied tobuild {2}

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


HAT5579 CAPAR {0} for build {1} will be appliedto build {2}

Explanation: This is an informational message toconfirm CAPAR {0} will be applied to your product'sbuild level {2}. CAPARs change the build level. Yourproduct's build level will be {1} after the CAPAR isapplied.


HAT5581 Source file {0} is available

Explanation: This is an informational message toconfirm file {0} is available and has read permission.


HAT5582 There are no CAPARs applied to thiscomponent.

Explanation: This is an informational message toconfirm there are no CAPARs applied to your product.


HAT5583 There are no APARs applied to thiscomponent.

Explanation: This is an informational message toconfirm there are no APARs applied to your product.


HAT5584 There are no CAPARs or APARs appliedto this component

Explanation: This is an informational message toconfirm there are no CAPARs or APARs applied toyour product.


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

Explanation: This is an informational message statingthe current build level is {1} for component {0}.



HAT5586 Report for {0} version {1}

Explanation: This is an informational message. Themessages following this message refer to product {0}version {1}.


HAT5587 CAPAR {0} includes fix {1}

Explanation: This is an informational message statingfix {1} is included in applied CAPAR {0}.


HAT5588 APAR {0} includes fix {1}

Explanation: This is an informational message statingfix {1} is included in applied APAR {0}.


HAT5589 {0} is not applied or committed

Explanation: This is an informational message statingfix {0} is not applied or committed.


HAT5590 {0} is included in fix {1}

Explanation: This is an informational message statingfix {0} is included in applied fix {1}.


HAT5591 {0} cannot be applied because it wassuperseded by {1}

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

User response: No user action required. You do notneed fix {0}.

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

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

User response: If you are satisfied that fix {1} isworking correctly, commit fix {1} and then apply fix {0}.

HAT5593 {0} cannot be applied because it requiresprereq fix {1}

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

User response: Apply, test and commit fix {1}.

HAT5594 {0} has already been applied

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

User response: Run the report command to see a listof applied and committed fixes.

HAT5595 Write permission is denied for target {0}.

Explanation: File {0} cannot be opened for writing orthe file does not exist.

User response: Make sure file {0} exists and allowswrite permission by the logged-on user.

HAT5596 Source file {0} is missing

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

User response: Make sure file {0} exists and allowsread/write permission by the logged-on user.

HAT5597 Read permission is denied for {0}

Explanation: File {0} cannot be opened for reading orthe file does not exist.

User response: Make sure file {0} exists and allowsread permission by the logged-on user.

HAT5598 Checking source file {0}

Explanation: This is an informational message statingfile {0} is being tested for read permissions.


HAT5599 {0} - Checking applied fix {1}

Explanation: This is an informational message statingfix {0} is being checked to see if it is already installed.


HAT5602 Checking target file {0}

Explanation: This is an informational message statingfile {0} is being tested for write permissions.


HAT5603 Target file {0} is missing and cannot bereplaced

Explanation: File {0} cannot be opened for writing orthe file does not exist.

User response: Make sure file {0} exists and allowsread/write permission by the logged-on user.

Messages 19

HAT5604 Directory {0} is missing

Explanation: The APAR or CAPAR is trying to run aprocess from directory {0} and directory {0} is missing.

User response: Create directory {0} and retry theapply command. Contact the IBM Software SupportCenter if the problem persists.

HAT5605 Existing file {0} will be replaced

Explanation: This is an informational message statingexpected missing file {0} already exists. File {0} will bebacked up. If you have to restore the fix, file {0} will berestored.


HAT5606 Target file {0} is missing and cannot beremoved

Explanation: The APAR or CAPAR is trying to removefile {0} but file {0} does not exist. The file might havebeen manually removed or removed as part of aprevious fix.


HAT5607 Target file {0} is missing and cannot berestored

Explanation: File {0} does not exist and cannot berestored. No files will be restored and the applied fix isstill installed.

User response: Use the report command to see a listof applied fixes. Because you are trying to restore a fix,you can create a dummy file {0} and rerun the restorecommand. See the fixes.log file for the fully qualifiedfile name.

HAT5611 File {0} was previously backed up

Explanation: File {0} is shared between twocomponents and was previously backed up whilebacking up the same fix to the other shared component.


HAT5612 Checking backup file {0}

Explanation: This is an informational message statingfile {0} is being tested for read permissions.


HAT5613 Backup file {0} is missing

Explanation: File {0} was backed up and is expectedto exist but does not exist. This could be the result ofinsufficient disk space.

User response: Check to make sure your system is notlow on disk space.

HAT5614 Target file {0} is missing and will becreated.

Explanation: File {0} was expected to exist but doesnot exist. The apply command will create file {0}. Afterthe fix is applied, and you use the restore command toremove the fix, the restore command will delete file {0}.


HAT5615 Write access is permitted for target {0}.

Explanation: This is an informational message toconfirm file {0} is available and has write permission.


HAT5616 Read access is permitted for {0}

Explanation: This is an informational message toconfirm file {0} is available and has read permission.


HAT5617 Source file {0}

Explanation: This is an informational message statingthe name of a source file. Fixes.log will contain thefully qualified file name.


HAT5618 Target file {0}

Explanation: This is an informational message statingthe name of a target file. Fixes.log will contain the fullyqualified file name.


HAT5619 Creating directory {0}

Explanation: This is an informational message statingdirectory {0} does not exist and will be created.


HAT5620 Existing target file {0} will be backed up

Explanation: This is an informational message statingproduct file {0} will be saved. The restore commandwill use the saved file to restore the product to theprevious state. The commit command will delete thesaved file {0}.


HAT5621 Backing up file {0}

Explanation: This is an informational messageconfirming file {0} is being saved. The restore commandwill use the saved file to restore the product to theprevious state. The commit command will delete the


saved file {0}. Fixes.log will contain the fully qualifiedfile name.


HAT5623 Applying new file {0}

Explanation: This is an informational messageconfirming file {0} is being applied. Fixes.log willcontain the fully qualified file name.


HAT5624 Removing old file {0}

Explanation: This is an informational messageconfirming file {0} is being deleted. The restorecommand will use a saved copy of file {0} to restore theproduct to the previous state. Fixes.log will contain thefully qualified file name.


HAT5627 File {0} was previously restored

Explanation: File {0} is shared between twocomponents and was previously restored whilerestoring the same fix to the other shared component.


HAT5628 Restoring original file {0}

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


HAT5629 {0} cannot be restored because it hasbeen committed

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

User response: Use the report command to see a listof applied and committed fixes. Reevaluate the need toremove fix {0}. If you really need to remove the fix youwill have to reinstall the product. Reinstalling theproduct will remove all CAPARs and APARs.

HAT5630 {0} cannot be restored because it has notbeen applied

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


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

Explanation: The fix you have applied may require aconcurrent fix or fixes to product {1}.

User response: Review the readme file packaged withthe CAPAR or APAR. The readme file name will besame name as the fix number with the .TXT extension.For example, the readme file for fix JR12345 is namedJR12345.txt.

HAT5641 {0} has already been committed

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


HAT5642 {0} must be committed before a new fixcan be applied

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

User response: Run the report command to see a listof applied and committed fixes. Test and commit fix{0}.

HAT5643 {0} for build {1} cannot be applied tobuild {2}

Explanation: The fix you are trying to apply cannot beapplied to the installed product. The most commonreason for this is you are trying to apply an APAR thatis not required for your product build level. Forexample, you applied and committed CAPAR-1followed by CAPAR-2 and then tried to apply an APARthat was written for CAPAR-1.


HAT5644 {0} for build {1} cannot be applied tobuild {2}

Explanation: The fix you are trying to apply cannot beapplied to the installed product. The most commonreason for this is you are trying to apply a CAPAR thatis not required for your product build level. Forexample, you applied and committed CAPAR-1followed by CAPAR-3 and then tried to applyCAPAR-2. Another reason for this message is you aretrying to apply a CAPAR to a beta version of theproduct.


Messages 21

HAT5645 The request was successful

Explanation: The apply, commit or restore commandwas able to successfully complete your request. If therequest was apply, the fix has been applied and isready to be tested. If the request was commit, the fixhas been made permanent. If the request was restore,the fix has been removed.


HAT5646 The request was not successful

Explanation: The apply, commit or restore commandwas not able to successfully complete your request.

User response: See the previous messages for moreinformation. See messages HAT5648 and HAT5649.

HAT5647 The final return code is {0}

Explanation: This is an informational message used bythe IBM Software Support Center.


HAT5648 Log file {0} contains 1 additionalmessage.

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

User response: Review the log file {0} for theadditional message.

HAT5649 Log file {0} contains {1} additionalmessages.

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

User response: Review the log file {0} for additionalmessages.

HAT5653 System Information {0} {1}

Explanation: This is an informational message used bythe IBM Software Support Center.


HAT5654 Today is {0}

Explanation: This is an informational messageshowing the time and date.


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

Explanation: No user action required.

User response: Contact the IBM Software SupportCenter.

HAT5656 Unable to construct the XML image {0}



HAT5657 Unexpected xerces exception {0}



HAT5658 Unexpected exception {0}

Explanation: An unexpected exception occurred. Nouser action required.


HAT5659 Internal program problem {0}



HAT5700 User Parameter {0} {1}

Explanation: This is an informational message listingthe APAR installation utility parameter number {0} andvalue {1}.


HAT5703 Checking {0} root {1}

Explanation: This is an informational message statingthat the APAR installation utility will try to locate {0} at{1}.


HAT5704 Unable to locate {0} root {1}

Explanation: The APAR Installation utility was unableto locate {0} at {1}.

User response: Ensure that HATS Toolkit is installedat {1}. If the problem persists, contact the IBM SoftwareSupport Center.

HAT5705 {0} root located {1}

Explanation: This is an information message statingthat {0} was successfully located at {1}.



HAT5706 {0} product not found

Explanation: Product {0} was not found. The onlyvalid product name is HATS Toolkit.

User response: Correct the spelling of {0} and retrythe command.

HAT5708 {0} not found.

Explanation: A required file {0} was not found.

User response: Ensure that Rational SDP is installedcorrectly. If the problem persists, contact the IBMSoftware Support Center.

HAT5710 {0} located {1}

Explanation: This is an informational message statingthat {0} was located at {1}.


HAT5711 Fix file not found {0}

Explanation: The file containing the fix was notfound. Fix file names are the same as the fix number.For example, fix JR12345 is contained in a file namedJR12345.jar. When specifying fix names, do not specifythe .jar extension. Fix files must exist in the servicedirectory of the com.ibm.hats plugin

User response: Correct the spelling of {0} and retrythe command or copy fix file {0}.jar to the servicedirectory of the com.ibm.hats plugin and retry thecommand.

HAT5712 Unknown action {0}

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


HAT5713 Extracting fix {0} ...

Explanation: This is an informational message statingfix {0} is being extracted from file {0}.jar.


HAT5714 Extracting the fix control file {0}

Explanation: This is an informational message statingfile {0}.xml is being extracted from file {0}.jar.


HAT5715 Fix control file {0} is missing

Explanation: Fix control file {0}.xml is missing fromfile {0}.jar. The most common reason for this error is amismatch in fix name letter case. Fix names are casesensitive.

User response: Correct the spelling of {0} and retry.

HAT5716 Extracting the fix data files

Explanation: This is an informational messageconfirming the specified fix was located in the fix fileand updated product files are being extracted.


HAT5745 {0} can not be applied until previousmaintenance is applied to your HATSprojects. See the readme for informationon applying maintenance to your HATSprojects.

Explanation: Previous maintenance must be applied toyour HATS projects before {0} can be applied.

User response: Apply the previous maintenance toyour HATS projects. To apply maintenance to yourHATS projects you must open Rational SDP and switchto the HATS perspective. This will automatically applymaintenance to your HATS projects. If there is aproblem applying maintenance to your HATS projects,contact the IBM Software Support Center.

HPS5747E Unable to copy applicationconfiguration files

Explanation: This message appears with messageHPS5604. An application directory WebSphereApplication Server configuration list contains no files.


HPS5748E Security Exception {0}

Explanation: A security exception occurred whiletrying to create a directory.

User response: Ensure you are authorized to createdirectories on this server. Check WebSphere ApplicationServer security settings.

HPS5750E Arguments are {0}

Explanation: This message appears with messageHPS5749E and lists the arguments that were received.

User response: Contact IBM service and provide theargument information.

Messages 23

HPS5901 Exception occurred attempting to createor activate the HATS EJB

Explanation: An exception occurred while attemptingto create or activate the HATS EJB.

User response: Check the following related messagesor refer to the message log for other messages thatprovide more details about this problem.

HPS5902 Exception occurred while processing theEJB Properties input argument

Explanation: An exception occurred while the HATSEJB was processing the input argument received froman EJB Access bean.


HPS5903 Exception occurred while processing theEJB Helper object

Explanation: An exception occurred while the HATSEJB was processing the Helper object name receivedfrom an EJB Access bean.

User response: Check the following related messagesor refer to the message log for other messages thatprovide more details about this problem. Check the EJB.jar file to verify that the Integration Object Helper classexists.

HPS5904 Exception occurred invoking the EJBHelper object

Explanation: An exception occurred when the HATSEJB invoked the Helper object to process the EJB Accessbean request.


HPS5905 Exception occurred attempting to invokeConnMgr to cleanup a connection

Explanation: An exception occurred when the HATSEJB attempted to clean up the connection assigned tothe processing of an Integration Object chain.


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

Explanation: The EJB Access bean was unable tolocate or connect to the HATS EJB with the specifiedJNDI_NAME.

User response: Check the following related messagesfor additional detail on the problem. Verify that theHPubEJB2_Reference, JNDI_NAME andPROVIDER_URL of the HATS EJB are correct, andmodify the .war module's deployment descriptor orAccess bean .jar .properties file with the correct values.Verify that the module containing the HATS EJB isinstalled and started on the target application serverwith the same JNDI name; correct if necessary.

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

Explanation: An Integration Object chain is beingprocessed and the EJB Access bean is unable to retrievethe handle of the HATS EJB or the key used to accessthe connection for the chain.

User response: Check the following related messagesfor additional detail on the problem. If this EJB AccessBean is being processed by a servlet or JSP, see theExplanation and User Action for message HPS5035 onpage 8 for possible causes. If this EJB Access bean isbeing processed from a Java program, verify that theprogram is setting the accessHandle and hPubLinkKeyproperties prior to invoking the middle or lastIntegration Objects in the chain. Refer to the HATSProgrammer's Guide for information on hPubLinkKey.

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

Explanation: An exception occurred during an attemptto retrieve the EJB object for an Integration Objectchain.

User response: Retry the request. If this problempersists, turn on all WebSphere Application Servertraces if the EJB Access bean is running in a WebSphereApplication Server environment, and try to re-createthe condition. Contact IBM service and provide thetrace information.

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

Explanation: An exception occurred while processingthe execution method of the HATS EJB.

User response: Check the following related messagesfor additional detail on the problem.

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

Explanation: An exception occurred while removingan instance of the HATS EJB.

User response: Check the following related messagesfor additional detail on the problem. If the followingmessages indicate the remove failed because the EJBhad timed out, then this is an informational message. Ifthis problem persists and the messages indicate ajava.rmi.RemoteException occurred, turn on theWebSphere 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 attemptto get a handle for the HATS EJB object.


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

Explanation: An Integration Object chain is beingprocessed and an error occurred with the linkKeypreventing further processing of the chain.


HPS6002 Conn exception while releasing sessionto the Session Manager

Explanation: A connection resource could not beappropriately freed. This may cause resources toaccumulate and therefore degrade performance.

User response: Use a resource-usage monitoring toolto check memory, threads, and handle usage. UseHATS Administration to disconnect unusedconnections. Increasing use of these resources indicatesthe server may run out of resources. Check precedingerror messages for more information.

HPS6003 Unable to acquire connection from theSession Manager

Explanation: A connection to the data resource couldnot be acquired. This could mean either that the dataresource is inactive or unreachable, or that the pool hasbeen exhausted.

User response: Examine the message log for othermessages that should give more details about thisproblem.

HPS6004 Exception while invoking a property'sread method

Explanation: An exception occurred when trying toaccess a routine that returns the value of a programvariable.

User response: Contact application vendor if problempersists.

HPS6005 Internal processing error

Explanation: An unexpected error occurred duringprogram execution. One of the following conditionscould have occurred:

v The hPubStartType in the Integration Objectcontained an unexpected value.

v The runtime could not find the macro specified bythe Integration Object.

v An unexpected error occurred during macro play.


HPS6006 Introspection exception

Explanation: An Exception occurred while theIntegration Object was performing internalintrospection.


HPS6007 Connection Link Key is null whentrying to acquire a chained non-webconnection

Explanation: A chain of Integration Objects isattempting to run, and the identification of thissequence has been lost.

User response: Ensure that you have retrievedhPubLinkKey from the first Integration Object in thechain, and set it properly for all subsequent IntegrationObjects in the chain. If the request continues to fail,contact the application vendor.

HPS6008 Connection Link Key is null whentrying to release a chained non-webconnection

Explanation: A sequence of Integration Objects isattempting to run, and the identification of thissequence has been lost.

User response: Ensure that you have retrievedhPubLinkKey from the first Integration Object in thechain, and set it properly for all subsequent IntegrationObjects in the chain. If the request continues to fail,contact the application vendor.

HPS6009 Unexpected exception: {exception text}

Explanation: An unexpected exception has occurredduring execution of the Integration Object. Theexception text is included in the message.

User response: Correct the error identified in theexception text, then retry your request. If you do notknow how to correct the error, contact the applicationvendor.

Messages 25

HPS6100 Unable to acquire session from theSession Manager

Explanation: A connection to the data source, using aconfigured pool or connection, could not be established.This could mean either that the data source is inactiveor unreachable, or that the pool has been exhausted.


HPS6101 Internal HOD macro processing error

Explanation: An error occurred during execution ofthe host macro. The host macro is a step-by-step,predefined interaction between the terminal connectionand the host.

User response: Examine the message log for othermessages that should give more details about thisproblem. Typically, the failing macro screen iscontained in the log. Examine the screen to determinewhether the macro needs to be modified. Perhaps anew screen has been added to the host application, orsomething has changed on the host screen that is beingused as screen recognition criteria. Contact theapplication vendor if the problem persists.

HPS6102 Internal macro processing error,extraction coordinates out of bounds

Explanation: An error occurred during execution ofthe host macro. An attempt was made to extract datafrom the terminal screen, but the terminal screencoordinates of this data are not defined within thisterminal screen.

User response: Examine the failing screen containedin the log. Use it determine whether the macro needs tobe modified. Contact the application vendor if theproblem persists.

HPS6103 Internal macro processing error, macroempty

Explanation: An error occurred during execution ofthe host macro. The host macro that was to be executedwas either not found, or was empty.

User response:

1. Check whether the macro file is empty. If it is, goback to HATS Toolkit and attempt to recover orrecord the macro again.

2. If the problem persists, contact IBM service.

HPS6105 Received unexpected interruptedexception while waiting

Explanation: The synchronization logic of theapplication received an unexpected error.


HPS6106 Unable to communicate with theSession Manager

Explanation: The application was not able to establishcommunications with the program that is responsiblefor maintaining connections to the data sources.


HPS6107 Illegal access exception while invokinga property's read method



HPS6108 Invocation target exception whileinvoking a property's read method



HPS6109 Exception occurred, cannot retrievecurrent screen

Explanation: An exception occurred while attemptingto gather information about a prior error condition.

User response: This message can be ignored. Examinethe message log for messages about the original errorcondition.

HPS6112 Received the following MacroErrorEventwhile playing Host On-Demand macro:{0}

Explanation: Host On-Demand returned the specifiedMacroErrorEvent during while attempting to play amacro.

User response: Examine the MacroErrorEvent todetermine whether the condition is temporary or mustbe resolved by a macro modification. Refer to HostOn-Demand documentation for more details onMacroErrorEvents. If the problem persists, contact IBMservice.


HPS6202 Internal error: Unable to locate readmethod for property

Explanation: An attempt was made to access amethod that returns a value for a user or applicationprogram defined variable. This method does not exist.

User response: The application is in error or aproblem is present in the Java Virtual Machineenvironment. If the problem persists, contact theapplication vendor.

HPS6203 Internal error: Unable to locate markerfor end-of-input-variable in SQLstatement

Explanation: Unable to parse the internally generatedSQL statement.


HPS6204 Internal error: Unable to locate ForSQLread method for property

Explanation: An attempt was made to access amethod that returns a value for a user or applicationprogram defined variable. This method does not exist.


HPS6205 SQL error while opening statement

Explanation: An error was received for the SQL call:createStatement.

User response: Investigate the cause of the SQL error.A more detailed description of the SQL exceptionshould be in message log file.

HPS6209 SQL error while executing SQLstatement: {0}

Explanation: An error was received for the SQL call:executeUpdate.

User response: Investigate the cause of the SQL error.A more detailed description of the SQL exceptionshould be in message log file.

HPS6210 Numeric input values cannot be blank.Enter a value for all numeric inputfields

Explanation: At least one of the entry fields on theWeb page is blank. All numeric fields must have avalue.

User response: Enter a value for all numeric entryfields on the Web page.

HPS7001 Unexpected exception {0}.

Explanation: An unexpected exception {0} has beenlogged during the XML Legacy Gateway (XLGW)session migration process. None of your XLGWsessions were migrated.

User response: Review the text of the exceptioncondition {0}. Correct the problem and rerun themigration utility.

Messages 27

Appendix. Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

© Copyright IBM Corp. 2003, 2013 29

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

Intellectual Property Dept. for Rational SoftwareIBM Corporation5 Technology Park DriveWestford, MA 01886U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

Readers’ Comments — We'd Like to Hear from You

IBM Rational Host Access Transformation ServicesMessagesVersion 9.0

Publication No. SC27-5901-00

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,organization, subject matter, or completeness of this book. The comments you send should pertain to only theinformation in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, yourIBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you. IBM or any other organizations will only usethe personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Submit your comments using one of these channels:v Send your comments to the address on the reverse side of this form.v Send a fax to the following number: 1-800-227-5088 (US and Canada)v Send your comments via email to: [email protected]

If you would like a response from IBM, please fill in the following information:

Name Address

Company or Organization

Phone No. Email address

Readers’ Comments — We'd Like to Hear from YouSC27-5901-00

SC27-5901-00

��Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM CorporationRational Enterprise Modernization UADDepartment 67RA/Building 503 ResearchTriangle Park, NC 27709-9990

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

��

Printed in USA

SC27-5901-00

ibm rational host access transformation services: … an error occurred while processing this...

Documents