Error messages and the message relating to the start of the function, as well as the concluding success message are routed to the same output destination as the information on inconsistencies, i.e. to the output destination(s) specified by TEXT-OUTPUT.
In interactive mode, the message relating to the start of the function and the success message are also output to SYSOUT if TEXT-OUTPUT=*SYSLST is specified.
If the information on inconsistencies is not output in text form (TEXT-OUTPUT=*NONE), the error messages, the message relating to the start of the function, and the concluding success message are output to SYSOUT.
The following information is output:
Table of affected pubsets along with disk format, allocation unit (DRV, DUALCOPY), maximum I/O length and flag indicating whether a cache is defined. (For further information on the cache definition, use
/SHOW-PUBSET-PARAMETERS.)Refer to mask 1 in section "Outputs to screen masks" for format details. This mask provides the user with the option of canceling the function by making an appropriate entry in the footer.
Logging messages:
Result message (consistency check successful or not).
The result message is always output to SYSOUT in interactive mode, independent of the TEXT-OUTPUT operand.In special cases, or in the event of termination on error, further messages may be issued first.
If the user is privileged, the size of the old pubset administration files is output in order to be able to estimate the space required for the new control volume set; and for specification of the control volume set ID also the free space required on the pubset to be used.
In the event of an error, or if warnings are issued, before the result message is output the following takes place
(If STRUCTURE-OUTPUT was specified, the information is stored in S variables, regardless of the required scope of information).for ERROR-INFOMATION=*SUMMARY:
Number of files, job variables and guard name conflicts
In the case of file generation groups, only the conflicts of the group names, not those in the individual file generations, are counted.
Number of file names and job variable names that are too long
For file generation groups, only the generation group, not the individual file generations, are counted.
Number of guard conditions that could not be automatically adapted to the new pubset ID (warnings)
for ERROR-INFORMATION=*DETAIL, detailed error information is output:
Lists of name conflicts
For file generation groups, only the generation group is given; the conflicts for the individual file generations are not reported and not counted. See masks 3-8, starting on "Outputs to screen masks" for details of the list formats.
Lists of the file and job variable names that are too long
For file generation groups, only the generation group is given (with addition: FGG); the conflicts for the individual file generations are not given and not counted. See masks 9-10, starting on "Outputs to screen masks" for details of the list formats.
List of guard conditions that cannot be matched to the new pubset ID automatically. See mask 11 in section "Outputs to screen masks" for details of the list format.
Regardless of the required scope of information, the following error information is output for the privileged user (before all other error information):
If one of the pubsets contains files migrated to S1 and S1-MIGRATED-FILES=*ALLOWED was not specified, an error message is returned (one message for each pubset affected).
List of illegal files
This refers to the files mentioned in the previous statement descriptions, which must not be cataloged in the pubsets because SMPGEN creates work files or new administration files under this name. See mask 2 in section "Outputs to screen masks" for details of the list format.
The following table explains the names and contents of the S variables. For further information on S variables, refer to the “Commands” manual [1 (Related publications)], volume 1.
Output information | Name of the S variable | T | Contents | Condition |
|---|---|---|---|---|
Multiple occurrence of file name without catalog ID and user ID | var(*LIST).F.CONFL(*LIST).F | S | " | INF=*DETAIL |
Number of checked pubsets on which the multiple file exists | var(*LIST).F.CONFL(*LIST).NUM-OF- | I | " | INF=*DETAIL |
Catalog ID of relevant pubset | var(*LIST).F.CONFL(*LIST).PUBSET(*LIST). | S | " | INF=*DETAIL |
User ID of multiple file name | var(*LIST).F.CONFL(*LIST).USER-ID | S | " | INF=*DETAIL |
Catalog ID of file name that is too long | var(*LIST).F-LEN.ERROR(*LIST).CAT-ID | S | " | INF=*DETAIL |
File name that is too long without catalog ID and user ID | var(*LIST).F-LEN.ERROR(*LIST).F | S | " | INF=*DETAIL |
Flag to indicate whether or not it is a file generation group (Y) or (N) | var(*LIST),F-LEN.ERROR(*LIST).FGG-IND | S | Y | INF=*DETAIL |
Number of characters in the file name that exceed the maximum of 54 (with catalog ID) | var(*LIST).F-LEN.ERROR(*LIST).NUM-OF- | I | " | INF=*DETAIL |
User ID of the file name that is too long | var(*LIST).F-LEN.ERROR(*LIST).USER-ID | " | INF=*DETAIL | |
Number of file names that are too long | var(*LIST).F-LEN.NUM-OF-ERRORS | I | <integer> | INF=*DETAIL/ |
Number of file name conflicts | var(*LIST).F.NUM-OF-CONFL | I | <integer> | INF=*DETAIL/ |
Number of cases in which a guard condition is not automatically matched to the new pubset ID | var(*LIST).GUARD-COND.NUM-OF-WARN | I | <integer> | INF=*DETAIL/ |
Catalog ID of the guard where guard condition does not match | var(*LIST).GUARD-COND.WARN(*LIST). | S | " | INF=*DETAIL |
Name of the guard where the guard condition does not match, without catalog ID and user ID | var(*LIST).GUARD-COND.WARN(*LIST). | S | " | INF=*DETAIL |
Reason for not automatically matching the guard condition | var(*LIST).GUARD-COND.WARN(*LIST). | S | " | INF=*DETAIL |
User ID of the relevant guard | var(*LIST).GUARD-COND.WARN(*LIST). | S | " | INF=*DETAIL |
Name of the relevant guard which occurs more than once without catalog ID and user ID | var(*LIST).GUARD.CONFL(*LIST).GUARD | S | " | INF=*DETAIL |
Number of checked pubsets on which multiple guards exist | var(*LIST).GUARD.CONFL(*LIST).NUM-OF- | I | " | INF=*DETAIL |
Catalog ID of the relevant pubset | var(*LIST).GUARD.CONFL(*LIST). | S | " | INF=*DETAIL |
User ID of the relevant guard | var(*LIST).GUARD.CONFL(*LIST).USER-ID | S | " | INF=*DETAIL |
Number of guard name conflicts | var(*LIST).GUARD.NUM-OF-CONFL | I | <integer> | INF=*DETAIL/ |
Path name of the impermissible file | var(*LIST).INADMIS.F(*LIST) | S | " | INF=*DETAIL/ |
Number of file name conflicts (0 if check carried out by a nonprivileged user) | var(*LIST).INADMIS.NUM-OF-ERRORS | I | <integer> | INF=*DETAIL/ |
Name of job variable that occurs more than once without catalog | var(*LIST).JV.CONFL(*LIST).JV | S | " | INF=*DETAIL |
Number of checked pubsets on which multiple job variables exist | var(*LIST).JV.CONFL(*LIST).NUM-OF- | I | " | INF=*DETAIL |
Catalog ID of the relevant pubset | var(*LIST).JV.CONFL(*LIST).PUBSET(*LIST). | S | " | INF=*DETAIL |
User ID of the job variable that occurs more than once | var(*LIST).JV.CONFL(*LIST).USER-ID | S | " | INF=*DETAIL |
Catalog ID of the JV name that is too long | var(*LIST).JV-LEN.ERROR(*LIST).CAT-ID | S | " | INF=*DETAIL |
Name of the JV that is too long without catalog ID and user ID | var(*LIST).JV-LEN.ERROR(*LIST).JV | S | " | INF=*DETAIL |
Number of characters in the JV name that is too long which exceed the maximum of 54 (with catalog ID) | var(*LIST).JV-LEN.ERROR(*LIST).NUM-OF- | I | " | INF=*DETAIL |
User ID of the JV name that is too long | var(*LIST).JV-LEN.ERROR(*LIST).USER-ID | " | INF=*DETAIL | |
Number of JV names that are too long | var(*LIST).JV-LEN.NUM-OF-ERRORS | I | <integer> | INF=*DETAIL/ |
Number of JV name conflicts | var(*LIST).JV.NUM-OF-CONFL | I | <integer> | INF=*DETAIL/ |