PM88676: CHANGES MADE BY APAR PM70710 CAUSE PROBLEMS FOR SOME USERS OF FM/IMS, AS THE ORDER WAS CHANGED FOR LOAD (ILB)

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • PM70710 handled the issue of twin segments extracted from one
    database and loaded into another not being in the same sequence
    in the loaded database as they were in the extracted database.
    The behavior was changed of the Load (ILB) because users of
    FM/IMS objected that when they used the Extract (IXB) and Load
    (ILB) to extract data from one database and load it into
    another, twin segments in the loaded database were not in the
    same sequence as they were in the extracted database. FM/IMS
    was modified with the fix for APAR PM70710 to maintain the
    sequence of twin segments when they are extracted from one
    database and loaded into another. This has been found to be a
    problem for some users who depend on the pre-PM70710 behavior.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All FM/IMS Load (ILB) users.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: The fix for APAR PM70710 changed the    *
    *                      behaviour of the Load (ILB) function.   *
    *                      Some customers were relying on the      *
    *                      pre-PM70710 behaviour.                  *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    Without the fix for APAR PM70710, segments with no key or a non
    unique key, are inserted according to the insert rule for the
    segment type.
    With the fix for APAR PM70710, segments with no key or a non
    unique key are inserted as the last occurrence - this is
    irrespective of the insert rule for the segment type.
    The modification was made so that twin segments extracted from
    one database and loaded into another are in the same sequence
    in the loaded database as they were in the extracted database.
    Pre-PM70710, the Extract (IXB) and Load (ILB) did not maintain
    the sequence of twin segments when the insert rule for these
    segments was FIRST or HERE.
    Nevertheless, some customers were relying on the pre-PM70710
    behaviour.
    

Problem conclusion

  • The FM/IMS Load (ILB) has been modified to support a new
    parameter - USELCMD. When the USELCMD parameter is set to N,
    segments with no key or a non unique key are inserted according
    to the insert rule for the segment type - that is the
    pre-PM70710 behaviour. When the USELCMD parameter is set to Y or
    is not specified, segments with no key or a non unique key are
    inserted as the last occurrence - that is the post-PM70710
    behaviour.
    The FM/IMS Load dialog has been modified to include the 'Do not
    override insert rules' option. When this option is selected and
    there is a segment with an insert rule of FIRST or HERE in the
    primary database or a logically related database, the JCL
    generated by the dialog includes the card:
    $$FILEM     USELCMD=N,
    When this option is not selected and there is a segment with an
    insert rule of FIRST or HERE in the primary database or a
    logically related database, the JCL generated by the dialog
    includes the card:
    $$FILEM     USELCMD=Y,
    Otherwise, the dialog does not generate a USELCMD= card.
    
    Publication Closing Code: DEVCHNG
    For the documentation changes associated with this APAR,
    please refer to:
    ftp://public.dhe.ibm.com/software/websphere/awdtools/
        filemanager/fmv11apar.pdf
    
    The changes are to the following publications:
    
    PUB ID        PUB NAME
    ------------  ----------------------------------------
    SC19-3136-01  File Manager for z/OS V11R1 User's Guide
                  and Reference for IMS Data
    
    The latest published manuals can be found at:
    http://www.ibm.com/software/awdtools/filemanager/library/
           index.html.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM88676

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655W4700

  • Reported release

    B14

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-08

  • Closed date

    2013-08-18

  • Last modified date

    2013-09-03

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

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

    PM94819

Modules/Macros

  • FMN1LVL  FMN1LVLJ FMN1LVLK
    

Publications Referenced
SC19313601        

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655W4700

Applicable component levels

  • RB1C PSY UK96740

       UP13/08/24 P F308

  • RB14 PSY UK96741

       UP13/08/24 P F308

  • RB15 PSY UK96747

       UP13/08/24 P F308

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

Document information


More support for:

z/OS family

Software version:

B14

Reference #:

PM88676

Modified date:

2013-09-03

Translate my page

Machine Translation

Content navigation