IBM Support

PM38341: INCORRECT "UNSUPPORTED DASD DEVICE" MESSAGE ISSUED WHEN USING THE DSLIST - WORK WITH VTOC UTILITY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • User goes into FileManager Base and selects 3 for Utilities,
    then selecting 4 for Dslist - work with VTOC. They enter the
    name of a KSDS VSAM dataset. They receive an "Unsupported
    DASD device" error message in upper right corner of the screen.
    
    The problem occurs when File Manager is analyzing the LISTCAT
    output - specifically it breaks when looking at the REC-TOTAL
    field which has a very large value. (REC-TOTAL-----4294967165*)
    The Unsupported DASD device is just a consequence of corrupted
    output from this analysis.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All File Manager users.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the prefix command I is issued     *
    *                      against a VSAM data set from the        *
    *                      Catalog Services Data Set List panel    *
    *                      the message 'Unsupported device type'   *
    *                      may be issued.                          *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    The IDCAMS Listcat query used to populate VSAM Entry Detail
    panel can return a total number of records which is more than
    10 characters in length including the possible * at the end of
    the value.  The * denotes that the value is not necessarily
    correct. A total number of records value which contains more
    than 10 characters causes File Manager to stop gathering
    information for the panel.
    

Problem conclusion

  • File Manager now supports up to 12 characters for the total
    number of records in the Data component of a VSAM data set.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM38341

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655W4700

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-05-03

  • Closed date

    2011-06-23

  • Last modified date

    2011-07-05

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

    PM35818

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

Modules/Macros

  • FMN0LVL  FMN0LVLJ FMN0LVLK
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655W4700

Applicable component levels

  • RB1A PSY UK69036

       UP11/06/25 P F106

  • RB10 PSY UK69035

       UP11/06/25 P F106

  • RB11 PSY UK69037

       UP11/06/25 P F106

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":"B10","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":"B10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
05 July 2011