Skip to Main Content
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.

Status Delivered
Created by Guest
Created on Oct 15, 2014

RDz - JES Purge/Cancel Enhanecment

Please enhance RDz to verify the issuer of all job cancel, hold and release functions has RACF ALTER access to the JESSPOOL resource profile for the job prior to issuing any $C, $H or $A JES2 console commands. JES2 only validates that the issuer of $C/$H/$A has authority to issue the command; it doesn't validate that the issuer has authority to modify the job in question. That means any user w/ authority to issue $C/$H/$A console commands has authority to cancel/hold/release any job in the system. That may be sufficient authority for some installations where limited personnel have console access but RDz requires that console access be expanded to all RDz users, which breaks the security provided by restricted console access. These same job resource restrictions are enforced by other spool management products, such as SDSF and IOF. FYI, the format of the JESSPOOL resource to be used in this scenario is: class JESSPOOL profile localnodeid.userid.jobname.jobid.

Idea priority Medium
  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Developer for System z

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Developer for System z

  • Guest
    Reply
    |
    Nov 7, 2014

    This functionality already exists.

    As documented in the Host Reference Guide, Chapter 2 Security Considerations, section JES security, JMON, (RDz's JES Job Monitor) does honor JESSPOOL definitions.

    By default, JMON will only allow actions against jobs owned by the same user (LIMIT_COMMANDS=USERID). Through the FEJJCNFG configuration file, JMON can be instructed to broaden the scope, and rely on JESSPOOL definitions to allow actions against a job. There are 2 modes;
    * LIMIT_COMMANDS=LIMITED will allow a command only if it is explictly permitted by security profiles.
    * LIMIT_COMMANDS=NOLIMIT will allow a command if it is explictly permitted by security profiles, and when the JESSPOOL class is not active.

    An attempt to do an action against a job (owned by someone else) to which you do not have ALTER permit will fail

    JMON
    FEJ222N LIMIT_COMMANDS: 'LIMITED'

    JOBNAME JobID Owner
    BR14ALTR JOB00231 FEJALTER (everyone has full access)
    BR14READ JOB00230 FEJREAD (everyone has read access)
    BR14NONE JOB00229 FEJNONE (nobody has access)

    -> client, bottom right corner: Not authorized for job ...
    -> syslog
    ICH408I USER(MYUSER ) GROUP(MYGROUP ) NAME(MYNAME )
    MVS000.FEJNONE.BR14READ.JOB00230 CL(JESSPOOL)
    INSUFFICIENT ACCESS AUTHORITY
    FROM MVS000.FEJREAD.** (G)
    ACCESS INTENT(ALTER ) ACCESS ALLOWED(READ )
    ICH408I USER(MYUSER ) GROUP(MYGROUP ) NAME(MYNAME )
    MVS000.FEJNONE.BR14NONE.JOB00229 CL(JESSPOOL)
    INSUFFICIENT ACCESS AUTHORITY
    FROM MVS000.FEJNONE.** (G)
    ACCESS INTENT(ALTER ) ACCESS ALLOWED(NONE )