Multi-System Facility › Recovery from Failures › Cross-system Command Failures

Cross-system Command Failures

A cross-system command can fail for a variety of reasons:

• An MSF system failure
• An MSF session failure
• An excessive number of messages are returned in response to the command
• The command takes an excessive amount of time to complete
• The z/OS (sub)system that will process the command fails

Except for the first two causes, the MSF automatically recovers from cross-system command failures.

In most cases, the command issuer receives a message to show the specific cause of the command failure; for example, session deactivated, VTAM shutdown, excessive output. If the originating OPSRMT command was issued from a TSO CLIST, the return code from OPSRMT also indicates the type of failure.

If possible, the MSF also writes a message to the system log to identify a failing cross-system command.