Pubset states

The functions of the SIR utility routine create and modify pubsets and thereby also their states. In this case, you must bear in mind a number of accompanying conditions in order to avoid execution problems. This section outlines the effects of the SIR actions on the pubsets involved.

The ACTION operand of the DECLARE-PUBSET statement defines the processing mode of a pubset.

ACTION=*INSTALL (pubsets)

• The desired pubset ID may already have been entered in the MRS catalog of the home pubset. In this case, the device type is checked. If an inconsistency is detected, creation is aborted. If an MRS catalog entry is missing, it is added by SIR.

• If the pubset is to be created in the existing BS2000 environment, no pubset with the same pubset ID may have been imported at execution time.

• If new volume sets are created or existing volume sets added while an SM pubset is being set up, the volume set must not be used at that time or entered in the MRS catalog.

• SIR always executes an /IMPORT-PUBSET when setting up an SM pubset, and when setting up an SF pubset if any of the following statements were specified:

  CREATE-CATALOG DISK-NUMBER not equal 00 
  CREATE-PAGING-FILE 
  CREATE-SNAP-FILE 
  COPY 
  CREATE-IPL-VOLUME 
  MODIFY-IPL-VOLUME 
  

ACTION=*EXTEND (pubsets)

• The pubset must have been entered in the MRS catalog of the home pubset.

• If the pubset has already been imported, it should have been imported exclusively. Although it is possible to extend shared pubsets, it will only work for certain if the local system is the only sharer.

• If the pubset has not been imported yet, it must be possible to import it using /IMPORT-PUBSET ACTUAL-JOIN=*STD. To be able to do that, an import with ACTUAL-JOIN=*FIRST must have taken place (see the corresponding note under ACTION=*INSTALL).

• If volume sets are set up or added while an SM pubset is being extended, the same conditions apply as for setting up an SM pubset.

 

ACTION=*IPL (SF pubset only)

• The pubset must have been entered in the MRS catalog of the home pubset.

• The pubset must have been either imported or exported in its entirety. Intermediate states such as may arise in the course of execution of /IMPORT-PUBSET or /EXPORT-PUBSET are not permitted; if they occur, the SIR function is aborted.

The following applies to the allocation of the pubset with respect to other systems or tasks:

• The disks remain exclusively allocated until processing with CREATE-VOLUME has been completed.

• During execution of the subsequent statements, the disks are always allocated as shareable. During these phases, it is basically possible for other systems or tasks to share the pubset. However, allocation by other systems can lead to inconsistencies, particularly during creation or extension of a DRV (Dual Recording by Volume) pubset. These allocations by other systems cannot be prevented by SIR. No suitable functions which work across several systems are available for this purpose. System administration should implement the necessary organizational measures to ensure that no other users access the pubset during the SIR run.

The subsequent setting up of paging files is supported outside SIR by commands.

“Large” disks and files

Each pubset has two attributes which signal whether or not disks and files with a capacity in excess of 32 Gbytes (referred to simply as large disks/files) are permitted for this pubset.

Large files (without a PAM key) can be created on NK and K disks (large files generally have no PAM key).

The attributes are set by SIR when creating a pubset using the LARGE-DISKS-ALLOWED and LARGE-FILES-ALLOWED operands of the //DECLARE-PUBSET statement. Alternatively, large disks/files can be permitted subsequently using the BS2000 command /SET-PUBSET-PARAMETER.

If a large disk is specified while creating or extending a pubset despite the fact that this is not permitted by the relevant attribute, the disk will be rejected with a corresponding message. If you wish to add this disk to the pubset nonetheless, the operand LARGE-DISKS-ALLOWED=*YES must be specified with ACTION=*INSTALL, and the attribute must be changed beforehand using the BS2000 command /SET-PUBSET-ATTRIBUTES with ACTION=*EXTEND.

A home pubset may contain large disks and large files.

Once a pubset is set to permit large disks/files, this setting cannot be reversed.

A disk/file with a capacity of less than 32 Gbytes (small disk) can be included in any pubset, irrespective of the attribute settings.