PM87151: HIGH CPU UTILIZATION CAPTURED WHEN USING FM/IMS BROWSE WITH A VIEW, AND ISSUING A FIND COMMAND USING A LARGE IMS DATABASE

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When issuing a Find command using a large IMS database and a
    view, as outlined below, high CPU utilization for FM/IMS
    is captured.
    
     1. In FM/IMS Browse, enter command -
    
        F 'TEST ' 12
    
        Search argument is found.
    
     2. Press PF5 - receive pop up which states 10,000 segments
        searched and search argument found 0 times.
    
     3. Press enter to continue search, receive pop up which states
        40,000 segments searched and search argument found 0 times.
    
     4. Press enter to continue search, at this point high CPU
        utilization for FM/IMS is captured.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All FM/IMS Edit and Browse users, all FM/DB2 *
    *                 Edit and View users and all FM base Edit and *
    *                 View users.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. FM/IMS Edit or Browse session hangs  *
    *                      when the Editor is short on storage.    *
    *                                                              *
    *                      2. Attention interrupt problems:        *
    *                      i. Pressing the attention interrupt key *
    *                      when FM/IMS is processing a CHILD, TWIN *
    *                      or DPRINT command does not interrupt    *
    *                      the processing.                         *
    *                      ii. Pressing the attention interrupt    *
    *                      key when FM/IMS is processing a         *
    *                      FIND/CHANGE or NEXT command throws the  *
    *                      user out of the Edit/Browse session.    *
    *                      iii. Pressing the attention interrupt   *
    *                      key when FM/IMS is retrieving the data  *
    *                      that is to be displayed on the IMS data *
    *                      panel throws the user out of the        *
    *                      Edit/Browse session.                    *
    *                      iv. Pressing the attention interrupt    *
    *                      key when FM/IMS is processing the       *
    *                      BOTTOM or DOWN command interrupts the   *
    *                      processing but the                      *
    *                      '****  End of database  ****' line is   *
    *                      displayed on the IMS data panel even    *
    *                      though FM/IMS did not reach the end of  *
    *                      the database.                           *
    *                      v. (All components except FM/IMS) If    *
    *                      the attention interrupt key is pressed  *
    *                      when File Manager is processing a       *
    *                      FIND/CHANGE command and an occurrence   *
    *                      of the search string is yet to be       *
    *                      found, File Manager displays the data   *
    *                      that was being scanned just prior to    *
    *                      the interrupt.                          *
    *                                                              *
    *                      3. The NEXT and PREV command does not   *
    *                      behave as documented in the FM/IMS      *
    *                      User's Guide.                           *
    *                                                              *
    *                      4. FIND/CHANGE scrolling problems:      *
    *                      The FIND/CHANGE command is supposed to  *
    *                      move the cursor to the first or next    *
    *                      occurrence of the search string in the  *
    *                      data and, if this occurrence is not     *
    *                      visible on the screen, scroll forward   *
    *                      so the occurrence is displayed at the   *
    *                      top of the data area.                   *
    *                      However:                                *
    *                      i. (All components) The FIND/CHANGE     *
    *                      command does not scroll forward when    *
    *                      the next occurrence of the search       *
    *                      string is at the top of the next page   *
    *                      and the format is either HEX or TABL    *
    *                      with HEX on.                            *
    *                      ii. (IMS only) The first occurrence of  *
    *                      the search string is not displayed at   *
    *                      the top of the data area when:          *
    *                      - you issue a FIND/CHANGE...FIRST/ALL   *
    *                      command or an RFIND/RCHANGE command     *
    *                      after the end of the search range has   *
    *                      been reached and                        *
    *                      - the start of the search range is      *
    *                      before the data that was displayed at   *
    *                      the top of the data area when the       *
    *                      command was issued and                  *
    *                      - the first occurrence of the search    *
    *                      string is on the first page of the      *
    *                      search range.                           *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    1. FM/IMS loops when the Editor is low on storage.
    
    3. The 'Use * (any segment type) as default on NEXT and PREVIOUS
    commands' option on the Editor options panel (0.5) is used to
    specify the default behaviour for the NEXT and PREV commands.
    However, * is always used as the default, irrespective of
    whether or not this option is selected.
    

