Use of Global Defaults within Database Management Solutions for Db2 for z/OS
search cancel

Use of Global Defaults within Database Management Solutions for Db2 for z/OS

book

Article ID: 13870

calendar_today

Updated On:

Products

DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS Database Management for DB2 for z/OS - Administration Suite Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Utilities Suite

Issue/Introduction

The Global Defaults administration facility is flexible and can define different defaults for various subsystems.

For example, if the Interactive SQL facility is used, the SQL changes option can specify if these should be
committed or rolled back. SQL changes can be specified as a default on a test subsystem to be committed,
but have all SQL rolled back for your production subsystem.

How to set Global Defaults as the execution default so that the hlq.CDBAPARM member DEFAULTS
settings are in effect for anyone using the Database Management Solutions for Db2 for z/OS tools.

Resolution

Set the DEFAULTS option in the hlq.CDBAPARM member SETUPxx to DEFAULTS (YES).
This option is specified in the header of the SETUPxx member thus:

COMPANY  (xxxxxxxx) 
WORKUNIT (SYSDA)
FULLMENU (YES)
ASSEMBLR (ASMA90)
DEFAULTS (YES)
SDI (NO)
...,

This facility allows for 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.

Additional Information

For more information about the SETUPxx member options please refer to the Installing section:
Creating and Editing Global and Product Parmlib Members, section Create a SETUP Global Parmlib Member.