MSF Session Failures

When a session between two MSF systems fails, all communication between the two MSF systems halts.

Any of the following conditions can cause an MSF session failure:

Two things can cause a session failure on the local system:
- MSF system failure on a remote system
- Deactivation of the VTAM application definition of a remote system
Sessions will fail on both systems involved in the session if the communications link between two systems is disrupted (a lost phone connection, a lost satellite link, and so on).

After an MSF session failure:

You cannot issue cross-system commands between the two systems involved in the MSF session.
Unsolicited messages are no longer passed between the two systems.
Any commands that were in progress will be aborted with a message showing that the MSF session was deactivated.
Systems that have defined the session with the RETRY option automatically try to reestablish the session (assuming that both systems involved in the session are still active).

If possible, the MSF writes messages to the system log to identify the commands, messages, or both, that were being processed when a session failed.