SF pubsets

Setting up an SF pubset

An SF pubset (single-feature pubset) is set up in the same way as a pubset has always been set up. In other words, the disks are initialized with the VSN, the archive numbers and device types of the disks in the pubset are anchored in the SVL of the system disk of the pubsets (pubres) and a file catalog is defined for the pubset.

The following statements are available for the “Set up an SF pubset” function:

DECLARE-PUBSET PUBSET-TYPE=*S-F(...,ACTION=*INSTALL) 
CREATE-VOLUME 
CREATE-CATALOG 
CREATE-PAGING-FILE

If no CREATE-CATALOG statement is specified, a file catalog with a size of at least 2000 PAM pages is created by default on the Pubres and rounded up to the next multiple of the allocation unit size.

The CREATE-VOLUME statement must be specified for each disk of the pubset to be set up because all disks must be anchored in the SVL of the Pubres.

The function supports the setting up of DRV pubsets and of pubsets with disks with a physical block size of 4 Kbytes.

Attempts to set up an IPL disk with a physical block size of 4K will be rejected.

Extending an SF pubset

Additional disks can be included in an SF pubset that has already been set up. If the pubset is imported then this extension is performed dynamically, i.e. the pubset does not have to be exported first.

The following statements are available for the “Extend an SF pubset” function:

DECLARE-PUBSET PUBSET-TYPE=*S-F(...,ACTION=*EXTEND) 
CREATE-VOLUME 
CREATE-PAGING-FILE
COPY                      (only necessary when extending the home pubset)
CREATE-IPL-VOLUME                        - " -
MODIFY-IPL-VOLUME                        - " -
CREATE-SNAP-FILE                         - " -

A CREATE-VOLUME statement must be specified for each disk to be added to the pubset (see section “SM pubsets”). The disk number specified must not already exist in the pubset.

The disks added to a pubset must have the same disk formats (K/NK, NK2/NK4) as the ones already in the pubset. The allocation unit must also be homogeneous within a pubset. The volumes are therefore automatically initialized by SIR.

Creating a home pubset

If a BS2000 operating system is to be installed and its home pubset is to be created, all files required for the operating system (BS2000 V21.0 and the associated system-related software products) must be transferred to the pubset. At least one disk must be turned into an IPL disk (see next section below). A paging file of sufficient size (>= 200 MB) must be set up for system initialization.

Creation of a snapshot file is recommended when the SNAP dump is already to be available after system initialization. See the SNAP-ACTIVE-SWITCH parameter in the startup parameter service, “Introduction to System Administration” [5].

The following statements are available for the creation of a home pubset.

DECLARE-PUBSET PUBSET-TYPE=*S-F(...,ACTION=*INSTALL) 
CREATE-VOLUME 
CREATE-CATALOG 
COPY 
CREATE-IPL-VOLUME 
CREATE-PAGING-FILE 
CREATE-SNAP-FILE 

The conditions described in section “SM pubsets” apply here, too.

Setting up an IPL disk

With the aid of SIR, public or private disks can be made bootstrappable, i.e. turned into IPL disks.

Public disks of an existing SF pubset can be set up as the IPL disks of the new BS2000 version.
When creating a new SF pubset, several IPL disks can be set up for different BS2000 versions, where the corresponding SIR version must be used for versions other than the current version of BS2000. Only one operating system version can ever be loaded from an IPL disk. Several IPL disks of the same version can also be set up.
Disks of a pubset with the attribute LARGE-FILES-ALLOWED=*YES can be made bootstrappable as well. Disks of a pubset with the standard SYS ID “250” cannot be made bootstrappable.

A disk is bootstrappable if the operator can use it to initiate the operating session (startup). For this to be possible, the disk must have the following attributes:

• It must contain
  the IPL module (SYSPRG.IPL.DSKxxx),

  as well as the save files

  BOOTSAVE (SYSPRG.BOOT.DSKxxx.SAVE),
  SLEDSAVE (SYSPRG.SLED.DSKxxx.SAVE) and
  the startup configuration data (SYSDAT.IPL-CONF.DSKxxx)

  and, if required, the

  IPL REP file (SYSREP.IPL.DSKxxx) and
  SLED REP file (SYSREP.SLED.DSKxxx)

  If the REP files for IPL and SLED are not present, a message is issued during anchoring and processing is continued.

  <.DSKxxx> is replaced by <.vsn> for private disks.

• The standard volume label (SVL) contains pointers to these files.

 

The BOOTSAVE, SLEDSAVE and IPL-CONF files are created as part of the “Set up an IPL disk” function. These files are anchored in the boot or SVL block of the disk.

These files must not reside on the disk to be turned into an IPL disk before SIR is called. By means of internal copying, SIR ensures that this condition is met when anchoring the IPL files in the SVL:
SIR copies the output files to the destination disk under a disk-specific name. The output files are neither anchored nor modified.
The files in question are the following: SYSPRG/SKMPRG.IPL.<ver>, SYSREP.IPL.<ver> and SYSREP.SLED.<ver>

The anchored files are not taken into account during a logical backup, but their output files are.

The following statements are available for the “Set up an IPL disk” function:

DECLARE-PUBSET PUBSET-TYPE=*S-F(...,ACTION=*IPL) 
CREATE-IPL-VOLUME 
MODIFY-IPL-VOLUME 
       (may be additionally or alternatively added) 

During the run, all CREATE-IPL-VOLUME statements are executed by the MODIFY-IPL-VOLUME statements.

If only private disks are to be turned into IPL disks, no DECLARE-PUBSET or BEGIN-VOLUME-SET-DECLARATION statement may be issued.

If the IPL files do not reside on the pubset, they must first be transcribed there. The COPY statement must then be added to the statements specified above.

For private disks, the IPL files in the home pubset must be in a format that is compatible with the private disk (e.g. usually NK format).

You should bear in mind when setting up the IPL disk: Modifying the output files does not affect the anchored files. If the anchored files are to be modified, SIR must be called again.

All other files required for BS2000 system initialization (startup files, see the “Introductory Guide to System Support” [5 (Related publications)]) are sought in the catalog. They can be located on any of the home pubset disks, so do not necessarily have to be contained on the IPL disk.

Modifying an IPL disk

This function modifies an IPL disk. Unlike when setting up the IPL disk, the specified source files (IPL, IPL-Rep, SLED-Rep) may have names deviating from the standard. The files are then copied to the IPL disk under a disk-specific name and anchored afresh in the boot/SVL block. When IPL is anchored, the BOOTSAVE, SLEDSAVE and IPL-CONF files are created anew. The anchors for the remaining files that are required for an IPL disk remain unchanged.

If all the necessary files are specified, this function is the same as the function “setting up an IPL disk”. In this case the disk concerned need not have been bootstrappable.

The following statements are available for the “Modifying an IPL disk” function:

DECLARE-PUBSET PUBSET-TYPE=*S-F(...,ACTION=*IPL)
MODIFY-IPL-VOLUME

The notes under “Setting up an IPL disk” also apply to the function “Modifying an IPL disk”.