IBMlogo
IBM eNetwork Communications Server for Windows NT
Host Publisher Feature, Version 6.01
[Next|Previous|Contents]

Host Publisher Hints and Tips

Disconnect

Host Publisher drops the connection to the host after playing the Disconnect macro. Sometimes the session is disconnected before the logoff is completed. The host does not complete the logoff, but leaves the userid in a disconnected state.

There are two ways you can avoid this problem. To decide which to use, find out whether your host sends another screen after processing the logoff, or disconnects the session without sending another screen.

  1. If the host sends another screen after processing the logoff, record a Disconnect macro that waits for the next screen. Recording any screen input on the next screen forces a WaitForScreen() to occur in the Disconnect macro after the logoff.
  2. If the host does not send another screen after processing the logoff, edit the macro to use the waitForConnection() macro command. For example,
    screenDesc.Clear();
    screenDesc.AddCursorPos(20,16);
    ps.WaitForScreen(screenDesc,10000);
    ps.SendKeys("logoff[enter]");
    waitForConnection(ECLConnection.CONNECTION_INACTIVE);
    

    When the Disconnect macro contains the waitForConnection(ECLConnection.CONNECTION_INACTIVE); macro command, Host Publisher waits after playing the Disconnect macro for the host to disconnect the session, allowing the logoff to complete. If the host does not disconnect the session within a short time, Host Publisher disconnects it.


[Next|Previous|Contents]
IBM eNetwork Communications Server for Windows NT
Host Publisher Feature, Version 6.01