IBM Support

EHLLAPI With the Access Client Solutions Emulator

Troubleshooting


Problem

This document describes how to use the EHLLAPI programming interface with the emulator provided with the IBM i Access Client Solutions product.

Resolving The Problem

This document describes how to use the EHLLAPI programming interface with the emulator provided with the IBM i Access Client Solutions product.

Applications that were previously written to use industry-standard EHLLAPI and PCSAPI interfaces can also work with the IBM i Access Client Solutions 5250 emulator. Using these interfaces requires some extra setup. This document explains the steps you need to take in order to use EHLLAPI and PCSAPI with IBM i Access Client Solutions (ACS).

Note: Starting at IBM i Access Client Solutions 1.1.8.1 when used with the IBM i Access Client Solutions EHLLAPI Bridge 8.18.316 or later code levels the IBM i Access Client Solutions EHLLAPI environment is now supported in a 64-bit Java runtime.

The support documented here is only supported with IBM i Access Client Solutions (ACS) Version 1.1.6.2 or later.

 

  • - Step 1 – Install the IBM i Access Client Solutions EHLLAPI Enablement Tool

     

     

    The EHLLAPI enablement tool can be downloaded from the IBM i Access Client Solutions Base Package and Update website at the following URL:


    https://www-01.ibm.com/marketing/iwm/iwm/web/preLogin.do?source=swg-ia

     

    Signon with IBM Registered ID, agree to the License Agreement and on the Download page select the ACS EHLLAPI package. Download the tool, and run acshllapi.exe to install it. The installation tool uses Windows Installer technology to place the bridge into a default or user-selected location. The default location is C:\Program Files\IBM\EHLLAPI (C:\Program Files (x86)\IBM\EHLLAPI on 64-bit systems).

    Note: If IBM Personal Communications or IBM i Access for Windows PC5250 is installed on the same PC as IBM i ACS, you need to ensure that the above locations are listed first in the Windows "system" environment variable PATH. If not the ACS 5250 emulator will attempt to bind to the wrong EHLLAPI module, and it will not work.

     

     

     

  • - Step 2 – Start IBM i ACS for PCSAPI, if needed

     

     

    If you plan to use the PCSAPI programming interface to start emulator sessions when IBM i Access Client solutions is not already running, you must take an extra step to ensure the emulator environment is initialized, before attempting to start any sessions using PCSAPI. The way to do this is by launching IBM i Access Client Solutions PCS plugin.

    The following command will start the IBM i ACS PCS Plugin as a background task:

     

    START C:\Users\<userprofile>\IBM\ClientSolutions\Start_Programs\Windows_i386-32\acslaunch_win-32.exe /plugin=pcs

    Note: This example assumes you are running IBM i Access Client Solutions from the default deployment location of C:\Users\<userprofile>\IBM\ClientSolutions directory. Substitute your actual location for the one shown in this example.

    Note:
    IBM i Access Client Solutions 1.1.8.0 and earlier do not support running in 64-bit mode, you must run IBM i ACS in a 32-bit JVM, which if a 32-bit JRE is installed can usually be accomplished by using the 32-bit launch program, even on a 64-bit PC.

    You can now start emulator sessions programmatically through the PCSAPI interface.

     

     

 

Note: The IBM i Access Client Solutions EHLLAPI support is designed, other than the differences mentioned above, to provide comparable specification support as Personal Communications 6.0. You can link to the Personal Communications 6.0 "Introduction to IBM Standard EHLLAPI, IBM Enhanced EHLAPI and WinHLLAPI Programming" document here (Personal Communications 6.0 EHLLAPI).

 

[{"Product":{"code":"SGYQGH","label":"IBM i"},"Business Unit":{"code":"BU009","label":"Systems - Server"},"Component":"Access Client Solutions","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"Version Independent","Edition":""}]

Historical Number

653368666

Document Information

Modified date:
14 December 2018

UID

nas8N1010639