IBM Support

PI11466: MESSAGE "FM/DB2 COULD NOT ACCESS COLUMN LENGTH2" ATTEMPTING TO USE THE FM/DB2 EDITOR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Message "FM/DB2 could not access column LENGTH2" attempting to
    use the FM/DB2 editor, target system is DB2 V10 NFM and sample
    member FMN2GV20 used to define views of the DB2 catalog tables
    for File Manager's use.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All user of File Manager DB2 component.      *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. Message "FM/DB2 could not access     *
    *                      column LENGTH2" attempting to use the   *
    *                      FM/DB2 editor.                          *
    *                      2. Message "SQLCODE = -206, ERROR:      *
    *                      REMARKS IS NOT VALID IN THE CONTEXT     *
    *                      WHERE IT IS USED" in the FM/DB2 object  *
    *                      list utility, attempting to create a    *
    *                      LABEL against a table.                  *
    *                      3. Message "SQLCODE = -206, ERROR:      *
    *                      FKY.IBMREQD IS NOT VALID IN THE CONTEXT *
    *                      WHERE IT IS USED" in the FM/DB2 object  *
    *                      list utility, attempting to list        *
    *                      foreign keys for a table.               *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    This problem occurs only when using the "minimal subset" views
    of the DB2 catalog tables, as defined in sample members FMN2GV29
    and FMN2GV20.  The view definitions are missing column names
    that are required for FM/DB2 to function correctly.
    

Problem conclusion

  • File Manager DB2 component has been updated to correct the
    problem.
    Users who are using the "minimal subset" views to
    provide access to the DB2 catalog tables should drop and
    re-create those views, using the updated sample member,
    to complete application of the APAR.
    See the File Manager Customization Guide SC19-4118-00
    Chapter 13 Customizing the operating environment for FM/DB2;
    Granting access to the DB2 Catalog;
    Sample jobs to grant SELECT access on the DB2 catalog tables -
    for more information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI11466

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655Q1200

  • Reported release

    D12

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-02-11

  • Closed date

    2014-04-13

  • Last modified date

    2014-05-02

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

    PM98029

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

Modules/Macros

  • FMN2LVL
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655Q1200

Applicable component levels

  • RD12 PSY UI17000

       UP14/04/19 P F404

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"D12","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 May 2014