Checklists for installing and customizing Application Performance Analyzer

To customize Application Performance Analyzer, complete the tasks in the following checklist.

  1. If you ordered Application Performance Analyzer using the Custom-Built Product Delivery Offering (CBPDO), follow the steps in the IBM Application Performance Analyzer for z/OS® Program Directory for installation. (If Application Performance Analyzer is delivered through a ServerPac, the installation is completed for you.)
  2. Ensure that security access is configured.
  3. Place SCAZLINK in the LNKLST.
  4. Enable the Application Performance Analyzer system exits.
  5. APF-authorize libraries hlq.SCAZAUTH and hlq.SCAZLINK.
  6. Modify the TSO/E logon procedure.
  7. Choose a started task instance identifier.
  8. Make the Application Performance Analyzer-started task available.
  9. Create installation-level settings and settings for the started task.
  10. Pre-allocate a checkpoint file and common data store file (optional).
  11. Create your own descriptive program attribution table (optional).
  12. Modify Application Performance Analyzer procedure to provide access to third party repository products for source program mapping support (optional).
  13. Start the Application Performance Analyzer-started task.
  14. Start Application Performance Analyzer.
  15. Run an IVP to verify the customization of Application Performance Analyzer (optional).

J9VM Checklist

If you plan to use Application Performance Analyzer to measure Java™ applications, you must choose between using a dynamically loaded JVMTI agent and using a preloaded JVMTI agent. Depending on which one you choose, you might have to perform some or all of the following customization tasks:
  1. APF authorize the Application Performance Analyzer USS files.
  2. Assign USS permissions to the Application Performance Analyzer started task.
  3. Set up J9VM related security rules.
  4. Update the J9VM related started task configuration settings.
  5. Enable the Java Attach API (for a dynamically loaded JVMTI agent) or specify a preloaded JVMTI agent.
Further details are found in Customizing Application Performance Analyzer for use with J9VM.

Application Performance Analyzer Problem Determination Tools Common Component Extension Checklist

If the Application Performance Analyzer Graphical User Interface (GUI) plug-in is to be used in your organization, you must first complete the installation of Application Performance Analyzer and the Problem Determination Tools common component (PDTCC). Then perform the following steps to customize the Application Performance Analyzer PDTCC extension:

  1. Choose a high-level qualifier for the data sets created by the Application Performance Analyzer PDTCC extension.
  2. Establish external security.
  3. Configure the Application Performance Analyzer PDTCC extension CONFIG settings.
  4. Customize the PDTCC server for the Application Performance Analyzer PDTCC extension.
  5. Activate the Application Performance Analyzer PDTCC extension.
Further details are found in Customizing the Application Performance Analyzer Problem Determination Tools Common Component Extension.

Application Performance Analyzer Plug-in for Eclipse Checklist

Perform the following steps to install the Application Performance Analyzer GUI plug-in on each client:
  1. Verify that the Application Performance Analyzer PDTCC extension is installed and activated.
  2. Obtain the Problem Determination Tools Common Server host address and port.
  3. Determine the default Application Performance Analyzer started task to which you will connect.
  4. Obtain the appropriate Problem Determination Tools Readme PDF and product .zip file from the IBM® Problem Determination Tools download website. http://www-01.ibm.com/software/awdtools/deployment/pdtplugins/
  5. Install the appropriate Problem Determination Tools product or package, following the instructions in the Readme PDF.
Further details are found in About the Application Performance Analyzer Plug-in for Eclipse.

DB2 Checklist

If you plan to use the DB2® EXPLAIN feature, want to report plan and package BIND timestamps, or want to display actual host variable names in SQL statements, you must complete the following steps:
  1. Choose a unique authorization ID.
  2. Create and bind a DB2 access package and plan.
  3. Create a PLAN_TABLE.
  4. Provide DB2 authorization.
  5. Update the started task JCL.
  6. Update the started task configuration settings.

Further details are found in Customizing Application Performance Analyzer for use with DB2 Universal Database.

WebSphere Application Services (WAS) Checklist

Application Performance Analyzer provides a feature to measure applications running under WebSphere® Application Services by capturing SMF type 120 subtype 9 records. If you plan to use Application Performance Analyzer to measure applications running under WebSphere Application Services, you must also perform the following additional customization tasks:

  1. Add SAF FACILITY class authorities for CAZ00993
  2. Add RACF® authority for EMCS consoles
  3. Add SMF exit CAZ00993 to LNKLST
  4. Enable IEFU83 SMF record exit
  5. Calculate above-the-bar common storage required
  6. Determine who can measure applications running under WebSphere Application Services and then assign the internal access rule UseWAS or RACF external access rule USE.WAS to the appropriate users.
  7. Determine how recording of SMF type 120 subtype 9 and 10 records is controlled. You may turn this trace on permanently, or you may direct Application Performance Analyzer to start and stop the trace as needed.
  8. Update CONFIG SAMPLE setting to turn on the WAS extractor and enable SMF capture and/or recording.
  9. Update CONFIG SAMPLE setting to assign a value to the MemObjSize keyword.
  10. Start of changeUpdate CONFIG SAMPLE setting to enable the WLM Intercept (WLMI=YES), and ensure WebSphere Application Services for z/OS uses WLM for workload queuing (server_use_wlm_to_queue_work=1).End of change

Further details are found in this chapter and in Customizing Application Performance Analyzer

DB2 SMF Accounting Trace Checklist

Application Performance Analyzer provides a feature to capture DB2 accounting data from SMF type 101 records during measurement of applications with the DB2+ data extractor selected. This data will be reported in the Application Performance Analyzer reports, for example, the F20 DB2 Class 3 Wait Times report. If you want Application Performance Analyzer to capture and report SMF DB2 accounting data, you must also complete the following additional customization tasks:

  1. Add SAF FACILITY class authorities for CAZ00994.
  2. Add RACF authority for EMCS consoles.
  3. Add SMF exit CAZ00994 to LNKLST.
  4. Enable IEFU84 SMF record exit.
  5. Calculate above-the-bar common storage required.
  6. Determine how the DB2 accounting trace is controlled. You may turn this trace on permanently or you may direct Application Performance Analyzer to start and stop the trace as needed. If you want Application Performance Analyzer to stop and start the trace, ensure the Application Performance Analyzer started task has DB2 TRACE privileges or DB2 authorization to issue TRACE commands.
  7. Update CONFIG SAMPLE setting to turn on the DB2I extractor and enable SMF capture and/or recording.
  8. Update CONFIG SAMPLE setting to assign a value to the MemObjSize keyword.
  9. Set the DSNZPARM ACCUMACC parameter to NO to improve the accuracy of DB2 Class 3 Wait Times report for DDF and RRSAF threads.

Further details are found in this chapter and in Customizing Application Performance Analyzer

Parent topic: Preparing to customize Application Performance Analyzer