|
The NEW PUBSETS command is used to check and note a new UDS/SQL pubset declaration. UDS/SQL checks again whether a valid UDS/SQL pubset declaration is available in the job variable with the LINK name UDSPS01. The check takes place immediately. However, the checked UDS/SQL pubset declaration only becomes effective with the next PERFORM (which will possibly be triggered internally).
If the DBH is running in interactive mode, the new UDS/SQL pubset declaration can be made known by assigning another job variable, however, in practice only a modification of the job variable content should be relevant in the case of a master task which is executing in the background.
Modification of the current UDS/SQL pubset declaration using DAL NEW PUBSETS is rejected if the new UDS/SQL pubset declaration does not cover the pubsets which were specified for LOG, LOG-2, RESERVE of RLOG logging and for DEFAULT-SUPPORT and RESERVE-SUPPORT of ALOG logging of every attached database.
The output after a successful check has the following layout:
UDS0220 UDS RECEIVED COMMAND: NEW PUBSETS (...,tsn4) UDS0746 UDS PUBSET DECLARATION (PENDING) FOLLOWS (...,tsn4) tsn4: UDS-PUBSET-JV: jv-name tsn4: PUBSETS: catidgroup_1 tsn4: PUBSETS: catidgroup_2 tsn4: PUBSETS: ... Once each for every catid group specified in the UDS/SQL pubset declaration. tsn4: DEFAULT PUBSET: <default catalog ID of the execution user ID> tsn4: ---------------------------------------------------------- UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND. (...,tsn4)
If no UDS/SQL pubset declaration is assigned, the catid group "*" is used. The following is output to distinguish this from an explicitly specified catid group "*":
UDS0220 UDS RECEIVED COMMAND: NEW PUBSETS (...,tsn4) UDS0747 UDS PUBSET DECLARATION NOT PRESENT, DEFAULT IS CATID * (PENDING) (...,tsn4) UDS0218 UUDS COMPLETED EXECUTION OF DAL COMMAND. (...,tsn4).
The assignment of a UDS/SQL pubset declaration job variable which only contains blanks is permissible; the Default Public Volume Set of the execution user ID is taken into account.
If an error is detected when the UDS/SQL pubset declaration is checked, the UDS/SQL pubset declaration which was previously valid continues to apply.
A DAL NEW PUBSETS command (also one containing errors) deletes any previous DAL NEW PUBSETS command which has existed since the last PERFORM.
Incorrect assignment of a pubset declaration job variable
The assignment of a non-existent or an inaccessible job variable or a job variable with the length 0 is rejected as follows:
UDS0220 UDS RECEIVED COMMAND: NEW PUBSETS (...,tsn4) UDS0752 UDS USER ERROR: ACCESS TO UDS-PUBSET-JV VIA JV-LINKNAME UDSPS01 FAILED (...,tsn4) UDS0209 UDS USER ERROR: COMMAND REJECTED ERROR IN UDS PUBSET DECLARATION (...,tsn4)
Additional information on the cause of the error may be provided in other messages. Content errors in the UDS/SQL pubset declaration are reported as follows depending on the type of error and the time at which it was detected:
Syntax errors which were detected during the syntactical analysis (identification of the catid groups):
UDS0220 UDS RECEIVED COMMAND: NEW PUBSETS (...,tsn4) UDS0748 UDS USER ERROR IN UDS PUBSET DECLARATION (SYNTAX): <reason> (...,tsn4)
where <reason> can have the following values:
CATID GROUP TOO LONG
TOO MANY CATID GROUPS
EXCLUDE CATID GROUP NOT ALONE
tsn4: UDS-PUBSET-JV: jv-name tsn4: UDS-PUBSET-JV-CONTENTS: tsn4: Content of the job variable may be distributed over several lines tsn4: ----------------------------------------------------------------- UDS0209 UDS USER ERROR: COMMAND REJECTED ERROR IN UDS PUBSET DECLARATION (...,tsn4)
Errors detected while the catid groups are being checked using the SDF macro CMDWCC:
UDS0220 UDS RECEIVED COMMAND: NEW PUBSETS (...,tsn4) UDS0749 UDS USER ERROR IN UDS PUBSET DECLARATION (SYNTAX) CATID GROUP REJECTED BY CMDWCC (...,tsn4) tsn4: UDS-PUBSET-JV: jv-name tsn4: PUBSETS: catid-group
For each catid group in which the CMDWCC macro detected a fault and which resulted in failure, up to 10 times.
If there are more than 10 catid groups with errors, only the first 10 are logged, and the line below is used to show that further catid groups with errors exist:tsn4: FURTHER ERRORS NOT SHOWN tsn4: ---------------------------------------------------------- UDS0209 UDS USER ERROR: COMMAND REJECTED ERROR IN UDS PUBSET DECLARATION (...,tsn4)
Errors detected while the catid groups are being checked using FSTAT:
UDS0220 UDS RECEIVED COMMAND: NEW PUBSETS (...,tsn4) UDS0749 UDS USER ERROR IN UDS PUBSET DECLARATION (SYNTAX) CATID GROUP REJECTED BY FSTAT (...,tsn4) tsn4: UDS-PUBSET-JV: jv-name tsn4: PUBSETS: catid-group, FSTAT-DMS-RC: xxxx
For each catid group in which FSTAT detected a fault and which resulted in failure. The catid group is output in its actual length; the line format is consequently variable.
tsn4: ---------------------------------------------------------- UDS0209 UDS USER ERROR: COMMAND REJECTED ERROR IN UDS PUBSET DECLARATION (...,tsn4)
- The new UDS/SQL pubset declaration does not cover the pubsets which were specified for LOG, LOG-2, RESERVE of RLOG logging and for DEFAULT-SUPPORT and RESERVE-SUPPORT for ALOG logging of every attached database:
UDS0220 UDS RECEIVED COMMAND: NEW PUBSETS (...,tsn4) UDS0755 UDS USER ERROR: CATID MISSING IN UDS PUBSET DECLARATION (NEW): <loginfo>: (...,tsn4)
The message may be issued several times.
<loginfo> specifies which catalog ID is missing for which logging object:
:catid: , RLOG
:catid: , RLOG-2
:catid: , RLOG-RESERVE
:catid: , ALOG-DEFAULT ,DB: <dbname>
- :catid: , ALOG-RESERVE ,DB: <dbname>
UDS0209 UDS USER ERROR: COMMAND REJECTED ERROR IN UDS PUBSET DECLARATION (...,tsn4)