Db2 and DDF Parameters

Detailed descriptions and default values for the parameters associated with the Strobe Db2 and DDF options are provided below.

DB2AUTOFILTER=YES

Description: Specifies whether Strobe automatically adds a filter to the Db2 trace started by the SSA to capture SQL results. Turning on this option decreases the overhead placed on the Db2 address space by the trace that the SSA starts, but limits the number of concurrent Db2 measurements per Db2 subsystem to a maximum of 8. If other traces are active per Db2 subsystem, this number may be less. You can override this option at the measurement level. Valid values are YES and NO.

Default: YES

COLLECT_DB2_PRED_DATA=DISABLE

Description: Specifies whether Strobe enables a measurement option to save the Db2 dynamic SQL literal information (for the most CPU intensive occurrence of each SQL statement) that is currently stripped out of the SQL during measurement. If the option is enabled and is requested at measurement time, the literal information that is removed is saved and put back into its original place within the SQL text prior to SQL Analysis and iStrobe reporting. Valid values are ENABLE and DISABLE. 

Warning

If this parameter is not enabled, then the ability to request this feature at measurement time is not available. Care should be taken when enabling this feature. See the Using-Strobe-options for additional information.

Default: DISABLE

DB2CONTYPE=RRSAF

Description: Specifies the connection type for Strobe's SSA to use to connect to Db2. Valid values are RRSAF and CAF.

Default: RRSAF

DB2SMOSIZE=2000

Description: Specifies the number of megabytes of 64-bit shared memory object used to pass information between the measured address space and the SSA process. 

Warning

Change the default value only under direction of BMC Support.

Default: 2000

DDFRQSTR

Description: Specifies the Strobe for Db2 DDF parameter that determines how SQL data is collected for the DDF SQL Statement by DBRM by Requester report. The requester is the remote source of the SQL that is executing in the DDF address space. You can assign any one or two of the following valid values in the REQUESTER1 and REQUESTER 2 subparameters:

  • REQLOC: Produces the DDF SQL Statement by DBRM by Requester report by location, which is either the IP address or LU name of the requester.
  • CORRID: Produces the DDF SQL Statement by DBRM by Requester report by correlation ID.
  • AUTHID: Produces the DDF SQL Statement by DBRM by Requester report by primary authorization ID.
  • EUUSER: End user’s user ID.
  • EUWORK: End user’s workstation.
  • EUTRAN: End user’s transaction.

Important

You can temporarily override the value of this parameter when submitting a measurement request by specifying a different value for DDFRQSTR in the OTHER PARAMETERS field on the  - Add Active Request panel. Refer to the Db2 section of the Using-Strobe-options for more information on the syntax for assigning the values.

Default: 

DDFRQSTR
REQUESTER1=REQLOC
REQUESTER2=AUTHID
END

IFITRACE=BOTH

Description: Controls the type of Db2 trace—and subsequently the type of reports—for Db2 and DDF applications. Valid values are BOTH, PERFORMANCE, and ACCOUNTING.

  • If set to BOTH, a Db2 performance and Db2 accounting trace is started. The SQL Activity reports for Db2 and the SQL Activity Summary report for Db2 are generated.
  • If set to PERFORMANCE, only a Db2 performance trace is started and only the SQL Activity reports for Db2 can be generated.
  • If set to ACCOUNTING, only a Db2 accounting trace is started and only the SQL Activity Summary report for Db2 can be generated. 
Warning

If all of the following conditions exist, the SQL Activity Summary report for Db2 will not be produced:

  • ACCOUNTING is specified for the IFITRACE parameter of the Strobe PARMLIB member and was not overridden when the measurement was submitted, or the value of the IFITRACE parameter was overridden by specifying A (Accounting) during measurement submission.
  • You are measuring a batch job that utilizes a Db2 RRSAF type connection.
  • The batch job name was not used as the correlation ID in the RRSAF SIGNON statement.

Default: BOTH

SQLATTR@SAMPLE=NO

Description: Specifies whether SQL statement information is provided in the Attribution of CPU Execution Time (#ACE) and Attribution of CPU Wait Time (#ACW) reports, and whether Strobe includes the SQL Wait Summary (#SWS) and Wait by SQL Statement (#WBS) reports in a profile. Providing this information may require significant system resources, particularly for Db2 applications with a considerable amount of SQL activity. Valid values are YES and NO.

Default: NO

SSA=YES

Description: Specifies whether to start the Strobe SQL Agent when Strobe is initialized. SSA is intended only for Strobe for Db2 when you want to analyze SQL statement counts and service time information. Valid values are YES and NO.

Default: YES

SSAPROCNAME=STRSSA

Description: Specifies the name of the PROC for the Strobe SQL Agent job name when SSA=YES. The default is STRSSA. Because this value is the Strobe SQL Agent authorization ID, if the value STRSSA is changed here in the Strobe PARMLIB member, it must also be changed to match in the Strobe allocation configuration member $07ALSTR and in the BIND/GRANT member SBDB2INS in the STROBE.hlq.SSTRSAMP. A user ID with the new value must also be added to the security system.

Default: STRSSA

SSADB2HOOK=NO

Description: Controls the method of SQL capture initiation. This value controls whether Strobe will install a Strobe Db2 SQL Intercept routine in Db2 to detect automatically the presence of SQL activity in applications being measured. The SQL Intercept code is implanted when the Strobe SQL Agent is initialized. If this keyword is not coded or the value specified is NO, the SQL Intercept code is not implanted in Db2 and a non-intrusive alternative method is used to detect the SQL activity. Valid values are YES and NO.

Default: NO

 

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