PK56005: DB2 LOG MERGED WITH IMS LOG TO PROVIDE IMPROVED DIAGNOSIS

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• This APAR introduces DB2 log file support in IMSPI to provide
  improved diagnostic capability for IMS transactions that use
  DB2.
  When merged with the IMS log file, DB2 and IMS events associated
  with IMS transactions can be viewed together in a single
  diagnostic session.
  Merging DB2 with IMS log data will allow you to:
  1. Track both IMS and DB2 events associated with an IMS
  transaction, to help determine whether DB2 is the cause of a
  problem in IMS.
  2. Measure DB2 and IMS event latencies that can be the cause
  poor performance.
  3. Investigate the type of DB2 activity undertaken by IMS
  transactions.
  4. Review update activity against DB2 databases.
  5. Identify the DB2 URID and LUW tokens associated with an IMS
  transaction, then use this information to investigate the
  problem further with tools like the DB2 Log Analyzer.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Problem Investigator V2.1   *
  ****************************************************************
  * PROBLEM DESCRIPTION: DB2 Log merged with IMS Log to provide  *
  *                      improved diagnosis.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR introduces DB2 log file support in IMSPI to provide
  improved diagnostic capability for IMS transactions that use
  DB2. When merged with the IMS log file, DB2 and IMS events
  associated with IMS transactions can be viewed together in a
  single diagnostic session.
  Merging DB2 with IMS log data will allow you to:
  1. Track both IMS and DB2 events associated with an IMS
     transaction, to help determine whether DB2 is the cause
     of a problem in IMS.
  2. Measure DB2 and IMS event latencies that can be the cause
     poor performance.
  3. Investigate the type of DB2 activity undertaken by IMS
     transactions.
  4. Review update activity against DB2 databases.
  5. Identify the DB2 URID and LUW tokens associated
     with an IMS transaction, then use this information
     to investigate the problem further with tools like the
     DB2 Log Analyzer.
  

Problem conclusion

Temporary fix

Comments

• This APAR has added new function as described above.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK32909

Modules/Macros

• ALZ##GLB ALZ##PRO ALZ##TRK ALZ#LFDS ALZ#NV21
  ALZ#PRIM ALZ#RTYP ALZBATCH ALZBRAPI ALZBRFMT ALZBRMIO ALZBRPRE
  ALZBRXCM ALZCDOLI ALZDB02W ALZEXEC  ALZFLDRV ALZFMDRV ALZFMNWP
  ALZIMSPA ALZLCAT  ALZLFMER ALZLRFIL ALZPOM   ALZPRDRV ALZPRIM
  ALZRXDSP ALZTRACK ALZULDRV ALZ4QMGR H28T210J
  

Fix information

• Fixed component name

  PRBLEM INVESTIG

• Fixed component ID

  5655K5000

Applicable component levels

• R210 PSY UK32909

     UP08/01/16 P F801

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.