Skip to Content

Checking or modifying the output groups

An output group is a collection of specifications that is used to collect and process data for writing to the LOGSET log file data sets for batch or historical reporting.

To check or modify the output group

  1. Select the Administration option from your product main menu.
  2. On the Administration menu, select 2 (DOMPLEX Option Sets).
  3. On the DOMPLEX Option Sets panel, type E next to the option set for which you want to modify option groups and press Enter.

  4. Expand the Output Groups section on the DOMPLEX option set panel (as shown in the following figure).

     File  Filter  Confirm  Help
                                       
                   AFDQA111 - AFDQA 11.1 PLEX FOR DBC/NGL
    Command ===>                                         Scroll ===> CSR
                                                        
    Filter: Off                                          More:     
    + DOMPLEX Parameters               Parameters that apply to entire DOMPLEX  
    + Data Collector List (1)          Data Collector(DBC) subsystems in DOMPLEX  
    + DB2 Monitor List (11)            DB2 Sub-systems to be monitored  
    - OutGp DCID DspSize (6)           Output Groups - valid range: 001-256
      - 011 N11J 20                     Dataspace buffer size: 1-2000 (MB)  
        + Data Classes                   Specify IFCIDs to be stored in this group
        + NGL LOGSET Parameters          LOGSET attributes used by this group
        DB2 Subsystem IDs. . . : *                                            
      + 012 N11J 20                     Dataspace buffer size: 1-2000 (MB)    
      + 013 N11J 20                     Dataspace buffer size: 1-2000 (MB)    
      + 014 N11J 20                     Dataspace buffer size: 1-2000 (MB)    
      + 015 N11J 20                     Dataspace buffer size: 1-2000 (MB)    
      + 016 N11J 20                     Dataspace buffer size: 1-2000 (MB)    
    *********************************** End of List *****************************

  5. Expand the group number that you want to edit.

    Warning

    Important

    If you need to create a new output group, type I on the - (minus) sign on the Output Groups section and press Enter.

    The new output group is created at the top of the list with the number 001. If the group number 001 is already in use, rename the group by typing a new unused value in the range 001- 256 over the 001 group number and pressing Enter

  6. Specify the following values:

    1. In the Group Number field, specify the number of the corresponding output group. Possible values are numbers in the range 001-256. In the Data Collector SSID field, specify the ID of the Data Collector that owns the output group.

      Only the data from Db2s that are running on the same system as that Data Collector are captured and stored by this output group. If you specify Db2s that are running on a different system, they are ignored.

    2. In the Data space size, specify the size of the data space (in megabytes) assigned to collect and process the data for this output group before it is written to the log files.

      Possible values are any number in the range 0-2000. The total amount of data space specified for all output groups defined to the same Data Collector cannot exceed 2 GB.

  7. Specify the IFCIDs that you want to capture and store in this output group:
    1. Expand the Data Classes section.

    2. Specify the values for the parameters shown in the following table. The valid values for each parameter are Y (Yes) or N (No).

      Name

      Description

      Related IFCIDs

      APERROR

      Specify whether to collect APPTUNE error data.

      Apptune/SQL Performance BMC IFCID:

      007—SQL Errors

      APOBJECT

      Specify whether to collect APPTUNE object summary data.

      Apptune / SQL Performance Object Statistics. BMC IFCIDs:

      008—SQL Statement/Object Cross-Reference
      009—Access Object Statistics

      APSTACC

      Specify whether to collect APPTUNE statement accounting interval data.

      Apptune / SQL Performance BMC IFCIDs:

      006—Interval Statistics
      307—SQL Statement Summary
      318—Filter Data

      APSTACCS

      Specify whether to collect APPTUNE statement accounting summaries data.

      Apptune / SQL Performance Accounting Statement
      Summary records: (BMC IFCIDs 308-310)

      APSTMT

      Specify whether 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

      DB2ACCT

      Specify whether to collect Db2 accounting data.

      Db2 accounting records. DB2 IFCIDS:

      003—Accounting
      239—Package Accounting DBRMs

      DB2AUDIT

      Specify whether to collect Db2 audit data.

      Db2 audit records. DB2 IFCIDs:

      140—Audit Authorization Failures
      141—Audit GRANTs and REVOKEs
      142—Audited Object DDL
      143—Audited Object First Write Attempt
      144—Audited Object First Read Attempt
      145—Audited Object DML at BIND
      146—User-Defined Audit Trace
      312—Audit Trail for DCE Security Processing

      DB2PERF

      Specify whether to collect Db2 performance data.

      Db2 Performance Records (all other DB2 IFCIDs)

      BMC AMI Ops Monitor for Db2
      - Data Collector IFCIDs:

      023-025—Utility Processing 1 
      090—Text of DB2 Command
      173—ASUTIME Exceeded
      125—RID List Processing

      DB2SYS

      Specify whether to collect Db2 statistics events data.

      Db2 system records. DB2 IFCIDs:

      001—System Statistics
      002—Database Statistics
      031—EDM Pool Full Condition
      054—Lock Contention
      102—Start Short on Storage
      103—End Short on Storage
      104—Log Data Set Names
      105—DBID/OBID Translate to Names
      106—System Parameters (DSNZPARM)
      107—Page Set OPEN/CLOSE
      172—Deadlock Detail
      196—Timeout Detail
      199—Data Set I/O Statistics
      202—Statistics Dynamic DSNZPARMS
      203—Heuristic Decision (DDF COMMIT/ABORT)
      204—Partner COLD START Detected
      206—SNA Compare States (CS) Protocol Error
      205—WARM START logname or syncpoint error
      206—SNA Compare States (CS) Protocol Error
      207—Heuristic Damage During CS Exchange
      208—SNA Syncpoint Protocol Error
      209—Syncpoint Communication Failure
      210—LOGNAME Changed on WARM START
      225—Storage Summary 1 
      230—Global Statistics
      232—Thread Entry or Exit from DB2
      233—Start/End Call Stored Procedure Server

      DCSYSTEM

      Specify whether to collect DATA Collector events data.

      Data Collector events. BMC IFCIDs:

      241—Command Response
      245—DB2 WTO Messages

      MVDBACC

      Specify whether to collect BMC AMI Ops Monitor for Db2
       - DC accounting summary data.

      BMC AMI Ops Monitor for Db2
       - Data Collector Accounting Summary Records (BMC IFCIDs 350-352)

      OPERTUNE

      Specify whether to collect OPERTUNEevents data.

      OPERTUNErecords (BMC IFCID 17)

      PAHIST 2

      Specify whether to collect BMC AMI Pool Advisorhistory data.

      BMC AMI Pool AdvisorHistory. 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)

        1 This IFCID is disabled by default. It can be used optionally for batch reporting. See the MainView for Db2 documentation for instructions on how to activate additional IFCIDs when you want to produce a report that requires them.

       2 If you are installing BMC AMI Pool Advisor or the BMC AMI Pool Advisor component of System Performance for the first time, ensure that the PAHIST data class is included in an output group for each Db2 that will be involved in BMC AMI Pool Advisor reporting.

  8. Specify the NGL LOGSET parameters associated with the output group.

    1. Expand the NGL LOGSET Parameters section.
    2. Specify the values described in the following table. These values define the LOGSETs that the NGL will use when collecting and archiving data.

    Parameter

    Description

    LOGSET compression

    Specify whether log file data will be compressed, and if so, to what degree.

    • A selection of LOW (default), is considered the optimal balance of compression and CPU usage.
    • A selection of HIGH will save more DASD space but use significantly more CPU (including zIIP usage where available).
    • A selection of NO disables compression, saving CPU usage at the expense of DASD space.

    LOGSET time span

    Specify the LOGSET time span in days (D), hours (H), or minutes (M).

    You can only specify one type of time D, H, or M. If you specify a number without a type, the value defaults to days.

    This value specifies the amount of time that you would like to have data kept in log files. If the log files are all filled up in less time than this target value, more log files will be allocated up to the Max LOGSET data sets specified.

    Max log buffers

    Specify the maximum number of log I/O buffers that are used. Valid values are from 2 through 20.

    Max read buffers

    Specify the maximum number of read I/O buffers that are used. Valid values are from 2 through 99.

    Deferred write time

    Specify the deferred write time. The deferred write time is the maximum time delay before buffered records are written to the DASD log files. Shorter deferred times mean less vulnerability to data loss in the event of an outage, but it requires more write I/Os. Valid values are from 1 through 999 seconds.

    Minimum log file data sets (LDS)

    Specify the minimum number of data sets to use in the LOGSET. The NGL agent will allocate this number of data sets at start up. Valid values are from 1 through 99.

    Maximum log file data sets (LDS)

    Specify the maximum number of data sets to use in the LOGSET. The NGL agent will allocate up to this number of data sets, as needed, to meet the retention goal specified in the LOGSET time specification. Valid values are from 1 through 99.

    Space to allocate (per LDS)

    Specify the total space used for the LOGFILE. This space is used to create each LOGFILE data set. Valid values are from 1 through 9999 MB.

    LDS allocation type

    Specify the type of allocation parameters to be used.

    • SMS means that DFSMS parameters will be used and at least one of the 3 SMS parameters (storage class, management class, data class) must be provided.
    • VOL means that a traditional VOLSER will be provided to indicate where the LOGFILE should be allocated.
    • NONE means that no allocation parameters will be provided and the system defaults will handle the details.

    LDS Volume

    Specify the volume for the LOGSET. This value is required if the allocation type is VOL; otherwise, this value is ignored.

    LDS DFSMS Data class

    (optional)

    Specify the DFSMS Data class for the LOGSET.

    You must specify one of the LDS DFSMS parameters if the allocation type is SMS. This parameter is ignored if the allocation type is not SMS.

    LDS DFSMS Management class

    (optional)

    Specify the DFSMS Management class for the LOGSET.

    You must specify one of the LDS DFSMS parameters if the allocation type is SMS. This parameter is ignored if the allocation type is not SMS.

    LDS DFSMS Storage class

    (optional)

    Specify the DFSMS Storage class for the LOGSET.

    You must specify one of the LDS DFSMS parameters if the allocation type is SMS. This parameter is ignored if the allocation type is not SMS.

    LDS DSN prefix

    Specify the DSN prefix for the LOGSET log file data sets.

    BMC recommends referencing the Data Collector ID and Output Group Number in the DSN prefix to make it unique (for example, BMCPERF.DC01.OG001).

    Enable Archiving

    Specify whether to enable LOGSET data set archiving. Valid values are Y (Yes) and N (No).

    For more information about archiving, see Additional-information-about-archiving-and-the-NGL.

    Archive Wait Time

    (optional)

    Specify the maximum time in seconds to wait for an archive to finish before reusing a LOGFILE. Allowed values are 1-9999 with the default value of 600 seconds.

    Archive post processing job

    (optional)

    Specify the member that contains the job that executes when the archive job is done. The data set that contains the member is defined by the DOMPARMS DD in the DBC started task.

    For more information about the post-processing job, see Additional-information-about-archiving-and-the-NGL.

    Max days to keep archives

    Specify the number of days that archive data sets are kept. You can specify 1 to 999 days, or specify 0 (zero) for no limit.

    Max numbers of archives to keep

    Specify the number of archived data sets that are kept. You can specify 1 to 999, or specify 0 (zero) for no limit.

    Max combined size of archives

    Specify the maximum DASD space usage allowed in all archives. You can specify 1 to 999999 MB, or specify 0 (zero) for no limit.

    Archive file Allocation type

    Specify the type of allocation parameters to be used.

    • SMS means that DFSMS parameters will be used. At least one of the three SMS parameters (storage class, management class, data class) must be provided. If you select this value, VOL and UNIT parameters are ignored.
    • VOL means that a traditional VOLSER will be provided to indicate where the LOGFILE should be allocated, and SMS parameters are ignored.
    • UNIT means that a traditional UNIT will be provided to indicate where the LOGFILE should be allocated, and SMS parameters

    Archive Volume

    (optional)

    Specify the volume for the archive.

    Archive DFSMS Data class

    (optional)

    Specify the DFSMS data class.

    Archive DFSMS Management class

    (optional)

    Specify the DFSMS management class for the archive.

    Archive DFSMS Storage class

    (optional)

    Specify the DFSMS storage class for the archive.

    Archive GDG

    Specify the GDG element to control whether ARCPREFIX or ARCDSN is the base name for a generation data group. Valid values are Y (Yes) and N (No).

    You must specify GDG as Y if the archive output data set is to be a member of a generation data group. The archive program will create a +1 version for the output data set.

    Archive DSN prefix

    (optional)

    Specify the DSN prefix for the NGL archive data set.

    Warning

    Important

    Instead of this field you can specify a fully qualified DSN for the archive by specifying an archive data set prefix in the Alternate full archive DSN option. The Archive DSN prefix and Alternate full archive DSN options are mutually exclusive.

    BMC recommends referencing the Data Collector ID and Output Group Number in the DSN prefix to make it unique (for example, BMCPERF.DC01.OG001). A sequence number prefixed by the letter A will be appended as the last node.

    Alternate full archive DSN

    (optional)

    Specify the fully qualified NGL archive data set name.

    Warning

    Important

    Instead of this field you can specify an archive data set prefix for the archive by using the Archive DSN prefix option. The Archive DSN prefix and Alternate full Archive DSN options are mutually exclusive.

    BMC recommends referencing the Data Collector ID and Output Group Number as well as using date and time symbolics to make the data set name unique each time (for example, BMCPERF.DC01.OG001.D&JDAY..T&HHMMSS).

  9. Specify the Db2 SSIDs associated with this group:
    1. Place your cursor on the > (greater than) sign next to Subsystems supported by this group and press Enter.

    2. At the Zoom panel, specify up to 63 Db2 SSIDs for the DB2 subsystems supported by this output group.

      You can also specify * to associate all Db2 subsystems in your Db2 Monitor List with this output group. Any Db2 subsystems that are running on a different system are ignored.

    3. Press F3 to return to the previous panel when finished.

Related topic

Verifying-or-customizing-the-DOMPLEX-option-set


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Common Db2 documents 12.1