PASSPORT Knowledge Base
HLLAPI

Date Published: October 2, 2003

Date Updated: March 13, 2008

Title

HLLAPI Failure

Product

PASSPORT PC to Host, PASSPORT Web to Host

Emulation Types

TN3270, TN5250, VT, SCO ANSI, Wyse 60

Issue

What to look for if your HLLAPI application fails.

Solution

If you are having trouble with your HLLAPI application, please check the following:

1. Make sure that the current path contains a path to the PASSHLL.DLL. Also, the HLLAPI application must be configured to load the PASSHLL.DLL.
2. The HLLAPI application must be either a 32-bit HLLAPI Windows application.  16-bit or DOS HLLAPI applications are not supported.
3. Make sure that the session short name is correct. By default, PASSPORT assigns sequentially A to session 1 up to Z for session 26. If your HLLAPI application is talking to E and you are running just one session configured as A, there will never be communication between the application and the emulator. Either re-configure the PASSPORT session short name or reassign the session name in your application.
4. Some HLLAPI applications require the configuration and use of specific emulators (Attachmate EXTRA!, IBM Personal Communications (PCOMM), NetManage Rumba, etc.). If PASSPORT is not listed as a pre-configured emulator, you should configure the HLLAPI application for use with the IBM Personal Communications/3270 Software, specify the PASSPORT HLLAPI DLL and proceed with PASSPORT as the terminal emulator. For example, with SAS Connect: OPTIONS SET = VQDLLNAME "PASSHLL.DLL"

More Information

• Migrating from PASSPORT PC to Host

• If you still cannot use the HLLAPI application with PASSPORT, disconnect your current session and configure PASSPORT to run a HLLAPI trace as follows: Running Traces

Keywords

api, hllapi, screen, application, integration, failure, dll, configuration