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.

ADD A NEW IDEA

JES2

Showing 85

A JES2 Policy that scans JCL cards is required

Submitted By: SHARE-MVSE Submitted Date: 02/05/2023 Submitter Name: Mike Shorkend (System Software Specialist) Submitter Email: mike@shorkend.com Description: The same way as JES2 provides exits 4/54 to scan all JCL cards for a job, this is needed...
about 1 year ago in z/OS / JES2 0 Future consideration

Allow the number of JES2 NODES to be reduced without a cold start

We have a number of JES2 environments which have evolved over time. Decades ago, someone decided that it would be useful to define the NODENUM on the NJEDEF init parm as 9999, meaning we now have many systems defined with 9999 possible nodes. We a...
over 1 year ago in z/OS / JES2 0 Future consideration

Provide JES2 health check to show when init parms do not match currently active parms

We have a number of JES2 environments which have evolved over time. Due to consolidation, acquisitions and simplification, JES2 init parms may have been modified without the active environment being updated. With many parameters, a JES2 warm start...
over 1 year ago in z/OS / JES2 0 Future consideration

JES2 Policy to examine the job card time parameter

We use the job card TIME parameter to assign a job class so the ability to read the value will simplify our ability to reduce/eliminate JES exits.
almost 2 years ago in z/OS / JES2 0 Future consideration

JES2 Policy - enhancement

z/OS2.4 has brought up great function of JES2 Policy however there are many fields which are not modifiable and bring a constrain in the way if we like to replace our jes2 exits. One of the example is SYSOUTGROUP where XMITTER field is not mention...
almost 2 years ago in z/OS / JES2 0 Future consideration

SDSF SJ command

Allow SJ SDSF command to support remote jobs .
almost 2 years ago in z/OS / JES2 1 Future consideration

JES2 - Improve reaction to PROCLIB moves and Open/Close

In the above IBM Case we described a problem on one of our customer's system, whereby a PROC(00) data set was moved by the customer to a new volume and the catalogue entry adapted (DELETE & DEFINE NONVSAM). We do realise this is not a good thi...
over 2 years ago in z/OS / JES2 1 Future consideration

JES2 - no automatic Reconfiguration driven after Site Outage

After a planned SITE1 outage we saw that JES2 Reconfiguration was started driven by member "x", but just a few seconds later member "x" was QUIESCED as it was running in SITE1. Because of that we see that member "Y" has taken over with RECONFIGURA...
over 2 years ago in z/OS / JES2 0 Future consideration

JES2 POLICY - read and use value of /*ROUTE XEQ node or /*XEQ node

Within the new JES2 POLICY we need the possibility to read and use the value of node name from /*ROUTE XEQ node or /*XEQ node.
over 2 years ago in z/OS / JES2 0 Future consideration

JES_NJE_SECURITY Health Check Modification

Our environments unique design does not require only one component of the JES_NJE_Security check. We've determined that we are unable to deactivate just this component and are therefore requesting that the component be separated from the original ...
almost 3 years ago in z/OS / JES2 1 Future consideration

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.