Visit our Home Page on the Internet: Host Publisher Support http://www.ibm.com/software/webservers/hostpublisher/support.html ________________________________________________________________________ ________________________________________________________________________ Date: 10/08/2001 Product/Version: Host Publisher V2.2.1 Cumulative APAR JR16477 Platform: Windows, AIX, Solaris, and OS/400 ________________________________________________________________________ This APAR supersedes the following APARs: APAR# JR15233 JR15245 JR15247 JR15359 JR15409 JR15538 JR15575 JR15605 JR15784 JR15816 JR15871 JR15891 JR15893 JR15959 OW49898 JR16086 JR16120 _________________________________________________________________________ PROBLEM(s) FIXED: JR15409: Keystroke actions associated with the global screens are written out to file incorrectly. When an Integration Object which has a Global Screen is saved to the file system, the Global Screen is saved in three separate macro files (X.macro, Xlogon.macro, and Xlogoff.macro). When a Global Screen has an associated action which is a keystroke, the keystroke in truncated to one character (or action key) in the Xlogon.macro file and Xlogoff.macro file, but written out correctly in the X.macro file. For instance, a keystroke of "id[enter]" would be written out to the X.macro file correctly, but would be written out as "i" in the Xlogon.macro file and the Xlogoff.macro file, while a keystroke of "[clear]" would be written out correctly in all three macro files. JR15245: Several problems with typing Korean characters: address exception in Javaw.exe after typing Korean characters address exception in Fontmanager.dll after typing Korean characters the Studio window disappears after typing Korean characters JR15247 (16796): Fix HTTP Session persistence problems JR15538(OW46901): Problem where \ should be / in application transfer from Host Publisher Studio to the Server on OS/400 and OS/390 platforms. JR15359 (JR15317): Protect HttpSessionBindingListener running in a JVM other than the JVM running the Integration Object JR15575: Host Publisher Studio performance issue when loading connection pools. JR15784 (JR15233): Multithread RIO problem (which could happen in high stress situations) This APAR adds the following variables now available to RIO: hPubStartPoolName hPubStartChainName hPubEndChainName HPubScreenState (get only) All of the above variables are read/write except HPubScreenState which is read (get) only. Fix for HPubErrorOccurred that sometimes returned 0 when an error occurred on the server (it should always return 1 when an error occurs). Memory leak if getting "java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key hPubStartPoolName" message in stdout log. Note that you must regenerate the Integration Objects to eliminate the exceptions and therefore eliminate the memory leak. JR15816: Problem creating multiple sessions using the XML Gateway with different LU names JR15871: Changes to Pool Configurations are not reflected in the Connection Pools tree until saving to file system, and restarting Host Access JR15891: Trace enhancements to determine when connections go down during macro execution JR15893: IllegalStateException Exception during HTTP Session invalidation JR15959: IO output button not enabled for defining input source in Studio. JR16011 (JR15233, JR15605, JR15886, JR15714) Problem in a Double Byte Character Set (DBCS) environment ( Japanese, Korean, Simplified Chinese, Traditional Chinese ) experiencing duplicate DBCS characters from your Host Integration Objects. One outward symptom of this problem is duplicated TN3270 or TN5250 DBCS characters on your browser. This APAR includes a series of fixes to fix OIA locking. With this fix Host Publisher does not unlock when the unlock is requested from the client but moves the state of the system to unlock-pending. The actual unlock is performed after an EOR (end-of-record) is received from the server. This allows the screen recognition engine to attempt the recognition process after the entire screen is received on the client. This APAR also fixes a memory leak that occurs when macros have multiple next screens. Macros cannot recognize the host screen by the keyword that consists of multiple DBCS letters . JR16086 (JR16083/JR16054): 0-byte file causes exception which keeps Transfer wizard from displaying If an INPUT statement is missing the TYPE attribute, an exception is generated. The page Hierarchy area is incomplete message during transfer. OW49898: Transfer to OS/390 needs to specify non-default translation table The Host Publisher Studio allows you to specify the ftp CONNECT_COMMAND parameter in the studio.ini. This new parm will be executed after the ftp connection to the host is established. The parameter will except any command that is valid from the FTP command line and it must by syntactically correct according to FTP. For example, CONNECT_COMMAND= SITE SBD=(IBM-1047,ISO8859-1) To use the CONNECT_COMMAND you will need to know many things such as if you are running in a SBCS or DBCS environment, what code page you need, the correct ascii and ebcdic translation tables, etc. Also if the SITE command doesn't work the QUOTE SITE command may be needed. 16359: Log and trace files names can not be changed to include Japanese characters 17479: Problems with Right Alt (AltGr) with non-US keyboards 17793: Fix XML Legacy Gateway fonts and colors for Netscape browsers 18530: Unable to find file names which are parameters or response.encodeURL Parsing pages for anchor tags in preparation for transfer to server does not locate page names which are method parameters such as: a href="<%= response.encodeUrl("buildmenu.jsp") %>" Also, parsing does not ignore lines within comments such as: 18563: Inputs (especially &) not processed correctly in RIO/RIOServlet 18579: Exception when custom bean output method has no property descriptor 18583: Installing the Studio to an alternate character directory, such as "C:\HostPub2.2.1(42301)" causes problems transferring applications to the server 18645: Compiler errors in Integration Object when RIO is selected and data is formatted in a table 18668: Performance problem with transferring large files which currently exist on the server 18674: NullPointerException when running XML Legacy Gateway 18710: XML Legacy Gateway fails to contact host after restarting Host Publisher Server using Host Publisher Admin 18728: The jsp textfield shows condition variable with default value "null" string instead of no default value 18737: Add bi-directional support to TN3270 and TN5250 connections 61923: Submit button on FORM doesn't work in nonchained applications _________________________________________________________________________ KNOWN PROBLEMS: 1. If you receive a Windows 95\98 "Out of Environment Space" message when applying this APAR, you will have to increase the size of the MS-DOS command processor environment. Righ-Click on the MS-DOS icon and select "Properties". On the "MS-DOS Prompt Properties" panel, add /e:2048 to the end of the entry in the "Cmd Line" field. For example: c:\windows\command.com /e:2048 If you continue to receive the "Out of Environment Space" message, increase the value to 4096. For example: c:\windows\command.com /e:4096 After you increase the environment space, apply the APAR from a newly opened window. 2. Before removing Host Publisher, after applying this APAR, you should erase the service directory created following the installation instructions below. 3. The timestamp of the files installed by this APAR is not preserved when JDK 1.1.8 is used. 4) Under OS/400, the timestamp of the files installed by this APAR is corrupted. This problem can be avoided by installing the following before applying this APAR. V4R5 and JDK 1.2 - Install 5769JV1 SF66230 ( Also requires 5769SS1 SF66226 ) V4R5 and JDK 1.3 - Install 5769JV1 SF66229 ( Also requires 5769SS1 SF66226 ) V5R1 and JDK 1.2 - Install 5722SS1 SI01945 V5R1 and JDK 1.3 - Install 5722JV1 SI01944 _________________________________________________________________________ TEST ENVIRONMENT(s): Platform WebSphere Advanced Edition IBM HTTP Server Windows NT / Windows 2000 Server 3.5.4 1.3.12.3 Windows NT / Windows 2000 Server 3.0.2 1.3.6 AIX 4.3.3 3.5.4 1.3.12.3 Solaris 8 3.5.4 1.3.12.3 OS/400 4.5 3.5.4 5769DG1 OS/400 5.1 3.5.4 5722DG1 _________________________________________________________________________ Default Install Directories for Host Publisher AIX /usr/lpp/HostPublisher/ OS/400 /QIBM/ProdData/HostPublisher/ Solaris /opt/HostPublisher/ S/390 /usr/lpp/HostPublisher/ Windows NT, 2000 c:\HostPublisher _________________________________________________________________________ INSTALLATION INSTRUCTIONS This APAR contains a cumulative set of fixes for Host Publisher v2.2.1. In addition, this APAR will install the Host Publisher Software Maintenance Utility. This utility will be used to manage future Host Publisher fixes. After this APAR is installed, refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for additional information about applying Host Publisher software updates. If your computer is running Windows NT or Windows 2000 and you have Host Publisher Server and Host Publisher Studio installed on your computer, you must apply this APAR to both components at the same time. This APAR needs to be applied to BOTH Host Publisher Studio and Host Publisher Server Make sure to stop WebSphere Application Server before applying or restoring this APAR on Host Publisher Server Be aware that the timestamp of the files installed by this APAR is not preserved when JDK 1.1.8 is used The Software Maintenance Utility includes various commands to manage the application and restoration of Host Publisher code fixes. The apply command applies a fix to Host Publisher. Once a fix is applied, you should verify the fix corrected the problem by attempting to recreate the problem. After you verify the fix is working as expected, run the commit command to make the change permanent. The restore command removes an applied fix from Host Publisher. If a fix does not correct a problem or you experience unexpected results, you can remove the fix and restore Host Publisher to the state prior to applying the fix. Once a fix has been restored, you can reapply the fix. Once a fix has been committed, the fix can not be restored. The report command displays the status of all applied or committed fixes. ---------------------------------------------------------------------- HOW TO APPLY JR16477 - Windows ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. Note: Make sure to stop WebSphere Application Server before applying this APAR on Host Publisher Server 1) Change to the Host Publisher installation directory ( Example: cd d:\HostPub ) 2) Change to subdirectory common ( Example: cd common ) 3) Create a new subdirectory under common named service ( Example: mkdir service ) 4) Change to subdirectory service ( Example: cd service ) 5) Copy the JR16477.zip file to the service subdirectory 6) Unzip JR16477.zip 7) If you have Host Publisher Server installed, type: apply JR16477 server 8) If you have Host Publisher Studio installed, type: apply JR16477 studio 9) Message "HPS5645I: The request was successful" indicates JR16477 has been correctly applied. Refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for a complete list of messages and meanings. 10) Replace DefaultErrorPage.jsp with the language-specific DefaultErrorPage.jsp that comes with this APAR: If you have Host Publisher Server installed copy DefaultErrorPage.jsp from hostpub_root\nls\xxx\Server\production\documents where xxx is the language you are using to hostpub_root\server\production\documents If you have Host Publisher Studio installed copy DefaultErrorPage.jsp from hostpub_root\nls\xxx\Studio where xxx is the language you are using to hostpub_root\Studio 11) To verify that the APAR was applied successfully, type: report ---------------------------------------------------------------------- HOW TO APPLY JR16477 - AIX, Solaris ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. Note: Make sure to stop WebSphere Application Server before proceeding. 1) Change to the Host Publisher installation directory ( Example: cd /usr/lpp/HostPublisher ) 2) Change to subdirectory common ( Example: cd common ) 3) Create a new subdirectory under common named service ( Example: mkdir service ) 4) Change to subdirectory service ( Example: cd service ) 5) Using a Windows workstation copy the JR16477.zip file to the service subdirectory and unzip it. 6) Change the apply file permission to execute ( Example: chmod 755 apply.sh ) 7) Type: ./apply.sh JR16477 8) Message "HPS5645I: The request was successful" indicates JR16477 has been correctly applied. Refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for a complete list of messages and meanings. 9) To verify that the APAR was applied successfully, type: ./report.sh ---------------------------------------------------------------------- HOW TO APPLY JR16477 - OS/400 ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. Note: Make sure to stop WebSphere Application Server before proceeding. 1) Enter the QShell Command prompt by typing qsh on the command line. 2) Change to the Host Publisher installation directory ( Example: cd /QIBM/ProdData/HostPublisher ) 3) Change to subdirectory common ( Example: cd common ) 4) Create a new subdirectory under common named service ( Example: mkdir service ) 5) Change to subdirectory service ( Example: cd service ) 5) Using a Windows workstation copy JR16288.zip into the service directory just created and unzip it. 6) From the QShell Command prompt type: sh apply.sh JR16477 7) Message "HPS5645I: The request was successful" indicates JR16477 has been correctly applied. Refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for a complete list of messages and meanings. 8) To verify that the APAR was applied successfully, type: sh report.sh ---------------------------------------------------------------------- HOW TO RESTORE JR16477 - Windows ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. Note: Make sure to stop WebSphere Application Server before restoring this APAR on Host Publisher Server 1) Change to the Host Publisher installation directory ( Example: cd d:\HostPub ) 2) Change to subdirectory common ( Example: cd common ) 3) Change to subdirectory service ( Example: cd service ) 4) If you have Host Publisher Server installed, type: restore JR16477 server 5) If you have Host Publisher Studio installed, type: restore JR16477 studio 6) Message "HPS5645I: The request was successful" indicates JR16477 has been correctly restored. Refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for a complete list of messages and meanings. 7) Replace DefaultErrorPage.jsp with the language-specific DefaultErrorPage.jsp that was restored by the restore command If you have Host Publisher Server installed copy DefaultErrorPage.jsp from hostpub_root\nls\xxx\Server\production\documents where xxx is the language you are using to hostpub_root\server\production\documents If you have Host Publisher Studio installed copy DefaultErrorPage.jsp from hostpub_root\nls\xxx\Studio where xxx is the language you are using to hostpub_root\Studio 8) To verify that the system was restored successfully, type: report ---------------------------------------------------------------------- HOW TO RESTORE JR16477 - AIX, Solaris ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. Note: Make sure to stop WebSphere Application Server before proceeding. 1) Change to the Host Publisher installation directory ( Example: cd /usr/lpp/HostPublisher ) 2) Change to subdirectory common ( Example: cd common ) 3) Change to subdirectory service ( Example: cd service ) 4) Type: ./restore.sh JR16477 5) Message "HPS5645I: The request was successful" indicates JR16477 has been correctly restored. Refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for a complete list of messages and meanings. 6) To verify that the system was restored successfully, type: ./report.sh ---------------------------------------------------------------------- HOW TO RESTORE JR16477 - OS/400 ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. Note: Make sure to stop WebSphere Application Server before proceeding. 1) Enter the QShell Command prompt by typing qsh on the command line. 2) Change to the Host Publisher installation directory ( Example: cd /QIBM/ProdData/HostPublisher) 3) Change to subdirectory common ( Example: cd common ) 4) Change to subdirectory service ( Example: cd service ) 5) Type: sh restore.sh JR16477 6) Message "HPS5645I: The request was successful" indicates JR16477 has been correctly restored. Refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for a complete list of messages and meanings. 7) To verify that the system was restored successfully, type: sh report.sh ---------------------------------------------------------------------- HOW TO COMMIT JR16477 - Windows ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. 1) Change to the Host Publisher installation directory ( Example: cd d:\HostPub ) 2) Change to subdirectory common ( Example: cd common ) 3) Change to subdirectory service ( Example: cd service ) 4) If you have Host Publisher Server installed, type: commit JR16477 server 5) If you have Host Publisher Studio installed, type: commit JR16477 studio 6) Message "HPS5645I: The request was successful" indicates JR16477 has been correctly committed. Refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for a complete list of messages and meanings. ---------------------------------------------------------------------- HOW TO COMMIT JR16477 - AIX, Solaris ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. 1) Change to the Host Publisher installation directory ( Example: cd /usr/lpp/HostPublisher ) 2) Change to subdirectory common ( Example: cd common ) 3) Change to subdirectory service ( Example: cd service ) 4) Type: ./commit.sh JR16477 5) Message "HPS5645I: The request was successful" indicates JR16477 has been correctly committed. Refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for a complete list of messages and meanings. ---------------------------------------------------------------------- HOW TO COMMIT JR16477 - OS/400 ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. 1) Enter the QShell Command prompt by typing qsh on the command line. 2) Change to the Host Publisher installation directory ( Example: cd /QIBM/ProdData/HostPublisher) 3) Change to subdirectory common ( Example: cd common ) 4) Change to subdirectory service ( Example: cd service ) 5) Type: sh commit.sh JR16477 6) Message "HPS5645I: The request was successful" indicates JR16477 has been correctly committed. Refer to the Service Guide ( serviceGuide.html located in the hostpub_root/common/service directory ) for a complete list of messages and meanings. ---------------------------------------------------------------------- FILES INCLUDED This APAR fix contains the following files: SHIPPED (fn.ft) File Destination JR16477.jar - contains changed files JR16477.txt - readme file apply.bat - installation utility for Windows apply.sh - installation utility for AIX, Solaris, OS/400 habeansnlv.jar - %hp_install_dir%/common HpRte.jar - %hp_install_dir%/common HPubCommon.jar - %hp_install_dir%/common product.xml - %hp_install_dir%/Server RIOServlet.jar - %hp_install_dir%/Server/production/beans xmlLegacyGWS.jar - %hp_install_dir%/Server/production/beans lxgwfunctions.js - %hp_install_dir%/Server/production/documents/xmlLegacyGateway DefaultErrorPage.jsp - %hp_install_dir%/nls/tr_TR/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/zh_TW/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/ko_KR/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/de_DE/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/ja_JP/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/pt_BR/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/it_IT/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/fr_FR/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/es_ES/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/en_US/Server/production/documents DefaultErrorPage.jsp - %hp_install_dir%/nls/zh_CN/Server/production/documents HostAccess.jar - %hp_install_dir%/Studio/HostAccess.jar HPStudioCommon.jar - %hp_install_dir%/Studio/HPStudioCommon.jar product.xml - %hp_install_dir%/Studio/product.xml RIO.jar - %hp_install_dir%/Studio/RIO.jar sm.zip - %hp_install_dir%/Studio/sm.zip WebBridge.jar - %hp_install_dir%/Studio/WebBridge.jar commit.bat - %hp_install_dir%/Common/service commit.sh - %hp_install_dir%/Common/service hppdtool.bat - %hp_install_dir%/Common/service hppdtool.sh - %hp_install_dir%/Common/service hppd400.sh - %hp_install_dir%/Common/service report.bat - %hp_install_dir%/Common/service report.sh - %hp_install_dir%/Common/service restore.bat - %hp_install_dir%/Common/service restore.sh - %hp_install_dir%/Common/service *.class - %hp_install_dir%/Common/service/com/ibm/fixutility/install *.properties - %hp_install_dir%/Common/service/com/ibm/fixutility/install xerces.jar - %hp_install_dir%/Common/service/com/ibm/fixutility/install TECHNICAL SUPPORT For technical assistance or questions, please call the IBM SUPPORT CENTER for your Country. For example in the USA call: 1-800-237-5511 COPYRIGHT INFORMATION Copyright International Business Machines Corp. 1999, 2001. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, transmitted, or translated into any language without the express written consent of the publisher: International Business Machines Corp. P.O. Box 12195 Research Triangle Park, NC 27709-2195 USA Note to U.S. Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. LIMIT OF LIABILITY License to the contained APAR fixes is conditioned upon the recipient holding a license to the prerequisite product. The license terms and conditions of the APAR fixes are the same as those for the prerequisite product. Please see the product license for specifics.