Setting up an SM pubset
This function is used to put together volume sets to make up an SM pubset.
Set up is performed in two internal SIR stages:
First the disks are initialized and formatted for each volume set that is to be set up in the same SIR run. After that, the related disks are entered in the SVLs of the Volres of the individual volume, thus forming the volume sets. Then a file catalog is created on the Volres. On the control volume set, which is the preferred volume set of the SM pubset, further special files are created.
An SM pubset is set up from the volume sets created during stage one, or from volume sets that were previously created in earlier SIR runs.
The volume set that is to become the control volume set must always be set up afresh in the same SIR run because its structure is different from that of a simple volume set.
The following statements are available for the “Set up an SM pubset” function:
DECLARE-PUBSET PUBSET-TYPE=*S-M(ACTION=*INSTALL) BEGIN-VOLUME-SET-DECLARATION ...,ACTION=*ADD / *INSTALL CREATE-VOLUME ... CREATE-CATALOG ... ... END-VOLUME-SET-DECLARATION BEGIN-VOLUME-SET-DECLARATION ...,ACTION=*ADD / *INSTALL ... END-VOLUME-SET-DECLARATION COPY ... ... END
The same conditions as for setting up a volume set apply to the declaration of the individual volume sets when setting up an SM pubset. However, when setting up an SM pubset, catalog extents can be set up for individual volume sets on disks other than Volres.
If no CREATE-CATALOG statement is given for a volume set that is to be set up, a catalog of at least 2000 PAM pages in size, rounded up to the next multiple of the allocation unit size, is automatically set up on the Volres.
In the declaration of a control volume set, ACTION=*INSTALL must be specified in the BEGIN-VOLUME-SET-DECLARATION statement.
COPY statements are only permitted outside the statement block BEGIN-/END-VOLUME-SET-DECLARATION. The position of the files to be copied within the SM pubset is defined by the performance attribute of the various source files.
The following statements are not permitted when setting up an SM pubset since it is not permitted to use an SM pubset as a home pubset:
CREATE-SNAP-FILE, CREATE-IPL-VOLUME, MODIFY-IPL-VOLUME
Example
/START-SIR
//DECLARE-PUBSET PUBSET-TYPE=*SYSTEM-MANAGED(PUBSET=SMP1,
ACTION=*INSTALL(CONTROL-VOLUME-SET=XYZ)) 1.
//BEGIN-VOLUME-SET-DECLARATION VOLUME-SET=AB,
ACTION=*ADD(VOLUME-SET-ATTR=*PAR(
USAGE=*STD,AVAILABILITY=*HIGH,PERFORMANCE-ATTR=*PAR(
PERFORMANCE=*HIGH,WRITE-CONSISTENCY=*IMMEDIATE))) 2.
//END-VOLUME-SET-DECLARATION
//BEGIN-VOLUME-SET-DECLARATION VOLUME-SET=XYZ,
ACTION=*INSTALL(FORMAT=*K,AVAILABILITY=*DRV) 3.
//CREATE-VOLUME DISK-NUMBER=00(OVERWRITE-DISK=*ANY,UNIT=XY(SUBUNIT=XZ)),
FORMAT=*YES 4.
//CREATE-CATALOG DISK-NUMBER=00,FILE-SIZE=96 4.
//END-VOLUME-SET-DECLARATION
//END
An SM pubset with the catalog ID SMP1 is defined. The volume set with the ID XYZ is designated as the control volume set.
The volume set with the ID AB, which was defined in a prior SIR run, is to be included in the SM pubset with ID SMP1. The following logical properties are defined for it: it is to be used as the storage location for standard files and provide high failure security and performance. The consistency for writes is to be immediate.
Subsequently, a volume set with the ID XYZ is to be set up. It is known from (1) that this volume set is to be the control volume set. The volume set is to have DRV capability.
A volume is defined (VSN XYZ.00) and a range is set for the catalog.
Extending an SM pubset
An SM pubset or volume sets that belong to an SM pubset can be extended by volume sets or disks.
An SM pubset is extended SIR-internally in two stages in the same way as described under “Setting up an SM pubset”:
The specified volume sets are extended by disks as defined in the CREATE-VOLUME statement. The new disks are first initialized and formatted and then entered in the Volres of the individual volume sets. The creation of catalog extents is not supported.
In the second stage, additional volume sets are included in the SM pubset and the COPY statement is executed.
The following statements are available for the “Extend an SM pubset” function:
DECLARE-PUBSET PUBSET-TYPE=*S-M(ACTION=*EXTEND) BEGIN-VOLUME-SET-DECLARATION ...,ACTION=*ADD / *INSTALL / *EXTEND CREATE-VOLUME ... ... END-VOLUME-SET-DECLARATION BEGIN-VOLUME-SET-DECLARATION ...,ACTION=*ADD / *INSTALL / *EXTEND ... END-VOLUME-SET-DECLARATION COPY ... ... END
Notes
The pubset must not contain volume sets that are to be processed with ACTION= *ADD / *INSTALL.
Volume sets that are to be processed with ACTION=*ADD must not belong to any other pubset.
For ACTION=*EXTEND, the volume set must already be part of the pubset to be processed.
A volume set can only be extended if it is in a consistent state.
Example
/START-SIR
//DECLARE-PUBSET PUBSET-TYPE=*SYSTEM-MANAGED(PUBSET=SMP1,
ACTION=*EXTEND(CONTROL-VOLUME-SET=XYZ)) 1.
//BEGIN-VOLUME-SET-DECLARATION VOLUME-SET=X,
ACTION=*ADD(VOLUME-SET-ATTR=*PAR(PERFORMANCE-ATTR=*PAR(
PERFORMANCE=*VERY-HIGH,WRITE-CONSISTENCY=*BY-CLOSE))) 2.
//END-VOLUME-SET-DECLARATION
//BEGIN-VOLUME-SET-DECLARATION VOLUME-SET=AB,
ACTION=*EXTEND 3.
//CREATE-VOLUME DISK-NUMBER=*RANGE(0A1,0A3,OVERWRITE-DISK=*ANY,
UNIT=(MT(SUBUNIT=MU),MV(SUBUNIT=MW),MX(SUBUNIT=MY))),
FORMAT=*YES 4.
//END-VOLUME-SET-DECLARATION
//BEGIN-VOLUME-SET-DECLARATION VOLUME-SET=XYZ,
ACTION=*EXTEND 5.
//CREATE-VOLUME DISK-NUMBER=02(OVERWRITE-DISK=*ANY,UNIT=Y1(SUBUNIT=Y2)),
FORMAT=*YES 6.
//END-VOLUME-SET-DECLARATION
:
//COPY FILE=:SF01:SYSMES.(NEW=SYSMES.) 7.
//COPY FILE=ARCHIV.(NEW=*PREFIX(REMOVE=ARCHIV)),FROM=*PUBSET 8.
//END
The SM pubset SMP1 is to be extended.
The previously defined volume set X (see "Volume sets") is to be included in the SM pubset. Its logical properties are defined as follows: it is to be used for storing standard files and provide normal failure security with increased performance. The consistency for writes is to be after file closure.
The volume set AB is to be extended.
A fourth, fifth and sixth volume now also belong to this volume set with the VSNs AB.0A1, AB.0A2 and AB.0A3.
The control volume set XYZ is to be extended.
A second volume now also belongs to this volume set with the VSN XYZ.02.
All files from pubset SF01 whose names begin with “SYSMES” retain their file names and are copied to volumes of SM pubset SMP1 which was specified in the DECLARE-PUBSET statement (1).
All files in the default pubset whose names begin with “ARCHIV” are to be copied to SMP1. The “ARCHIV” prefix is to be omitted for the target files.
SM pubset SMP1 configuration after processing the examples
A pubset generated by SIR provides system administration with the basis for further management measures. Their order and chronological sequence is not fixed. They do not have to be carried out during pubset creation, but can be made as required during pubset maintenance. It is recommended to modify the pubset immediately after generation if the defaults which cannot be influenced during generation (e.g. usage restrictions, cache assignments, saturation thresholds) are to be changed. It is also thereby possible to generate the part of the pubset environment that was not taken into account during generation (storage classes, management classes, GUARDS profile, HSMS environment, etc.). The pubset must be in operation for this post-processing. A detailed description of post-processing newly generated SM pubsets can be found in the “SMS” manual [8 (Related publications)].