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

Status Future consideration
Workspace z/OS
Categories JES2
Created by Guest
Created on Jul 20, 2019

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
drives the dialog that then issues this highlighted message once the reconfiguration is complete.
We would like to have all members issue the
$HASP256 (where the driver issues it as a highlighted message and the other members issue it just to syslog).
In this manner, automations can detect there is no longer a value for NEWCKPT1 even if the driving system fails.

Idea priority Medium
  • Guest
    Reply
    |
    Apr 15, 2020

    In z/OS 2.4, a health check named JES2_CKPT_CONFIG_nodename was added to detect, among other things, that the NEWCKPTn data set is not set appropriately. Until this request can be completed, the messages from this health check can be used to detect that the value for NEWCKPTn is null.