This statement is used to initialize disks or ranges of a pubset or volume set. This corresponds to the VOLIN function.
CREATE-VOLUME | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
DISK-NUMBER
Specifies which disk or which range of a pubset or volume set is to be initialized.
DISK-NUMBER=n(...)
Number of the disk within the pubset or volume set. The permissible range depends on the selected format of the pubset or volume set ID.
pubset-id1, volumeset-id1: (the identifier is 1 character long)
The number n of the disk in the pubset must consist of two digits. it is added to the new VSN of the disk to be processed as characters 5 and 6.
Value: 00 ≤ n ≤ 31
The VSN of the disk thus has the following format: PUBpnn where p is the singlecharacter pubset or volume set identifier.
pubset-id2, volumeset-id2: (the identifier is 2 to 4 characters long).
The number of the disk in the pubset depends on the allocation unit:
ALLOCATION-UNIT = 6:
The number of the disk has one character.
Permissible value range for z: 0 - 9, A - V
The VSN of the disk can thus have the following format:
pp.00z or ppp.0z or pppp.z
where p is the two- to four-digit pubset or volume set identifier.
ALLOCATION-UNIT > 6:
The number of the disk may have up to three characters.
Permissible value range for x,y,z: 0 - 9, A - Z, where:
1) 0< 1 <...< 9 < A < B...< Z < 10
2) 10<11...<99<AA<BB...<ZZ<100
3) 100<101...<999<AAA<BBB...<ZZZ
If less than three digits are specified, the disk number is padded with zeros from the left.
The VSN of the disk can thus have the following format:
1) pppp.z or 2) ppp.yz or 3) pp.xyz
where p is the two- to four-digit pubset or volume set identifier.
A list is permitted. It may contain up to 32 elements. The OVERWRITE-DISK operand always refers to the associated ‘n’ specification.
OVERWRITE-DISK
Specifies whether the VSN is to be checked prior to initialization.
OVERWRITE-DISK=*ANY
The initialization takes place without a prior VSN check by SIR. In this case, VOLIN will later issue the NVL0024 question. I.E., the VSN check is conducted manually, in interactive mode by the caller, in batch mode by the operator.
OVERWRITE-DISK=vsn
VSN of the disk to be mounted. VOLIN initializes this disk only when the value vsn
coincides with the VSN of the disk.
UNIT
Introduces a list of disk devices.
UNIT=*NO
Specifies that no disk mnemonics are to be predefined.
UNIT=mn(...)
Mnemonic name of the first disk (MAINUNIT disk) of a disk pair or, in the case of non-DRV pubsets, the only disk to be used.
SUBUNIT=*NO
No second disk is specified.
SUBUNIT=mn
Mnemonic name of the second disk (SUBUNIT disk) of a disk pair. This may only be specified with DRV.
DISK-NUMBER=*RANGE(...)
A number of disks within a range are to be processed. The range is delimited by means of the FROM and TO operands.
FROM=n
Start of the range.
TO=m
End of the range.
DISK-NUMBER
operand. n must be smaller than m.Irrespective of the notation, the value range for both n and m is 0..9, A-Z. This means, for example, that the specification FROM=1,TO=14
covers a total of 40 disks (1-9, A-Z, 10-14). So if you wish to create a pubset containing 14 disks (1-14), you will need two statements:
//CREATE-VOLUME DISK-NUMBER=*RANGE(FROM=1,TO=9,UNIT=(...))
//CREATE-VOLUME DISK-NUMBER=*RANGE(FROM=10,TO=14,UNIT=(...))
OVERWRITE-DISK
Specifies whether the VSN is to be checked prior to initialization.
OVERWRITE-DISK=*ANY
The initialization takes place without a prior VSN check by SIR. In this case, VOLIN will later issue the NVL0024 question. I.E., the VSN check is conducted manually, in interactive mode by the caller, in batch mode by the operator.
OVERWRITE-DISK=list-poss(32): vsn
A list of VSNs is only admissible if several disks within an area are to be processed with the *RANGE operand. The number of list elements must match the number of disks in the range. The statement is rejected if this is not the case. If a DRV pubset/volume set is formed, each VSN specified must be present twice in the system.
UNIT
Introduces a list of disk devices.
UNIT=*NO
Specifies that no disk mnemonics are to be predefined.
UNIT=mn(...)
Mnemonic name of the first disk of a disk pair or, in the case of non-DRV pubsets, the only disk to be used.
SUBUNIT=*NO
No second disk is specified.
SUBUNIT=mn
Mnemonic name of the second disk of a disk pair. This may only be specified with DRV.
FORMAT
Specifies the type of processing.
FORMAT=*YES
The disk is overwritten with a specific bit pattern during the initialization run (default value), i.e. all files are deleted.
FORMAT=*NO
The disk is not overwritten with a bit pattern, instead it is only initialized. A change in the operating mode with regard to the user of PAM keys must apply to the whole pubset/volume set.
Notes
During initialization, every disk of the pubset to be processed must be specified in a CREATE-VOLUME statement, since they must all be anchored with VSN and device type in the SVL of the system disk of the pubset (Pubres).
In the case of a pubset extension (operand ACTION=*EXTEND in the DECLARE-PUBSET statement), the disks specified in this CREATE-VOLUME statement are added to the pubset. If a disk that already belongs to the pubset is specified, this statement is ignored.
In contrast to the VOLIN statements or to the INITIALIZE-PRIVATE/PUBLIC-VOLUME statements, it is possible to process a number of disks with a single CREATE-VOLUME statement in this case. However, as a precondition for this, all disks listed in a statement must either have the same device type or be specified via UNIT and be handled the same way by the FORMAT parameter.
When OVERWRITE-DISK=*ANY is specified, the mounted disk is only overwritten if system administration agrees to this in a message. In this message, the VSN of the mounted disk should be specified.
During creation/extension of a pubset with dual-recording disks (“mirror” disks), two disks are always initialized together. If the operand OVERWRITE-DISK=vsn is specified, there must in this case be two disks with the specified VSN.
If there is more than one disk to be initialized with a specific bit pattern, they can, due to time constraints, be initialized in parallel SIR tasks using the statement INITIALIZE-PUBLIC-VOLUME since initializations with a specific bit pattern are processed sequentially when CREATE-VOLUME with FORMAT=*YES is used.