Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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
Workspace z/OS
Categories USS
Created by Guest
Created on Dec 31, 2014

CICS - automount permissions for UNIX files

Preparing our environment for Java, we engaged our operating systems and security groups to help with file allocations for CICS JVM directories. These allocations occur when a CICS JVM is installed into the region. The UNIX automount feature was utilized to eliminate the need for of defining mount points in the BPXPRM member of parmlib.

This works and allows CICS JVMs to run and create files as needed within the automount generated. The issue we are struggling with is this: The CICS region userid is in a different RACF group than the CICS staff userids, and the allocation permissions make it difficult for staff to manage these files, or even to look at them.

A solution our infosecurity came up with is to combine the CICS region userids and staff userids into one RACF group. This effectively puts the userids of both CICS region and staff into two groups at once. This will work but we must first alter the group owner to the shared group, which requires unique authority. We would like to somehow force the group owner to the shared group name in the automount but have not had any luck so far.

We would like to be able to control the group owner and/or permissions on the allocation.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 24, 2021

    .This item is not in our plans but is being kept in our backlog.

  • Guest
    Reply
    |
    Jan 8, 2015

    The requirement is saying that when the USS automounter process is used, the customer wants to give r/w permissions to the creating process (CICS) and r/o permission to another group (the admins). This makes a lot of sense. However the problem is not within the remit of CICS to solve but is an issue for USS, either via the FILE.GROUPOWNER.SETGID profile which controls how the gid is set or by using file inheritence ACLs. However, both of these processes do not work for file system mounts as inheritance only works from the start of the mount point.

    The requirement will be transferred to our colleagues in z/OS to give an opinion.

  • Guest
    Reply
    |
    Jan 8, 2015

    Creating a new RFE based on Community RFE #63921 in product z/OS.

  • Guest
    Reply
    |
    Jan 8, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - zSeries Software
    Product - z/OS
    Component - USS
    Operating system - IBM z/OS

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server
    Component - Runtime
    Operating system - IBM z/OS