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
Categories SMP/E
Created by Guest
Created on Apr 24, 2026

SMPE APPLY: Support ++SRC Element Data Residing in USS

Hi,
We are trying to manage our IMS Internal Assembler/Cobol sources using git. Git Clone to USS & then we were trying to point TXLIB in SRC to a USS path directly rather than having a dataset. Currently SMP/E has no capability for element data in SYSMODs, like ++SRC for assembler source, to reside in a UNIX file. So the only way out for us is to copy USS data to MVS and then point that to a DDDEF but that seems inefficient in the modern world of GIT.

Could this be something looked at please?


Thank You,
Madhavi

Idea priority Medium