PK14330: IMPROVED INTERNAL RESOURCE USAGE REPORT

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• The Internal Resource Usage report (IRUR) provides statistics on
  the use of various IMS pools and resources. By default one
  summary report is produced at end of run, unless a Minimum CHKP
  Interval option is specified, which might cause several sets of
  reports to be produced.
  An option is required to produce a report after each checkpoint
  encountered in the input log file.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Performance Analyzer.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: IMPROVED INTERNAL RESOURCE USAGE REPORT *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Internal Resource Usage report (IRUR) provides statistics
  on the use of various IMS pools and resources. By default, one
  summary report is produced at the end of a run, unless a
  Minimum CHKP Interval option is specified, which might cause
  several sets of reports to be produced. An option is required
  to produce a report after each checkpoint encountered in the
  input log file.
  

Problem conclusion

Temporary fix

Comments

• IRUR report options now include the PRINTAT(INTERVAL/STOP)
  keyword. This option takes precedence over the Global Report
  Option PRINTAT only for the IRUR report. The default of
  PRINTAT(STOP) will produce output at the end of run as per
  current functionality.
  PRINTAT(INTERVAL) will cause IRUR to produce report output at
  each checkpoint, subsequent to the initial checkpoint pair.
  (i.e. 1+'n' checkpoints encountered during the log duration
  will produce 'n' reports).
  The PRINTAT option is available only as a Batch option and
  is not available through the ISPF dialog.
  i.e. PRINTAT(INTERVAL) must be coded directly in the Batch JCL
  as per the following IPICMD input example:
  IMSPALOG INPUTDD(LOGIN),OUTPUTDD(RPTOUT),PAGESIZE(60),
  PRINTAT(STOP)
  IMSPALOG INMAX(0),OUTMAX(0),IGNORSEQ
  IMSPALOG IRUR(INCLUDE(IMSID(IMSA,IMSB)),PRINTAT(INTERVAL))
  IMSPALOG EXECUTE
  Additional resolved problems:
   Program Isolation Statistics
   - Incorrect Maximum Bytes ever used count.
   - Include Current Bytes used count.
   DL/I Cal Statistics
   - Transactions process count incorrect for APPC
   - Incorrect Retrieve Command calls count
   Scheduling Statistics
   - Incorrect Programs Scheduled count
   - PSB Pool Get/Free and PSB Work Area time format changed to
     increase precision to hh.mm.ss.msec, also handle overflow
     issues.
   Dispatcher Statistics
   - Time format changed to increase precision to hh.mm.ss.msec,
     also handle overflow issues.
   Logger Statistics
   - Incorrect WADS Track Groups and WAD Tracks
   Fixed Pool Usage Statistics
   - Incorrect High/Low Block and High/Low Buffer counts.
  

APAR Information

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

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

  UK09094 UK09095

Modules/Macros

• IPIPCO71 IPIPCO81 IPIPCO91 IPIPIR71 IPIPIR81
  IPIPIR91
  

Fix information

• Fixed component name

  IMS PERF ANALYZ

• Fixed component ID

  5655E1500

Applicable component levels

• R320 PSY UK09094

     UP05/11/16 P F511

• R330 PSY UK09095

     UP05/11/16 P F511

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.