SA z/OS : unable to view DB2 MSTR APL under DISPSTAT panel

Answer

Determined following error condition when reviewing customer log:

AOF867I WARNING: VALUE DB2S1 FOR KEYWORD SUBID INVALID - "SUBSYSTEM DBAUMSTR DISCARDED"

Client had defined an improper value for the DB2 Subsystem ID for the DB2 MSTR APL region in SA policy. The subsystem id was "DB2&SYSCLONE." which resolved to 5 characters once the parmlib symbol was evaluated. This is contrary to DB2 as the subsystem id is limited to 4 characters.

Following is the help on the panel if defining DB2 subsystem id:

All characters must be alphabetic, numeric, or one of @, #, or $. The first character must not be numeric. Two system and/or system automation symbols(&AOCCLONEx.) can be used. Without symbols the maximum length is 4 characters.

To define the DB2 subsystem id, go to the DB2 MSTR APL (ensure it is type=DB2 subtype=MSTR), and go to the "DB2 Control" section:

DB2 Control Entries

Entry Type : Application PolicyDB Name :
Entry Name : DB2_MASTER Enterprise Name :

Subsystem : DB2_MASTER
Subtype : MSTR defined in policy APPLICATION INFO

Subsystem ID . . . . . . . ____

Possible example values to code on the subsystem id line are:

DB2X (ie. a hardcoded value)
DB&SYSCLONE. (a system symbolic ; &SYSCLONE resolves to 2 characters)
DB2&AOCCLONE1. (ie. an SA symbolic ; &AOCCLONE1 resolves to 1 character)

Once customer corrected this definition the DB2 were operating properly under SA control.