With Automation Point it's possible to establish a direct MCS console connections to an Open Systems Adapter-Express Integrated console Controller (OSA-ICC) using native protocol support for TN3270E.
This article describes how the OSA-ICC session parameter, Defer Host Disconnect (DHD), impacts Automation Point's MCS console automation when the OSA-ICC server detects a TN3270E client (Automation Point MCS console session) disconnect.
Automation Point
The DHD option is primarily intended for use by z/OS operator console sessions. When DHD is enabled, the OSA-ICC controller defers reporting the console disconnect status to z/OS for a designated period.
If a reconnect is done before the designated period times out, the OSA-ICC controller automatically simulates the 3270 CLEAR key, triggering z/OS to reformat the console screen and to continue sending console messages. This makes it unnecessary for an operator to have to manually vary the MCS console device back to ONLINE status. The DHD option is described in detail in IBM Redbook, OSA-Express Integrated Console Controller Implementation Guide. Or check the IBM Redbooks section
A TN3270E console client disconnect occurs in the following situations:
When an Automation Point MCS console session is disconnected for any of the reasons mentioned above, the OSA-ICC server handles the subsequent reconnect according to the settings configured for the DHD option. Once reconnected, Automation Point resumes MCS console automation (when the console session is in a recognized state), enabling Automation Point MCS session scripts to control the console session.
Upon session reconnect, operator intervention may be necessary to recover the MCS console and restart Automation Point MCS console automation. The following scenarios help you determine how to adjust your site automation, if necessary:
*Note: Be aware that while the Automation Point MCS console session is disconnected, the OSA-ICC controller continues to allow z/OS to direct messages to the MCS console until the deferred disconnect period expires. While disconnected, those messages are not monitored by Automation Point and therefore are not automated.