Problem conclusion

  • 1. FM/IMS has been modified to correct this and other Editor
    short on storage problems.
    
    2. File Manager has been modified to correct the attention
    interrupt problems described above. With these modifications,
    File Manager behaves as follows:
    - If the attention interrupt key is pressed when FM/IMS is
    processing a NEXT, CHILD or TWIN command, the message 'Scan
    interrupted' is issued and the data that was showing before the
    command was issued is redisplayed.
    - If the attention interrupt key is pressed when FM/IMS is
    processing a DPRINT command, the message 'Print interrupted by
    attention request - nnnnn records printed' is issued and the
    data that was showing before the command was issued is
    redisplayed.
    - If the attention interrupt key is pressed when FM/IMS is
    processing a DOWN or BOTTOM comand, the message 'Scroll
    interrupted' is issued and the data that was retrieved just
    prior to the interrupt is displayed.
    - If the attention interrupt key is pressed when FM/IMS is
    retrieving the data that is to be displayed on the IMS data
    panel, the message 'Data retrieval interrupted by attention
    request' is issued and the '****  Bottom of window ****' line
    is displayed after the last line of data.
    - (All components) If the attention interrupt key is pressed
    when File Manager is processing a FIND/CHANGE command and an
    occurrence of the search string is yet to be found, the message
    'Scan interrupted' is issued and the data that was showing
    before the command was issued is redisplayed.
    - (All components) If the attention interrupt key is pressed
    when File Manager is processing a FIND/CHANGE...ALL command
    and the first occurrence of the search string has already been
    found, the message 'Scan interrupted' is issued and, if the
    first occurrence of the search string was not visible before
    the command was issued, it is displayed at the top of the data
    area.
    
    3. The FM/IMS NEXT and PREV commands have been modified to
    behave as documented in the FM/IMS User's Guide.
    
    4. File Manager has been modified to correct the FIND/CHANGE
    scrolling problems described above
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM87151

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655W4700

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-16

  • Closed date

    2013-07-16

  • Last modified date

    2013-08-02

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

    PM80087

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

    UK95863 UK95864 UK95865 UK95866 UK95867 UK95868 UK95869 UK95870

Modules/Macros

  • FMNAUDCH FMNBA07  FMNBA39  FMNBDIRS FMNBDI0K FMNBDI0P FMNBE80
    FMNBE94  FMNBF42  FMNBF43  FMNDB51  FMNDB89  FMNDD60  FMNDSC
    FMNEDIT  FMNEDIT1 FMNEDIT2 FMNEDIT6 FMNEDIT7 FMNED0DY FMNED0SE
    FMNED008 FMNFCOPT FMNFHOPT FMNFPOPT FMNFWPRT FMNIA00  FMNIA20
    FMNIB53  FMNIB81  FMNIEBCP FMNMQQE  FMNMQQV  FMNMSEL  FMNPSAS
    FMNPSCB  FMNPSPL  FMNRLSSF FMN0LVL  FMN0LVLJ FMN0LVLK FMN0MENU
    FMN0MJPN FMN0MKOR FMN1ECMD FMN1EDIF FMN1FIND FMN1GSEG FMN1LVL
    FMN1LVLJ FMN1LVLK FMN1MENU FMN1MJPN FMN1MKOR FMN1NOXP FMN1PACB
    FMN1PACD FMN1PASM FMN1PLNK FMN1PSAS FMN1PSB  FMN1PSCB FMN1PSPL
    FMN1RMDT FMN2FE43 FMN2LVLJ FMN2LVLK FMN2MJPN FMN2MKOR FMN2POCX
    FMN2POXK FMN2PSAS FMN2PSCB FMN2PSPL FMN2PUCR FMN2RD63 FMN2RD64
    FMN2ROCX FMN2ROXK FMN2RO3H FMN2RXO8
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655W4700

Applicable component levels

  • RB1A PSY UK95864

       UP13/07/19 P F307

  • RB1B PSY UK95865

       UP13/07/19 P F307

  • RB1C PSY UK95866

       UP13/07/19 P F307

  • RB10 PSY UK95863

       UP13/07/19 P F307

  • RB11 PSY UK95867

       UP13/07/19 P F307

  • RB13 PSY UK95868

       UP13/07/19 P F307

  • RB14 PSY UK95869

       UP13/07/19 P F307

  • RB15 PSY UK95870

       UP13/07/19 P F307

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

B10

Reference #:

PM87151

Modified date:

2013-08-02

Translate my page

Machine Translation

Content navigation