IBM Support

PI23328: FM/IMS ENHANCEMENT ADDRESSING IMS LOG PROCESSING DEFICIENCIES.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • FM/IMS Enhancement addressing IMS log processing deficiencies.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All FM/IMS users running functions in DLI    *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. FM/IMS administrators cannot enforce *
    *                      the usage and retention of IMS log data *
    *                      sets when functions are run in DLI      *
    *                      mode.                                   *
    *                      2. The names given to the IMS log data  *
    *                      sets that FM/IMS functions use do not   *
    *                      conform with the naming conventions at  *
    *                      some customer installations and FM/IMS  *
    *                      does not support the specification of   *
    *                      alternate names by either the user or   *
    *                      the FM/IMS administrator.               *
    *                      3. FM/IMS read-only functions using     *
    *                      PSBs that have update intent produce    *
    *                      IMS log records. However, unlike the    *
    *                      update functions, the read-only         *
    *                      functions do not allow the user to      *
    *                      specify whether the records are written *
    *                      to a dummy or a permanent data set and, *
    *                      if they are written to a permanent data *
    *                      set, whether the permanent data set is  *
    *                      kept when the function ends.            *
    *                      4. If the JCL for a batch function that *
    *                      is run in DLI mode does not include an  *
    *                      IEFRDER DD and the function uses a PSB  *
    *                      that has update intent, then FM/IMS     *
    *                      dynamically allocates an IMS log data   *
    *                      set. However, there are no parameters   *
    *                      that allow the user to specify whether  *
    *                      to allocate a dummy or a permanent data *
    *                      set, and if a permanent data set is to  *
    *                      be allocated, the attributes of the     *
    *                      data set and whether or not it is to be *
    *                      kept when the function ends.            *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    *                 File Manager Plugin users should upgrade the *
    *                 PD Tools Plugin to v13.1.0.14 or later.      *
    ****************************************************************
    1. Just as FM/IMS administrators can enforce the usage of DBRC,
    they should be able to enforce the usage and retention of IMS
    log data sets.
    2. &UID..FMNLOG.&YYMMDD..&HHMMSS..&DBNAME. is the name pattern
    used by FM/IMS functions to generate IMS log data set names
    where:
    - &UID. is either the user's TSO prefix (if its value is not
    null) or the User ID (otherwise).
    - &YYMMDD. is Dyymmdd where yymmdd is the date that the IMS log
    data set name is generated expressed as a 2-digit year (YY),
    month (MM) and day (DD).
    - &HHMMSS. is Thhmmss where hhmmss is the time of day that the
    IMS log data set name is generated expressed in hours (HH),
    minutes (MM) and seconds (SS).
    - &DBNAME. is the name of the primary database that the function
    accesses.
    FM/IMS should allow the user or the FM/IMS administrator to
    specify the name pattern that is to be used to generate IMS log
    data set names.
    3. The update functions support the IMS log option which allows
    the user to specify whether or not the IMS log records are
    written to a dummy or a permanent data set, and if they are
    written to a permanent data set whether the permanent data set
    is kept when the function ends.
    For read-only functions, on the other hand, the user is not
    given this option - IMS log records are written to a temporary
    data set (when the function is using DBRC) or a dummy data set
    (otherwise).
    

Problem conclusion

Temporary fix

Comments

  • FM/IMS has been modified to:
    1. Provide subsystem parameters that allow the FM/IMS
    administrator to enforce the usage and retention of IMS log data
    sets when functions are run in DLI mode.
    2. Allow the user or the FM/IMS administrator to specify the
    name pattern that is used to generate IMS log data set names.
    3. Broaden the scope of the IMS log option to all functions
    using PSBs that have update intent.
    4. Provide batch parameters that allow the user to specify
    whether the IMS log data set that a batch functions dynamically
    allocates is a dummy or a permanent data set, and if it is a
    permanent data set:
    - The name pattern that the function uses to generate the data
    set name.
    - Allocation attributes of the data set.
    - Whether or not to keep the data set when the function ends.
    
    Publication Closing Code: DEVCHNG
    For the documentation changes associated with this APAR,
    please refer to:
    
    PUB ID        PUB NAME
    ------------  ----------------------------------------
    SC19-4118-01  File Manager for z/OS V13R1 Customization
                  Guide
    SC19-4121-01  File Manager for z/OS V13R1 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.
    

APAR Information

  • APAR number

    PI23328

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655Q1200

  • Reported release

    D14

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-05

  • Closed date

    2014-12-16

  • Last modified date

    2015-01-02

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

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

Modules/Macros

  •    FMN1LVL  FMN1LVLJ FMN1LVLK
    

Publications Referenced
SC19411801SC19412101   

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655Q1200

Applicable component levels

  • RD1C PSY UI23946

       UP14/12/20 P F412

  • RD14 PSY UI23950

       UP14/12/20 P F412

  • RD15 PSY UI23951

       UP14/12/20 P F412

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
29 April 2020