CREATE-IPL-VOLUME - Convert disk to IPL disk

This statement makes a disk bootstrappable, i.e. converts it into an IPL disk. The IPL capability of disks is described in detail on "SF pubsets".

CREATE-IPL-VOLUME                                                                                                                                  

DISK-NUMBER=n / *PRIVATE(...)
	*PRIVATE(...)
		|	DISK=vsn
		|	,DEVICE-TYPE= STDDISK / device-type
,HSI-TYPE= *BY-OWN-HSI / *390 / *X86 1)

¹⁾ The *7500 operand value can still be specified for reasons of compatibility.

DISK-NUMBER
Specifies the disk that is to be made into an IPL disk. Depending on the format of the pubset ID (see the DECLARE-PUBSET statement), the number of the disk on the pubset must be specified.

DISK-NUMBER=n
One- to three-digit number of the IPL disk in the pubset (see "CREATE-VOLUME - Initialize disks").

DISK-NUMBER=*PRIVATE(...)
Specifies a private disk that is to be made into an IPL disk.

DISK=vsn
VSN of the private disk

DEVICE-TYPE=STDDISK
Default device type of the private disk.

DEVICE-TYPE=device-type
Device type of the private disk.

HSI-TYPE
Defines the HSI for which IPL capability is to be established.

HSI-TYPE=*BY-OWN-HSI
IPL capability is to be established for the HSI where SIR is running.

HSI-TYPE=*390
IPL capability is established for the /390 HSI (/390 servers).

HSI-TYPE=*X86
IPL capability is to be established for the X86 HSI (x86 servers).

 

Notes

1. The IPL files must be cataloged in the pubset if DISK-NUMBER=n is specified. IPL files include the IPL module (SYSPRG.IPL.<ver> with HSI=*390 and SKMPRG.IPL.<ver> with HSI=*X86), as well as the REP files for IPL and SLED (SYSREP.IPL.<ver> and SYSREP.SLED.<ver>), if these are available.

2. As explained above, for IPL conversion to be possible, the data must be present on the disk. CREATE-IPL-VOLUME fulfils this condition by copying the files to a file copy.

3. In the case of DISK-NUMBER=*PRIVATE, the IPL files must already be in the home pubset and in a format that is compatible with the private disk. A DECLARE-PUBSET statement must not be issued if during this SIR run one or more private disks are to be turned into IPL disks.
   If the REP files are not available for IPL and SLED, a message is output and processing continued.

4. A disk can only ever be bootstrappable for one HSI. This means that if IPL capability is established for HSI-TYPE=*X86 using CREATE-IPL-VOLUME, any IPL capability which previously existed for a /390 HSI is lost.

5. When establishing the IPL capability of a disk, the following backup files are created so as to record both memory data which is overwritten when BOOT and/or SLED is loaded and startup configuration data:

   • BOOT-file.<x>.SAVE

   • SLED-file.<x>.SAVE

   • SYSDAT.IPL-CONF.<x> (24 pages of 2 Kb each)

   where	BOOT-file:	file name of the BOOT load module
   	SLED-file:	file name of the SLED load module
   	<x>:	DSKxxx or vsn

   The files are created with BLOCKSIZE=(STD,2).

   The procedure is as follows if files with these names already exist:

   • The correct size file is on the correct disk.
     No further action is necessary.

   • The incorrect size file is on the correct disk.
     The file size is corrected.

   • The file is on another disk within the pubset. The file is created on the correct disk and deleted from the other disk.

   Example

   Standard IPL	SYSPRG.IPL.<ver>
   Standard IPL Rep	SYSREP.IPL.<ver>
   Standard SLED Rep	SYSREP.SLED.<ver>

   CREATE-IPL-VOLUME DISK-NUMBER=*PRIVATE(PRIV00),HSI-TYPE=*390 generates the following files on the IPL disk:

   IPL	SYSPRG.IPL.PRIV00
   BOOTSAVE	SYSPRG.BOOT.PRIV00.SAVE
   SLEDSAVE	SYSPRG.SLED.PRIV00.SAVE
   IPL-CONF	SYSDAT.IPL-CONF.PRIV00
   IPL-REP	SYSREP.IPL.PRIV00
   SLED-REP	SYSREP.SLED.PRIV00

6. If at least one disk of a pubset is converted to an IPL disk, SIR creates the file SYS.NSI.SAVEREP in order to save system corrections during system initialization.

7. All anchored files are given the file attributes BACKUP=E, DESTROY=*YES, ACCESS=*READ and MIGRATION=*FORBIDDEN.

8. SIR does not support file protection with BASIC-ACL for IPL files. If the user has protected one of these files with BASIC-ACL, the protection must be canceled to enable SIR to modify the IPL files.

9. The file names for storing the IPL files are formed implicitly. It is important to ensure that the IPL files are stored under the default name in the pubset. Otherwise a message is output and the statement ignored.

10. The HSI-TYPE operand should only be specified if IPL disk capability is not to beestablished for the HSI on which SIR is currently running.

11. The statement is rejected for disks of pubsets, which cannot be used as home pubsets:

    • pubsets with SYS-ID=*STD

    • pubsets with PHYSICAL-BLOCK-SIZE=*4K

    • SM pubsets