Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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
Created by Guest
Created on Apr 28, 2025

Setting local permission controls in userfile.cfg for landed files

Connect:Direct (aka NDM) provides great power over sending files to report systems, allowing the potential for running jobs or tasks on a remote system. But receiving system lacks some simple security controls within the usefile.cfg over files landed on a system. Right now, the receiving server can only set the ID of the landed file, and restrict the location the file can land in. I propose adding two (2) more pstmt controls in the userfile.cfg specification for a user@server: pstmt.mode= and pstmt.group= . On Linux/Unix, an ID has a primary group and secondary groups. Secondary groups are used to allow specific groups of users/IDs to have access to appropriate sets of files, like setting entitlements. But the actual group assigned to the file has to match. When creating a file, the assigned group is the primary group of the ID, which may be and should generally be very restrictive. Changing the group to a controlled common secondary group and then being able set the mode of the file to 640 maintains security restrictions for access while keeping the same owner ID for the file.

What is your industry? Banking
How will this idea be used?

This will allow for a local NDM node to better control landed file access and permissions, improving security.