PM10094: PROVIDE REPORTING FROM EXTRA FIELDS PROVIDED BY OMEGAMON APPLICATION TRACE FACILITY

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Using online monitoring of OMEGAMON ATF data, customers want
  IMS PA reports to augment this.
  
  We are looking to produce Summary, List and Trace (summary and
  detail) reports, including CPU times, from the OMEGAMON ATF
  journals.
  This is based off FITS MR0206097533 and MR020609438.
  This is phase 2 of APAR PM00967.
  
  Additional issue addressed:
  ABEND0C4 showing in IPIIPROC x'45F8' LMOD is IPI4PROC
  Failure is on MVC D20710003054 as R3 cannot be obtained.
  Keywords: S0C4 ABENDS0C4
  
  This APAR is a retro-fit of IMSPA V420 APAR's PM07056 and
  PM09536.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IMS Performance Analyzer V4.1       *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. ABEND0C4 in IPIIPROC.                *
  *                      2. Invalid numbers on form-based        *
  *                      reports.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1. Log record x'47' not processed correctly for 'Protected
  Conversation'.
  2. Because not all IMS log records have a UTC-format timestamp,
  IMS PA tries to establish whether Leap Seconds  Offset
  should be applied to STCK times in log records by comparing
  the UTC and STCK over 3 x'35' log records.
  This was being incorrectly calculated in some circumstances,
  particularly when there was a delay in writing records to
  OLDS caused by the IMS Logger Structure usage exceeding
  90%; this caused there to be a gap of about 20 seconds
  between STC and UTC, but previous x'35' records had
  provided evidence that no LSO was to be applied. Once set,
  the value was used for subsequent transactions with
  consequent incorrect output.
  

Problem conclusion

Temporary fix

Comments

• 1. Correct handling of x'47' record.
  2. Change order of checks in x'35' record processing to
  ensure LSO is calculated correctly.
  

APAR Information

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

  PM07056

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

  UK55649

Modules/Macros

• IPIIPROC
  

Fix information

• Fixed component name

  IMS PERF ANALYZ

• Fixed component ID

  5655E1500

Applicable component levels

• R410 PSY UK55649

     UP10/04/02 P F004

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.