Visit our Home Page on the Internet: Host Publisher Support http://www.ibm.com/software/webservers/hostpublisher/support.html ________________________________________________________________________ ________________________________________________________________________ Cumulative APAR JR17402 Date: 19 September 2002 Product/Version: Host Publisher V3.5 APAR JR17402 Platform: Windows, AIX, Solaris, and OS/400 ________________________________________________________________________ This APAR requires the following APARs: none ________________________________________________________________________ This APAR supersedes the following APARs: APAR# JR17344 JR17324 JR17227 JR17135 JR17119 JR16930 JR16927 JR16923 JR16898 JR16886 JR16885 JR16827 JR16728 JR16511 JR16295 JR16288 JR16185 JR16056 JR16055 _________________________________________________________________________ PROBLEM(s) FIXED: JR17344 XML Gateway 5250 screen with single input field is not processed correctly. JR17324 Wrong user id displayed in the iSeries Access for Web banner. JR17227 This APAR includes a new habeansnlv.jar file with two fixes. 1 - Default behavior is to replace SO/SI in extracted data with SBCS blank. If SO/SI is automatically added when field is input, extra spaces are added. Add a option to omit SO/SI from extracted data. To use the option, you must edit the .connspec file and add omitSOSI=true between and . For example, ... ... omitSOSI=true ... ... 2 - Extracted DBCS spaces or blanks were being replaced with SBCS spaces. The code was changed so that extracted DBCS spaces are not changed. JR17135 Studio - Out of memory condition due to recursively loading page and checking for dependents in priming publish directory for transfer. JR17119 Chained application fails with error HPS5103 when an attempt is made to use a connection that has been recovered and returned to the connection pool. The connection was recovered because the maxbusytimer had expired. JR16923 MACRO_ACTIONS_SAME_THREAD value being set to null in .connspec file because it is not needed anymore. It should be removed when connections containing this value are edited. JR16930 When trying to read the User's Guide and the Readme from Host Publisher Server Administration via https (secure sockets), the user gets an error message. The code was hard-coded to use only http. JR16898 If your parameter string for RIO is too long to be used with Get, you need to use Post. To do this, invoke the setDoPost method passing it a parameter of true. The problem is: your invocation will not succeed because your invocation will be redirected with a Get and your original parameters truncated. Most of the time RIOServlet will throw a "Integration Object not found", or "invalid Integration Object", or "no Integration Object is specified", since the name of the Integration Object that gets sent to the RIOServlet usually will be truncated when the input is too large. Limitation: If you apply this APAR JR16898, session affinity is not supported for cases where you use Post with RIO. You cannot vertically or horizontally clone your application server and use chained applications with RIO if you are using Post JR16827 If you attempt to put an input field into a global screen, the Integration Object won't compile. JR16728: Host Access would not allow Connection Information modifications. Non-USASCII characters in the tag of a .connspec file were not being read properly. Remember the .connspec file is UTF8-encoded, and should not be edited or viewed with a non-UTF8 editor. JR16886: Application deployment fails with error HPS5005 when the application does not contain a JSP and the application has already been deployed once. JR16295: When transferring a Host Publisher application from Studio to Server, if there are multiple user lists, only the passwords of the first user list are encrypted or scrambled. The passwords of the remaining user lists are transferred in plain text, even if the user requested that they be encrypted. JR16185: Using the Host Access Macro Editor can cause the integration object creation to fail. Using the Host Access Macro Editor to make changes to the Data Macro containing two or more extracts with the same name causes the integration object creation will fail. JR16511: Color masking incorrect. JR16056: This APAR fixes the following problems: Integration Object property with name of 'value' does not work with ejb support (18729) PropertyVetoException when we try to create a VT session in Host Access (18717) NullPointerException when opening open an existing I.O. which has the symmetricSwapEnabled variable and the numericSwapEnabled variable set in the ConnSpec (18717) ConnSpec properties are not passed to the HOD terminal when creating a new IO that uses a new Pool, but shares an existing Connection Configuration (18688) Symmetric and numeric swapping not loaded from connspec (18675) Maximum number of connections in pool not updated (18647) Bidi visual session not created when textTypeDisp=VISUAL_DISP is set in the .connspec file for the integration object (18609) Problem transferring application to server when studio installed to alternate character directory such as "C:\HostPub3.5(42301)" (18603) Back & Next mixes up regions in CompTwoRegs (18684) JR16055: Arabic characters problem with XML Legacy Gateway When editing a file on the vm and saving it , all arabic characters are displayed as garbage. When saved in the file they are also saved as garbage. 61923: Submit button on FORM doesn't work in non chained applications 22924 Compile error in jsp for sess variable not found 19073: If Host Access or Database Access is launched from Host Publisher Studio before the Transfer to Server wizard is invoked, the Transfer to Server wizard doesn't display the Security panel for applications which contain user lists. As a result, the user is not given the opportunity to encrypt passwords in user lists. 18993: When "Create Remote Integration Objects" is checked in the Studio, the message "Failed to create Integration Objects" may appear when certain names are picked for input and output variables. In this case, the Remote Integration Object Samples are not created correctly. 18934: Extract in global screens are lost if the macro editor is used 18888: Change HP Admin Security to not require uid pw at start Remove server startup from the list of protected actions when WebSphere Global Security is on. That is, use of Global Security will no longer require that a userid and password be provided when the server is starting, regardless of whether the server is auto- starting as the result of WebSphere start-up or starting as the result of administrator action in Host Pub Admin. 18866: The .connspec file is saved with null values causing HostAccess to not start correctly because of the corrupted .connspec files 18780: Password entry field incorrect when level 2 password is set 18725: Problems of mixed bidi-numerals characters 18721: Session properties, symmetricswapenabled and numericswapenabled, are not default when creating a new integration object for Arabic after opening previously created integration object. 18712: Use all the properties specified in the connspec to initialize the Terminal. Host Access does not use all the properties specified in the connspec file when initializing the HOD Terminal object. 18704: New XML session does not use the LU or Pool Name field 18695: 0-byte file causes exception which keeps Transfer wizard from displaying If an INPUT statement is missing the TYPE attribute, an exception is generated Page Hierarchy area is incomplete message during transfer 18690, 18694, 18638: Add screen reverse support to XML Legacy Gateway. The document hpbidi.html (located in the hostpub_root/SDK/Bidi) contains instructions for developers who are preparing Host Publisher applications that include Hebrew and Arabic data. It also provides the information necessary to add the bidirectional tags and directives to the JavaServer Pages (JSPs) generated by the Host Publisher Studio application. The JavaBean bidibean.jar (located in the hostpub_root/SDK/Bidi) in some cases is the only way to have correct BIDI text when this text must be passed from an HTML form, which is implicit, to the host as Visual text. 18632: "Invalid Condition" error replaying ELF application in Studio The problem occurs when an action in the HOD macro is executed before a custom action completes 18557: Multiple quotes in a macro reduced to single quotes 17606: HOD macro parser throws NULL pointer exception when editing macro in Hostaccess _________________________________________________________________________ INSTALLATION INSTRUCTIONS FOR APAR JR17402 This APAR has to be applied to Host Publisher Studio and Server. Follow the instructions below to install APAR JR17402 on Host Publisher Studio and Host Publisher Server. _________________________________________________________________________ KNOWN PROBLEMS: 1. If you receive a Windows 98 "Out of Environment Space" message when applying this APAR, you will have to increase the size of the MS-DOS command processor environment. Right-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 ENVIRONMENTs: Platform WebSphere Advanced Edition IBM HTTP Server -------------- ---------------------- ---------------- Windows NT / Windows 2000 Server 3.5.6 1.3.19.x AIX 4.3.3 3.5.6 1.3.19.x Solaris 8 3.5.6 1.3.19.x AS/400 OS/400 V5R1 3.5.4, 3.5.6 5769DG1 _________________________________________________________________________ Default Install Directories for Host Publisher AIX /usr/lpp/HostPublisher/ OS/400 /QIBM/ProdData/HostPublisher/ Solaris /opt/HostPublisher/ Windows NT, 2000 c:\HostPublisher _________________________________________________________________________ INSTALLATION INSTRUCTIONS The Software Maintenance Utility includes various commands to manage the application and restoration of Host Publisher code fixes. The commands are case sensitive on all platforms. 1. 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. 2. The commit command makes the change permanent. Run this command after you verify the fix is working as expected. 3. 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. 4. The report command displays the status of all applied or committed fixes. ---------------------------------------------------------------------- HOW TO APPLY APAR JR17402 - Windows 98, Windows NT, Windows 2000 ---------------------------------------------------------------------- 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) If the subdirectory named service does not exist under the directory common, create a new subdirectory under common named service ( Example: mkdir service ) 4) Change to subdirectory service ( Example: cd service ) 5) Copy the JR17402.zip file to the service subdirectory 6) Unzip JR17402.zip 7) To apply JR17402 to Host Publisher Server: A) Stop WebSphere Application Server B) From the \common\service directory type: apply JR17402 server C) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly applied. Refer to the Host Publisher product documentation for a complete list of messages and meanings. 8) To apply JR17402 to Host Publisher Studio: A) Exit any open Studio components. B) From the \common\service directory type: apply JR17402 studio C) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly applied. Refer to the Host Publisher product documentation for a complete list of messages and meanings 9) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly applied. Refer to the Service Guide ( serviceGuide.html located in the service directory ) for a complete list of messages and meanings. 10) To verify that the APAR was applied successfully, type: report 11) Change to the Host Publisher installation directory ( Example: cd d:\HostPub ) 12) Copy existing file HostPubWAS.bat to HostPubWASexp.bat ( Example: copy HostPubWAS.bat HostPubWASexp.bat ) 13) Use notepad to edit newly created file HostPubWASexp.bat and change "-import" to "-export". ---------------------------------------------------------------------- HOW TO APPLY APAR JR17402 - 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) Create a new subdirectory under common named service ( Example: mkdir service ) 4) Change to subdirectory service ( Example: cd service ) 5) Copy the JR17402.zip file to the service subdirectory 6) Unzip JR17402.zip 7) Stop WebSphere Application Server 8) The script files apply.sh, report.sh, etc. must all have execute permissions. If one or more does not, you can run chmod -R 755 *.sh from the ../common/service directory to give this permission to all the script files. ( Example: from the ../common/service directory, type chmod -R 755 *.sh ) 9) From the service subdirectory, type: sh apply.sh JR17402 10) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly applied. Refer to the Service Guide ( serviceGuide.html located in the service directory ) for a complete list of messages and meanings. 11) To verify that the APAR was applied successfully, type: ./report.sh ---------------------------------------------------------------------- HOW TO APPLY APAR JR17402 - OS/400 ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. Note: Make sure your userid has QSECOFR or equivalent authority before executing the next steps. 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) If the subdirectory named service does not exist under the directory common, create a new subdirectory under common named service ( Example: mkdir service ) 5) Using a Windows workstation copy JR17402.zip into the service directory and unzip it. 6) From the QShell Command prompt change to subdirectory service ( Example: cd service ) 7) Stop WebSphere Application Server 8) From service subdirectory, type: sh apply.sh JR17402 9) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly applied. Refer to the Service Guide ( serviceGuide.html located in the service directory ) for a complete list of messages and meanings. 9) To verify that the APAR was applied successfully, type: sh report.sh ---------------------------------------------------------------------- HOW TO RESTORE APAR JR17402 - Windows 98, Windows NT, Windows 2000 ---------------------------------------------------------------------- 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) To remove JR17402 from Host Publisher Server: A) Stop WebSphere Application Server B) From the \common\service directory type: restore JR17402 server C) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly restored. Refer to the Host Publisher product documentation for a complete list of messages and meanings. 5) To remove JR17402 from Host Publisher Studio: A) Exit any open Studio components. B) From the \common\service directory type: restore JR17402 studio C) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly restored. Refer to the Host Publisher product documentation for a complete list of messages and meanings 6) To verify that the system was restored successfully, type: report ---------------------------------------------------------------------- HOW TO RESTORE APAR JR17402 - 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) Stop WebSphere Application Server 5) From the service subdirectory, type: sh restore.sh JR17402 6) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly restored. Refer to the Service Guide ( serviceGuide.html located in the service directory ) for a complete list of messages and meanings. 7) To verify that the system was restored successfully, type: ./report.sh ---------------------------------------------------------------------- HOW TO RESTORE APAR JR17402 - OS/400 ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. Note: Make sure your userid has QSECOFR or equivalent authority before executing the next steps. 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) Stop WebSphere Application Server 6) From the service subdirectory, type: sh restore.sh JR17402 7) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly restored. Refer to the Service Guide ( serviceGuide.html located in the service directory ) for a complete list of messages and meanings. 8) To verify that the system was restored successfully, type: sh report.sh ---------------------------------------------------------------------- HOW TO COMMIT APAR JR17402 - Windows 98, Windows NT, Windows 2000 ---------------------------------------------------------------------- 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) To commit an APAR applied to Host Publisher Server, type: commit JR17402 server 5) To commit an APAR applied to Host Publisher Studio, type: commit JR17402 studio 6) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly committed. Refer to the Service Guide ( serviceGuide.html located in the service directory ) for a complete list of messages and meanings. ---------------------------------------------------------------------- HOW TO COMMIT APAR JR17402 - 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 JR17402 5) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly committed. Refer to the Service Guide ( serviceGuide.html located in the service directory ) for a complete list of messages and meanings. ---------------------------------------------------------------------- HOW TO COMMIT APAR JR17402 - OS/400 ---------------------------------------------------------------------- Note: Letter case must be adhered to in the following instructions. Note: Make sure your userid has QSECOFR or equivalent authority before executing the next steps. 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 JR17402 6) Message "HPS5645I: The request was successful" indicates JR17402 has been correctly committed. Refer to the Service Guide ( serviceGuide.html located in the service directory ) for a complete list of messages and meanings. ---------------------------------------------------------------------- FILES INCLUDED This APAR fix contains the following files: SHIPPED (fn.ft) File Destination JR17402.jar - contains changed files JR17402.txt - readme file 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, 2002. 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.