PK60772: MQ LOG EXTRACT 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 Websphere MQ log file support in IMSPI to
  provide
  improved diagnostic capability for IMS transactions that use MQ.
  When merged with the IMS log file, MQ and IMS events associated
  with IMS transactions can be viewed together in a single
  diagnostic session.
  Merging MQ with IMS log data will allow you to:
  1. Track both IMS and MQ events associated with an IMS
  transaction, to help determine whether MQ is the cause of a
  problem in IMS.
  2. Measure MQ and IMS event latencies that can be the cause poor
  performance.
  3. Investigate the type of MQ activity undertaken by IMS
  transactions.
  4. Review messages PUT onto a queue, including Message
  Descriptor and text.
  5. For transactions that use both DB2 and MQ, the IMS, DB2 and
  MQ logs can be merged or provide the complete picture of
  transaction activity.
  Note that IMSPI does not support the native MQ log, requiring
  instead the extract created by the print log map utility
  CSQJU004.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Problem Investigator V2.1.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: MQ Log Extract merged with IMS log to   *
  *                      provide improved diagnosis.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR introduces Websphere MQ log file support in IMSPI to
  provide improved diagnostic capability for IMS transactions that
  use MQ. When merged with the IMS log file, MQ and IMS events
  associated with IMS transactions can be viewed together in a
  single diagnostic session. Merging MQ with IMS log data will
  allow you to:
  1. Track both IMS and MQ events associated with an IMS
  transaction, to help determine whether MQ is the cause
  of a problem in IMS.
  2. Measure MQ and IMS event latencies that can be the cause
  of poor performance.
  3. Investigate the type of MQ activity undertaken by IMS
  transactions.
  4. Review messages PUT onto a queue, including Message
  Descriptor and text.
  5. For transactions that use both DB2 and MQ, the IMS, DB2
  and MQ logs can be merged to provide the complete picture of
  transaction activity.
  Note: IMSPI does not support the native MQ log, requiring
  instead the extract created by the print log map utility
  CSQJU004.
  Additional new function provided by this APAR:
  1. Extract support for DB2 logs
  DB2 log files can now be extracted using the batch extract
  utility. Message ALZ0016E is no longer issued.
  Note that the DB2 records are reformatted into IMS log
  format and are not suitable for analysis by other DB2 utilities.
  2. Multiple file support for Extract function
  The SUB line action is enhanced to allow multiple files to be
  selected for any batch request, including extract.
  For example, the following line actions (SUB followed by = or
  another SUB command) will process both files in a single request
  ------------------------------
               Process Log Files
  Command ===>
  
  Select a Log File to browse.
  
  /        Log File
  SUB      'IMS.LOG'
  =        'DB2.LOG'
  ------------------------------
  
  The resultant JCL is:
  
  //IMSPI    JOB ,NOTIFY=&SYSUID
  //IMSPI    EXEC PGM=ALZBATCH,PARM=V910
  //STEPLIB  DD  DISP=SHR,DSN=ALZ.V2R1M0.SALZLINK
  //SYSPRINT DD  SYSOUT=*
  //L0001001 DD  DISP=SHR,DSN=IMS.LOG
  //L0002001 DD  DISP=SHR,DSN=DB2.LOG
  //EXTRACT  DD  DISP=SHR,DSN=JCH.EXTRACT
  //LOGRPT   DD  SYSOUT=*
  //SYSIN    DD  *
  EXTRACT
  Slash Astrick(end of JCL)
  
  The extract file will contain both IMS and DB2 records.
  

Problem conclusion

Temporary fix

Comments

• Code has been added in this APAR for Websphere MQ log
  file support in IMSPI.
  Code has also been added for Extract support for DB2 logs
  as well as Multiple file support for Extract function.
  

APAR Information

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

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

  UK36625

Modules/Macros

• ALZ##PRO ALZ#LFDS ALZ#LFOP ALZ#NV21 ALZ#PRIM
  ALZ#RTYP ALZ@PRIM ALZBATCH ALZBRAPI ALZBRFMT ALZBRPRE ALZBRXCM
  ALZB04   ALZDB02W ALZFLDRV ALZFMDRV ALZFMNWP ALZIMSPA ALZLCAT
  ALZLFINI ALZLFMER ALZMQ00M ALZPOM   ALZPRDRV ALZPRIM  ALZPRSUB
  ALZRXDSP ALZTRACK ALZULDRV ALZU002  H28T210J
  

Fix information

• Fixed component name

  PRBLEM INVESTIG

• Fixed component ID

  5655K5000

Applicable component levels

• R210 PSY UK36625

     UP08/06/10 P F806

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.