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.

Add a new idea Subscribe
Status Under review
Workspace IBM Java SDK for z/OS
Created by Guest
Created on Feb 16, 2024

RELATED IDEAS

Sharing one Java Shared Classcache between different users and its restrictions

We plan to use the Java Shared Classcache for our Java Batch Jobs to improve CPU usage and performance of our batch jobs. The batch jobs use for security reasons different users but should share one classcache. Sharing the same Shared Class Cache requires, that with the activation of the shared class cache via java -Xshareclasses:name=sample an additional parameter groupaccess must be used (no problem), and second (this is the problem), that all users must have the same default RACF group, or, to be more precisely, have the same GID for their default group. This is a very strong implication, especially in established environments, where default groups and their GIDs follow other rules and can't be changed easily. A better implementation would be, for example, to require for access to the cache, that the different users are member of a RACF group and this RACF group can be passed via a parameter to the job which creates the cache. Other solutions which don't require changes of over years established determinations would also be welcome. 

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.