This statement is for the HSMS administrator only and is used for placing a node S0 under HSMS management or for redefining the parameters of a node S0.
An entry in the HSMS control file must be made for each node S0 to be processed by HSMS. HSMS cannot process any node S0 not entered in its control file.
The first MODIFY-NODE-PARAMETERS statement for a node causes the node to be placed under HSMS management (with default values).
A MODIFY-NODE-PARAMETERS statement with HSMS-CONTROL=*NO removes the entry for the specified node from the HSMS control file.
The operand value *UNCHANGED of the MODIFY-NODE-PARAMETERS statement has two different meanings, depending on the two different functions of the statement:
Placing a node S0 under HSMS management
In this case, *UNCHANGED means that the default values apply; these are listed for the MODIFY-SM-PUBSET-PARAMETERS statement under "Presettings" in section "MODIFY-SM-PUBSET-PARAMETERS Modify parameters of SM pubset".Redefining the parameter values for a node S0
In this case, *UNCHANGED means that the parameter values defined via a previous MODIFY-NODE-PARAMETERS statement are retained. These can be queried by means of the HSMS statement SHOW-NODE-PARAMETERS.
Format (only for HSMS administrators)
MODIFY-NODE-PARAMETERS | Alias: MNP | ||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||
NODE-ID = *BS2000-UFS
ID of the local BS2000-UFS.
NODE-ID = <posix-filename 1..48 without-wild>
Name of the node S0 on which the node file resides. The node S0 which is defined with //MODIFY-NODE-PARAMETERS is mounted under the directory /HSMS/<node-id> in POSIX, and access takes place via NFS.
ENVIRONMENT =
HSMS environment in which the user wishes to work with the associated standard system archives SYSNODEARCHIVE and SYSNODEBACKUP.
ENVIRONMENT = *NODE-STD
*NODE-STD is set to the value *SINGLE-FEATURE.
ENVIRONMENT = *SINGLE-FEATURE
The HSMS statement is valid in the SF environment.
ENVIRONMENT = *SYSTEM-MANAGED(...)
The HSMS statement is valid in the specified SM pubset environment.
CATALOG-ID = <cat-id>
Catalog ID of the SM pubset for which the HSMS statement is valid.
HSMS-CONTROL = *YES(...)
The specified node S0 is to be placed under HSMS management. If the specified node S0 already is under HSMS management, this operand value permits the parameters for the node S0 to be modified.
SYSNODEARCHIVE = *UNCHANGED / *STD / <filename 1..22 without-cat-gen-vers>
Name of the default long-term system archive for node files.
The HSMS administrator must previously have created the specified archive as the public long-term archive for node files by means of the HSMS statement CREATE-ARCHIVE.
SYSNODEARCHIVE = *STD
Global default long-term system archive for node files (according to HSMS parameters for the SF environment and according to SM pubset parameters for each SM environments).
SYSNODEBACKUP = *UNCHANGED / *STD / <filename 1..22 without-cat-gen-vers>
Name of the default system backup archive for node files.
The HSMS administrator must previously have created the specified archive as the public backup archive for node files by means of the HSMS statement CREATE-ARCHIVE.
SYSNODEBACKUP = *STD
Global default system backup archive for node files (according to HSMS parameters for the SF environment and according to SM pubset parameters for each SM environments).
HSMS-CONTROL = *NO
The specified node S0 is to be deleted from the HSMS parameters for the given environment.
Notes
Several MODIFY-NODE-PARAMETERS statements are required for BS2000-UFS. One MODIFY-NODE-PARAMETERS statement is required for each environment covered by BS2000-UFS:
The SF environment is always affected, because the BS2000-UFS contains the root file system which generally resides in the SF environment.
Furthermore those SM environments are affected which correspond to the SM-PUB/X branches.
A remote workstation is always defined in its own environment and therefore only requires one MODIFY-NODE-PARAMETERS statement.
If a workstation is to be relocated to another environment, it must first be removed from the old environment using MODIFY-NODE-PARAMETERS HSMS-CONTROL=*NO. It must then be made known to the new environment using a second MODIFY-NODE-PARAMETERS statement.
When inputting the node ID, you must pay careful attention to the use of uppercase and lowercase characters. The node ID must be written in exactly the same way as the directory /HSMS/<node-s0> in POSIX under which the remote file system is mounted.