This file contains information that became available too late for inclusion in the publications or the online help. This file also contains important support information.
Third Party Components' names and license terms are referenced in license.txt, located in the directory where you installed Host On-Demand.
For product documentation, visit the Host On-Demand InfoCenter. For Windows, the Host On-Demand InfoCenter is located at Start > Programs > IBM WebSphere Host On-Demand > InfoCenter.
For the latest information, please visit the US or Japanese Host On-Demand Web site.
For hints and tips and other support, please visit the Host On-Demand support page.
For product brochures, white papers, redbooks, and other documentation, visit the Host On-Demand library.
For a list of APARs fixed in this release, please refer to the apars.txt file located in the root directory of the CD.
To print a complete copy of Planning, Installing, and Configuring Host On-Demand with page numbers and a table of contents, use install.pdf, located on the CD in /doc/xx/doc/install, where xx is your two letter language suffix. You can also open the HTML version, install.html, located on the CD in /doc/xx/doc/install, where xx is your two letter language suffix.
For the most current Smart Card information, see Technotes on the Host On-Demand support page.
The Programmer's Guide for the AS/400 Toolbox for Java is located on the Toolkit CD in the as400 directory. The guide is available in zip files for the following languages: English, Japanese, Korean, Spanish, and Russian.
Host On-Demand customers who use the zSeries platform might want to use the following two tools to remove the ASCII file extension from their Host On-Demand HTML, TXT, JS, PROPS, and PROPERTIES files. Typical customers who might benefit from these tools are those who serve Host On-Demand through IBM WebSphere Application Server.
The first tool is a shell script called hodAscii.sh, which can be found in the Host On-Demand product samples S390 directory, for example, usr/lpp/HOD/hostondemand/lib/samples/zSeries. This script removes the ASCII file extension from all files that are included in the Host On-Demand publish directory and subdirectories. Note that you might need to update your Web server's Pass directives to reflect the changed file extensions. Optionally, this script can also remove the ASCII extension from Deployment Wizard files that are located in a separate user publish directory. The script has an undo feature that allows users to reappend the ASCII extension.
The second tool is an enhancement to the DWunzip-S390 utility, which can be found in the Host On-Demand product samples directory in DWunzipCommandFiles folder. The DWunzip tool unzips a Deployment Wizard zip file, places the files into the appropriate directories, appends the ASCII file extensions, and sets files permissions and ownerships on the files and directories. The enhancement allows you to choose whether or not you want to append the ASCII extension to the files. You can set this option inside the DWunzip-S390 script with an environment variable called ADD_ASCII_EXTENSION.
The CICS function in Host On-Demand can only be used with the CICS Transaction Gateway v5.01 or later.
If you use the Apache 2.0.x Web server, you might experience problems when viewing HTML files provided by Host On-Demand in some languages. If the file does not display correctly, try changing or commenting out the following line in httpd.conf, located in the Web server's conf directory:
When using FTP through an HTTP Proxy, be aware that some HTTP proxies now include a configuration parameter called AllowCONNECT. This parameter lists the ports through which the HTTP Proxy allows outgoing connections when an HTTP CONNECT command is received. When you FTP through an HTTP Proxy, the FTP process uses passive mode. In passive mode, after the initial FTP connection, the FTP process receives a port number from the FTP server. The FTP server wants the client to use this port number when establishing a second connection, the data connection, to the FTP server. If this port number is not in the AllowCONNECT port list in the HTTP Proxy configuration, then the proxy does not allow the second connection to be established with the FTP server. Some FTP servers, as part of their configurations, allow the ports returned to the client to be restricted to a certain range. In this case, you must add all the port numbers within the range to the AllowCONNECT HTTP Proxy directive for the FTP session to connect through the HTTP Proxy.
Bidirectional Edit Options are now available from the Edit > Preferences > Edit menu. See Understanding bidirectional language support for more information.
The following options are now available for 3270 Printer Session and ZipPrint:
When recording a Web Express Logon macro, the checkbox for Field Count may disappear on the Wait Conditions window. To resolve this, either click the words 'Field Count' to make the checkbox reappear or upgrade to IBM JRE Version 1.4.1, which is available on the IBM Software Internet Service Delivery site at http://www6.software.ibm.com/aim/home.html.
The Web Express Logon Reference describes how to deploy a WAR file in a WebSphere Application Server environment. If you are planning to enable Java 2 security in this environment, the Credential Mapper Servlet (CMS) or Host Credential Mapper plug-in may fail to run due to inadequate Java security permissions, which are defined in the was.policy file. This happens because when the WAR file is deployed, WebSphere Application Server uses the default was.policy file instead of the was.policy file supplied with Host On-Demand. To resolve this, do one of the following:
If you use Host On-Demand's Web Express Logon feature with z/OS V1R4 or z/OS V1R5 and Digitial Certificate Access Server (DCAS), and the specified certificates contain an 'empty string value' in the organization unit (OU) field (for example, cn=Tom Jones,ou=,o=IBM,c=US), apply System Secure Socket Layer's APAR OA04226 (UA04423) to avoid an ABEND0C4 when a client attempts to connect.
When using the Sun JRE 1.4.0, you might encounter the following error message when running a Web Express Logon macro for the first time:
If you run the macro again, it should work correctly, and continue to work until you close the 3270 session window.
To avoid this problem, migrate to a later level (1.4.1) of the Sun JRE. You can also use IBM JRE 1.4.0, which you can download from the IBM Host On-Demand Server (HODMain.html).
You can use the following information as a guide for estimating the load capacity of the Host On-Demand 8 Redirector.
To achieve the maximum throughput, you might have to modify the following parameters in the Windows Registry:
Parameter | Description |
MaxUserPort | Controls the maximum port number used when an application requests any available user port from the system. |
KeepAlive | Keeps the Redirector connection alive during a period of inactivity. |
-Xms | Minimum memory parameter for Java. It must be greater than 256 MB. |
-Xmx | Maximum Java heap size. |
When running the Host On-Demand Redirector on a Microsoft Windows server, you should review the following Microsoft Knowledge articles:
The first article describes how to modify the registry entry for MaxUserPort to increase the allocated TCPIP ports. We suggest modifying the existing registry entry or adding the parameter to the registry. The value of this parameter should be 65534.
The second article describes other Microsoft Windows TCPIP parameters. We suggest that you modify the value for KeepAliveTime. The default value for this parameter is two hours; causing the operating system to keep TCP resources for connections that have terminated in use for two hours. If the Host On-Demand client disconnects from the Host On-Demand server for reasons other than logging off from the telnet session, it could take two hours for the Host On-Demand Redirector to close and free up all of the TCP connection resources being used between the Host On-Demand Redirector and Telnet server. Shortening the time from two hours to 30 minutes helps prevent TCP resources from being consumed for two hours by inactive sessions not yet fully closed. Shortening the time forces the operating system to check on connections more frequently so that the TCP protocol stack of Microsoft Windows can quickly detect the closed sessions and free up the resources.
The Java parameters -Xms and -Xmx might require modification if you attempt to load the Host On-Demand server to the maximum connections.
Make the following changes directly in the Windows Registry to update the Java options:
Make sure that you leave a space before -classpath and the additional parameters. For example, on a system with one Gigabyte of memory:
-Xms256M -Xmx768Mwhere -Xms<size> sets the initial Java heap size. Adjust this value based on the total memory on your machine. The minimum value for this parameter should be 256M -Xmx<size> sets the maximum Java heap size. Adjust this value based on the total memory on your machine. The size of this parameter is influenced by the amount of memory you have installed and should be set as large as possible.
Connection type | Recommended number of users |
SSL | 500 |
non-SSL | 1000 |
Connection type | Recommended number of users |
SSL | 200 |
non-SSL | 500 |
Parameter | Description |
ulimit -n | Controls the number of open file descriptors. |
-Xms | Minimum memory parameter for Java. It must be greater than 256 MB. |
Set the parameters in the sample service manager shell script.
Connection type | Recommended number of users |
SSL | 1000 |
non-SSL | 2000 |
Parameter | Description |
ulimit | Controls the number of open file descriptors. |
-Xms | Minimum memory parameter for Java. It must be greater than 256 MB. |
Connection type | Recommended number of users |
non-SSL | 1000 |
On Windows with the Turkish locale, Host On-Demand signed applets run without security permissions with IBM JRE 1.4.0. To avoid this problem, you should install IBM JRE 1.4.1 or Sun JRE 1.4.1. The IBM JRE 1.4.1 is available for download from the service key Web site at http://www6.software.ibm.com/aim/home.html.
If the Wrap option is set to false (the default setting), then the macro runtime searches each row of the rectangular area separately. This method works well when the entire string is contained within one row. For example, if the string is Utility Selection Panel and the rectangular area is (1,1), (24,80), then the macro runtime searches for the string as follows:
In contrast, if the Wrap option is set to true then the macro runtime searches for the string as follows:
If the string you are searching for can wrap from one line of the session window to the next, then you should set the Wrap option to true. Do not confuse this option with the Unwrap attribute of the Extract action, which is based on fields rather than blocks of text. For more information, refer to Unwrap Text option in the Macro Programming Guide.
The following description provides an example in which the Wrap option is set to true.
6 Hardcopy Initiate hardcopy output 7 Transfer Download ISPF Client/Server or Transfer data set 8 Outlist Display, delete, or print held job output 9 Commands Create/change an application command table * Reserved This option reserved for future expansion
In the rows above, the first character of each row is a blank space. For example, in row 14, the the first two characters are ' 6', that is, a blank space followed by the numeral 6. Suppose that you want to set up a String descriptor that checks for the following rectangular block of text on this application screen:
Hardcopy Transfer Outlist Commands Reserved
The steps in setting up the String descriptor for this multi-row block are as follows:
'HardcopyTransferOutlist CommandsReserved'
Notice that in step 3 above the five rows are concatenated as a single string, without any filler characters added (such as a newline or space at the end). However, the string does contain a blank space after 'Outlist' because that blank space does fall within the boundaries of the rectangle.
In May 2001, an efficiency enhancement called Contention Resolution was introduced to the Telnet protocol 3270E. Several bugs persist in its implementation, however; the IETF has not yet issued fixes for all of them.
If you determine that server-side Contention Resolution bugs cause connectivity issues in your Host On-Demand environment, you can now disable Contention Resolution for TN3270E sessions. Set either the following HTML parameter or Session Bean property to a value of false:
HTML parameter (Deployment Wizard Advanced Options window):Name: NegotiateCResolution Value: true; any value other than true is interpreted as falseSession Bean property name (for use with Host Access Toolkit APIs):
Name: negotiateCResolution Value: true or falseThe default value for either parameter or property is true, which enables Contention Resolution.
Stop the Host On-Demand Service Manager on Windows 98 and Windows Millennium before you migrate from an earlier version of the Host On-Demand local client to the Host On-Demand 8 local client.
If the Deployment Wizard is installed on a Simplified Chinese workstation, it is unable to edit HTML files created with the Host On-Demand 8 Deployment Wizard. For more information on the problem, search the Host On-Demand Hints & Tips for Reference Number 1116143.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Other company, product and service names may be trademarks or service marks of others.