Logon Components,Connections and Connection Pools
81
NOTE: When possible, use the Try/On Error action to trap potential logon errors
that may be recoverable. Otherwise, the UserID trying to establish the failed logon
will be discarded from the pool decreasing the potential pool size. The pool size will
remain smaller until you manually reset the discarded connections using the
exteNd Composer Enterprise Server Console for 5250. See “Managing Pools” on
page -100 for more details.
Keep Alive Actions
The Keep Alive block is where you will place actions that “ping the host” in
whatever way necessary to keep the connection alive so that it can be reused.
Keep Alive actions usually involve sending an AID key, such as <ENTER>, to the
host at some specified interval. However, if after sending the AID key the screen
changes to some screen that is different than the launch screen, you must be sure
to return the Logon Component to the launch screen in the Keep Alive section.
Failure to do so will leave the next component at an incorrect screen, causing it to
fail.
The Pool Info dialog of a Logon Connection (see discussion entitled “Creating a
Logon Connection Using a Pool Connection” below) is where you control how
often the Keep Alive actions will execute. If you specify in your Logon
Connection pool that you would like to keep a free connection active for three
minutes, but the host will normally drop a connection after two minutes of
inactivity, you can specify keyboard actions to take place at 30-second intervals to
let the host know the connection is still active.
