IBM Support

OA31112: NEW FUNCTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • New function
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the Distributed File Service    *
    *                 SMB Server.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    *                      DFS/SMB cannot export zFS read/write    *
    *                      file systems that are sysplex-aware.    *
    *                      In V1R11, zFS implemented a change with *
    *                      APAR OA29619 to allow individual        *
    *                      file systems to be sysplex-aware        *
    *                      rather than relying on the sysplex      *
    *                      state of the system. DFS/SMB does not   *
    *                      support zFS sysplex-aware on a file     *
    *                      system basis.                           *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    DFS/SMB cannot export sysplex aware zFS read/write file systems.
    When exporting a zFS read/write file system, DFS/SMB only checks
    the state of the system that it is running on to determine if
    it can export the file system. With the zFS APAR OA29619 the
    sysplex-aware indicator can be on the file system itself.
    DFS/SMB will need to check that indicator. This SPE will
    exploit the function added by OA29619.
    

Problem conclusion

Temporary fix

Comments

  • ================================================================
    Several messages have been added or changed with the fix
    for OA31112. The following is a summary of those changes:
    
    Chapter 12. IOEPnnnnnt Messages - DFS Kernel (dfskern) and
                General DFS Errors
    
    The following messages have been added :
    
    IOEP01711I
    IOEP01712I
    IOEP01713I
    
    
    IOEP01711I DFS kernel cannot export the file
    system filesystem_name because zFS is
    running sysplex=on.
    
    Severity: svc_c_sev_warning
    
    Explanation: The Distributed File Service kernel is not
    able to export the read/write zFS file system,
    filesystem_name, because zFS is running
    sysplex-aware on a system basis (sysplex=on). If you
    need to export the file system, you must run zFS
    non-sysplex aware (sysplex=off) or run zFS as
    sysplex-aware on a file system basis (sysplex=filesys)
    and ensure that the zFS file system is mounted
    non-sysplex aware. For more information, see z/OS
    Distributed File Service zSeries File System
    Administration.
    
    System action: The program continues.
    
    User response: None.
    
    
    IOEP01712I DFS kernel cannot export the file
    system filesystem_name because zFS is
    sysplex-ware.
    
    Severity: svc_c_sev_warning
    
    Explanation: The Distributed File Service kernel is not
    able to export the read/write zFS file system,
    filesystem_name, because the file system was mounted
    as sysplex-aware. If you need to export the file system,
    the file system cannot be mounted sysplex-aware. For
    more information, see z/OS Distributed File Service
    zSeries File System Administration.
    
    System action: The program continues.
    
    User response: None.
    
    
    IOEP01713I DFS kernel cannot export the file
    system filesystem_name because a zFS
    PFSCTL call failed. Command
    command, subcommand subcommand,
    failed with RC=rc and reason=reason.
    
    Severity: svc_c_sev_warning
    
    Explanation: The Distributed File Service kernel calls
    the zFS PFSCTL to access file system information but
    the call failed and the file system information could not
    be obtained. For more information about the indicated
    command, subcommand and reason code, refer to z/OS
    Distributed File Service zSeries File System
    Administration and Appendix A,  Reason Codes,  on
    page 307.
    
    System action: The program continues.
    
    User response: None.
    ================================================================
    The following messages have been modified:
    
    Chapter 16. IOEWHnnnnt
    
    IOEWH0011E Not all systems are at a zFS sysplex state of 1 or
               lower.
    
    Explanation:  Not all DFS/SMB systems are running at a zFS
    sysplex state of 1 or lower. DFS/SMB cannot export/share any R/W
    zFS file systems owned by a system running zFS sysplex-aware on
    system basis (sysplex state is 2) or zFS file systems owned by a
    system running zFS sysplex-aware on a file system basis (sysplex
    state is 3) and the file system was mounted as sysplex-aware.
    
    System Action:  The system continues processing.
    
    Operator Response:  Report this problem to the system programmer
    
    System Programmer Response:  Message IOEWH0012I presents a list
    of systems and their sysplex state. If you need to export/share
    zFS R/W file systems owned by the systems indicated in the list,
    you must run zFS non-sysplex aware (sysplex=off) or run zFS as
    sysplex-plex on a file system basis (sysplex=filesys) and ensure
    that the ZFS file system is mounted non-sysplex aware.
    
    Problem Determination:  N/A
    
    Source:  DFS/SMB File Server
    
    Reference Documentation:  See "Sharing files" in z/OS Distribute
    File Service DFS/SMB Administration and "Enabling the zFS
    sysplex-aware function" in z/OS Distributed File Service zSeries
    File System Administration
    
    Automation:  N/A
    
    Module: IOESHCK1
    
    Routing code: N/A
    
    Descriptor code: N/A
    
    
    Section: DF04rrrr Reason Codes
    
    Here is the new text from DF040002
    
    0002        The File Exporter Exit Routine made an
                invalid request. This is not supported.
    
    Action: To export this zFS file system, you must run
    zFS non-sysplex aware by specifying sysplex=off in the
    IOEFSPRM or by specifying sysplex=filesys in the
    IOEFSPRM and ensure that the zFS file system is
    mounted non-sysplex aware. See z/OS Distributed File
    Service zSeries File System Administration for further
    details.
    
    ×**** PE10/04/15 FIX IN ERROR. SEE APAR OA32648  FOR DESCRIPTION
    

APAR Information

  • APAR number

    OA31112

  • Reported component name

    DFS FILE SERVIC

  • Reported component ID

    569694200

  • Reported release

    3B0

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2009-11-16

  • Closed date

    2010-03-03

  • Last modified date

    2010-04-30

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

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

    UA52995

Modules/Macros

  •    IOEBOSRV IOEBUTC  IOEDFSCL IOEDFSKN IOEDFSXP
    IOEM0021 IOEPDCT  IOESHENU IOESHMSG
    

Publications Referenced
SC24591713    

Fix information

  • Fixed component name

    DFS FILE SERVIC

  • Fixed component ID

    569694200

Applicable component levels

  • R3B0 PSY UA52995

       UP10/03/23 P F003

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"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"3B0"}]

Document Information

Modified date:
09 January 2021