Analyzing the system status

Errors occurring within an MSCF network can be multifaceted. The following commands help to analyze the particular situation and determine the cause of the error.

Information functions (see the "Commands" manual [ 10 (Related publications) ])

Command	Function
SHOW‑MASTER‑CATALOG‑ENTRY SELECT=SHARED	Displays the pubsets currently used as shared pubsets. The information is taken from the local MRSCAT.
SHOW-MSCF-CONFIGURATION	Provides information on the status of the MSCF connections, the MSCF networks, and the reconfiguration entities from the point of view of the local processor, as well as information on the global control parameters.
SHOW-PUBSET-ATTRIBUTES	Displays the current pubset settings with regard to shareability and mastership or master change, which were defined via the SET-PUBSET-ATTRIBUTES command. The information is taken from the SVL of the first pubset volume.
SHOW-PUBSET-PARAMETERS	Displays the preset and currently used operating parameters of the pubset, as well as the occupying tasks. Selection based on shared or XCS pubsets is supported. The command provides information for the error situation "hanging shared pubset occupation". The information is taken from the local MRSCAT.
SHOW-SHARED-PUBSET	Displays the sharer configuration of the individual shared pubsets (from the point of view of the local processor) if the local processor is connected to shared pubset networks. Selection based on shared or XCS pubsets is supported. The information is taken from the local watchdog tables.
SHOW-SUBSYSTEM-STATUS MSCF	In addition to the status of the MSCF subsystem from the point of view of DSSM, this command displays the TSNs of the tasks connected to the subsystem. With MSCF, these are the tasks MSCC, MSCM, MXCM, WDGS und WDWT and the MSCF server tasks.
SHOW-XCS-OCCUPATION	If the local processor is connected to an XCS network, this command is used to determine the local TU tasks that are currently using XCS-wide locks. This command provides information for the error situation "hanging XCS occupation".

Table 1: Command overview of information functions

In the event of disk or connection problems, the following commands may be useful:

Command

Function

SHOW-DISK-STATUS
UNIT=<mnemonic>
    | *VOLUME(VOLUME=<vsn>),
INFORMATION=*SYSTEMS *ALL

(see the "Commands" manual [10 (Related publications)])

The SYSIDs of the processors in a shared pubset network which are entered in the SVL of the pubset are displayed under SYSTEMS.

BCSHOW

(see the manual "openNet Server - BCAM" [13 (Related publications)])

Displays detailed information on the BCAM network on which the MSCF network is based.

BCSHOW APPLICATION=..., SHOW=ROUTE

(see the "openNet Server - BCAM" manual [13 (Related publications)])

For each application, displays the established BCAM connections and their data (e.g. protocol used (TCP/IP, ISO4), MAXTSDU setting). An MSCF connection is made up of four or five BCAM connections, one between each of the following applications:

(local) $MRSAPP $MRSAPP $MRSAPPS $MRSAPP4 $MRSAPP5

(remote) $MRSAPP $MRSAPPS $MRSAPP $MRSAPP4 $MRSAPP5 (optional)

Two routes for the $MRSAPP application and one route each for the $MRSAPPS, $MRSAPP4 and possibly the $MRSAPP5 application are therefore displayed on a processor for each partner, if the MSCF connection is intact (i.e. no recovery is active).
All sharers in the XCS network are connected via the $MCSNLX applications. In an intact XCS network, one route is therefore displayed per partner on each processor for the $MCSNLX application.
The sharers of the XCS network are connected to form a ring via the $MCSNSM applications; for this application, a route is therefore not displayed for each partner.

Table 2: Command overview of information functions for disk and connection problems

Documentation for error diagnosis

The following documentation should be made available for error diagnosis:

• CONSLOG file

• SERSLOG file

• MSCF trace file

• BCAM trace