5250 Connect User’s Guide
78
Instead of calling the Logon Component directly, using (for example) a
Component Action, you will associate the Logon Component with a special
connection resource called a Logon Connection. When your 5250 Terminal
Component executes, it executes via the Logon Connection, which in turn
executes the Logon Component.
Logon, Keep Alive, and Logoff Actions
The Logon Component provides several screen-management capabilities that are
important factors in overall performance. These capabilities are implemented in
terms of Logon, Keep Alive, and Logoff actions:
Logon Actions—These actions navigate through the host environment and
park at a desired launch screen in the host system. The connection is
activated using UserIDs from the pool. The 5250 Terminal components that
subsequently reuse the connection have the performance benefit of already
being at the launch screen and won’t incur the overhead of navigating to the
launch screen as if they had come in under their own new session.
Keep Alive Actions—These actions do two important tasks. First, they
prevent the host from dropping a connection if it is not used within a
standard timeout period defined by the host. Second, these actions must
insure that the connection is always positioned at the “launch screen” in the
host, even after performing the Keep Alive actions needed to prevent the
connection from dropping (the first important task).
Logoff Actions—These actions exit the host environment in a manner you
prescribe for all the connections made by User IDs from the pool, when a
connection is being terminated.
These actions and their meanings will be discussed in greater detail below. For
now, it’s enough to know that these three action groupings are created for you
automatically when you first create a Logon Component. Note the (empty) Logon,
Keep Alive, and Logoff action blocks in the action model shown below: