IBM Support

Updates to IMS Buffer Pool Analyzer V1R4 User’s Guide

Product Documentation


Abstract

Updates that apply to IMS Buffer Pool Analyzer V1R4 User’s Guide (SC19-3980-00).

Content

The most recent updates appear at the top of the list.


Update 3
Date of change: July 2019
Change description: Documentation changes by APAR PI95633
Topics: Changes apply to multiple topics.

==============================

Topic: Gathering trace data > BPLTRACE started task parameters


The description of the IMSID parameter has been changed.

IMSID

The IMSID of an IMS DB/DC or DBCTL subsystem to be monitored. Either the IMSID or JOB parameter must be specified, but not both. When monitoring DEDB lookaside buffer pools, IMS RESLIB must be specified in STEPLIB/JOBLIB DD of the IMS subsystem or IMS RESLIB must be concatenated to LINKLIST.


==============================

Topic: Troubleshooting: Error messages

Messages BPL159E and BPL702E have been changed.
 

BPL159E DYNAMIC {ALLOCATION | CONCATENATION} FAILED RC=nn ERROR CODE=nnnn INFO CODE=nnnn
Explanation:
A failure occurred during dynamic allocation processing. The return code, error code, and information code are indicated in the message. This message follows the preceding BPL159I message: BPL159I DSN=dataset-name.
System action: Buffer Pool Analyzer ends the BPLTRACE task and the trace process.
User response: Review the reason for the dynamic allocation error. Contact IBM Software Support for assistance.
 

BPL702E BLDL FAILED FOR MODULE module
Explanation:
A BLDL for the named module failed.
System action: Buffer Pool Analyzer ends the BPLTRACE task and the trace process.
User response: The named module was not found in either the IMS control region STEPLIB/JOBLIB or LINKLIST. Contact IBM Software Support for assistance.


Update 2

Date of change: January 2019
Change description: Documentation changes regarding working under IMS Dynamic database buffer pools environment
Topics: Changes apply to multiple topics.

Topic: IMS Buffer Pool Analyzer overview > What does IMS Buffer Pool Analyzer do?

The following sentence has been added to the Product features section as the last item in the list:
 
IMS Buffer Pool Analyzer works under an IMS dynamic database buffer pools environment with several restrictions. For details, see "How to gather data" on page 26.

 

Topic: Gathering trace data > How to gather data

The following sentences have been added to the bottom of this topic.

Restrictions for gathering trace data: IMS Buffer Pool Analyzer works under an IMS dynamic database buffer pools environment with the following restrictions:

  • You must stop BPLTRACE before entering the IMS UPDATE POOL TYPE(DBAS) SECTION(xxxxxxxx) command. Then, after that command is completed, restart BPLTRACE by using another trace data set. 
  • To generate reports, run a job by using the trace data set that was obtained before the IMS UPDATE POOL command was entered, and run another job by using the trace data set that was obtained after the IMS UPDATE POOL command was entered.

 


Update 1
Date of change: December 2017
Change description: Documentation changes by APAR PI87559 and other updates related to multiple traces
Topics: Changes apply to multiple topics.

  • Topic: Gathering trace data > Combining multiple traces into a single report

    This topic has been updated as follows:

    When creating multiple trace data sets that will be combined into a single report, the trace data must be consistent to generate meaningful reports. In addition, all trace data sets must include the trace data that was acquired from the same IMS or the same DL/I batch job.

    The information that must be the same includes:

  • Buffer pool definitions
    This includes not only the same pool buffer sizes and subpool definitions, but the same number of buffers
     
  • Database definitions
    Definitions include:
    • number and names of the databases in the subsystem (batch or online)
    • DD names associated with each DBD
    • block sizes
    • CI size
    • subpool assignments for each database data set

Also, ensure that you do not concatenate trace data sets in report JCL. Each trace data set you want to use as input to one of the report jobs must have a different DD name, each name starting with the word TRACE.
 

  • Topic: IMS buffer pool reports > Generating the buffer pool reports

    This topic has been updated as follows:

    TRACE
    The TRACE symbolic parameter can be used to set the data set name of one trace data set. Since multiple data sets can be used as input to a report, other trace data sets should be added to the JCL using additional DD names that start with TRACE. Note that trace data sets cannot be concatenated to a single DD name.

    For other considerations, see "Combining multiple traces into a single report.”

    TRACExxx
    Any number of TRACExxx DD names can be included in the report job. The last three characters of the DD name can be any valid characters that are allowed in JCL. Each DD name must have only one GTF trace data set. All data sets are read and combined for reporting purposes. At least one TRACExxx DD statement is required.

    For other considerations, see "Combining multiple traces into a single report.”

  • Topic: Coupling facility IMS OSAM cache reports > BPLCF coupling facility report > BPLCF JCL

    The JCL (Figure 35 in PDF) and descriptions of the TRACExxx DD names have been updated as follows:

    You can generate a coupling facility report by running the batch coupling facility report job.

    The following sample JCL is included in the SBPLSAMP library in member BPLCF.




    TRACExxx
    You can include an unlimited number of TRACExxx DD names in the report job. The last three characters of the DD name can be any characters that are valid in JCL. All of the specified trace data sets are read and combined for reporting purposes. At least one TRACExxx DD statement is required.

    Restriction: Each TRACExxx DD statement can have only one trace data set. Concatenated data sets are not supported. To include multiple trace data sets, code each data set with a different DD name.

    For other considerations, see "Combining multiple traces into a single report.”

  • Topic: Troubleshooting: Error messages

    Message BPL723W has been added.

    BPL723W BUFFER POOL ANALYZER TRACE RECORDS MISSING - TYPE=xxxxxxxx DDNAME=ddname

    Explanation: While scanning the first configuration records of the trace data set, the Buffer Pool Analyzer reporting job was unable to find one or more Buffer Pool Analyzer trace records of record type xxxxxxxx.

    In the message,

    ddname
    Indicates the DD name of the trace data set to be scanned.
    xxxxxxxx
    Indicates the type of 440 trace record that was not found. The value can be either SUBPOOL or DDT.

    System action: Buffer Pool Analyzer continues processing and reads the second configuration trace records to gather information for reporting.

    Programmer response: Check the job log to see if BPL542E message follows this message. If so, follow the instructions for BPL542E message. Otherwise, ignore this message.


Publication Number

SC19-3980-00

Copyright Date

2013, 2017

Document information

More support for: IMS Tools

Component: IMS Buffer Pool Analyzer

Software version: 1.4.0

Operating system(s): z/OS

Reference #: 7050630

Modified date: 01 July 2019