Can the Sysview PMO for DB2 for z/OS (IDB2) Data Collector STC be defined to Top Secret as a MULTIUSER address space instead of the prescribed (SUAS) Single User Address Space ?

book

Article ID: 39424

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

Question: 

If the Sysview PMO for DB2 for z/OS (IDB2) Vtam UI started task meets the criteria (as defined in the IDB2 System Reference Guide) to run as a MULTIUSER address space, and it shares the same FAC ID as the Sysview PMO for DB2 for z/OS (IDB2) Data Collector started task.  Will this Top Secret MULTIUSER definition have impact on the IDB2 Data Collector which should be run as a Single User Address Space (SUAS)?

Answer: 

The IDB2 Data Collector by design should run as a SUAS (Single User Address Space) for users never sign on to it, but instead, connect to the User Interface (UI) via TSO or VTAM.  If the VTAM UI started task meets the criteria to run as a MULTIUSER address space you will need to create a unique FAC ID for the VTAM UI started task to differentiate it from the IDB2 Data Collector ID.  The impact of running the Sysview PMO for DB2 for z/OS (IDB2) Data Collector started task as a MULTIUSER address space instead of as a Single User Address Space (SUAS) will be in Top Secret's unnecessary processing and overhead.  

 

Environment

Release:
Component: CIDB