Attachmate myEXTRA! Terminal Viewers
Version 3.1


HLLAPI Client Release Notes
November 2002

Introduction

Attachmate Terminal Viewers provides a HLLAPI interface to the Java Viewers to enable you to run an existing Windows-based HLLAPI client application.

For information about the current HLLAPI version of myEXTRA! Terminal Viewers, visit our support website at http://www.supportweb.attachmate.com.


Installation Notes

Supported HLLAPI Interfaces

Interface Component
32-bit Standard EHLLAPI ehlapi32.dll
pcshll32.dll
32-bit WinHLLAPI whlapi32.dll
16-bit Standard EHLLAPI acs3ehap.dll
16-bit WinHLLAPI whllapi.dll
DOS EHLLAPI

Supported Web Browsers

For HLLAPI support, the Terminal Viewers require Microsoft Internet Explorer version 5.0 (or later), with the most recent Java VM upgrade available.

The latest versions of these are available at the following Web sites:

Microsoft Internet Explorer - http://www.microsoft.com/windows/ie
Microsoft Java VM Updates - http://www.microsoft.com/java


Client Installation

Before running any HLLAPI-enabled configurations from the Terminal Viewers, you must install the HLLAPI components needed to run HLLAPI-enabled Terminal Viewers sessions.

To install the HLLAPI Client Components 

  1. On the Terminal Viewers myAccess Links page, select Preferences.
  2. From the Preferences page, click Install HLLAPI Client Components.
  3. From the File Download dialog box, select "Run this program from its current location?", then choose OK.

  4. When the following security warning appears, choose Yes:

    Authenticode signature not found.

    If you choose the "Save this program to disk" option, the message won't appear.

  5. Follow the instructions in the installation wizard.
  6. This setup program copies several files to your computer, and modifies your computer's PATH environment variable.

Note You must re-start your computer after installation is complete.

To use your HLLAPI application with a Terminal Viewers session 

  1. On the myAccess Links page, highlight and click the HLLAPI terminal session name.
  2. The HLLAPI short name appears at the bottom of the display on the status line.

Note Your System Administrator specifies which configurations assigned to you will support HLLAPI, and whether the "session short-name" (used by HLLAPI to identify a particular session) is a specific letter, or the first available letter.

back to top


DOS-Based HLLAPI Applications

If you are using DOS-based HLLAPI applications with Terminal Viewers, additional configuration of your system is necessary. Choose the procedure appropriate to the version of Windows you are using.

Windows NT/2000

The HLLAPI Client Components directory must be part of the system PATH environment variable. To do so, you must edit the config.nt file.

To edit the configuration for Windows NT/2000 

  1. In Notepad, open the config.nt file.
  2. At the end of the file, add the following line:
  3. device=path\hllinit.sys

    ...where path is the HLLAPI Client Components directory. The path must be entered using short directory names, such as:

    c:\MyDire~1\hllinit.sys

    ...instead of:

    c:\MyDirectory\hllinit.sys

  4. To verify that your system is properly configured, at the command prompt, type the following and verify that HLLINIT.SYS is listed in memory:

    mem /c
  5. -or-

    You can also verify that HLLAPI support is enabled if the short session name is visible on the status line.



Windows 98

Make certain that the HLLAPI client components directory is part of the system PATH environment variable. To do so, you must edit the system.ini file.

To edit the configuration for Windows 98 

  1. In Notepad, open the system.ini file.
  2. Under the heading, 386enh, add the following line:
  3. device=path\redir95.vxd

    ...where path is the HLLAPI Client Components directory. The path must be entered using short directory names, as described in the procedure for editing the configuration for Windows NT/2000.

  4. Restart Windows.

Before starting your DOS-HLLAPI application in Windows 98

Once you have edited the configuration and re-started Windows, you must launch the HLL95.exe program before starting your DOS-HLLAPI application.

To launch the HLL95.exe program 

  1. From the HLLAPI Client Components directory, start the HLL95.exe program.
  2. A small icon shaped like a computer monitor appears on the left side of the taskbar.

  3. Launch a Terminal Viewers session.

back to top


Known Issues

Technical Information

Function 104: Query/Set Window Status

Terminal Viewers HLLAPI supports the use of function 104, Query/Set Window Status to show/hide/minimize a session.

For more information on this and other HLLAPI functions, see the Attachmate EHLLAPI Language Reference, which is distributed with the EXTRA! Developer Series API SDK.

Verifying HLLAPI Support

In Microsoft Internet Explorer, in the Java Console, you can verify that HLLAPI support is enabled for a session.

To verify that HLLAPI support is enabled 

  • In the Java Console, enter "t" (to view threads).
  • You should see a thread named HLLAPI-A, HLLAPI-B, and so forth.

    -or-

  • Verify that the short session name is visible on the status line.


WinHLLAPIStartup and WinHLLAPICleanup Functions

In addition to the standard WinHLLAPI entry point, WinHLLAPIStartup and WinHLLAPICleanup functions are supported.


Limitations

Not Supported

Calls Fail when Session is Closed

When you close a session to which a HLLAPI client application is currently connected, Terminal Viewers HLLAPI sessions are released immediately and subsequent HLLAPI calls fail.

Terminal Viewers Session Must be Launched First

It is necessary to launch a HLLAPI-enabled Terminal Viewers session before attempting to use your HLLAPI application. The HLLAPI function, ConnectmyAccess Linkspace, will return 1 (INVALIDPSID) if the requested session has not been opened first.

Session Parameter WRITE Client Threads

Session parameters WRITE_SUPER (default), WRITE_READ, and WRITE_NONE allow only one client thread to be HLLAPI-connected. Parameters SUPER_WRITE and WRITE_WRITE allow multiple client threads to connect to a single session.

back to top


Troubleshooting

Troubleshooting Log

To aid troubleshooting, you can create a log of HLLAPI function calls.

To create a log file 

  1. In the root directory of your C drive, create an empty text file, naming it as follows:

    AttachmateJavaHLLAPITrace.txt

  2. Run your HLLAPI application as usual.
  3. Information about each HLLAPI call is automatically recorded to the file.

Note It is important to remove or delete the log file when logging is no longer desired; otherwise it will continue to grow in size each time you run your HLLAPI applications.

back to top