Attachmate 3270 Terminal Viewer and 3270 Printer
Version 3.1.1


Release Notes
June, 2003

Introduction

Attachmate 3270 Terminal Viewer provides web-based terminal emulation to an IBM 3270 host, as well as the capabilities to print screen data and to cut, copy, and paste data among different applications. Attachmate 3270 Printer provides web-based host printing from an IBM 3270 host.


Known Issues

Browsers

Launching a New Viewer using Netscape 6.2.3 and Sun JVM 1.3.1_02 Closes Existing Viewer.

When you launch a new viewer, it terminates the viewer in the original window. If you want to use multiple terminals or printers, use Layouts to do so.

Feature on Demand Not Supported With Sun Plugin

Feature on demand is not supported using Sun Microsystems Java plugin.

Cache All Features: Run Locally Configuration Update Does Not Check for New Jars/Cabs

The Cache All Features: Run Locally option by default checks the server for updates for any macros or XML configuration changes on startup; this occurs every time the desktop icon is clicked and the session is started. However, any updates made to the jar/cab files on the server will NOT be automatically updated on the local client PC using this mechanism. You must log onto the server (as was done originally) and click the channel (configuration) to update any jar or cab files currently cached on the local client PC.

No Uninstall for Cache All Features: Run Locally

Cache All Features: Run Locally does not have an uninstaller. (On the server, this feature is enabled when the Run Locally option is selected. On the client, this feature is enabled when Cache All Features: Run Locally is selected.) Files must be removed manually. For different client operating systems and browsers the location will vary. The following examples assume the operating system and applications (Netscape) have been installed in the default locations. If necessary, you can adjust for variations in your installation.

If the default, myEXTRA!CacheRunLocal, is not used files may be written to the profile name you created.

Cache All Features: Run Locally Does Not Download Configuration Update from Client Requiring Encryption

Cache All Features: Run Locally checks the server for configuration changes on startup from the local client PC when the desktop icon is clicked. When the session starts on the local client PC, if the server (MCS) is set to require encryption, it will not be able to check for configuration changes.

Switching JVMs Requires Reload of Cached Version of the Viewer

If you decide to switch JVMs (for example, IE to Netscape) after you have downloaded a cached version of the viewer, you must download it again before launching the cached version from Cache All Features: Run Locally. Changing the JVM changes the location of the cached files, and possibly the mechanism for caching those files.

Netscape 4.72 Limitation Using the Cache All Features: Run Locally Option

Using the Cache All Features: Run Locally option with Netscape 4.72, if the server is not available, the viewer may take a few minutes to start up (based upon the operating system's timeout for a socket - for example, on NT it's set to 420 seconds).

A workaround is to edit the configuration's .dat file on the local machine and change check=yes to check=no.

Netscape 6.0 Limitation with Caching Terminal Viewers

The Terminal viewers cannot be loaded into the Netscape 6.0 cache.

Netscape 4.77 and 4.78 Limitation with Saving Settings

Viewer settings cannot be saved using Netscape 4.77 and 4.78 with caching enabled.

Launching Java Viewers Quickly Under Netscape

You can automatically start the Java VM at the same time you start Netscape by appending the -start_java command to the Run command you use to start Netscape. For example, you could modify the properties of your Netscape start icon or shortcut to something like this:

"c:\Program Files\Netscape\Communicator\Program\netscape.exe" -start_java

This will make the Attachmate Terminal Viewers and Printers start up much more quickly.

Netscape Limitation with Local File Browsing

The Netscape Java Virtual Machine (JVM) does not support local file system browsing.

Chinese Characters (DBCS) Cannot be Displayed in Chinese Locale

If Chinese characters cannot be displayed or are not input-capable, set the non-unicode locale in Windows to be consistent with the setting in the viewer.

For example, in Windows XP
 

  1. Open the Control Panel, choose Regional and Language Options, then choose the Advanced tab.
  2. Set Language for Non-Unicode Programs to Chinese (PRC).

For other operating systems, such as Windows NT, the path to the language settings may differ slightly.

Netscape Display of Traditional Chinese Characters

Certain Traditional Chinese characters are not displayed correctly in Netscape 4.72 and 4.51. The characters may be shown as question marks (?), particularly in the frame/group captions on the property pages.

Using Internet Explorer and the CLASSPATH Setting

Internet Explorer uses the CLASSPATH environment variable to search for Java support files. It may find the support files specified in the CLASSPATH before those delivered with the Terminal Viewers. For correct results when using the Terminal Viewers, you should either not set CLASSPATH or you should set it only to directories that you know do not conflict with the Terminal Viewers.

Back to top

The Visual Keyboard

The Default Visual Keyboard (Keyboard Map)

Because the Java VM is unable to determine which model of keyboard you are using, the keyboard map displayed will always appear as the PC 101-key keyboard for English, and the PC 102-key keyboard for other languages.

Ctrl, Alt and Shift Modifier Keys

The Java VM does not support the ability to differentiate between right and left modifer keys. Therefore, the Terminal Viewers only map each key once. In addition, the ALT+GR key will present different key assignments depending on the keyboard language selected.

