Skip to Main Content
IBM Z Software
Hide about this portal


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.

Require that SMF retain original ID for batch jobs

See this idea on ideas.ibm.com

Current design for SMF batch job data (Type-30 and others) provides data fields for SUBMITTER and EXECUTION IDs. When more than 2 Surrogate IDs are used within job-to-job submissions and the number of job-to-job submissions with different IDs exceeds 2, the original submitter ID no longer appears in the SMF data. This removes the detail needed to identify the original batch job submitter as well as the date, time, and location of submission.

Idea priority Urgent
  • ADMIN RESPONSE
    Sep 24, 2024

    Information needed to pursue this request was not provided.

  • Guest
    Reply
    |
    Sep 24, 2024

    Thank you for submitting your idea for zSecure. We appreciate you taking time to help improve the product. At this time, we have not received requested information to clarify the request from the submitter and are no longer considering it. If you can provide the requested details in the future, we can reopen and better evaluate the request.

  • Admin
    Pradeep Parameshwaran
    Reply
    |
    Aug 21, 2024

    Hi Raymond,


    I'm trying to understand more of a context here. For me the scenario you explained looks more like auditing facility inside RACF. if yes can you please open this RFE towards RACF: This is idea portal for IBM Z Security and Compliance Center.

  • Guest
    Reply
    |
    Jan 3, 2024

    When a breach occurs on z/OS, the person or team responsible for detecting and remediating the source of the breach needs to know:

    1. Which ID was used to initiate the event

    2. How entry to the system was obtained

      1. Misuse of an existing service that already had access

      2. Compromise of a user login account

    When a Surrogate ID is used to perform the breach (usu. with escalation of privilege), the originating ID must be identified. If the breach is still in progress, time is of the essence and the research must be done quickly. If Surrogate to Surrogate access exists and the SMF data does not identify the initial submitter, the researcher must follow the submit chain which could cross multiple sysplex environments, subsystems, and privileged and non-privileged IDs.