Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Not under consideration
Workspace IBM i
Created by Guest
Created on Dec 13, 2016

CPYFRMSTMF needs SRCCHGDATE parameter as on CPYSRCF

CPYFRMSTMF needs a new parameter SRCCHGDATE(*FROMMBR) that works just like the SRCCHGDATE parameter on the CPYSRCF command.

SRCCHGDATE(*NEW) can allow for compatibility with the existing behavior of the CPYFRMSTMF command.

Note that this proposed new SRCCHGDATE behavior need only apply when copying to a source physical file member, not any other type of physical file member(s).


Use Case:

Suppose I want to use git or any other popular Source Code Version Control tool for collaborative development. This usually requires copying all of the source members from source physical files to IFS streamfiles, to put them into the SCM/VCS repository. Then, when I need to pull them out of the SCM/VCS repository, I need to copy from a streamfile back to a source file member, if I want the benefits of the object-to-source cross reference information in the object information repository (OIR).

If I use CPYFRMSTMF today, the resulting source members will all have today's date/time as the last changed date/time.

This is also undesirable, because many make or build tools (like QUSRTOOLS TMKMAKE) will look at the file's last changed date/time to determine "what has changed" and to determine what needs to be recompiled.

Also, that is the last changed date that the compilers will insert into the *OIR for the compiled object's source cross-reference information.

This is important for any projects where customers would have a distributed team of developers sharing source code using git or github, or hg, or CVS or SubVersion, or almost any popular SCM/VCS to enable collaborative development across a widely disbursed development team.

This is also very important for shops that must have PCI compliance or Sarbanes-Oxley Act compliance and auditing requirements, etc.,if they want to be able to compile their production objects from source that is maintained using a SCM/VCS or they just want to keep the source in the IFS.


Idea priority High
  • Guest
    Nov 11, 2021

    Thank you for taking the time to submit your request. After careful consideration, we know that we cannot deliver your requested enhancement soon, so it is being declined. However, we believe it may have future value, so we will add it to an internal list for us to keep in mind for the future.

  • Guest
    May 5, 2020

    We will prioritize this request in our future plans.

  • Guest
    Jul 11, 2017

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Dawn May - CAAC Program Manager

  • Guest
    Jan 31, 2017

    Thank you for submitting this request. The IBM team needs to investigate this further.

  • Guest
    Dec 15, 2016

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - IFS (Integrated File System) and Servers
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Core OS
    Operating system - IBM i
    Source - None