Generate entry in MRSCAT of home pubset
Component: | BS2000 |
Functional area: | Pubset and MRSCAT management |
Domain: | MULTI-CATALOG-AND-PUBSET-MGMT |
Privileges: | TSOS |
Routing code: | $ |
Function
The command can be used to create MRSCAT entries both for single-feature pubsets
(SF pubsets) and for system-managed pubsets (SM pubsets). The newly entered catalog is assigned the status “inaccessible”. An entry is not created if one already exists for the specified catalog ID. The catalog IDs must be unique throughout the entire network, i.e. the disks must be initialized accordingly using the VOLIN utility routine.
Unlike the IMPORT-PUBSET and EXPORT-PUBSET commands, this command does not affect the accessibility of the catalogs. With single-feature pubsets, default values are assigned for all cache attributes; with system-managed pubsets they are assigned for the cache attributes FORCE-IMPORT and SIZE-TOLERANCE only. If attributes need to be modified later, the MODIFY-PUBSET-CACHE-ATTRIBUTES command must be used (see the “Introduction to System Administration” [14]; for administration of SM pubsets see also “System-Managed Storage” [45]).
This command cannot be used to create a volume set entry. Volume set entries are generated automatically by the system when required.
Format
ADD-MASTER-CATALOG-ENTRY | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
ENTRY-NAME = <cat-id 1..4>
Catalog ID of the pubset for which a new entry is to be generated in the MRSCAT.
PUBSET-TYPE = *SINGLE-FEATURE(...) / *SYSTEM-MANAGED(...)
Indicates the type of pubset for which a new entry is to be generated in the MRSCAT.
PUBSET-TYPE = *SINGLE-FEATURE(...)
The pubset for which a new entry is to be generated in the MRSCAT is an SF pubset.
START-SPEEDCAT = *AUTOMATIC / *NO / *SPEEDCAT-TASK / *OWN-TASK
Governs whether SCA is to be available for this pubset.
START-SPEEDCAT = *AUTOMATIC
If the SPEEDCAT function is available, SCA is started automatically when the pubset is imported under a local task, the SPEEDCAT task.
START-SPEEDCAT = *NO
SCA is not to be available.
START-SPEEDCAT = *SPEEDCAT-TASK
SCA is to be available, and should run under a separate task, the SPEEDCAT task.
START-SPEEDCAT = *OWN-TASK
SCA should be available and run under the user’s task.
PHYSICAL-ALLOCATION = *ADMINISTRATOR-ONLY / *USER-ALLOWED
Specifies whether users may directly allocate individual volumes of this pubset.
PHYSICAL-ALLOCATION = *ADMINISTRATOR-ONLY
Users may not directly allocate the volumes of this pubset. This right is reserved for the privileged caller under TSOS.
PHYSICAL-ALLOCATION = *USER-ALLOWED
On this pubset, nonprivileged users will also be permitted to allocate individual volumes.
ALLOCATION = *STD / *PARAMETERS(...)
Specifies whether particular allocation parameters should be set for data processing on the pubset.
ALLOCATION = *STD
The setting *STD, i.e. the value of the system parameter concerned (see the description of the *STD operand values for the various allocation parameters below), should be specified for all allocation parameters.
ALLOCATION = *PARAMETERS(...)
Specifies allocation parameters for the pubset, with the values which follow.
SATURATION-LEVEL4 = *STD / <integer 66..2147483647 2Kbyte >
The value specified in the system parameter L4SPDEF is to apply.
SATURATION-LEVEL4 = *STD
The standard value established at system generation (class 2 system parameter L4SPDEF) is to apply.
SATURATION-LEVEL4 = <integer 66..2147483647 2Kbyte >
Value of memory saturation level 4 which is to apply to this pubset.
PRIMARY-ALLOCATION = *STD / <integer 1..16777215 2Kbyte >
The allocation parameter for the primary allocation when a storage space request is made (file processing) is to be set.
PRIMARY-ALLOCATION = *STD
The value specified in the system parameter DMPRALL is to apply.
PRIMARY-ALLOCATION = <integer 1..16777215 2Kbyte >
The value to be applied for this pubset, for primary storage space allocations during file processing. This value will apply as the default value for any user who does not specify an initial allocation in a storage space request.
SECONDARY-ALLOCATION = *STD / <integer 1..32767 2Kbyte >
The allocation parameter for secondary allocations when a storage space request is made (file processing) is to be set.
SECONDARY-ALLOCATION = *STD
The value specified in the system parameter DMSCALL is to apply.
SECONDARY-ALLOCATION = <integer 1..32767 2Kbyte >
The value to be applied for this pubset, for secondary storage space allocations during file processing. This value will apply as the default value for any user who does not specify an initial allocation in a storage space request.
MAXIMAL-ALLOCATION = *STD / <integer 1..32767 2Kbyte >
The allocation parameter for doubling the secondary allocation when a storage space request is made (file processing) is to be set.
MAXIMAL-ALLOCATION = *STD
The value specified in the system parameter DMMAXSC is to apply.
MAXIMAL-ALLOCATION = <integer 1..32767 2Kbyte >
The value assigned to this pubset for doubling of the secondary storage space allocation during file processing. This value will be the maximum value for any user, for whom the space remains inadequate even after a secondary allocation has been made. The value for the secondary allocation will be repeatedly doubled until the specified maximum value is reached.
PUBSET-TYPE = *SYSTEM-MANAGED(...)
The pubset for which a new entry is to be generated in the MRSCAT is an SM pubset.
CONTROL-VOLUME-SET = *NONE / <cat-id 1..4>
Governs whether a control volume set is used.
CONTROL-VOLUME-SET = *NONE
A control volume set is not to be used.
CONTROL-VOLUME-SET = <cat-id 1..4>
Specifies the catalog ID of the pubset that is to be used as the control volume set.
PARTNER-NAME = *OWN / <alphanum-name 1..8>
BCAM name of the partner processor for remote file access.
PARTNER-NAME = *OWN
No BCAM name is specified.
PARTNER-NAME = <alphanum-name 1..8>
BCAM name of the processor for remote file access (RFA). A processor can only be specified if no MSCF connection exists but RFA is nevertheless required.
If an MSCF connection exists and REMOTE-IMPORT=*BY-CONNECTION is specified, the system automatically enters the name of the master computer.
ACCESS-FAILURE = *HOLD-JOBS / *CANCEL-JOBS
Only for a shared pubset:
Defines the behavior if the MSCF connection to the master of an imported shared pubset is lost.
ACCESS-FAILURE = *HOLD JOBS
The pubset is set to the LOCAL-IMPORTED, QUIET state for the duration of the connection interruption.
Tasks that access the pubset enter a wait state, the duration of which is defined by the
BATCH-WAIT-TIME or DIALOG-WAIT-TIME parameter (see below).
ACCESS-FAILURE = *CANCEL-JOBS
The pubset is set to the INACC state for the duration of the connection interruption. Attempts to access
the pubset are immediately rejected - at program level with a corresponding return code, at command
level by triggering a spin-off.
RESIDENT-BUFFERS = *SYSTEM-STD / *NO / *YES
Specifies whether resident or nonresident buffers are to be created.
RESIDENT-BUFFERS = *SYSTEM-STD
The value definition of *SYSTEM-STD depends on the specifications of the NUMBER-OF-BUFFERS operand (see there).
RESIDENT-BUFFERS = *NO
Nonresident buffers are used.
RESIDENT-BUFFERS = *YES
Resident buffers are used.
NUMBER-OF-BUFFERS = *SYSTEM-STD / <integer 1..255>
Defines the number of buffers.
If the value *SYSTEM-STD is specified for both RESIDENT-BUFFERS and NUMBER-OF-BUFFERS, in the MRSCAT is entered that the system parameters CATBUFR and BMTNUM should take effect.
If the value *SYSTEM-STD is specified for only one of the two operands, this corresponds to a standard value (RESIDENT-BUFFERS = * NO, NUMBER-OF-BUFFERS = 32).
The buffer specification is evaluated - according to the following hierarchy - only when the pubset is imported:
Explicit parameter specification in the IMPORT-PUBSET command.
- Values entered in the MRSCAT.
- Specification due to system parameters CATBUFR and BMTNUM.
- If the value specified for NUMBER-OF-BUFFERS is less than 32, it is increased to 32.
BATCH-WAIT-TIME = 28800 / <integer 0..2147483647 seconds >
Only for a shared pubset:
Time in seconds that batch jobs are to wait for the availability of pubsets that cannot be accessed due to a connection failure. If the time specified is exceeded, command processing is aborted with an error code and the spin-off mechanism is triggered. The default value for this wait time is 28800 seconds (8 hours).
DIALOG-WAIT-TIME = 30 / <integer 0..2147483647 seconds >
Only for a shared pubset:
As with batch jobs, defines wait time for interactive jobs. If the time specified is exceeded, the interactive job receives a message and is resumed. The default value here is 30 seconds.
SHARED-PUBSET = *NO / *YES
Determines the shareability of the pubset for local processors.
ACCESS-CONTROLLED = *NO / *YES
Specifies whether access to the pubset is to be restricted to one user ID.
ACCESS-CONTROLLED = *NO
Access to the pubset is not subject to any restrictions.
ACCESS-CONTROLLED = *YES(...)
Access to the pubset is to be restricted to one user ID.
USER-IDENTIFICATION = *TSOS / <alphanum-name 1..8>
Specifies the user ID which is to have access to the pubset.
USER-IDENTIFICATION = *TSOS
Only the TSOS user ID has access to the pubset.
USER-IDENTIFICATION = <alphanum-name 1..8>
Specifies a user ID, in addition to the TSOS user ID, which is to be permitted access to the pubset.
EAM = *STD / *PARAMETERS(...)
Specifies the SYSEAM file parameters specific to this pubset.
EAM = *STD
The setting *STD, i.e. the value of the system parameter concerned (see the description of the *STD operand values for the various SYSEAM parameters below), should be specified for all SYSEAM parameters.
EAM = *PARAMETERS(...)
Specifies the SYSEAM parameters which follow for the pubset.
MAXIMAL-SIZE = *STD / <integer 12..193536 2Kbyte >
This operand is only supported for reasons of compatibility and is no longer evaluated.
MINIMAL-SIZE = *STD / <integer 12..193536 2Kbyte >
Specifies the minimum size (number of half pages) that the SYSEAM file may occupy in the specified pubset.
MINIMAL-SIZE = *STD
The value specified in the system parameter EAMMIN is to apply.
MINIMAL-SIZE = <integer 12..193536 2Kbyte >
Minimum size (number of half pages) that the SYSEAM file may occupy in the pubset.
SECONDARY-ALLOCATION = *STD / <integer 1..193536 2Kbyte >
Specifies the secondary allocation for the SYSEAM file, for this pubset.
SECONDARY-ALLOCATION = *STD
The value specified in the system parameter EAMSEC is to apply.
SECONDARY-ALLOCATION = <integer 1..193536 2Kbyte >
Value of the secondary allocation for the SYSEAM file (number of half pages). This value should be a multiple of 24.
VIRTUAL-MEMORY = *STD / <integer 0..8192 2Kbyte >
Specifies the number of half pages to be used in determining the size of the EAM cache area in class 4 memory. A cache area can only be created for the SYSEAM file of the home pubset. The parameter has no effect for any other pubsets.
VIRTUAL-MEMORY = *STD
The size of the EAM cache area will be determined from the value of the class 2 system parameter EAMMEM.
VIRTUAL-MEMORY = <integer 0..8192 2Kbyte >
The number of half pages specified here determines the size of the EAM cache area.
REMOTE-IMPORT = *BY-CONNECTION / *BY-COMMAND-ONLY
Defines how the remote import status can be changed.
REMOTE-IMPORT = *BY-CONNECTION
The change is made on connection setup.
REMOTE-IMPORT = *BY-COMMAND-ONLY
The remote import status can only be changed by a command.
XCS-CONFIGURATION = *NO / *YES
For shared pubset only:
Defines whether the pubset may be automatically imported as an XCS pubset when a new XCS network is established.
XCS-CONFIGURATION = *NO
The pubset must not be imported automatically as an XCS pubset. (The pubset may nonetheless be used as an XCS pubset using the SET-XCS-PUBSET command.)
XCS-CONFIGURATION = *YES
The pubset is to be imported automatically as an XCS pubset by the MSCF subsystem when a new XCS network is established.
PUBRES-UNIT = *STD / <alphanum-name 2..2> / <x-text 4..4>
Mnemonic device name (MN) of the pubres of the SF pubset or of the volres of the SM pubset. VM2000 requires this entry when the pubset is specified by means of its catalog ID.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | Command executed without error | |
2 | 0 | CMS0002 | Disk error |
1 | CMS0011 | Syntax error | |
1 | CMS0314 | Syntax error in entry name or error in wildcard specification | |
32 | CMD0221 | Internal system error | |
32 | CMS0001 | SLOT manager error | |
32 | CMS031F | MRSCAT parameter error | |
32 | CMS0310 | Error during privilege checking | |
32 | CMS0317 | MRSCAT is locked | |
32 | CMS0318 | Synchronization error due to task lock manager problem | |
64 | CMS0004 | MRSCAT entry already exists | |
64 | CMS0005 | Too many entries in the MRSCAT | |
64 | CMS0010 | Command reserved for systems support |
Examples
Example of creating entries in the local catalog and import pubsets (MPVS)
The pubset MAX is also to be imported locally on the system with the HOME pubset FOR, and a paging file already contained on the pubset PAG is to be used. Furthermore, the pubset LUX, which is imported on the remote system XY, should be accessible via RFA.
Assuming that the disks belonging to pubsets MAX and PAG are already available, the following commands must be entered:
/ADD-MASTER-CATALOG-ENTRY MAX /ADD-MASTER-CATALOG-ENTRY PAG /ADD-MASTER-CATALOG-ENTRY LUX, PARTNER-NAME=XY /IMPORT-PUBSET MAX /IMPORT-PUBSET PAG /EXTEND-PAGING-AREA PAG.00 /EXPORT-PUBSET PAG
The catalog directory MRSCAT in the home pubset has the following contents:
PUBSET FOR: LOCAL-HOME, PAGING PUBSET LUX: INACC, HOST=XY PUBSET MAX: LOCAL-IMPORTED PUBSET PAG: INACC, PAGING
Example of creating catalog entries in a computer network (HIPLEX MSCF)
A computer network is to be set up for single-computer systems HOST1 and HOST2 with catalog IDs A and B. Each system has a MSCF configuration file containing an entry for the other system. The catalog directories contain the following information:
|
Thus, when the command START-SUBSYSTEM SUBSYS=MSCF is issued, a MSCF connection is set up between the two systems and the MRSCAT is updated.
If the commands are given in the order
1) - 2) - 3)
then pubset B is accessible to HOST1 since the ADD-MASTER-CATALOG-ENTRY command was issued before HOST1 and HOST2 were connected.
If the commands are given in the order
1) - 3) - 2)
the connection between HOST1 and HOST2 is established before the ADD-MASTER-CATALOG-ENTRY command is issued. In this case, the pubset B is not accessible to HOST1. Updating of this MRSCAT entry is not performed until the next time a connection is set up (recovery, STOP-/START-MSCF-CONNECTION, STOP-/START-SUBSYSTEM MSCF). If, however, this catalog is to be accessed immediately, the following command must be issued.
/IMPORT-PUBSET PUBSET=B, USE=*FROM-REMOTE(HOST-NAME=HOST2)
Note
If the two systems had no configuration files, the command /START-SUBSYSTEM SUBSYS=MSCF would not cause an MSCF connection to be set up and would not update the MRSCAT. MSCF would be loaded, but the systems would remain isolated.