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 Submitted
Workspace IBM i
Categories Core OS
Created by Guest
Created on Oct 30, 2025

create a temp per process ifs dir QTEMP like in use

For security and auto cleanup, would be useful to have a particular named directory in IFS called for example /QTEMP or /jobtmp etc. that is local to the process (and PASE process) and behaves just like the QTEMP library.

Or something autogenerated, or istantiated upon API call that will give a unique dir id.

When a process dies, the whole content vanishes.

This virtual dir then you can - in future - use it to support to mount "virtual remote" filesystems, like the now ubiquitous SFTP. Want to support SFTP in a super efficient way and revolutionary way? Just mount the remote server under /QTEMP/serverid and then let RPG use regular POSIX calls or the new SQL services, it is a "per process" mount view. Want to support S3 storage? same, if it has a filesystem like view and structure.

The uses are numerous.

And really, sometimes, after months, the current /tmp can become a real mess, lots of leftovers, a lot of security problem possibilities also due to lot of logs left there...

Idea priority High
  • Guest
    Nov 20, 2025

    This would deviate from generally accepted standards for *nix environments.