Description status: Functional area: Domain: Privileges: | MSCF V21.0A Pubset and MRSCAT management MULTI-CATALOG-AND-PUBSET-MGMT TSOS |
Routing code: | R |
Function
With MODIFY-MSCF-ENVIRONMENT, settings defined for the MSCF session in the MSCF configuration file using SET-MSCF-ENVIRONMENT can be modified dynamically. The following settings can be changed:
The recovery measures to be initiated in the case of a failure
Specification whether MSCF traces are to be generated and the file to which they are to be written
Value for limiting MSCF server tasks
How much time is available to the user tasks to close themselves down when terminating participation in an XCS network
Interval after which abort processing will be performed for an incomplete exit from the XCS network (i.e. interval after which a blocked leave reconfiguration is to be converted into an abort)
Time after which an abort which is not concluded properly leads to the system being closed down abnormally
Priority of a system in an automatic recovery following the loss of a connection in an XCS network
Specification whether a user ID is notified by email, and if so which user ID this is, when particular errors and critical situations occur
The MSCF configuration parameters are described in the section “Parameterization of MSCF”.
Format
MODIFY-MSCF-ENVIRONMENT | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
RECOVERY-START = *UNCHANGED / *AUTOMATIC / *BY-OPERATOR / *CONSISTENT-BY-OPERATOR / *SECURE
Defines how the system is to respond to the failure of a partner system, i.e. how the recovery mechanisms are to be started. The setting applies to all partners (= RECOVERY-START default value).
Note
The setting of RECOVERY-START cannot be modified while a system component holds the Cluster Recovery Lock (CRL) (see also the RELEASE-CLUSTER-RECOVERY-LOCK command).
The fail reconfiguration can only be started automatically if partner monitoring is certain that the partner has failed and this is permitted by both the general and the partner-specific RECOVERY-START settings on the local system and on the partner system (see the section “Inhibiting the automatic start of fail reconfiguration” (Global control parameters)).
RECOVERY-START = *UNCHANGED
The current setting remains unchanged.
RECOVERY-START = *AUTOMATIC
The local system can initiate recovery measures automatically.
RECOVERY-START = *BY-OPERATOR
The recovery measures are not to be initiated until the action has been confirmed by systems support.
RECOVERY-START = *CONSISTENT-BY-OPERATOR
The same behavior as on RECOVERY-START=*BY-OPERATOR. In addition, the partner system does not initiate fail reconfiguration for the local system unless confirmed by systems support.
RECOVERY-START = *SECURE
The value *SECURE is still accepted for reasons of compatibility. It works like *CONSISTENT-BY-OPERATOR.
TRACE-FILE = *UNCHANGED / *NONE / *STD / <partial-filename 2..31>
Governs whether the traces generated by the MSCF subsystem are to be logged in a file and if so, which file.
TRACE-FILE = *UNCHANGED
The current setting remains unchanged.
TRACE-FILE = *NONE
MSCF traces are not logged in a file. If a trace file is open, it will be closed.
TRACE-FILE = *STD
The MSCF traces are to be logged in a file with the default name
SYS.MSCF-TRACE.<datum>.<sysid>.<session>.<index>.
Key:
<date> <sysid> | Date in yyyy-mm-dd format External representation of the system ID of the local system |
<session> <index> | Number of the current BS2000 session Number of the MSCF trace file in the current BS2000 session |
Example: SYS.MSCF-TRACE.2009-01-25.A.001.002
TRACE-FILE = <partial-filename 2..31>
Defines the name of the file to which the MSCF traces are to be written. The file name is composed as follows:
<partial-filename 2..31><date>.<sysid>.<session>.<index>
(for the meaning of <date>, <sysid>, <session> and <index> see the operand TRACE-FILE=*STD).
Example: SYSTEM-TRACES.MSCF.2009-01-26.150.010.003
SERVER-TASK-LIMIT = *UNCHANGED / *STD / <integer 10..500>
Number of MSCF server tasks. This number defines the maximum number of tasks accepted on the partner system.
SERVER-TASK-LIMIT = *UNCHANGED
The server task limit is not changed.
SERVER-TASK-LIMIT = *STD
The server task limit is set to 20.
SERVER-TASK-LIMIT = <integer 10..500>
The server task limit is set to the specified number.
USER-TERM-LIMIT = *UNCHANGED / *STD / *UNLIMITED / <integer 0..6000 seconds>Time available to a user task that is using the XCS functionality, during which it can terminate, when MSCF is being unloaded. After this interval by the latest, MSCF termination is continued with the termination of the registered function.
USER-TERM-LIMIT = *UNCHANGED
The time remaining for a user task to be terminated after the shutdown of XCS has been initialized remains unchanged.
USER-TERM-LIMIT = *STD
The time available for terminating user tasks using global locks is to be set to the default value (300 seconds).
USER-TERM-LIMIT = *UNLIMITED
The system waits with terminating the registered functions until the XCS functionality used on the local system is released, i.e. the tasks canceled with CANCEL-JOB have released their global locks.
USER-TERM-LIMIT = <integer 0..6000 seconds>
Specifies the length of time in seconds available to the user tasks occupying XCS functionality to terminate while MSCF is unloading.
LEAVE-LIMIT = *UNCHANGED / *UNLIMITED / <integer 1..6000 seconds>
Specifies the period of time within which the computer has to conclude a LEAVE reconfiguration. If the LEAVE reconfiguration cannot be concluded within the given time, ABORT reconfiguration is performed instead (see "Global control parameters").
LEAVE-LIMIT = *UNCHANGED
The period of time available to the computer for performing a LEAVE reconfiguration remains unchanged.
LEAVE-LIMIT = *UNLIMITED
No time monitoring is performed, i.e. there is no time limit on a LEAVE reconfiguration.
LEAVE-LIMIT = <integer 1..6000 seconds>
Defines the period of time to be available to the computer for performing a LEAVE reconfiguration.
ABORT-LIMIT = *UNCHANGED / *UNLIMITED / <integer 0..6000 seconds>
Specifies the length of time within which the system must have completed an abort process. When this time expires, the system’s exit from the network is forced by an abnormal system termination (SETS) with MCS1304.
ABORT-LIMIT = *UNCHANGED
The period of time available to the computer to perform an ABORT operation remains unchanged.
ABORT-LIMIT = *UNLIMITED
No time monitoring is performed, i.e. there is no time limit on an ABORT operation.
ABORT-LIMIT = <integer 0..6000 seconds>
Defines the period of time in Sekunden to be available to the computer for performing an ABORT operation.
HOST-PRIORITY = *UNCHANGED / *STD / <integer 1..32>
In an XCS network, this defines a system’s priority for automatic recovery after a connection breakdown. The system to which the higher value was assigned is removed from the XCS network with an ABORT. If the systems have the same value assigned to them, then the system that entered the network last will be removed.
The default value *STD corresponds to the value 16 (see "Global control parameters").
HOST-PRIORITY is only defined for XCS systems. The attempt to change the priority of a CCS system is rejected with message MCS1029.
FADING-INTERVAL = *UNCHANGED / *STD / <integer 0..300 seconds>
For reasons of compatibility, this parameter is still accepted, but is no longer evaluated.
NOTIFY-BY-MAIL = *UNCHANGED / *NO / *YES(...)
Specifies whether, in addition to a message being output on the console, notification is sent by email when the following problems occur:
In the event of unexpected loss of an MSCF connection
If there is a danger of a change of master not succeeding
NOTIFY-BY-MAIL = *NO
No notification is to be provided by email.
NOTIFY-BY-MAIL = *YES(...)
Notifications are to be sent by email to a user ID. When an email is sent, the email address is taken from the EMAIL-ADDRESS field of the user entry concerned (see the MAIL-FILE command).
USER-ID = TSOS / <name 1..8>
Receiver’s user ID. The default is TSOS.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | Command executed without error | |
1 | CMD2201 | Parameter error | |
2 | CMD2202 | MSCF subsystem not defined | |
3 | CMD2203 | Installation error | |
32 | MCS0025 | Internal error (bourse call, request memory) | |
64 | CMD0216 | User is not privileged | |
65 | CMD2241 | MSCF subsystem is not loaded | |
65 | MCS0003 | MSCF subsystem currently being loaded | |
65 | MCS0004 | MSCF subsystem currently being unloaded | |
66 | CMD2242 | No connection to the MSCF subsystem | |
128 | CMD2280 | MSCF subsystem temporarily not available | |
129 | CMD2281 | MSCF subsystem unavailable for an extended period |