Release Notes EXTRA! Terminal Viewers
Attachmate EXTRA! Terminal Viewers Version 8 February 2005


This document provides late-breaking information about this release of Attachmate EXTRA! Mainframe Server Edition.

Depending on which components you have installed, one or more of the following readme files addressing component-specific issues may be available.

This file
Contains information about
readme_extra.htm EXTRA! X-treme, which provides access to IBM mainframe, AS/400, VAX/VMS, UNIX, or other asynchronous host applications.
readme_extra_connpak.htm EXTRA! X-treme Connections Pack, which provides additional connection types.
readme_extra_optionpak.htm EXTRA! X-treme Options Pack, which includes tools to provide AS/400 file sharing, API access to 16-bit HLLAPI and APPC applications, additional keyboard drivers, and support for the CASL macro language.
readme_viewers.htm Java-based terminal viewer clients (Java Viewers).
readme_hllapi.htm The HLLAPI interface to the Java Viewers.
readme_termviewers_express.htm Express Java clients, similar to Java Viewers with fewer features and less processing overhead.
readme_termviewers_ax.htm ActiveX-based terminal viewer clients.
readme_mcs.htm Management & Control Services (MCS), a Web-based server console that administrators can use to centrally manage and configure compatible Attachmate products.

Installation Notes

Installing MCS and Management Components with Windows XP SP2

During the installation of MCS or an MCS management component, a Windows security alert may appear one or more times. This alert displays only if you use Windows XP with the Windows XP firewall enabled (as it is by default). You are asked whether you want to continue blocking the program java or javaw. To continue with the installation, choose Unblock.

After you choose Unblock, these programs are logged in the Windows Firewall Exceptions page, and although it is not evident from this page, the entire path to the program is saved. Running either program from the logged location will not display the security alert; however, if you run them from a different location, the alert will display.

Known Issues

Advanced Generation of Host Access IDs

If you use MCS to manage host access IDs, you can omit unique connection data from the client session configuration. This lets you create a single configuration that can be used by multiple clients to establish multiple sessions with a host, rather than having to create a separate configuration for each host connection. The ID Management service now includes Advanced Generation options that let you generate a range of IDs using more complex generation criteria than is available on the New ID page.

Using the Advanced Generation options, you can create a new ID element, and designate the Type (text, counter, hex, or hex counter), Data or Start Value, and Number to Generate (the number of times to increment the value for the element). You can see a list of the ID elements that have been defined, and edit the list by moving selected elements up or down or by deleting elements. The ID elements are combined in the order listed to create IDs.

To access the Advanced Generation options
  1. In the MCS left pane under Services, choose ID Management.

  2. Under ID Management, choose Configure IDs.

  3. In the MCS right pane, in the pool tree, select All IDs, right-click to display the shortcut menu, and then choose New Pool.
    In the MCS right pane, in the pool tree, select an existing pool, right-click to display the shortcut menu, and then choose New ID.

  4. On the New ID page, select the Advanced Generation button.

In the following example for a Matip-ALC host, using the Advanced Generation options, you could create a range of six hexadecimal IDs by specifying four ID elements — two Hex and two Hex Counter.

First Hex 1122, representing the first two bytes of the ID.
Second Hex counter, representing the third byte of the ID, with Start Value of 33 and Number to Generate 2.
Third Hex 44, representing the fourth byte of the ID.
Fourth Hex counter, representing the fifth byte of the ID, with Start Value of 55 and Number to Generate 3.

After clicking Finish, the following IDs would be added to the pool:


Default Security Option in Windows XP SP2 Restricts JavaScript in Help

Windows XP SP2 includes the security option Local Machine Zone Lockdown, which by default restricts JavaScript from running in Internet Explorer. The help for this product uses JavaScript. If you use Internet Explorer, by default, when you attempt to display the help, a message is displayed in the Information bar stating that Internet Explorer has restricted the help from showing active content.

To display the help
  • Click the Information bar, and then click Yes to allow active content.
    Note You must do this each time you view the help. Alternatively, you can lower your security settings to avoid seeing this message. However, this change will apply to all files that include active content, and Microsoft does not recommend this approach. For more information about Local Machine Zone Lockdown, see the Microsoft Web site.

Unable to Connect via 802.2 on a Terminal Server when Running APPN Node as a Service

Microsoft has changed their default security settings for the following operating systems to tighten desktop security: Windows 2003, Windows 2000 Service Pack 4, and Windows XP Service Pack 2. As a result, a client that is running EXTRA! as a restricted user on a Terminal Server will need additional rights to connect via 802.2 when running the APPN node as a service. To provide the necessary rights, in the Local Security Policy, under User Rights Assignment, grant the user rights to create global objects.

Error with IBM z/OS Java v. 1.4 VM

A bug exists in the IBM z/OS Java v. 1.4 virtual machine (JVM) implementation, which prevents proper HTTP-chunked data decoding. HTTP headers are encoded in ASCII, but the JVM is decoding it as IBM-1047 (EBCDIC). This leads to a NumberFormatException when trying to parse the chunk-size header value.

IBM has acknowledged this issue and will address it in their next SR. To install centralized management under JDK v. 1.4.x on USS, you will need to obtain this patch from IBM.

Reassigning File Ownership when Installing in a UNIX Environment

When installing EXTRA! on UNIX while logged in as the root user, you can re-assign file ownership for all Attachmate files to another user. You can choose a user name, other than the default, "extra." If this user does not exist on the system, the installation script will create it for you, and will prompt you for group name, home directory, and password. If you specify a user other than the default, you must specify an existing user account for which a home directory already exists. Assigning files to a system user account such as "nobody" or "other" without an existing home directory will prevent the EXTRA! server from restarting properly.

Using the Attachmate HTTP Engine on UNIX Systems

If you are using the Attachmate HTTP engine on a UNIX system that will receive a high volume of traffic for MCS, you should increase your system's default setting for the number of "files" that can be concurrently opened by a particular process to 1024. This is advisable because UNIX considers a network connection to be a kind of file. Many systems have a default value of 64 or 256 for this setting, which may limit the concurrent connections available to your MCS Server.

To increase the number of files allowed by the Java process in which MCS is running
  1. After the UNIX installation is complete, edit, located in the (InstallDir)/HTTPEngine/bin directory, by adding the following line near the top of the file:

    ulimit -n 1024

  2. Restart the Attachmate HTTP engine.

Terminal Viewers with Windows 98 Second Edition

If problems arise when using Terminal Viewers and Windows 98 Second Edition, please install JDK or JRE v. 1.3.0x before downloading. When a Terminal Viewer is downloaded that requires Java, JRE 1.4.0_01 will be installed automatically. This overlay of JREs allows Terminal Viewers to function correctly in the Windows 98 environment.

UnsupportedEncodingException Cp1386

When a browser accesses the WebSphere v. 4.0 Application Server and it throws an "UnsupportedEncodingException Cp1386" exception, you will need to change the line in <was_root>\properties\ as follows:

From this
GB2312=Cp1386 GB2312=Gb2312

When you restart the Application Server, the problem should go away.

Uninstaller Lists Components Multiple Times

When different components have been installed from different CDs that have common components, such as MCS, the uninstaller dialog box will list these components more than once. The common component(s) will be listed under each main header section. Make sure that all references to a given component are treated the same way (either selected or cleared).