If Your HLLAPI Application Fails

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

• Make sure the HLLAPI application is 32-bit HLLAPI Windows application. 16-bit HLLAPI and DOS HLLAPI applications are not supported.

• Make sure that the current path contains a path to the PassHll.dll.

• The HLLAPI application must be configured to load the correct HLLAPI DLL - PassHll.dll.

• The HLLAPI application must use either the hllapi() or winhllapi() function call.

• 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 reassign the session name in your HLLAPI application or reconfigure the PASSPORT session HLLAPI short name. To reconfigure the PASSPORT session HLLAPI short name do the following:
  
  For PASSPORT PC TO HOST, this is done in the Session Profile – HLLAPI tab.
  
  For PASSPORT WEB TO HOST, your system administrator must do this for you using the PASSPORT WEB TO HOST Administration Configuration Program on the Server.

• Some HLLAPI applications require configuration for specific emulators. As mentioned earlier, try configuring the HLLAPI application for use with the IBM Personal Communications/3270 Software or Attachmate EXTRA!®.

• If you still cannot use the HLLAPI application with PASSPORT, disconnect your current session and configure PASSPORT to run a HLLAPI trace.

To run a HLLAPI trace:

1. Log off your mainframe session.

2. Disconnect the session using the Communication>Disconnect menu command.

3. Select the Communication>Diagnostics menu command.

4. Enable the HLLAPI Trace option, then click on the Connect button to reestablish the connection.

5. Try the HLLAPI application again.

6. Once you reach the point of failure, exit the HLLAPI program and PASSPORT. The file EHTRACE.log, located in the My Documents\Zephyr\Traces folder, contains a trace of all the HLLAPI function calls along with parameters.

7. Copy the file to another directory or rename the file.

Warning: Your trace information will be overwritten if you restart the HLLAPI program!

Note: Look at the EHTRACE.log file with a text editor, such as Notepad or WordPad, and see if there is any HLLAPI communication in the file. If there is no HLLAPI communication in the trace file, you have probably not managed to get the application to talk to the emulator.

If your HLLAPI trace file does show signs of activity, send the file to Rocket Technical Support. A 3270, 5250, VT or Wyse-60 data stream trace taken at the same time will also help.

To send your trace files to Rocket Technical Support:

• First, submit an issue to Rocket technical support at http://www.rocketsoftware.com/support. This ensures that we can track your problem and route it to the correct support technician.

• Next, email the trace file or files along with a detailed description of the problem to passport.support@rocketsoftware.com. Also, email any screen shots or other helpful information.