PM09536: MULTIPLE ISSUES BEING ADDRESSED WITH THIS APAR - SEE ERROR DESCRIPTION FOR DETAILS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Issues being addressed:
  1) FPxxxxx reports default to wrong DDNAME -
     Default DDNAMES for Fast Path reports are incorrect in IMS PA
     batch. ISPF dialog and manual are correct.
  2) IGNORSEQ not "sticking" when changed in Report Set -
     Unless a change is made at the Report Set level (IPIRSMNU),
     changes to the IGNORSEQ value in LOG Global Options may not
     be saved back to the report set without an explicit SAVE
     command.
  3) Many IPI316/317 messages even with IGNORSEQ specified -
     IGNORSEQ allows continued processing of the input data but
     issues many warning and informative messages.  Ignore should
     mean just that.
  4) Invalid numbers on form-based reports -
     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.
  5) IRUR does not count DBCTL transactions -
     The Internal Resource Usage Report does not count DBCTL
     transactions.
  Keywords: IPI0317W IPI0316I MSGIPI0317W MSGIPI0316I
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IMS Performance Analyzer V4.2       *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR is correcting the following:  *
  *                      1. FPxxxxx reports default to wrong     *
  *                      DDNAME.                                 *
  *                      2. IGNORSEQ not "sticking" when         *
  *                      changed in Report Set                   *
  *                      3. Many IPI316/317 messages even with   *
  *                      IGNORSEQ specified                      *
  *                      4. Invalid numbers on form-based        *
  *                      reports.                                *
  *                      5. IRUR does not count DBCTL            *
  *                      transactions.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1. Default DDNAMES for Fast Path reports are incorrect in
  IMS PA batch. ISPF dialog and manual are correct.
  2. Unless a change is made at the Report Set level
  (IPIRSMNU), changes to the IGNORSEQ value in LOG
  Global Options may not be saved back to the report
  set without an explicit SAVE command.
  3. IGNORSEQ allows continued processing of the input data
  but issues  many warning and informative messages.
  Ignore should mean just that.
  4. 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.
  5. The Internal Resource Usage Report does not count DBCTL
  transactions.
  

Problem conclusion

• The following changes have been made for the above problems:
  1. Correct monitor command processor to set correct default
  DDNAMES.
  2. Change the checksum technique to ensure all changed fields
  are recognised as changed.
  3. Bypass printing IPI316/317 messages when IGNORSEQ is
  specified.
  4. Change order of checks in x'35' record processing to ensure
  LSO is calculated correctly.
  5. Modify IRUR to better handle DBCTL logs.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• IPIACOMD IPIDSCRE IPIDSSAV IPIIPROC IPIMSGT
  IPIOCOMD IPIOLCRE IPIOLSAV IPIPMPA1 IPIPMPB1 IPIPMP71 IPIPMP81
  IPIPMP91 IPIRFSAV IPIRSCRE IPIRSSAV IPISIRUR IPISMCOP IPISMERG
  IPISPSCN IPIXSCRE IPIXSSAV
  

Fix information

• Fixed component name

  IMS PERF ANALYZ

• Fixed component ID

  5655E1500

Applicable component levels

• R420 PSY UK56101

     UP10/04/23 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.