Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Permitted functions

&pagelevel(4)&pagelevel

The range of functions permitted depends on the following questions:

  • Is the original database or shadow database involved?

  • Is the database or shadow database being processed by the DBH?

  • Is the database consistent?

  • Has AFIM logging been enabled?

Functions that are not permitted are not shown in the SDF mask.

The set of functions permitted may change in the course of a BMEND run, since BMEND statements can have an effect on consistency and AFIM logging.

Consistency point information can always be output at any time.

The KILL-LOG statement is only permitted for inconsistent databases. This statement is required for a database warm start without logging.

List of special cases

  • Original database with active DBH:

    UPDATE-DATABASE
    Concurrent updating with a session is only allowed for realms that are detached according to DBDIR-AK0.

  • Inconsistent original database with AFIM logging and without active DBH:

    ADD-REALM
    REMOVE-REALM
    START-LOG
    STOP-LOG
    Rejected if not preceded by an UPDATE-DATABASE statement to create a consistent database.

  • Consistent original database without AFIM logging and without active DBH:

    ENABLE-ONLINE-COPY
    Only permitted if the START-LOG statement has already been issued

  • Shadow database with active DBH:

    UPDATE-DATABASE
    Concurrent updating with a session is only allowed for realms that are detached according to DBDIR-AK0.

  • Inconsistent shadow database without active DBH:

    ADD-REALM
    REMOVE-REALM
    Rejected if not preceded by an UPDATE-DATABASE statement to create a consistent database.