HLLAPI Shortname Configuration in INFOConnect and EXTRA!

  • 7021718
  • 10-Feb-2011
  • 28-Feb-2020


InfoConnect version 9.1 or higher
Extra! X-treme version 9.2 or higher
Microsoft Windows Vista or later (Windows Server 2008, Windows 7, Windows 8, etc.)


HLLAPI implementation in INFOConnect (IHLAPI) and EXTRA! (EHLLAPI or WinHLLAPI) uses short name values, stored as keys in the Windows Registry.

HLLAPI (High-Level Language Application Programming Interface) is a widely used API that enables Windows applications to communicate with mainframe applications using the HLLAPI support provided by a 3270 or 5250 terminal emulation program, such as EXTRA! or INFOConnect.


HLLAPI Shortnames on Windows 10, 8.1, 8, 7, Vista, or Server 2008, 2012, or 2016, etc.

In INFOConnect and EXTRA! (except EXTRA! on Windows 8 and later – see next section), the HLLAPI Shortname Associations can be either "Unique to each user" (the default) or "Shared among all users."

Unique to each user

If you choose “Unique to each user.” the HLLAPI Shortnames can be accessed in the "Advanced" tab of the "Global Preferences" Options; however, the shortnames must be defined for each of the users that log on to that machine. 

The "Unique to each user" settings are stored in the HKEY_CURRENT_USER hive of the Windows Registry.

Shared among all users

If you choose "Shared among all users," the HLLAPI shortnames can be accessed in the "Advanced" tab of the "Global Preferences" Options, and the shortnames will be the same for all users that log on to the machine.

The "shared among all users" settings are stored in the HKEY_LOCAL_MACHINE hive.

HLLAPI Shortnames in EXTRA! on Windows 8 and Later

Shared HLLAPI session short name definitions are not supported when EXTRA! 9.5.1033 or earlier is installed on Windows 8 or later. Session configuration data for a shared HLLAPI session is stored in a part of the registry that the user cannot change on Windows 8. Shared HLLAPI session shortnames can be entered using the Browse button, but the values are not retained and the next time you open the “Advanced” tab the HLLAPI Shortname Associations will be set to “Unique to each user” and no error messages or warning will appear.

This issue is addressed in Extra! version 9.5.1042 and later, where a shared public file is used instead of the registry, as described in KB 7024463.

For InfoConnect or Extra! version 9.5.1033 and earlier, you can use the following workaround to set the values for a “Shared among all users” configuration:

1. Open Windows Regedit

2. For EXTRA! 9.4 navigate to HKEY_LOCAL_MACHINE\Software\Wow6432Node\Attachmate\EXTRA!\WorkstationUser
    For InfoConnect 9.4 navigate to HKEY_LOCAL_MACHINE\Software\Wow6432Node\Attachmate\Accessory Manager\WorkstationUser

3. Open the ConfiguredSessions key

4. Create a new String value (REG_SZ) key with a number (1,2,3, etc.) for the key name

5. Set the value of the string as follows:  (the string is comma separated)
        First element  - fully qualified path and Host session file (*.EDP) for the HLLAPI shortname association
        Second element - HLLAPI short name (letter a-to-z)
        Third element - number of rows in Host session (includes OIA line)
        Fourth element - number of columns in Host session
        Fifth element - binary-encoded number that represents Host session "state" (typically 2443277)
        Sixth element - typically zero
        Seventh element - typically zero
        EXTRA! 9.4 example:
                C:\Users\<username>\Documents\Micro Focus\EXTRA!\Sessions\Session1.EDP,A,25,80,2443277,0,0
        InfoConnect 9.4 example:
                C:\Users\<username>\Documents\Micro Focus\InfoConnect\Sessions\Session2.EDP,B,25,80,2443277,0,0

The best way to determine the correct comma delimited string to use, is to run EXTRA! 9.x on a Windows 7 machine and take a look at the registry key for the appropriate values.  InfoConnect 9.1 and later versions, under Windows 7, will not allow the user to set the HLLAPI value for “Shared among all users” under Global Preferences from the User Interface.

Once the appropriate registry key values have been determined, then this information can be manually deployed via a Windows *.REG file.

Additional Information

Legacy KB ID

This article was originally published as Attachmate Technical Note 2544.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.