How to set Global Defaults as the execution default so the hlq.CDBAPARM member DEFAULTS settings are in effect for anyone using the Database Management Solutions for Db2 for z/OS tools.
An advantage of using the Global Defaults administration facility is the flexibility to have different defaults defined for various subsystems. For example, if you use the Interactive SQL facility,
you specify if SQL changes should be committed or rolled back. You could specify the default for SQL changes on a test subsystem to be committed, but have all SQL rolled back for your
production subsystem. This facility allows you to specify defaults for individual users or groups of users for variables previously stored in the ISPF profiles. The default values will be saved inside
a Db2 table on a per-subsystem basis.
Set the DEFAULTS option in the hlq.CDBAPARM member SETUPxx to DEFAULTS (YES). This option is specified in the header of the SETUPxx member.
COMPANY (xxxxxxxx)
WORKUNIT (SYSDA)
FULLMENU (YES)
ASSEMBLR (ASMA90)
DEFAULTS (YES) <----------------
SDI (NO)
.
.
.
The GLBLDEF command is used to access the Global Defaults Administration facility.
S USERID SSID LOCATION DESCRIPTION
CA-DB2 ssid LOCAL CA-DB2 PARMLIB DEFAULTS
PD* ssid LOCAL DEVELOPEMENT DEFAULTS
PDX* ssid LOCAL DEVELOPEMENT DEFAULTS FOR GROUP X
PDXPGMR ssid LOCAL DEFAULTS FOR USER PDXPGMR
TD* ssid LOCAL DEFAULTS FOR TECHNICAL WRITERS
-------------------------------------------------------------------------------
The Global Defaults Selection screen displays each row that represents a Global Defaults Definition. A Global Defaults Definition can apply to an individual
user or a group of users. For example in the screen above the definition PDX* applies to all userids that start with PDX. PDXPGMR applies to an individual user.
From this screen the defaults administrator can select a definition to be templated, updated or deleted. The defaults administrator can also view a definition after
it has been merged with higher applicable definitions. For example for the screen above the administrator could view the definition PDX* after it has been merged
with the definitions PD* and the base defaults.
For more information about the SETUPxx member options please refer to the Create a SETUP Global Parmlib Member