New Filter Options for OMEGAMON For DB2 PE Application Trace Facility
GD1X_WAYNE_DRISCOLL 270005GD1X Visits (8302)
New Filter Options for Application Trace Facility
With APAR PI59278, the OMEGAMON for DB2 Performance Expert Application Trace Facility (ATF) introduces important filtering improvements. With these improvements, DBAs can more quickly zoom directly to problem areas, reducing the time needed to identify performance issues. With this APAR, not only are new filtering options supported, but existing options have been enhanced to improve usability.
The new filtering options are PACKAGE NAME, COLLECTION ID, PACKAGE LOCATION, WORKSTATION USERID, WORKSTATION NAME and CLIENT APPLICATION NAME. In addition, EXCLUDE options are supported for PLAN NAME, PACKAGE NAME, COLLECTION ID, PACKAGE LOCATION and AUTHORIZATION ID. Finally, all filter values that contain character strings can include wild card specification
Implementation of this change has resulted in a redesign of the ATF Trace Specification panel flow, adding a second panel of options. The first panel defines the trace collection data store, either a VSAM dataset or an in-memory field as well as the filter options.
Pressing enter will present the second panel, which contains the trace level details, as well as trace duration and scheduling opptions.
Pressing enter after this panel is displayed brings up the pre-filled option verification panel for confirmation before proceeding to start the trace. This is a display only panel and may require scrolling to see the full report, depending upon screen size and filter options specified.
This panel shows that for this trace, some of the new filters, PACKNAME, WSUSERID, WKSTN and APPNAME are being used. The package name filters show the use of wild carding, and the other fields show that these fields are mixed case, while the other fields are folded to upper case.
All string filter values now contain wild carding. The wildcard support follows the syntax rules of the DB2 –START TRACE command, so the wild card characters are either the under bar (“_”) or asterisk (“*”). The under bar matches one character in the requested location, while the asterisk will match all remaining characters. The asterisk can only be specified at the end of the string, it cannot be embedded within the string.
The workstation USERID, Workstation ID and Client Application name filters support mixed case, so the fields are case sensitive.
The exclude options allow the user to specify that certain filter options specify “everything but” filtering, for example If you have a plan that had changes to all but three of the packages, you can use the exclude flag to collect records for all packages in the plan selected, except for the three specified. If “Y” is specified, the corresponding filter needs to be specified. In addition, the exclude option for the plan name is only valid if specific plan names are specified, but invalid if PLANNAME=ALL is specified.
Multiple Value Fields
The DB2 –START TRACE command limits the filter fields so that only one field can support multiple values, for example if two plans are specified, only 1 (or zero) package names, collection ID’s, package locations and authorization ID’s can be specified. The panel processing checks for this, to reduce errors when the trace is started.
With these improvements in flexibility and usability, not only can DBAs pinpoint potential performance problems quicker, but the amount of trace data produced by DB2 can be reduced which could improve overall system performance.
(Trademarks: IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. A current list of IBM trademarks is available on the Web at http