Use of the UDS/SQL pubset declaration in the DBH

While the DBH is being initialized, any existing UDS/SQL pubset declaration is checked. The settings of an error-free UDS/SQL pubset declaration are recorded for further use.

If an error occurs in processing an allocated pubset declaration job variable while the DBH is being initialized, the session is terminated as the job variable can clearly not be used in the way that was intended.

It is recommended - especially in the case of a DBH which is running in the background - that you should assign a pubset declaration job variable in the start procedure because this cannot be done later from another task. If you do not want to restrict the pubsets which are to be taken into account, you can enter the default setting "*" in the pubset declaration job variable.

As a result you can modify the UDS/SQL pubset declaration for an active Independent DBH dynamically: enter the required UDS/SQL pubset declaration in the assigned pubset declaration job variable and then allocate the updated UDS/SQL pubset declaration using DAL NEW PUBSETS.

When defining a UDS/SQL pubset declaration, ensure that all the pubsets required for the application are entered so that no error occurs during operation. This applies in particular for the specifications regarding the location of the logging file made with load parameters (LOG, LOG-2 or RESERVE) or DAL commands (LOG, LOG-2 or RESERVE).

The effects of inconsistent specifications here are cushioned by means of the following measures:

• The DBH is not started if one of the RLOG logging specifications PP LOG, PP LOG-2 or PP RESERVE is outside the pubset space of the current UDS/SQL pubset declaration.

• A modification of the RLOG logging specifications using DAL MODIFY LOG, MODIFY LOG-2, or MODIFY RESERVE is rejected if the new specification is outside the pubset space of the current UDS/SQL pubset declaration or outside the pubset space of a new UDS/SQL pubset declaration which has already been specified using DAL NEW PUBSETS but has not yet been activated by PERFORM.

• A database cannot be attached if one of the ALOG logging specifications which were defined using the DEFAULT-SUPPORT or RESERVE-SUPPORT parameter of the BMEND statement START-LOG is outside the pubset space of the current UDS/SQL pubset declaration.

• Modification of the current UDS/SQL pubset declaration by means of DAL NEW PUBSETS is rejected if the new UDS/SQL pubset declaration does not include the pubsets which are predefined for LOG, LOG-2, RESERVE of RLOG logging and for DEFAULT-SUPPORT and RESERVE-SUPPORT of ALOG logging for each attached database.

The settings of a faulty UDS/SQL pubset declaration are logged. You can display the current UDS/SQL pubset declaration using DAL DISPLAY PUBSETS.