The exact nature of the output depends on which operand value is selected:
Output with INFORMATION=*LOCAL-ATTRIBUTES
SHOW-MSCF-CONFIGURATION DATE: yyyy-mm-dd, TIME: hh:mm:ss
------------------------------------------------------------------------------
LOCAL ATTRIBUTES
------------------------------------------------------------------------------
HOST NAME = aaaaaaaa HOST START DATE (UTC) = yyyy-mm-dd
PROCESSOR NAME = aaaaaaaa HOST START TIME (UTC) = hh:mm:ss
SYSID = nnn
SYSTEM VERSION = Vmm.na
MSCF VERSION = Vmm.na
SERVER TASK LIMIT = nnn FAILURE DETECTION LIMIT = nnnn
NUMBER OF SERVERS: USER TERM LIMIT = nnnn
CURRENT = nnn LEAVE LIMIT = nnnn
FREE = nnn ABORT LIMIT = nnnn
PROTECTED = kkk RECOVERY START = kkkkkkkkkkk
FADING INTERVAL = nnn REQ RECOVERY START = kkkkkkkkkkk
XCS NAME = aaaaaaaa XCS STATE = kkkkkkkkkkkkk
XCS CREATION DATE (UTC) = yyyy-mm-dd XCS CONFIGURATION = nnnnnnnnnn
XCS CREATION TIME (UTC) = hh:mm:ss HOST PRIORITY = nn
------------------------------------------------------------------------------
SHOW-MSCF-CONFIGURATION END OF DISPLAY
Notes on output
Output is split up into three groups:
The first group identifies the local system, the BS2000 and MSCF software running on it and the current MSCF session.
The second group shows the values currently set for the MSCF configuration for the local system.
The third group identifies the XCS network in which the system is participating and shows the values currently set for the XCS configuration parameters of the local system.
Example
|
|---|
Output with INFORMATION=*REGISTERED-FUNCTIONS
SHOW-MSCF-CONFIGURATION DATE: yyyy-mm-dd, TIME: hh:mm:ss ------------------------------------------------------------------------------ REGISTERED FUNCTIONS ------------------------------------------------------------------------------ NUMBER OF FUNCTIONS = nn ------------------------------------------------------------------------------ FUNCTION NAME = aaa FUNCTION STATE = kkkkkkkkkk FUNCTION TYPE = kkk FUNCTION ERROR = kkkkkkkk FUNCTION ATTRIBUTE = kkkkkkkkk ------------------------------------------------------------------------------ FUNCTION NAME = aaa FUNCTION STATE = kkkkkkkkkk FUNCTION TYPE = kkk FUNCTION ERROR = kkkkkkkk FUNCTION ATTRIBUTE = kkkkkkkkk ------------------------------------------------------------------------------ SHOW-MSCF-CONFIGURATION END OF DISPLAY
Example
|
Output with INFORMATION=*HOSTS
SHOW-MSCF-CONFIGURATION DATE: yyyy-mm-dd, TIME: hh:mm:ss
------------------------------------------------------------------------------
HOSTS
------------------------------------------------------------------------------
NUMBER OF HOSTS = nn
------------------------------------------------------------------------------
HOST NAME = aaaaaaaa HOST START DATE (UTC) = yyyy-mm-dd
PROCESSOR NAME = aaaaaaaa HOST START TIME (UTC) = hh:mm:ss
SYSID = nnn HOST SITE = kkkkkk
SYSTEM VERSION = Vmm.na PARTNER TYPE = kkk
MSCF VERSION = Vmm.na HOST STATE = kkkkkkkkkk
CONTROL CONNECTIONS: CONNECTION TYPE = kkkkkkkkk
(REQUESTED,IN USE) = (l,m) CONNECTION STATE = kkkkkkkkkkkkk
OVERLOADED: PROTECTED = kkk
(REQUEST,REPLY) = (k,k)
REQ CONN RECOVERY START = kkkkkkkkkkk REQ CONTROL GROUP = a
CONN RECOVERY START = kkkkkkkkkkk CONTROL GROUP = a
PARTNERS RECOVERY START = kkkkkkkkkkk CONTROL STATE = kkkkkkkkkkkk
XCS NAME = aaaaaaaa RECONFIGURATION STATE = kkkkkkkkkkkkk
XCS CREATION DATE (UTC) = yyyy-mm-dd JOINING ORDER = nnnnnnnnn
XCS CREATION TIME (UTC) = hh:mm:ss HOST PRIORITY = nn
------------------------------------------------------------------------------
SHOW-MSCF-CONFIGURATION END OF DISPLAY
Note on output
Output is split up into four groups:
The first group identifies the partner system, the BS2000 and MSCF software running on it and its MSCF session, and it shows the network status.
The second group identifies the status of the MSCF connection to the partner.
The third group shows the current settings for partner-specific monitoring parameters and the control status of the partner.
The fourth group shows the current settings for the partner-specific XCS configuration parameters.
Example
|
Output with INFORMATION=*SUMMARY
SHOW-MSCF-CONFIGURATION DATE: yyyy-mm-dd, TIME: hh:mm:ss
------------------------------------------------------------------------------
XCS NAME = aaaaaaaa XCS STATE = kkkkkkkkkkkkk
------------------------------------------------------------------------------
HOSTS:
HOST PROCESSOR MSCF SYS CONN CTRL OVL PART HOST CONTROL RECOVERY
NAME NAME VERS ID STATE CONN TYPE STATE G STATE START P
--------+---------+------+---+------+----+---+----+------+-+---------+------+-
aaaaaaaa aaaaaaaa Vmm.na nnn LOCAL kkk kkkkkk kkkkkk
[ aaaaaaaa kkkkkk ] (1)
aaaaaaaa aaaaaaaa Vmm.na nnn kkkkkk l,m k,k kkk kkkkkk k kkkkkkkkk kkkkkk k
[ aaaaaaaa k kkkkkk ] (1)
. . . . . . . . . . . . .
: : : : : : : : : : : : :
aaaaaaaa aaaaaaaa Vmm.na nnn kkkkkk l,m k,k kkk kkkkkk k kkkkkkkkk kkkkkk k
------------------------------------------------------------------------------
REGISTERED FUNCTIONS:
NAME TYPE ATTRIBUTE STATE ERROR
----+----+---------+----------+--------
aaa kkk kkkkkkkkk kkkkkkkkk kkkkkkkk
. . . . .
: : : : :
aaa kkk kkkkkkkkk kkkkkkkkk kkkkkkkk
------------------------------------------------------------------------------
SHOW-MSCF-CONFIGURATION END OF DISPLAY
Notes on output
The first block or the first line of the section “HOSTS” always describes the local system. The information relating to an MSCF partner comprises identification, connection, network and monitoring data.
The connection is identified by the processor name, i.e. the name under which the partner can be accessed from the system via BCAM. Several connections can exist simultaneously to a partner using different processor names, however, only one MSCF connection can be established between two systems. The systems within the network are identified by the system name (see section “Processor identification”).
The connection is managed by the communication system; the network is managed by configuration management. In the output, the data is combined partner-specifically into logical blocks, provided an MSCF connection exists to the partner. If there is no MSCF connection to the partner, the data is output in two blocks, one containing the connection data and the other containing the network and monitoring data. The connection data is identified through the processor name and the network and monitoring data through the system name.
During the connection recovery the connection status remains as “connected”, which means that the MSCF connection exists. But communication is not possible because the connection is displayed as overloaded. The non-availability of the connection is displayed in the monitoring status and the reconfiguration status of the partner.
- This line is additionally output if the connection parameter RECOVERY-START is currently being changed. It shows the values of the intended change.
Example
|
Key to output
If the SHOW-MSCF-CONFIGURATION command is issued with INFORMATION=
*SUMMARY, the names of the output fields and the field values may be output in a different format (shown in parenthesis in the table below).
Output field | Meaning / Information |
| Maximum period within which the system must have left the network abnormally within an abort reconfiguration.
|
| Status of the MSCF connection:
|
| Connection type:
|
| Beginning of partner monitoring and method of starting recovery measures (current value of partner-specific setting). The partner-specific setting is displayed in the block or line of the relevant partner (INFORMATION=*HOSTS/ *SUMMARY). <kkkkkkkkkkk>(<kkkkkk>):
A recovery measure can only be started automatically if both the general and the partner-specific setting on the partner and on the local system allow it. |
| Number of monitoring connections in the format <l>,<m>:
|
| Partner’s monitoring group, current value:
|
| Partner’s monitoring status:
|
| The value no longer has any meaning and is only output for reasons of compatibility. |
| Maximum crash detection time:
|
| Availability attribute of registered function:
|
| Error state of registered function with respect to MSCF network management:
|
| Name of the registered function. The following functions are defined:
|
| Reconfiguration state of the registered function:
|
| Type of registered function:
|
| Host name of the system
|
| Priority of a system in the XCS network with automatic recovery after a loss of connection. The system with the higher value is removed from the XCS network with ABORT. If both systems have the same priority, the system which entered the XCS network last is removed.
|
| Distinguishes the local entry from the entries of the partner
|
| The time stamp (UTC time) of the MSCF start with start date and start time on the system; used for network status comparison when re-establishing the MSCF connection between two systems.
|
| see “HOST START DATE”
|
| Status of the local system/partner: <nnnnnnnnnn>
|
|
|
| This number defined the order in which sharers join the XCS network.When a join reconfiguration is performed, the number of the current XCS
|
| Maximum period within which the local system must have completed a normal network exit (leave reconfiguration). When this period expires, the normal exit from the network is converted into an abnormal exit (ABORT).
|
MSCF VERSION | MSCF version of system:
|
| Number of functions registered with configuration management for which information is provided. |
| Number of systems for which information is provided:
|
| Number of MSCF server tasks: <nnn>: Current number of MSCF server tasks |
| Overloaded connections:
|
| Partner type:
In the case of INFORMATION=*SUMMARY the connection type is output (see |
| Partner setting with regard to the start method for recovery measures for the local system (combined general and partner-specific setting). The setting is shown in the block or line of the relevant partner.
|
|
|
|
|
PROTECTED | Password protection:
|
| Reconfiguration state:
|
|
|
|
If PARTNER-TYPE=*CCS
|
| Type of recovery measures (general setting):
|
| Method of starting recovery measures. Partner-specific setting last requested with /START-MSCF-CONNECTION or /MODIFY-MSCF-CONNECTION. The requested setting may temporarily differ from the current setting (until the partner has acknowledged the change). In the SUMMARY output, the requested value is only issued in a separate line for the partner if it differs from the current value. See |
| Partner’s control group (setting last requested with /START-MSCF-CONNECTION). The requested setting may temporarily differ from the current setting (while the connection is inactive). In the SUMMARY output, the requested value is only issued in a separate line for the partner if it differs from the current value. |
| Method of starting recovery measures. General setting last requested with /START-MSCF-CONNECTION or /MODIFY-MSCF-CONNECTION. The requested setting may temporarily differ from the current setting (until all partners have acknowledged the change). |
| Maximum number of MSCF server tasks:
|
|
|
| BS2000 version of the system:
|
| Time interval available to the tasks using XCS functionality to release the XCS functionality when disconnecting from the network before the registered XCS functions are terminated.
|
| Number of the current XCS configuration.
|
| The time stamp (UTC time) of the XCS start, comprising the start date and start time, marks the time at which the XCS network was established by the first joining system. Together with
|
| See
|
| Name of the XCS network:
|
| State of XCS functionality on the local system:
|