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 running under the IBM J9VM, you must also perform 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 Java Late attach API
Further details are found in Customizing Application Performance Analyzer for use with J9VM.

Listener Checklist

If the Application Performance Analyzer Graphical User Interface (GUI) is to be used in your organization, you must install and customize the Application Performance Analyzer Listener started task, and each user must install the GUI desktop application.

Perform the following steps to customize the Application Performance Analyzer Listener started task:
  1. Choose a Listener started task identifier.
  2. Choose a high-level qualifier for the Listener data sets. This can be the same high-level qualifier as the Application Performance Analyzer started task.
  3. Choose a TCP/IP port number on which the Listener will listen for client connections.
  4. Create security access rules for the Listener data sets.
  5. Assign priority to the Listener started task.
  6. Make the Listener started task available.
  7. If Application Performance Analyzer uses internal security to secure access to functions, update the installation-level configuration settings to allow use of the Listener.
  8. Create the Listener started task configuration settings.
  9. If Application Performance Analyzer uses an external security product to secure access to functions, add the new rule to allow use of the Listener.
  10. Start the Application Performance Analyzer Listener started task.
Further details are found in Customizing Application Performance Analyzer Listener.

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. Ensure all software prerequisites are in place.
  2. Obtain the Application Performance Analyzer Listener host address and port from your systems programmer.
  3. Determine the default Application Performance Analyzer started task to which you will connect.
  4. Obtain the Readme PDF and Application Performance Analyzer Plug-in for Eclipse .zip file from the IBM Problem Determination Tools Plug-ins website.
  5. Use the software installation function of your existing Eclipse-based desktop product to install the Application Performance Analyzer Plug-in for Eclipse.
Further details are found in About Application Performance Analyzer Plug-ins for Eclipse.

DB2 Checklist

If you plan to use the dynamic EXLAIN feature of Application Performance Analyzer, or want Application Performance Analyzer to report plan and package BIND timestamps, you must complete the following steps:

  1. Choose a unique authorization ID.
  2. Create and bind a DB2 UDB 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 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.

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 CAZ00993.
  2. Add RACF authority for EMCS consoles.
  3. Add SMF exit CAZ00993 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