Monitoring the network status

Monitoring job variables (MONJVs) can also be used for monitoring the network status. HIPLEX MSCF uses two classes of MONJVs to display the statuses of shared pubsets on the processor and the statuses of the processor’s MSCF partners. When a shared pubset is imported or an MSCF network is set up to a partner, HIPLEX MSCF automatically makes the MONJVs available. The MONJVs of both classes have a defined name, which contains the name of the pubsets or MSCF processor concerned as a partial string. They are stored under the TSOS ID on the home pubset of the processor.
If a MONJV is not available, it is created when the new status is set with the default attributes. MONJVs that are no longer required are not automatically removed by the system and must therefore be deleted, where necessary, by systems support.

Shared pubset-specific MONJV

There is a shared pubset-specific MONJV called $TSOS.SYS.PVS.<pvsid>.MASTER.CONTROL (pvsid = PVSID of the shared pubset) for each shared pubset on the home pubset of a sharer. This is automatically set up when the pubset is imported if it does not
already exist. The job variable contains information about the status of a shared pubset with the following values:

Value	Meaning	Explanation
$R	(Running)	The shared pubset was imported to the processor or the master change was completed successfully.
$A	(Abort)	The master processor of the shared pubset has crashed.
$C	(Change)	Import of the shared pubset with master change has been started.
$T	(Terminated)	The shared pubset is no longer monitored; it will be or is exported.

This enables systems support to respond appropriately to a crash, for example, using the CJC (see the "Job Variables" manual [9 (Related publications)]).

MONJV for monitoring the network status of an MSCF participant

The MONJV contains the network status of the HIPLEX MSCF partner concerned from the point of view of the local processor. It shows whether the partner is active for the processor or has terminated abnormally. A MONJV is also created for the local processor which contains information as to whether HIPLEX MSCF is active on the processor.

The job variable has the name $TSOS.SYS.MSCF.CONTROL-STATE.<hostname>. It is set at different times for CCS and XCS partners.

In the XCS network, the availability of the XCS functionality is still taken into account which for products based on the XCS network is more important than the setup of an MSCF connection. No MONJV is created for LCS partners.

The job variable contains information about the network status of an XCS/CCS participant with the following values:

Value	Meaning	Explanation
$R	(Running)	The participant has entered the MSCF network. XCS processor, XCS partner: the join reconfiguration was completed. XCS Ready was reached on the local processor. When the local processor enters the XCS, MONJV is set to '$R' for all currently participating partners in addition to the local MONJV. CCS processor: start of HIPLEX MSCF on the processor is complete, the MSCF configuration file has been processed. Shared pubsets can be imported. CCS partner: the partner is the processor’s CCS partner.
$L	(Leaving)	HIPLEX MSCF is terminated on the participant. XCS-/CCS processor, XCS partner: the participant leaves the XCS/CCS network and all imported shared pubsets are exported. CCS partner: is not used.
$A	(Abort)	HIPLEX MSCF is just terminating or has terminated abnormally on the partner. XCS/CCS processor: HIPLEX MSCF is terminating abnormally due to error. XCS/CCS partner: the partner has terminated HIPLEX MSCF abnormally and is removed from the XCS network or the shared pubset networks affected by the local processor by a fail reconfiguration.
$T	(Terminated)	The participant has terminated the MSCF network. XCS/CCS processor: the HIPLEX MSCF configuration management was terminated during termination of HIPLEX MSCF. The termination of the HIPLEX MSCF communication system was initiated. All XCS and CCS partners are set to '$T' at the same time as the processors. XCS/CCS partner: the partner has terminated the MSCF network with the processor. The partner was therefore dismissed from the XCS/CCS network and the shared pubset shared with the processor was exported to the partner. The MSCF connection between the two processors was cleared down.

MONJV for monitoring the MSCF connection to a partner processor

The MONJV provides information from the viewpoint of the local system about the status of the MSCF connection to a partner processor (CCS partner, XCS partner). The MONJV has the name $TSOS.SYS.MSCF.CONNECTION-STATE.<processor-name>.

Where <processor-name> is the processor name of the system to which an MSCF connection is to be set up (see also the description of the relevant operand with the command "START-MSCF-CONNECTION Dynamically establish MSCF connection to partner system").

The connection-specific MONJV is created the first time the MSCF connection concerned is started with the START-MSCF-CONNECTION command, it only exists as of this time.

The job variable shows the status of the MSCF connection concerned with the following values:

Value	Meaning	Explanation
$R	(Running)	An MSCF connection that is completely set up from both sides exists to the relevant partner. Unrestricted use of the MSCF connection is possible.
$S	(Starting)	Setup of an MSCF connection with the associated processor name has been initiated on the local system to the named partner.
$A	(Aborted)	An MSCF connection to the specified partner could not be set up due to an error. The cause of the problem could, for example, be taken from the error code of the message MCS0009; the measures for eliminating the problem that occurred are dependent on this.
$T	(Terminated)	The MSCF connection to the partner concerned was terminated normally by the local system. A new MSCF connection must be set up by the local system to the partner concerned to exchange messages with this partner.
$P	(Partner connect necessary)	The MSCF connection to the partner concerned was only set up from the local system. However, to use the MSCF connection, the connection setup to the local system by the partner is also required.
$W	(Recovery)	MSCF connection monitoring has detected that the relevant partner has not responded to a monitoring message and it is currently performing a recovery of the MSCF connection; MSCF itself shuts down the MSCF connection and an attempt is made to reestablish it. The connection is currently not usable. If the MSCF connection is reestablished, the MONJV is set back to the value "$R", otherwise it is set to "$A".