Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Loss of connection in an LCS/CCS network

&pagelevel(3)&pagelevel

If the MSCF connection to an LCS/CCS partner fails or is cleared down (messages MCS0014 and MCS0015 are output), the partner is no longer accessible. After the connection has been cleared down with a STOP-MSCF-CONNECTION command or MSCF has been terminated, pubsets imported remotely via the partner are exported  and set to the INACC state. If the connection is lost, the response depends on the ACCESS-FAILURE setting in MRSCAT (see ADD-MASTER-CATALOG-ENTRY command in the "Commands" manual [10]): Pubsets with the ACCESS-FAILURE = *HOLD-JOBS setting (default) are set to the QUIET state, pubsets with ACCESS-FAILURE = *CANCEL-JOBS to the INACC state.
Depending on this, JMS, CJC and catalog accesses to the partner go into a wait state (if the pubset is in the QUIET state) or are rejected (if the pubset is in the INACC state).

When the connection is terminated by a command or when MSCF is terminated (but not if the connection fails), the catalog locks held by the partner are reset on the system.

For further information, see also section “Wait time for reestablishment of MSCF connection” (Connection clear-down/loss in a shared pubset network ).