Modify pubset composition
Component: | BS2000 |
Functional area: | Pubset and MRSCAT management |
Domain: | MULTI-CATALOG-AND-PUBSET-MGMT |
Privileges: | TSOS |
Function
The MODIFY-PUBSET-PROCESSING command enables systems support to modify the composition of pubsets:
Individual disks (volumes) can be added to or removed from a single-feature pubset (SF pubset).
Individual volume sets can be added to or removed from a system-managed pubset (SM pubset).
Individual disks (volumes) can be added to or removed from a volume set which forms part of an SM pubset.
When individual volumes are added to a pubset or a volume set, they can at the same time be supplied with an allocation lock. Systems support can use the MODIFY-PUBSET-RESTRICTIONS command (q.v) to define other usage restrictions for volumes in an SF pubset or for volumes in a volume set which is part of an SM pubset.
The command is also supported for shared pubsets. In a shared-pubset network, the command can be issued on the master system or on a slave system. A system message refers to the system issuing the command, unless preceded by message DMS136D
. The latter includes the name of the system (master or slave) on which the error has occurred. If the command is entered on a slave system, the system name may also be the local system name.
Pubset extension with homogeneity check
The homogeneity check is performed for the currently supported full replication types (for detailed information, please refer to the SHC-OSD manual [37]).
If in the course of pubset extension a volume is detected which has different mirroring properties from volumes which have already been processed, the answerable message DMS1369
is output to SYSOUT. Depending on the caller’s answer, one of the following procedures is selected:
Extension of the pubset is aborted.
Extension of the pubset is continued despite the fact that the volume which has just been processed was recognized as inhomogeneous. Here the message
DMS136B
is output on the console for every further volume with different mirroring properties.
Format
MODIFY-PUBSET-PROCESSING | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operands
PUBSET = <cat-id 1..4>
Identifies the pubset which is to have its composition modified.
PUBSET-TYPE = *SINGLE-FEATURE(...) / *SYSTEM-MANAGED(...)
Specifies whether the pubset is an SF or SM pubset.
PUBSET-TYPE = *SINGLE-FEATURE(...)
The pubset is an SF pubset. Only individual volumes can be added or removed. An allocation lock can be imposed on volumes which are added.
VOLUME-ASSIGNMENT = *UNCHANGED / *ADD(...) / *REMOVE(...)
Specifies whether a volume is to be added or removed. The default is *UNCHANGED, i.e. the composition of the pubset is left unchanged.
VOLUME-ASSIGNMENT = *ADD(...)
A volume is to be added to the pubset. The volume serial number (VOLUME operand) must comply with the naming conventions for public volumes.
VOLUME = <vsn 1..6>
Identifies the volume by its volume serial number.
ALLOCATION-ON-VOLUME = *NOT-RESTRICTED / *NOT-ALLOWED
Governs the allocation options on the volume being added.
ALLOCATION-ON-VOLUME = *NOT-RESTRICTED
Storage space may be allocated on the volume being added.
ALLOCATION-ON-VOLUME = *NOT-ALLOWED
Storage space allocation on the volume being added is not allowed.
CHECK-PUBSET-MIRRORS = *NO / *YES
Determines whether the homogeneity of the pubset is to be checked. A pubset is homogeneous when all volumes of the pubset have the same mirroring properties.
CHECK-PUBSET-MIRRORS = *NO
No homogeneity check is performed.
CHECK-PUBSET-MIRRORS = *YES
A homogeneity check is performed when the volume is added.
VOLUME-ASSIGNMENT = *REMOVE(...)
A volume is to be removed from the pubset. The volume in question must be completely empty.
VOLUME = <vsn 1..6>
Identifies the volume by its volume serial number.
PUBSET-TYPE = *SYSTEM-MANAGED(...)
The pubset is an SM pubset. Entire volume sets can be added or removed. Individual volumes can be added to or removed from assigned volume sets.
VOLUME-SET-SUPPORT = *UNCHANGED / *ADD(...) / *REMOVE(...) / *MODIFY(...)
Specifies whether a volume set is to be added or removed or whether the composition of a volume set which is already available is to be modified.
VOLUME-SET-SUPPORT = *ADD(...)
A volume set which has been entered to the pubset configuration file (see the MODIFY-PUBSET-DEFINITION-FILE command) is to be added to the pubset and thereby made available.
VOLUME-SET = <cat-id 1..4>
Identifies the volume set.
CHECK-PUBSET-MIRRORS = *NO / *YES
Determines whether the homogeneity of the pubset is to be checked. A pubset is homogeneous when all volumes of the pubset have the same mirroring properties.
CHECK-PUBSET-MIRRORS = *NO
No homogeneity check is performed.
CHECK-PUBSET-MIRRORS = *YES
A homogeneity check is performed when the volume set is added.
VOLUME-SET-SUPPORT = *REMOVE(...)
A volume set which is available to the pubset is to be removed and thereby taken out of service. One of the following conditions must be met for this to be done:
- The volume set must be in NORMAL-USE status and must be empty, which means that it must contain no files other than the TSOSCAT file catalog. In addition, the volume set may not be the only one which supports the default file format. The NEW-FILE-ALLOCATION restriction must be set to *NOT-ALLOWED (see the MODIFY-PUBSET-RESTRICTIONS command).
- The volume set is defective, which means that it must be in IN-HOLD or DEFECT status. It can be put into this status either by a system component (such as CMS) or by systems support using the MODIFY-PUBSET-RESTRICTIONS command (PROCESSING-STATE operand).
VOLUME-SET = <cat-id 1..4>
Identifies the volume set.
CONDITION = *EMPTY-VOLUME-SET / *VOLUME-SET-DEFECTS
Specifies which of the above conditions for volume set removal must be met.
CONDITION = *EMPTY-VOLUME-SET
The volume set cannot be removed unless condition a) is met. If this is not the case, processing terminates abnormally.
CONDITION = *VOLUME-SET-DEFECTS
The volume set cannot be removed unless condition b) is met. If this is not the case, processing terminates abnormally.
TERMINATE-JOBS = *NO / *YES
Governs whether processing is to continue if reservations for the volume set are still in existence.
TERMINATE-JOBS = *NO
Processing terminates abnormally if reservations for the volume set are still in existence.
TERMINATE-JOBS = *YES
If reservations for the volume set are still in existence, the jobs which hold the reservations are terminated by the system and processing continues.
VOLUME-SET-SUPPORT = *MODIFY(...)
A volume is to be added to or removed from a volume set which is already available in the SM pubset.
VOLUME-SET = <cat-id 1..4>
Identifies the volume set.
VOLUME-ASSIGNMENT = *UNCHANGED / *ADD(...) / *REMOVE(...)
Specifies whether a volume is to be added or removed. The default is
*UNCHANGED, which means that the volume set stays as it is.
VOLUME-ASSIGNMENT = *ADD(...)
A volume is to be added to the volume set.
VOLUME = <vsn 1..6>
Volume serial number of the volume which is to be added.
ALLOCATION-ON-VOLUME = *NOT-RESTRICTED / *NOT-ALLOWED
Governs the allocation options on the volume being added.
ALLOCATION-ON-VOLUME = *NOT-RESTRICTED
Storage space may be allocated on the volume being added.
ALLOCATION-ON-VOLUME = *NOT-ALLOWED
Storage space allocation on the volume being added is not allowed.
CHECK-PUBSET-MIRRORS = *NO / *YES
Determines whether the homogeneity of the pubset is to be checked. A pubset is homogeneous when all volumes of the pubset have the same mirroring properties.
CHECK-PUBSET-MIRRORS = *NO
No homogeneity check is performed.
CHECK-PUBSET-MIRRORS = *YES
A homogeneity check is performed when the volume is added.
VOLUME-ASSIGNMENT = *REMOVE(...)
A volume is to be removed from the volume set.
VOLUME = <vsn 1..6>
Volume serial number of the volume which is to be removed.
Return codes
(SC2) | SC1 | Maincode | Meaning |
---|---|---|---|
0 | CMD0001 | No errors | |
32 | CMD0221 | Internal system error | |
32 | DMS138A | Internal parameter error | |
32 | DMS1398 | Reconfiguration no longer possible | |
64 | CMD0216 | No authorization to issue command | |
64 | DMS1355 | Cache configuration invalid | |
64 | DMS1358 | Disks already being cached through ADM PFA interfaces | |
64 | DMS135B | No more space on cache medium | |
64 | DMS135E | Cache management subsystem no longer available | |
64 | DMS1380 | Pubset or volume set inconsistent | |
64 | DMS1381 | Volume set conflict | |
64 | DMS1383 | Volume inconsistent | |
64 | DMS1385 | Volume set or volume cannot be removed | |
64 | DMS1387 | Volume cannot be reserved | |
64 | DMS1388 | Volume cannot be allocated to cache area | |
64 | DMS1389 | Error in transmission to partner system | |
64 | DMS138B | Pubset does not exist | |
64 | DMS138C | Pubset not accessible | |
64 | DMS138D | Pubset type conflict | |
64 | DMS138E | Volume set not defined | |
64 | DMS138F | Volume set not accessible | |
64 | DMS1390 | Earlier reconfiguration job not yet completed | |
64 | DMS1392 | Invalid VSN | |
64 | DMS1395 | Maximum number of volume sets exceeded or inhomogeneity of the pubset mirror detected | |
64 | DMS1397 | Reconfiguration of partner system not supported | |
64 | DMS139D | Volume not accessible | |
128 | DMS1386 | Not enough class 4/5 memory | |
128 | DMS139A | Another pubset reconfiguration job is still in progress | |
128 | DMS139B | Volume or volume set is reserved | |
128 | DMS139C | Pubset configuration file still locked |