Define attributes of pubset
Component: | BS2000 |
Functional area: | Pubset and MRSCAT management |
Domain: | MULTI-CATALOG-AND-PUBSET-MGMT |
Privileges: | TSOS |
Function
This command is used by systems support to define the following pubset attributes:
shareability of the pubset
desired owner (master) of the pubset
desired master change mode
desired backup owner (backup master) of the pubset
system identification (SYSID) of the processor that uses this pubset as the home pubset.
the pubset’s disk and file properties (> 32 GB)
maximum permitted number of Snapsets
Only the PUBRES of the pubset in question must be available for execution of the command (in an SM pubset this is the PUBRES of the control volume set). The attributes defined here (the pubset characteristics) are recorded in the SVL (standard volume label) of the PUBRES.
When assigning a SYSID which is used internally as a synonym of the BCAM name, a distinction must be made according to the type of catalog ID.
Single-character catalog identifier complying with naming convention PUBxyy
PUB = distinguishes public from private disksx = catalog identifier, 1 characteryy = no. within the pubset, 2 characters|| VSN (6 characters)
|The SYSID must be identical to the catalog identifier (x).
Multiple-character catalog identifier complying with naming convention xxx.yy (period notation)
xxx = catalog identifier, 2-3 characters long. = delimiter between catalog identifier and
no. within the pubset, distinguishes public
from private disksyy = no. within the pubset, 1-3 characters long||
| VSN (6 characters)
|
|The SYSID must be an integer in the range 65...192.
When assigning the SYSID it must be avoided that two processors of an MSCF network have the same SYSID.
Specification of new attributes is not immediately effective for pubsets that have already been imported but only after the pubset is re-imported.
Format
SET-PUBSET-ATTRIBUTES | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
PUBSET = <cat-id 1..4>
Pubset to which the following declarations are to apply.
PUBSET-TYPE = *ANY / *SINGLE-FEATURE / *SYSTEM-MANAGED(...)
Specifies the type of pubset involved.
The default applies if an MRSCAT entry exists or if the pubset identifier refers to a single-feature pubset.
PUBSET-TYPE = *ANY
Default: A valid MRSCAT entry exists (the pubset type is irrelevant), or the pubset is a single-feature pubset.
PUBSET-TYPE = *SINGLE-FEATURE
The pubset in question is a single-feature pubset.
PUBSET-TYPE = *SYSTEM-MANAGED(...)
The pubset in question is a system-managed pubset.
CONTROL-VOLUME-SET = *ANY
The pubset in question is an SM pubset with a valid MRSCAT entry.
CONTROL-VOLUME-SET = <cat-id 1..4>
The pubset in question is an SM pubset for which there is no MRSCAT entry.
DEVICE-TYPE = *STD / *NONE / <device>
Device type of the PUBRES of the SF pubset or of the control volume set of the SM pubset, as appropriate.
DEVICE-TYPE = *STD
The default value applies if an MRSCAT entry with the device type exists for this pubset.
DEVICE-TYPE = *NONE
A valid MRSCAT entry exists; there is no need to specify the device type.
DEVICE-TYPE = <device>
Device type of the PUBRES or of the control volume set, as appropriate.
Only disk device types known on the system will be accepted.
Entering DEVICE-TYPE=? in interactive mode calls up a list of available device types.
SYSID = *UNCHANGED / <alphanum-name 1..3>
Issues a SYSID assigned to the pubset.
SYSID = <alphanum-name 1..3>
If the pubset with the name convention PUBxyy is used as a home pubset, the specification here, which corresponds to the catalog identifier, is used as the SYSID for the processor. In the case of a catalog identifier with 2-4 characters, a whole number in the range 65 to 192 must be assigned to the pubset as the SYSID.
MASTER = *UNCHANGED / *NONE / <alphanum-name 1..3>
Specifies the ownership of the pubset.
MASTER = *NONE
Ownership is not explicitly declared. Instead, ownership passes to the system that executes the first IMPORT-PUBSET.
MASTER = <alphanum-name 1..3>
SYSID of the desired master system.
BACKUP-MASTER = *UNCHANGED / *NONE / <alphanum-name 1..3>
Specifies which system is to automatically take over the function of master if the owner of a shared pubset fails. The ALTERNATE-BACKUP operand can be used to define a secondary backup system to take over the function of the master if the backup master specified here is also unavailable.
BACKUP-MASTER = *UNCHANGED
Default: the existing backup master setting continues to apply.
BACKUP-MASTER = *NONE
No preselected system is to take over the role of master automatically if the owner of a shared pubset fails.
BACKUP-MASTER = <alphanum-name 1..3>
SYSID of the required backup owner system.
If the specified system is active as a slave at the time when the owner of a shared pubset fails, it automatically takes over the role of master; if it is not active, the ALTERNATE-BACKUP operand determines whether or how the new master can be identified.
After a change of master to the specified backup master, a further change of master can be carried out without modification of the BACKUP-MASTER operand if the system identified by the MASTER operand is active as a slave system.
ALTERNATE-MASTER = *UNCHANGED / *BACKUP-MASTER / *NONE
Specifies whether the backup master is used as owner in case the pubset is imported on it before the specified owner becomes active.
ALTERNATE-MASTER=*UNCHANGED
Default: the existing alternate master setting continues to apply.
ALTERNATE-MASTER =*BACKUP-MASTER
If the pubset is imported on the backup master before it is imported on the owner, the backup master becomes the owner and the originally specified owner becomes the slave.
ALTERNATE-MASTER=*NONE
During the pubset import, the backup master waits for the pubset import of the owner.
ALTERNATE-BACKUP = *UNCHANGED / *NONE / *BY-OPERATOR / *BY-SHARER
Defines how a change of master is to be implemented if the backup master is not active or not defined (BACKUP-MASTER operand). If the backup master is active, the master is changed automatically and the backup master becomes the new master.
ALTERNATE-BACKUP = *UNCHANGED
Default: the existing setting continues to apply.
ALTERNATE-BACKUP = *NONE
No alternate backup master is defined. If there is an explicitly defined backup master which is not active, no other system is allowed to act as master.
ALTERNATE-BACKUP = *BY-OPERATOR
If the backup master is not active or not defined, an operator can nominate an alternate backup master on one of the slave systems and thus initiate a change of masters (using the command /IMPORT-PUBSET ..., MASTER-CHANGE=*YES).
ALTERNATE-BACKUP = *BY-SHARER
If the backup master is not active or not defined, the role of master is automatically taken by the system which is the first sharer in the current SVL sharer list and hence currently the oldest slave system.
SHARE = *UNCHANGED / *NO / *YES
Governs whether the pubset may be operated as a shared pubset.
SHARE = *UNCHANGED
Default: the existing setting continues to apply.
SHARE = *NO
The pubset must not be imported as a shared pubset.
SHARE = *YES
The pubset may be imported as a shared pubset.
LARGE-VOLUMES = *UNCHANGED / *ALLOWED(...)
Specifies whether the pubset may contain large volumes (capacity > 32 GB).
LARGE-VOLUMES = *UNCHANGED
Default: the existing setting is unchanged.
LARGE-VOLUMES = *ALLOWED(...)
Once set, this attribute cannot be revoked using a command.
The pubset may contain large volumes.
LARGE-FILES = *UNCHANGED / *ALLOWED
Specifies whether the pubset may contain files >= 32 GB.
LARGE-FILES = *UNCHANGED
Default: the existing setting is unchanged.
LARGE-FILES = *ALLOWED
Once set, this attribute cannot be revoked using a command.
The pubset may contain large volumes.
SNAPSET-LIMIT = *UNCHANGED / <integer 1..52>
Specifies the maximum number of Snapsets permitted for the pubset. Up to 52 Snapsets can exist for a pubset (provided this maximum number is supported by the disk storage system).
Any attempt to reduce the Snapset limit to below the number of existing Snapsets is rejected. However, as this can only be checked in the case of imported pubsets, for safety’s sake all snap mirrors are treated as if they belonged to a Snapset in the case of a pubset which was not imported.
An increase to the Snapset limit is rejected if the number of unused snap units is not sufficient for this.
Notes
The /DELETE-SNAPSET SNAPSET=*ALL command causes all Snapsets of a pubset to be deleted, the Snapset catalog also being removed. When the Snapset catalog is removed, the Snapset limit in the SVL is reset to 0.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | No error | |
1 | CMD0202 | Syntax error | |
32 | DMS03BE | Error during communications processing:
| |
64 | DMS03BE | No authorization to use command | |
64 | DMS03BE | Device type missing in the MRSCAT | |
64 | DMS03BE | Current CATID is not a volume set CATID | |
64 | DMS13DA | Snapset limit not in the possible value range | |
64 | DMS13DF | SHC-OSD subsystem not available | |
64 | DMS13E7 | No Snapsets are supported for the pubset | |
130 | DMS03BE | Disk request rejected | |
130 | DMS03BE | Pubset in process of being exported |
Notes
A change of master can only take place in a shared pubset network if a backup master is defined and active, or if the ALTERNATE-BACKUP=*BY-SHARER operand is set. If none of the permissible backup masters is active, all pubset sharers are switched to “INACCESSIBLE, QUIET” if the master fails. In this case, a change of master can subsequently take place provided the ALTERNATE-BACKUP=*BY-OPERATOR operand is set. A subsequent change of master must be triggered manually by explicitly issuing an IMPORT-PUBSET command (specifying MASTER-CHANGE=*YES).
Once set, the pubset attributes LARGE-VOLUMES=*ALLOWED and LARGE-FILES=*ALLOWED cannot be changed using a command, i.e. they cannot be revoked.