Creating an output group

To create an output group

1. On the option set’s panel (see Creating a DOMPLEX option set), expand Output Groups.
2. On the Output Groups line, overtype I on the minus sign (-) and press Enter.

   • Type I on the - sign

   • Type R to replicate an existing Output Group and then type over the name with a new name

   • Type E to define a new instance using the default values.

   The new output group is displayed at the top of the list and is by default is numbered 001. However you can use any 3-digit number within the range. Each output group must have a unique number within the DOMPLEX set.

   Tip

   This step inserts a completely new output group. If you prefer repeating an existing output group, type R on the plus sign (+) next to that output group and press Enter.

   Doing so copies the new group under the original group and uses the same group number for both. Change the number for the new group to be unique.

3. To edit the parameters for the new output group, expand its group number.
4. In the Output Groups section, complete the following fields:

   Field	Description
   OutGp (Group Number)	Specify the number of the output group. Valid values are 001 through 256.
   DCID (Data Collector SSID)	Specify the subsystem ID of the Data Collector that owns the output group.
   DspSize (Data space size)	The recommended size depends on the types of data assigned to this group and the load expected for all types combined. The size is specified in megabytes in the range 0 to 2000. A value of zero causes all IFCIDs assigned to this group to be immediately discarded. Note The sum of data space for all output groups assigned to the same data collector cannot exceed 2000MB.

5. Expand the Data Classes section to specify the IFCIDs that this output group captures and stores.

   Data class	IFCIDs
   DCSYSTEM Specify Y to collect DATA Collector events data Note This information is also available from the SYSLOG, DB2 JESLOG, or DB2 IFCIDS	(BMC IFCIDs 241 and 245) Note Do not define an output group for DCSYSTEM unless recommended by BMC Customer Support.
   APSTACC Specify Y to collect APPTUNE statement accounting interval data.	APPTUNE/SQL Performance BMC IFCIDs: 006—Interval Statistics 307—SQL Statement Summary 318—Filter Data
   APSTACCS Specify Y to collect APPTUNE statement accounting summaries data.	APPTUNE/SQL Performance Accounting Statement Summary BMC IFCIDs: 305—MainView Application Summary 306—High Use Statement Summary 308–311—Statement Summary
   APSTMT Specify Y to collect APPTUNE statement text, host variables, and exceptions data.	APPTUNE/SQL Performance BMC IFCIDs: 004—SQL Exceptions 005—SQL Statement Text 010—Host Variables 011—Object Statistics per SQL Exception 012—Call stack info per exception
   APERROR Specify Y to collect APPTUNE SQL error data.	APPTUNE/SQL Performance BMC IFCID: 007—SQL Errors
   APOBJECT Specify Y to collect APPTUNE object summary data.	APPTUNE/SQL Performance Object Statistics. BMC IFCIDs: 008—SQL Statement/Object Cross-Reference 009—Access Object Statistics
   DB2ACCT 2 Specify Y to collect DB2 accounting data.	DB2 accounting records DB2 IFCIDs: 003—Accounting 239—Package Accounting DBRMs
   DB2SYS 2 Specify Y to collect DB2 statistics events data.	DB2 system records DB2 IFCIDs: 001—System Statistics 002—Database Statistics 105—DBID/OBID Translate to Names 107—Page Set OPEN/CLOSE 225—Storage Summary 1
   DB2AUDIT 2 Specify Y to collect DB2 audit data.	DB2 audit records DB2 IFCIDs: 140—Audit Authorization Failures141–Audit GRANTs and REVOKEs 142—Audited Object DDL 1 143—Audited Object First Write Attempt 1 144—Audited Object First Read Attempt 1 145—Audited Object DML at BIND 1 146—User-Defined Audit Trace 312—Audit Trail for DCE Security Processing
   DB2PERF 2 Specify Y to collect DB2 performance data.	DB2 performance records (all other DB2 IFCIDs) MainView for DB2 - Data Collector IFCIDs: 022 and 63 —Dynamic SQL Tracing 1 023-025—Utility Processing 1 090—Text of DB2 Command 125—RID List Processing 173—ASUTIME Exceeded
   OPERTUNE Specify Y to collect OPERTUNE events data. Note This data class applies only if you are using the OPERTUNE for DB2 product with another of the System and SQL Performance products	OPERTUNE records (BMC IFCID 17)
   PAHIST Specify Y to collect Pool Advisor history data.	Pool Advisor History. BMC IFCIDs: 072—DB2 Storage Usage Status 082—DB2 Page Set Access Statistics 086—DB2 Object Getpage Statistics 089—DB2 Object Getpage Event Trace 095—DB2 Dynamic Statement Cache Plan/DBRM (History) 096—DB2 Dynamic Statement Cache by Plan (History) 097—DB2 Dynamic Statement Cache by DBRM (History) 098—DB2 Dynamic Statement Cache by Corr ID (History) 099—DB2 Dynamic Statement Cache by Conn ID (History)
   MVDBACC Specify Y to collect MainView for DB2 - DC accounting summary data.	MainView for DB2 - Data Collector Accounting Summary Records (BMC IFCIDs 350–352)

    ^{1 This IFCID is disabled by default. It can be used optionally for batch reporting. F or instructions on how to activate additional IFCIDs when you want to produce a report that requires them, see Activating optional IFCIDs for batch reporting.}

    ^{2 Only valid for MainView for DB2}
   

