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.

ADD A NEW IDEA

Data Set File System (DSFS)

Showing 24

Enhance DSFS sysout to access all data in an open sysout file

Currently with SDSF it is possible to view all of the data in an open sysout file. With /dsfs/sysout/.... that same open sysout file is empty. It obviously works when the job step, or job, completes as it is closed *but* when open and active that ...
3 months ago in z/OS / Data Set File System (DSFS) 4 Future consideration

dsfs/sysout should use stepname.procstepname.ddname

Currently /dsfs/sysout/ ... uses stepname.ddname.something - that can be misleading as multiple steps can use the same ddname - adding the procstepname so it is stepname.procstepname.ddname.something would provide additional granularity and clarity.
3 months ago in z/OS / Data Set File System (DSFS) 3 Future consideration

DSFS support for GDGs

It would be very useful if DSFS would also support GDGs. We already exploit DSFS with ssh transfer, but missing GDG support is a road-blocker.
about 1 year ago in z/OS / Data Set File System (DSFS) 1 Future consideration

Enable access to input datasets for DSFS

Currently DSFS only supports output spool datasets. The addition of input spool datasets would be very helpful in providing a full user experience via the /dsfs/ sysout interface.
8 months ago in z/OS / Data Set File System (DSFS) 1 Future consideration

DSFS createparm limitations

Currently dsadm createparm has following limitation:The user ID of the issuer of the command must match the HLQ (just the first qualifier) in order to be allowed to save creation parameters for the HLQ directory. We have many technical/application...
about 1 year ago in z/OS / Data Set File System (DSFS) 1 Future consideration

ISPF and USS are applications that should be consistent in their ENQ behavior since they edit and browse datasets. Expecting DSFS to handle dataset ENQs like ISPF.

With Open Enterprise Foundation, using vim (with DSFS) to browse and edit datasets should be a similar experience as when using ISPF.Dataset ENQs with consistent messages would be expected.
about 2 months ago in z/OS / Data Set File System (DSFS) 1 Future consideration

Provide full sysout access (read only acceptable) mirroring SDSF access

Currently with /dsfs/sysout/ the user is only allowed to see and look at spool data that is owned by their userid, which includes any TSO sessions or batch jobs under that userid. With SDSF that same user can view the spool for not only my own sys...
4 months ago in z/OS / Data Set File System (DSFS) 1 Future consideration

Enhance DSFS to support Migrated z/OS Datasets

Ed Jaffe on the ibm-main listserv pointed out that using dsfs any DFSMShsm migrated data sets were not available. This is a critical oversight as DFSMShsm is still very heavily used. DSFS needs to be able to recognize data sets in a migrated state...
11 months ago in z/OS / Data Set File System (DSFS) 2 Future consideration

Enhance DSFS CreateParm to support masking for the path

The createparm path is currently a high-level-qualifier of one or more levels. It needs to be more granular such as hlq.*.ASM or hlq.*.EXEC as this makes more sense as all ASM would be FB 80 and EXEC would be either FB 80 or VB 255 depending on th...
about 1 year ago in z/OS / Data Set File System (DSFS) 1 Future consideration

Git path directory, for adding transparent git support for datasets

A `.git` file can be created with content: `gitdir: <path-to-zFS-where-no-pdspdse-constraints-exist>` to keep all git data elsewhere. Another advantage of keeping .git data separate (DSFS transparently handling just a representative `.git` f...
4 months ago in z/OS / Data Set File System (DSFS) 1 Future consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.