Back to top

Java Terminals

FTP Command Line Transfer Not Working with MVS/TSO

The FTP Command line program does not currently support get, mget, put or mput commands when transferring files to a mainframe MVS/TSO FTP server.

HAS v2.4 Configuration Migration - Telnet Display Background is White

When you open a migrated v2.4 Telnet configuration, the background appears as white which is the same as the foreground. To resolve the issue, open the configuration, then save it.

Can't Have Spaces in New Macro Names

The new macro filename cannot contain a space.

DBCS Does Not Support 81-column Display Mode

81-column Display Mode adds an 81st column to the display, and uses this to ensure that DBCS characters do not get split between the 80th column of one row, and the first column of the next. DBCS support, in this version of the Terminal Viewers, does not support the 81-column mode.

Repaint Problem in Netscape 4.7 on Windows NT

Terminal Viewers may experience occasional repaint problems when running in Netscape 4.7 on Windows NT.

Keyboard Remapper Redraw Problem in Netscape 4.5

In Netscape 4.5, the words "Loading Keyboard" may appear in the top-left corner of the keyboard remapper dialog box when changing the keyboard language or keyboard type.

Netscape Smart Update Feature Causes Browser Restart when Caching Terminal Viewers

When caching the Terminal Viewers, Netscape will prompt for a browser restart if the Smart Update feature is enabled.

Netscape Quality Feedback Agent Problem Closes All Applets, Including Terminal Viewers

If the Netscape Quality Feedback Agent appears while running the Terminal Viewers in Netscape on Windows, a Dr. Watson error occurs forcing you to close Netscape, which ends your terminal session. Disable the Netscape Quality Feedback Agent to prevent this problem from closing the Terminal Viewers.

Enabling, Then Disabling, Caching May Prevent Viewer Loading

If you cache a viewer, then disable caching, and try to load a different viewer it may not load properly. Clearing your browser's cache before loading the new viewer will prevent this problem.

Local Install: Session Manager May Not Run If Terminal Viewers Have Been Cached

If you have a cached Viewer (from a server download), and try to run the session manager from a local install, it may not load properly. Clearing the cache before running the session manager will prevent this problem.

The following are examples of how to clear the cache in some scenarios. If you are running a different version of a browser, you should be able to follow similar, if not precise, instructions to clear the cache.

High Contrast Setting in Windows' Accessibility Options Causes Text Fields to be Truncated

Closing and reopening the Viewer session fixes the problem.

Blue Cursor in Text Fields when Using Internet Explorer

Some display drivers conflict with the Internet Explorer VM, which results in a blue cursor in text fields that should have a black cursor. Setting your Windows Color Palette to True Color, or the highest (most colors) option available, will typically solve this problem.

Permissions for 3270 File Transfer

When the MCS administrator grants permission to use the File Transfer tool, he or she must also grant the user permission to modify the configuration. If these permissions are not granted, the File Transfer command on the Tools menu, and the File Transfer Settings command on the Options menu, will be unavailable to the user.

3270 IND$FILE File Transfer

Do not use a structured field size larger than 15K with an SSL connection when transferring a file from the PC to host.

Symantec VisualCafe and CLASSPATH Issues

If you have VisualCafe installed on your machine, some components may not appear on the screen due to a conflict in third-party class libraries. To properly run the Attachmate Viewers, all references to Symantec classes in the System CLASSPATH of the computer must be removed.

To remove all references to Symantec classes in the System CLASSPATH of the computer
  1. In Windows, from the Start menu, choose Settings, then Control Panel.

  2. In the Control Panel, click the System icon, then choose the Environment tab.

  3. Locate the CLASSPATH variable (if it exists).

    If there is a CLASSPATH variable for the system, the user must remove all references to any Symantec (VisualCafe) classes (which will be wrapped in JAR or ZIP files).

    The following statement is an example of what must be removed from the CLASSPATH variable:

    C:\VisualCafe\BIN\COMPONENTS\SYMBEANS.JAR;C:\
    VisualCafe\JAVA\LIB\CLASSES.ZIP;C:\VisualCafe\JAVA\
    LIB;C:\VisualCafe\BIN\COMPONENTS\SFC.JAR;C:\
    VisualCafe\JFC\Swingall.jar

  4. Choose the Apply or OK button.

If your web browser is running, you must restart it for the changes to take effect.

Browsers Closing Sessions

In some circumstances, due to Microsoft and Netscape VM limitations, your browser may close a Terminal Viewers display or printer session. For instance, this can happen if you navigate to a different page. If your browser closes a session, the Terminal window may turn gray.

To avoid losing sessions when navigating to a different page
  • From the File menu of your browser, create a new browser window.

When you create a browser window, a new viewer may be created at the same time. If you don't need it, just close the extra viewer.

Changing Focus when a Dialog Box is Open

You cannot switch from one viewer display or printer window to another if there is an open dialog box (for example, an Open Settings dialog box). When a dialog box is open, you must close it before switching to a different viewer window.

Auto Reconnect Feature

