Support Services Address Space overview
IBM Guardium S-TAP for Db2 uses a Support Services Address Space, also referred to as a Primary Address Space. Learn about how the Primary Address Space works, as well as the implications for using and stopping it.
A Support Services Address Space, also referred to as a Primary Address Space, starts for each z/OS® image after the first instance of IBM Guardium S-TAP for Db2, InfoSphere® Optim™ Query Workload Replay for Db2, or IBM Db2 Query Monitor for z/OS starts with a MASTER_PROCNAME value that is not yet in use on that z/OS image.
The Primary Address Space is a Service Address Space for all instances of IBM Guardium S-TAP for Db2, InfoSphere Optim Query Workload Replay for Db2, or IBM Db2 Query Monitor for z/OS that specify the same MASTER_PROCNAME parameter value that is running on the z/OS image. The Primary Address Space acts as a placeholder for shared collector resources, and is similar to other Primary Address Spaces that are used throughout MVS™. For sample, MVS and Db2 both have Primary Address Spaces.
- Never shuts down
- Does not run any code except for its initialization routines
- Owns resources that are needed by the shared collector
- Does not require a formal shutdown and should not be canceled or forced to shut down during the operation of IBM Guardium S-TAP for Db2, InfoSphere Optim Query Workload Replay for Db2, or IBM Db2 Query Monitor for z/OS.
- When forced to stop causes abnormal termination of all IBM Guardium S-TAP for Db2, InfoSphere Optim Query Workload Replay for Db2, and IBM Db2 Query Monitor for z/OS subsystems on the LPAR.
- Is different from the Db2 <Db2 Subsystem> MSTR address space. The Support Services Address Space is specified by the MASTER_PROCNAME parameter and created by the STAP-started task (which exists only for STAP for Db2 and is not related to the Db2 Subsystem).