6. Expand the NGL LOGSET Parameters section to specify the Next Generation Logger (NGL) LOGSET parameters for the output group. See the following table for a description of the NGL LOGSET parameters.

   Parameter	Description
   Logset Compression	Specify how to compress the log file data or to disable compression: LOW (default), is considered the optimal balance of compression and CPU usage HIGH saves more DASD space but use significantly more CPU (including zIIP usage where available) NO disables compression, saving CPU usage at the expense of DASD space
   LOGSET time span	Specify the amount of time that you would like to have data kept in log files, in days (D), hours (H), or minutes (M). You can specify only one type. If you specify a number without a type, the value defaults to days. If all of the log files become full in less time than this time span allows, more log files are allocated, up to the maximum allowed.
   Max log buffers	Specify the maximum number of log I/O buffers to use. Valid values are 2 through 20.
   Max read buffers	Specify the maximum number of read I/O buffers to use. Valid values are 2 through 99.
   Deferred write time	Specify the maximum time delay before buffered records are written to the DASD log files. A shorter deferred time requires more write I/Os but means less vulnerability to data loss if an outage occurs. Valid values are 1 through 999 seconds.
   Minimum log file data sets (LDS)	Specify the number of log file datasets that are allocated when the data collector starts. Valid values are 1 through 99.
   Maximum log file data sets (LDS)	Specify the maximum number of log file datasets that can be allocated as needed to meet the LOGSET time span goal. Valid values are 1 through 99.
   Space to allocate (per LDS)	Specify the total space used for each LOGFILE. Valid values are 1 through 9999 MB.
   LDS Allocation Type	Specify the type of allocation parameters to be used. SMS: DFSMS parameters are used and you must provide at least one of the SMS parameters (storage class, management class, data class) VOL: you must provide a traditional VOLSER to indicate where the LOGFILE should be allocated. NONE: you provide no allocation parameters and the system defaults are used
   LDS Volume	(mandatory if you select type volume) Specify the volume for the LOGSET.
   LDS DFSMS Data Class	(mandatory if you select type SMS) Specify the DFSMS data class for the LOGSET.
   LDS DFSMS Management class	(mandatory if you select type SMS) Specify the DFSMS management class for the LOGSET.
   LDS DFSMS Storage Class	(mandatory if you select type SMS) Specify the DFSMS storage class for the LOGSET.
   LDS DSN prefix	Specify the DSN prefix for the LOGSET (log file) data sets. Note Supports system static and dynamic symbols
   Enable Archiving	Specify Y to enable LOGSET data set archiving.
   Archive Wait Time	Specify the maximum time in seconds to wait for an archive to finish before reusing a LOGFILE. Allowed values are 1-9999, with a default of 600.
   Archive post processing job	(optional) Specify the data set that contains the job that will execute when the archive job is done.
   Max days to keep archives	Specify the number of days to keep archive data sets. Valid values are 1 through 999 days, or 0 which indicates no limit.
   Max number of archives to keep	Specify the number of archived data sets to keep. Valid values are 1 through 999 archives, or 0 which indicates no limit.
   Max combined size of archives	Specify the total space used by all archive data sets. Valid values are 1 through 999999 MB, or 0 which indicates no limit.
   Archive file allocation type	Specify the type of allocation parameters to be used. SMS: DFSMS parameters are used and you must provide at least one of the following SMS parameters (storage class, management class, data class) VOL: you must provide a traditional VOLSER to indicate where the LOGFILE should be allocated. UNIT: Specify any valid unit name NONE: you provide no allocation parameters and the system defaults are used
   Archive Volume	(mandatory if you select type volume) Specify the volume for the LOGSET.
   Archive Unit	(mandatory if you select type unit) Specify the unit for the LOGSET.
   Archive DFSMS Data class	(mandatory if you select type SMS) Specify the volume for the archive.
   Archive DFSMS Management class	(mandatory if you select type SMS) Specify the DFSMS management class for the archive.
   Archive DFSMS Storage class	(mandatory if you select type SMS) Specify the DFSMS storage class for the archive.
   Archive GDG	Specify Yes to configure the enabled DSN prefix (Archive DSN Prefix or the Alternate full archive DSN) as the base name for a generation data group. All members of the archive output data set are members of a generation data group (GDG).
   Archive DSN prefix	(optional) Specify the DSN prefix for the archive. 1
   Alternate full archive DSN	(optional) Specify the archive DSN. The product uses this value in place of the value defined as the Archive DSN prefix. You must ensure that the name is unique for each archive created. BMC suggests using date and time symbolics in the name. 1 Example For example: BMCPERF.D&YYMMDD.T&HHMMSS

    ^{1 Supports system static and dynamic symbols} 

   ^{The Archive DSN prefix and Alternate full archive DSN are mutually exclusive. Specify a value for one or the other.}
   

7. Enter DB2 subsystem names on the lines in the DB2 Subsystem IDs fields. Place your cursor on > (the greater-than sign) and press Enter to zoom to more fields to enter additional SSIDs.

   Note

   You must recycle the Data Collector, using the DOMSTOP and DOMSTART, or DOMREFRESH commands, to make your changes take effect.

   For more information regarding DOMSTOP, DOMREFRESH, and DOMSTART commands, see System and SQL Performance for DB2 Administrator Guide .