After you log off from a session, the Terminal Viewers may be configured to reconnect automatically to the mainframe. The Terminal Viewers' attempt to reconnect could slow the performance of the Attachmate SNA Gateway if the Gateway runs out of resources.

To turn the Auto Reconnect feature off
  1. From the Options menu, choose Connection Settings.

  2. In the Connection Settings dialog box, on the General page, clear the Auto Reconnect on Host Disconnect check box.

Fixing Window Appearance Problems

In some circumstances, you may encounter these window appearance problems:

These problems do not affect your session to the host and can easily be corrected.

To fix window appearance problems
  • For a display session, either re-size the window slightly, or toggle the toolbar on/off.

    -or-

  • For a printer session, toggle the toolbar on/off.

Runtime Error Using IE v. 4.0 or v. 5.0 with VM v. 5.0.0.3165

When loading the Terminal Viewers Help in MS Internet Explorer v. 4.0 or v. 5.0 with VM v. 5.0.0.3165, a runtime error occurs. You can fix this by updating your VM.

Terminal Viewers Applications on a Multi-Processor Computer

Multi-thread Terminal Viewers applications may stop responding when running on a multi-processor computer. However, the same application will run without problems on a single processor computer.

More information is available at the following Web site:

Microsoft Technologies for Java: http://support.microsoft.com/support/java/default.asp

Display Limitations

If you start a session and the screen appears gray, you need to restart the session.

The Terminal Viewers perform automatic 2/4 Color mode switching.

Print Screen Font Size

Printing a large screen may cut off some text if it extends beyond the page boundaries. For example, printing to an HP4Si on 8-1/2 x 11 paper, you can use up to a 14-point font in portrait mode, and up to an 18-point font in landscape mode before text is cropped.

3270 File Transfer with Host Code Pages

When using 3270 File Transfer, use "INDFILE" as the host alias when using the ANSI(1252) PC Code Page with the English UK Euro (1146) Host Code Page. The dollar sign ($) does not translate to the same character on the English UK Euro (1146) Host Code Page.

Back to top

Java Printers

Viewer Printer and Display Host Code Pages Must Match to Print DBCS Characters

To print the Double Byte Character Set (DBCS) characters for Far Eastern language fonts properly, you will need to change several settings so that the host code pages match in printer and display sessions.

To match host code page settings for DBCS LU1 and LU3 printing
  1. Open a printer session.

  2. From the Options menu, choose Printer Settings.

  3. In the Printer Settings dialog box, choose the Translations tab.

  4. Under Host Code Page, select the name of the host code page specified in your display session.

    In the display session, refer to the Display Settings dialog box, on the Host Code Page tab, to find the selected host code page name.

  5. Under PC Code Page, select a character display code compatible with the host code page selection.

  6. Click OK.

Narrow Margins May Cause Text to be Cut Off

If your printer's non-printable area exceeds the margins you've specified, your text may get cut off.

Text-Only Printing Produces Error with PostScript Driver

You may see a PostScript error when using the text-only option with PostScript drivers. Text-only printing works fine with a non-PostScript driver.

Changing Paper Size to A4

Changing paper size from 8-1/2 x 11 to A4 will not take effect unless the paper size is also changed in the print dialog box opened by your operating system.

Changing Page Orientation to Landscape

Changing page orientation from portrait to landscape will not take effect unless the page orientation is also changed in the print dialog box opened by your operating system.

Code Page Used when Printing to a Printer

The Terminal Viewers Printers always use Unicode (code page 1200) when printing to a printer regardless of the configured PC code page.

Terminal Viewers Printer Device and Driver Name

The Terminal Viewers Printer device name is always shown as "Terminal Viewers Printer." There is no way for a Java applet to determine the actual printer device name. This is also true for the driver name.

Active Desktop and Printing

If you are using Windows NT and have installed the Active Desktop, you will have problems with Terminal Viewers printing. With the Active Desktop, neither the Terminal Viewers Printer nor the Print Screen feature of the Terminal Viewers will work. A "blue screen" error will occur, after which you will have to restore the Active Desktop settings. To resolve this problem, you must completely uninstall Internet Explorer and reinstall it without the Active Desktop option.

Note Terminal Viewers printing and the Print Screen feature will work with the Active Desktop if it is used under Windows 98.

More information on Active Desktop limitations is available from the following URL:

http://support.microsoft.com/support/kb/articles/q175/3/79.asp

Printer Session Advanced Settings

Under Netscape v. 4.51 or 4.61, or IE with JVM 3167 or later, on the Advanced page of the Printer Settings dialog box, there are several items under the LU1 and LU3 columns that are not enabled but look as though you can select them.

Canceling a Print Job

You cannot cancel a print job in this release—the Cancel Print Job option is not supported.

Holding a Print Job

Currently, if you choose Hold while a large print job is printing, whatever data has been buffered by the printer will still print. Any pending data will be in a held state. Clicking Resume will send the remaining data to the printer.

Incorrect Print-out with Large System Fonts

If you have set your system font size to Large Fonts, a print job will print scaled to a smaller size with invalid right and bottom margins. If you change your system font size to Small Fonts, the print job will appear properly.

Back to top



  Attachmate