Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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
Categories VSCODE
Created by Guest
Created on Feb 18, 2026

Use local repository folder structure when uploading to USS from a multi-root workspace during User Build in IDz on VS Code

Currently, during User Build in IDz on VS Code for a multi-root workspace where the program being built in Repo 1 has dependencies on copybooks in Repo 2 in the same workspace, the copybooks from Repo 2 are uploaded to Repo 1’s working folder on USS. As these USS filepaths are reflected in the USS view of Zowe Explorer and referenced in the “IBM User Build” Output console log, this can be misleading for z/OS application developers, who need to be clear on the ownership of each element and for whom User Build is the first level of testing.

In contrast (and as a precedent for customers switching from IDz (Eclipse) to IDz on VS Code), IDz (Eclipse)’s User Build uploads copybooks from separate local repositories (in the same multi-root workspace) into separate respective working folders on USS. It would be beneficial for z/OS application developers if the User Build in IDz on VS Code would perform its uploads similarly, i.e. using the same folder structure in USS as the local repository folder structure from the multi-root workspace.

Idea priority High