Communications Access Methods for SAS/CONNECT and SAS/SHARE Software

Windows: EHLLAPI Access Method

SAS/CONNECT

If you encounter difficulties in establishing a session, SAS/CONNECT provides the following messages to help you troubleshoot the problem.

ERROR: No available HLLAPI session.

The wrong value for the REMOTE= option has been specified. The value for REMOTE= should match the remote host session name.

NOTE:    (11320k) badly formatted
SAS remote screen WARNING: - message received from Host 
ERROR: user-requested abort encountered. 
SASHOST ENDED DUE TO ERROR.

The NOTE and WARNING messages appear on the PC. The ERROR message appears on the remote host. These messages occur after the SIGNON statement if the 3174 controller does not set the file-transfer-aid byte correctly. Option 125 (file transfer aid) must have the digit 6 set to 1 to allow packets to be sent to complete the SIGNON. This problem also occurs with other controllers. Typically, the option is identified on other controllers by a name similar to file-transfer-aid.

Bad 3270 status.  Please reset keyboard.

A problem exists in either the software that you are using (other than SAS/CONNECT) or in VTAM. Add a WAITFOR statement that waits at least 1 second before issuing the TYPE statement that caused the message to occur.

ERROR: Failed to load the HLLAPI DLL module.

During SIGNON with Windows, the module may not load because:

The PATH of the emulator was not specified in the PATH statement in the AUTOEXEC.BAT file. Type the PATH command at a DOS prompt to determine if the emulator is listed. Only one 3270 emulation package should be listed in the PATH, and it should be listed first, if possible.
The HLLAPI interface was not loaded with the emulation package. Look at the documentation for your package to see what steps are necessary to load the HLLAPI interface.
The HLLAPI module name (.DLL) is not included in the default search order.

Chapter Contents
Previous
Next
Top of Page