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 84 of 3358

Retain policy source with internal policy object, add to $DPOLICY information

Retaining the source data set & member information for a policy provides history for problem resolution and disaster recovery. It should be displayed on a $DPOLICY (could be a ,LONG) option.
9 months ago in z/OS / JES2 0 Future consideration

Unsupported NJE remote executed commands improvement

The existing implementation of the $N command for NJE remote command execution does not fully support all commands. For instance, the $TA and $VS commands when send via the $N routing results in the issuance of $HASP649 - this is not a good error ...
almost 3 years 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 did not issue the $HASP256 message

We hit a problem where JES2 did not issue the $HASP256 message indicating that after a JES2 checkpoint reconfiguration dialog there is no long a value for NEWCKPT1. With the current design of the dialog, it is only the member of the MAS that drive...
almost 5 years ago in z/OS / JES2 1 Future consideration

JES2 health monitor for converter tasks

JES2 health monitor task should detect that all of the converter TCBs are in a long wait and issue an appropriate error message.
almost 9 years ago in z/OS / JES2 2 Future consideration

Group initiator controls in jes2

Currently in Jes3 initiator counts can be controlled at class and group level. In jes2 although there is the concept of groups for classes, initiator counts can only be controlled at class level.I would like to see this introduced in jes2 to confo...
about 5 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

Provide ability to dynamically increase JES2 initiators

Increasing the number of JES2 initiators requires a change to INITDEF PARTNUM, and then a JES2 warmstart. This is extremely disruptive and creates an outage. JES2 should provide a means to dynamically increase PARTNUM without requiring a JES2 warm...
about 4 years ago in z/OS / JES2 1 Future consideration

The mail-handling stop in JES2EDS until the failing mail has manually been removed from Queue.

If someone make an error in the Notify-parameter the mail-handling stop i JES2EDS until the failing mail has manually been removed using the $PS($EDSQ0xx),ONERROR-JES2-command.
about 1 year ago in z/OS / JES2 0 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.