5250 Connect User’s Guide
84
Logon Component Life Cycle
Each time a User ID is activated from the Logon Connection Pool, an instance of
the Logon Component is created and associated with that User ID. Then the Logon
actions are executed until the desired launch screen is reached. At this point the
5250 Terminal component execution begins. When it is finished another 5250
Terminal component using the same Logon Connection may begin executing,
starting from the same launch screen.
If no other component requests the connection, then the connection-intance enters
an active but free state (an “idle state”) defined by the Inactivity Lifetime and
KeepAlive settings on the Pool Info dialog of the Logon Connection. If the Keep
Alive period (e.g. 2 minutes) is shorter than the Inactivity Lifetime (e.g. 120
minutes), then at the appropriate (2 minute) intervals, the KeepAlive actions will
be executed, preventing a host timeout and dropped connection; and the
KeepAlive Period begins anew.
A Logon Component’s execution lifetime is dependent on the activity of the
Logon Connection that uses it. As long as one entry in the Logon Connection pool
is active, then one instance of the Logon Component will be in memory in a live
state. A Logon Component will go out of scope (cease executing) when the last
remaining pool entry expires due to inactivity. The only other way to stop
execution of a Logon Component is through the 5250 Console on the Server.
About the 5250 Logon Connection
The Logon Connection is not a true connection object like a TN5250 Connection
Resource, but a pointer to a Logon Component (which in turn connects to a host
either through a conventional Connection Resource or yet more intervening
Logon Connection/Logon Component pairs). The Logon Connection
encapsulates information needed to describe a pool of connections. That includes
User IDs and passwords, plus pool settings involving the time interval between
retries on discarded connections, etc. Another function of the Logon Connection
is that it ensures the use of different instances of the same Logon Component for
all the User IDs for which connections are made.
The dialogs you’ll use in setting up a pool of User IDs for a Logon Connection are
shown in the following set of illustrations. Arrows denote the buttons that lead to
continuation dialogs.
