If an MSCF connection is overloaded, MSCF may not be able to transfer any more messages to BCAM for transmission to the partner processors. This type of overload can occur sporadically, but should rectify itself again. The internal mechanisms of HIPLEX MSCF can bridge short-term overloads. However, if the bottleneck does not resolve itself, the connection to the respective partner processor can be cleared down as an emergency measure with the STOP-MSCF-CONNECTION command, possibly with FORCED=*YES (see "STOP-MSCF-CONNECTION " (Clear down MSCF connection to partner system)), and can then be re-established using the START-MSCF-CONNECTION command.
The SHOW-MSCF-CONFIGURATION command can be used to determine whether a connection is overloaded as outlined above. In the command output, the column "OVL" (OVERLOADED) indicates whether or not the connection is overloaded:
NN: | Congestion-free transmission |
YN: | Congestion for requests (=jobs from the local processor to the partner processor) |
NY: | Congestion for replies (=responses from the local processor to jobs from the |
YY: | Congestion for requests and replies (i.e. congestion in both directions) or |