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
Created by Guest
Created on Jul 16, 2026

Implement support for targetEncoding parameter when performing Unix to Unix (or PDS to PDS) file copy

Currently when type: copy is used in yaml configurations there is a parameter called targetEncoding that sets the encoding type for the target or destination file copy. This target encoding parameter only works for PDS->USS or USS->PDS copies. When performing a PDS->PDS or USS->USS file copy the targetEncoding parameter is not respected. When the source and destination environment are the same, the source file encoding is used for the destination copy as well. This RFE is to allow the targetEncoding parameter to be used for PDS->PDS and USS->USS file copies as well.

The example use case would that we want to publish a copybook in ascii format, so it will be included in a package to keep it readable on the pc side. To do that we would first use a copy step to copy it to a temporary unix directory on the z/OS side, where the package step would subsequently add it to the package in ascii format.

Idea priority Low