Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace z/OS
Created by Guest
Created on Oct 13, 2022

NFS : add official support for UNC paths from Windows clients

we are using NFS on z/OS2.4. We finished a migration project from DFS to NFS because DFS is no longer supported in z/OS.2.4. Our clients are NFS version3 clients on Windows servers and workstations accessing z/OS NFS by using kerberos.

Our Windows applications do not use NFS mount commands with a drive letter as recommended in NFS but UNC paths :

The main reasons we decided to continue with UNC paths are :

  • our previous DFS applications also only used UNC paths which made the conversion to NFS much easier (we just had to change the path names and not the code)

  • most of our applications run on Windows servers as a Windows service and not as an application started by a user that is logged on. We never succeeded to do a mount command with a drive letter from an application running as a Windows service. It seems not to be supported by Windows.

Although our NFS applications are running ok we have some operational issues because of the use of UNC paths :

  • lot's of INACTIVE mount points

  • Continious growth of the virtual storage used by the NFS server on z/OS

As a bypass we stop/start the NFS server once a day

:

Idea priority Medium