IBM Support

PM29188: COMMENTS/REMARKS IN FM/DB2 ARE TRUNCATED TO 60 CHARACTERS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Comments/remarks entered in panels FMN2POTI and FMN2POTR are
    being truncated to 60 characters.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of File Manager DB2 component.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. Comments displayed using FM/DB2      *
    *                      option 3.4 COM line command are         *
    *                      truncated to a maximum of 60            *
    *                      characters.                             *
    *                      2. FM DB2/CICS may abend when SQL       *
    *                      prefix command issued.                  *
    *                      3. When copying a VARCHAR to VARGRAPHIC *
    *                      field using FM/DB2 copy, the length of  *
    *                      the VARGRAPHIC field is doubled.        *
    *                      4. The second or third global export    *
    *                      options panel is shown after issuing    *
    *                      the command to change DB2 sub-systems.  *
    *                      5. In FM/DB2 Object create utility,     *
    *                      Indexes, entering an index or table     *
    *                      owner > 8 characters in length gives    *
    *                      an error.                               *
    *                      6. In FM/DB2 "Set Output Data Set       *
    *                      Allocation Options", the values for     *
    *                      SHOWSQL datasets are not initialized.   *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    1. The FM/DB2 ISQ processor is always truncating the width of
    REMARKS fields to 60 characters.  The "Other" column option on
    the second FM/DB2 Object List Option's panel should allow the
    maximum size for REMARKS columns to be set to values larger than
    60 characters.
    2. The ISPF variable ZTERMCID is being referenced when it is
    not available under IPV.
    3. The length field for VARGRAPHIC columns records the number of
    DBCS characters, not the number of bytes.
    4. When connected to DB2 system A, the FM/DB2 export data format
    is set to 1-3, which precludes the display of the second/third
    export option's panel(s).  When connected to DB2 system B, the
    FM/DB2 export data format is set to 4,5, which allows display
    of the second+third/second export option's panels, respectively.
    When connected to DB2 system B, and the command to change the
    DB2 sub-system is issued from the second/third export option's
    panel, the same panel is shown (erroneously) after the
    connection to DB2 sub-system A.
    5. An ISPF VER statement with NAME is used, this is invalid
    since NAME implies 1-8 chars, whereas an owner can be 1-128
    characters.
    6. There are no POPT options applying to the SHOWSQL dataset
    allocation parameters.
    

Problem conclusion

  • 1. File Manager DB2 component has been changed to correct the
    problem.  This APAR also modifies the behaviour for the minimum
    and maximum lengths for "Other" columns, in the FM/DB2 Object
    List options.  This option is altered to apply specifically to
    "REMARKS" columns in the DB2 catalog tables.
    2. FMDB2/CICS will not reference ISPF variable ZTERMCID.
    3-5. File Manager DB2 component has been updated to correct the
    problem.
    6. File Manager DB2 component has been updated to use the print
    dataset allocation parameters - if specified in FMN0POPT - when
    initializing the SHOWSQL dataset allocation parameters.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM29188

  • Reported component name

    FILE MANAGER ZO

  • Reported component ID

    5655V5200

  • Reported release

    A12

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-12-17

  • Closed date

    2011-04-18

  • Last modified date

    2011-05-10

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

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

    UK66838 UK66839 UK66840 UK66841 PM38779

Modules/Macros

  • FMNBRWS
    FMNEDIT
    FMNLOCAL
    FMNMSEL
    FMNRDCCO
    FMN0LVL
    FMN2CTQ2
    FMN2FL20
    FMN2FL29
    FMN2IPSU
    FMN2LOCL
    FMN2LVL
    FMN2LVLJ
    FMN2LVLK
    FMN2MENU
    FMN2MJPN
    FMN2MKOR
    FMN2MXXX
    FMN2PCX0
    FMN2POLE
    FMN2POLF
    FMN2POLJ
    FMN2POLO
    FMN2POLT
    FMN2POO2
    FMN2POTR
    FMN2PXO1
    FMN2RMDT
    FMN2ROLO
    FMN2SQLC
    

Fix information

  • Fixed component name

    FILE MANAGER ZO

  • Fixed component ID

    5655V5200

Applicable component levels

  • RA1B PSY UK66839

       UP11/04/20 P F104

  • RA10 PSY UK66838

       UP11/04/20 P F104

  • RA12 PSY UK66840

       UP11/04/20 P F104

  • RA13 PSY UK66841

       UP11/04/20 P F104

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A12","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A12","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
10 May 2011