For privileged users
The CREATE-SYSTEM-MANAGED-PUBSET statement either creates a new SM pubset or checks whether specified SF pubsets can be included in a new SM pubset without conflict. When a new SM pubset is created a maximum of 255 SF pubsets are converted to a new SM pubset, each SF pubset becoming a volume set of the SM pubset.The check function performs a consistency check which provides information on system-wide name conflicts in the pubsets concerned.
For nonprivileged users
The CREATE-SYSTEM-MANAGED-PUBSET statement only provides the check function for nonprivileged users. Here a consistency check decides whether the specified SF pubsets can be included in a new SM pubset. The checks relate only to the caller’s user ID. Callers can thus obtain information on which name conflicts they have caused and how they can resolve these.
Outputs
The outputs of this statement are described in the section “Outputs (Creating new SM pubsets)” or in the section “Outputs (Check function)”; the mask descriptions start on "Outputs to screen masks".
Operation
How this statement functions, its restrictions and the quota management are described in the section “Creating new SM pubsets”.
CREATE-SYSTEM-MANAGED-PUBSET OPERATIONAL-MODE= *OPERATION should never be called without a previous FDDRL backup of the pubset to be converted, since an abort due to an error would destroy all the pubsets and render them inaccessible.
A logical backup using HSMS is also recommended. Here, a new backup archive can be created which can be used for the creation of the HSMS environment for the SM pubset. For details of how to adapt the HSMS environment, refer to the description of SMS migration in the “System-Managed Storage” manual [8 (Related publications)].
SPOOL jobs for files that are cataloged in the pubsets to be converted should no longer be present, since they can no longer be carried out after renaming the catalog ID.
Simulation and check mode
If the operand OPERATIONAL-MODE=*SIMULATION is specified, the function described is not really executed. Only a syntax check is carried out and the specified volume sets are listed.
If the OPERATIONAL-MODE=*CHECK-NAME-CONSISTENCY operand is specified, only the check function is performed.
For more details, refer to the operand descriptions.
Format for privileged users
CREATE-SYSTEM-MANAGED-PUBSET | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||
Operands
PUBSET = <catid>
ID of the SM pubset to be created or which is to be checked to see whether it can be created.
The ID must differ from the IDs of the SF pubsets to be converted.
If not just a check is to take place (OPERATIONAL-MODE= *CHECK-NAME-
CONSISTENCY operand) but also a conversion, no identical MRSCAT entry may already exist.
The specified ID is included in the check of the file name length and of whether guard conditions can be modified automatically.
CONTROL-VOLUME-SET = <catid>(...)
ID of the SF pubset that is to become the control volume set of the new SM pubset.
It must differ from the ID of the SM pubset to be created.
As for all SF pubsets to be converted, there must also be an MRSCAT entry with the correct device type for this pubset.
If not just a check is to take place (OPERATIONAL-MODE= *CHECK-NAME-
CONSISTENCY operand) but also a conversion, the pubset may not be imported in either the local or any other system.
The control volume set must satisfy the requirements described in the section “Requirements for operation of SMPGEN”.
If just the test function is performed (OPERATIONAL-MODE=*CHECK-NAME-CONSISTENCY), the specification for the subsequent volume set attributes is ignored.
AVAILABILITY =
Defines the degree of availability of files with respect to the failsafe capacity of the volume set.
The availability is a logical attribute of the volume set that is used as a selection criterion when choosing storage space for archiving files. Changing the volume set attribute is a job that must be commissioned explicitly by systems support.
AVAILABILITY = *STD
Default value: the volume set does not offer enhanced availability.
AVAILABILITY = *HIGHThe volume set offers high availability.
It is the responsibility of systems support to check that failsafe performance is actually guaranteed physically and, for example, to activate DRV or DUALCOPY mode before starting conversion.
PERFORMANCE-ATTR =
Defines the performance attributes of the volume set for file access. These attributes are logical attributes which are used as a selection criterion when choosing the storage space. The available hardware is not verified (e.g. cache).
PERFORMANCE-ATTR = *STD
Default value: no enhanced performance attributes for file access are to be defined for the volume set.
PERFORMANCE-ATTR = *PARAMETERS(...)
The performance attributes that apply to the volume set are defined via the following substructure:
PERFORMANCE =
Describes the I/O performance profile of the volume set. It is possible to specify a list of up to three values.
PERFORMANCE = *STD
Default value: the volume set provides no enhanced I/O performance.
PERFORMANCE = *HIGH
The volume set provides enhanced I/O performance.
PERFORMANCE = *VERY-HIGH
The volume set provides very high I/O performance.
WRITE-CONSISTENCY =
Defines whether the hardware used to increase the I/O performance guarantees data consistency even in the event of a system crash.
WRITE-CONSISTENCY = *BY-CLOSE
Default value: write I/Os with enhanced performance are possible only in trade-off against immediate crash-proof data storage; until the file is closed the data is not physically stored on a medium which guarantees data retention even if the system crashes.
WRITE-CONSISTENCY = *IMMEDIATE
Also for write I/Os with enhanced performance, the data is immediately stored on a medium which guarantees data retention even in the event of a system crash.
ADD-VOLUME-SET =
Specifies whether further SF pubsets are to be added to the SM pubset, in addition to the pubset specified as the control volume set.
ADD-VOLUME-SET = *NONE
Default value: no further SF pubsets are to be added.
ADD-VOLUME-SET = <catid>(...)
IDs of further SF pubsets to be added to the SM pubset as a volume set. The pubset ID becomes the volume set ID.
All volume set IDs must be different from the ID of the control volume set and the selected SM pubset ID.
If not just a check is to take place (OPERATIONAL-MODE= *CHECK-NAME-
CONSISTENCY operand) but also a conversion, the SF pubsets may not be imported in either the local or any other system; however, MRSCAT entries with the correct device type must already exist for this purpose.
The volume sets must satisfy the requirements described in the section “Requirements foroperation of SMPGEN”.
The volume set attributes, except USAGE, that can be specified as the substructure are described under the CONTROL-VOLUME-SET operand.
If just the test function is performed (OPERATIONAL-MODE=*CHECK-NAME-CONSISTENCY), the specification for the subsequent volume set attributes is ignored.
USAGE =
Specifies the usage of the volume set.
USAGE = *STD
The volume set is to be used as the storage location for the default files. Work files (WORK file attribute) may not be stored there.
USAGE = *HSMS-CONTROLLED
The volume set is used by the HSMS subsystem to implement storage level S1 and the backup volume set of an SM pubset. Users may not store any files there.
KEEP-USER-ATTRIBUTES =
Specifies the procedure for the login IDs and the user group structure, as well as the user information relevant only to the home pubset (privileges, rights, operator roles).
If just the test function is performed (OPERATIONAL-MODE=*CHECK-NAME-CONSISTENCY), the specification for this operand is ignored.
KEEP-USER-ATTRIBUTES = *ALL(...)
Default value: the information is to be taken from one of the SF pubsets to be combined. The information on all other original pubsets is ignored.
ATTRIBUTE-ORIGIN = *CONTROL-VOLUME-SET
The information is to be taken from the pubset that is to become the control volume set.
ATTRIBUTE-ORIGIN = <catid>
Specifies the ID of the pubset from which the information is to be taken. It must be one of the pubsets to be converted.
KEEP-USER-ATTRIBUTES = *BASIC
Only the important user information relevant to the data pubset is to be taken. The information is lost during pubset conversion (even if only one pubset is converted).
S1-MIGRATED-FILES =
Specifies whether if one of the pubsets to be checked contains cataloged files which are currently migrated to S1 level this is to be defined as a conflict.
S1-MIGRATED-FILES = *NOT-ALLOWED
Default value: the case described above is deemed to be a conflict.
S1-MIGRATED-FILES = *ALLOWED
The case described above is not deemed to be a conflict.
The S1-migrated files are no longer accessible following conversion, but must be restored from a backup file. Their catalog entries are retained so that they can be selectively moved to the S1 level of the SM pubset after creation of the HSMS environment with REPAIR-CATALOG-BY-RESTORE.
MAX-ERRORS = 32767 / <integer 0..32767>
The consistency check is aborted when the specified number of errors have occurred. The conflicts encountered before the function is aborted are output, provided ERROR-INFORMATION = *DETAIL was specified. 32767 is the default value.
Specifies a job variable used for monitoring.
MONJV = *NONE
Default value: no monitoring job variable is specified.
MONJV = <filename 1..54 without-gen-vers>
Specifies the name of the monitoring job variable. It must already be cataloged in an accessible pubset and must not be password-protected.
The job variables’ status display is set as follows during conversion (OPERATIONAL-MODE=*OPERATION):
$I | at the start of processing |
| $R | on successful completion of processing |
| $A | on termination with error |
The job variables’ status display is set as follows during the consistency check (OPERATIONAL-MODE=*CHECK-NAME- CONSISTENCY):
$I | at the start of the consistency check |
| $R | at the end of the consistency check if consistency exists |
| $E | at the end of the consistency check if consistency does not exist |
| $A | in the event of an incomplete consistency check |
There is no point in specifying this operand unless you are using the software product JV.
If the job variable is to receive defined contents when execution of the function is started, the user must initialize this variable him/herself. If the function is aborted right at the start of execution, e.g. because a semantic error is detected, SMPGEN does not provide a value for the job variable.
If the job variable is contained on one of the pubsets that are to be combined and OPERATIONAL-MODE=*CHECK-NAME-CONSISTENCY(PUBSET-STATE= *IMPORTED) is not specified, the SMPGEN job is rejected.
ERROR-INFORMATION =
Controls the scope of the error information output in text and/or variable form.
ERROR-INFORMATION = *DETAIL
Default value: detailed error information is to be output. Not only is the number of name conflicts output, but also all names that occur more than once or names that are too long are listed.
In interactive mode, screen masks are output to the terminal that offer the option of suppressing follow-up screens or detail screens, or to switch to SYSLST (see section“Outputs to screen masks”).
In batch mode and to SYSLST, the output is made in the same format, but here there is no possibility of intervening.
ERROR-INFORMATION = *SUMMARY
No detailed error information is to be output, i.e. no lists of name conflicts but only the number of conflicts in the various name classes.
Specifies whether the function is to be executed in the current task or in a new batch task to be created.
EXECUTION-MODE = *SYNCHRONOUS(...)
Default value: the function is to be executed in the current task.
TEXT-OUTPUT =
Controls the output destination for data output in text format, i.e. lists, logging and error messages.
TEXT-OUTPUT = *STD
Default value: the output is to be carried out according to default setting. In interactive mode, output is to SYSOUT and to SYSLST. In batch mode, output is to SYSLST.
TEXT-OUTPUT = *SYSOUT
Output is directed to SYSOUT. This specification may only be made in interactive mode. SYSOUT may not have been reassigned to a file. If SYSOUT output is desired, screen masks are output and these must be confirmed by pressing the send key. If numerous errors occur, it is possible to apply or suppress a detailed error log for SYSLST later.
TEXT-OUTPUT = *SYSLST
Output is directed to SYSLST.
TEXT-OUTPUT = *NONE
No outputs in the form of lists or messages are desired. It makes sense to specify this value when the STRUCTURE-OUTPUT operand is used instead.
Error messages and messages reporting the start and success of the function cannot be suppressed; they are output to SYSOUT even if TEXT-OUTPUT=*NONE is specified.
STRUCTURE-OUTPUT =
Directs output of error information to S variables.
STRUCTURE-OUTPUT = *SYSINF
Default: the error information is to be output to an S variable to which the user has assigned the variable stream SYSINF.
If this variable stream is not active, no output is made to an S variable.
STRUCTURE-OUTPUT = *NONE
No output is made to an S variable.
STRUCTURE-OUTPUT = <composed-name 1..100>
Specifies the S variables in which the error information is to be stored.
The user must declare the variable as a dynamically defined structure (/DECLARE-VARIABLE ..., MULTIPLE-ELEMENTS=*LIST,TYPE=*STRUCTURE).
EXECUTION-MODE = *ASYNCHRONOUS(...)
The function is to be executed in a new batch task that is to be created. In this case, no information output takes place to an S variable.
TEXT-OUTPUT =
Controls the output of lists, logging and error messages.
TEXT-OUTPUT = *SYSLST
Output is made to a spoolout file that is printed at the end of the job and then deleted. The name of the spoolout file corresponds to the default setting of the SYSLST file for ENTER tasks.
TEXT-OUTPUT = <filename 1..54 without-gen-vers>
The text is to be output to the specified file. If the file already exists, the user must hold the appropriate write access right. The file must not be password-protected. It must be accessible locally and must not be a temporary file. The file is neither printed out nor deleted at the end of the job.
OPERATIONAL-MODE =
Specifies whether the function “Create an SM pubset” is really executed or only simulated or whether only the check function (consistency check) is to be performed.
OPERATIONAL-MODE = *OPERATION
Default value: the function is really executed.
OPERATIONAL-MODE = *SIMULATION
The function is only to be simulated.
The syntax of the operands specified is checked.
However, the operands MAX-ERRORS, MONJV, ERROR-INFORMATION and EXECUTION-MODE (with suboperands) do not have the meanings given in the operand descriptions.
Execution always takes place in the current task: if this is an interactive task, output is to SYSOUT and SYSLST; if it is a batch task, output is made only to SYSLST.
When the syntax check has been performed successfully, a table of volume sets with the specified logical attributes is output.
The original pubsets need not be accessible for this function; no disk operations are performed. Consequently, no checks that require disk availability are carried out, i.e. no name consistency check. The MRSCAT entries are not checked either.
OPERATIONAL-MODE = *CHECK-NAME-CONSISTENCY(...)
The check function (consistency check) is performed by SMPGEN.
Here the SF pubsets which were specified with the CONTROL-VOLUME-SET and ADD-VOLUME-SET operands are checked to see whether they can be transferred to the SM pubset that is to be created or can be converted.
PUBSET-STATE =
Specifies whether the consistency check is to performed for the current pubset session, i.e. possibly in parallel with other user accesses to the pubsets.
PUBSET-STATE = *IMPORTED
Default value: the consistency check is to be performed for the current pubset session. The pubsets have already been imported locally. The consistency check provides only a rough estimate which changes may since have rendered inaccurate.
PUBSET-STATE = *NOT-IMPORTED
SMPGEN is to allocate the pubsets exclusively for the consistency check. The pubsets are neither local nor imported from another system. During the consistency check they are locked against other accesses. This means that the result is correct at output time.
USER-ID =
Specifies the user ID(s) for which a pubset consistency check is to be performed.
USER-ID = *OWN
Default value: the consistency checks are to cover only the file names, job variables and guards under the user ID of the caller.
The system administration specific general checks referred to in the description of the statement (illegal files, S1 migration) are also performed when this value is specified.
USER-ID = *ALL
The consistency checks are to cover all user IDs. This specification is not allowed if one or more of the pubsets is/are imported in “shared slave” mode.
Format for nonprivileged users
CREATE-SYSTEM-MANAGED-PUBSET | ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Operands
PUBSET = <catid>
ID of an SM pubset which is to be checked to see whether it can be created.
The ID must differ from the IDs of the SF pubsets to be combined.
An identical MRSCAT entry may exist: such a pubset is not accessed (for example for checking purposes).
The specified ID is included in the check of the file name length and of whether guard conditions can be modified automatically.
CONTROL-VOLUME-SET = <catid>
ID of the SF pubset that is to become the control volume set of the new SM pubset. The ID becomes the volume set ID of the control volume set. It must differ from the ID of the SM pubset to be created. The SF pubset must have been imported into the local system.
ADD-VOLUME-SET =
Specifies whether, in addition to the pubset specified as the control volume set, further SF pubsets are to be checked for inclusion in the SM pubset.
ADD-VOLUME-SET = *NONE
Default value: no further SF pubsets are to be checked.
ADD-VOLUME-SET = <catid>
Specifies the IDs of further SF pubsets to be checked.
The pubset ID becomes the volume set ID.
All volume set IDs must be different from the ID of the control volume set and the selected SM pubset ID.
The SF pubsets must have been imported into the local system.
The volume set attributes, except USAGE, that can be specified as the substructure are described under the CONTROL-VOLUME-SET operand.
MAX-ERRORS = 32767 / <integer 0..32767>
The consistency check is aborted when the specified number of errors have occurred. The conflicts encountered before the function is aborted are output, provided ERROR-INFORMATION = *DETAIL was specified. 32767 is the default value.
MONJV =
Specifies a job variable used for monitoring.
MONJV = *NONE
Default value: no monitoring job variable is specified.
MONJV = <filename 1..54 without-gen-vers>
Specifies the name of the monitoring job variable. It must already be cataloged in an accessible pubset and must not be password-protected.
The job variables’ status display is set as follows during the consistency check:
$I | at the start of the consistency check |
| $R | at the end of the consistency check if consistency exists |
| $E | at the end of the consistency check if consistency does not exist |
| $A | in the event of an incomplete consistency check |
There is no point in specifying this operand unless you are using the software product JV.
If the job variable is to receive defined contents when execution of the function is started, the user must initialize this variable him/herself. If the function is aborted right at the start of execution, e.g. because a semantic error is detected, SMPGEN does not provide a value for the job variable.
ERROR-INFORMATION =
Controls the scope of the error information output in text and/or variable form.
ERROR-INFORMATION = *DETAIL
Default value: detailed error information is to be output. Not only is the number of name conflicts output, but also all names that occur more than once or names that are too long are listed.
In interactive mode, screen masks are output to the terminal that offer the option of suppressing follow-up screens or detail screens, or to switch to SYSLST (see section“Outputs to screen masks”).
In batch mode and to SYSLST, the output is made in the same format, but here there is no possibility of intervening.
ERROR-INFORMATION = *SUMMARY
No detailed error information is to be output, i.e. no lists of name conflicts but only the number of conflicts in the various name classes.
EXECUTION-MODE =
Specifies whether the function is to be executed in the current task or in a new batch task to be created.
EXECUTION-MODE = *SYNCHRONOUS(...)
Default value: the function is to be executed in the current task.
TEXT-OUTPUT =
Controls the output destination for data output in text format, i.e. lists, logging and error messages.
TEXT-OUTPUT = *STD
Default value: the output is to be carried out according to default setting. In interactive mode, output is to SYSOUT and to SYSLST. In batch mode, output is to SYSLST.
TEXT-OUTPUT = *SYSOUT
Output is directed to SYSOUT. This specification may only be made in interactive mode. SYSOUT may not have been reassigned to a file.
If SYSOUT output is desired, screen masks are output and these must be confirmed by pressing the send key. If numerous errors occur, it is possible to apply or suppress a detailed error log for SYSLST later.
TEXT-OUTPUT = *SYSLST
Output is directed to SYSLST.
TEXT-OUTPUT = *NONE
No outputs in the form of lists or messages are desired. It makes sense to specify this value when the STRUCTURE-OUTPUT operand is used instead.
Error messages and messages reporting the start and success of the function cannot be suppressed; they are output to SYSOUT even if TEXT-OUTPUT=*NONE is specified.
STRUCTURE-OUTPUT =
Directs output of error information to S variables.
STRUCTURE-OUTPUT = *SYSINF
Default: the error information is to be output to an S variable to which the user has assigned the variable stream SYSINF.
If this variable stream is not active, no output is made to an S variable.
STRUCTURE-OUTPUT = *NONENo output is made to an S variable.
STRUCTURE-OUTPUT = <composed-name 1..100>
Specifies the S variables in which the error information is to be stored.
The user must declare the variable as a dynamically defined structure (/DECLARE-VARIABLE ..., MULTIPLE-ELEMENTS=*LIST,TYPE=*STRUCTURE).
EXECUTION-MODE = *ASYNCHRONOUS(...)
The function is to be executed in a new batch task that is to be created. In this case, information output to an S variable is not supported.
TEXT-OUTPUT =
Controls the output of lists, logging and error messages.
TEXT-OUTPUT = *SYSLST
Output is made to a spoolout file that is printed at the end of the job and then deleted. The name of the spoolout file corresponds to the default setting of the SYSLST file for ENTER tasks.
TEXT-OUTPUT = <filename 1..54 without-gen-vers>
The text is to be output to the specified file. If the file already exists, the user must hold the appropriate write access right. The file must not be password-protected. It must be accessible locally and must not be a temporary file. The file is neither printed out nor deleted at the end of the job.