Top Secret

Hello,

usually an Acid, that has  MODE(WARN) puts the user in Warn-Mode. This overides the facility or global mode.

This is nice. In practice all Fac have MODE(FAIL). For testing in a non production environment an Acids may get mode(WARN) to collect neccessary permissions.

But this does not work for DB2 Facilities

According to manual the DB2FAC Facility mode is evaluated before.

Manual:

======

The MODE option is used to set a global mode. Modes can be assigned to a specific subsystem facility, permitted to a specific ACID, or assigned by the ACTION keyword on a permission. The order of the search for MODE is:

    ACTION on a permission
    Subsystem facility (DB2FAC)
    User mode permission
    Facility
    Global

=======

Th DB2 Facility mode cannot be null. So it either defaults to FAIL or has other values. Only FAIL makes sense in normal operation. But it would be nice to allow a test-acid to overrule this similiar to other facilities.

Is there a good reason for this strange search order?

Hello Erwin,

It's due to the fact you cannot access to DB2 subsystem directly, you need to connect to DB2 thru a third address space.

Like TSO, CICS, IMS, BATCH, etc...  

E.g. if a user is logged on onto TSO in FAIL mode and DB2 FACILITY specifies MODE=WARN, then access to DB2 resources will be made in WARN mode, access to TSO resources will be made in FAIL mode.

Sincerely, Jacques.