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 DFSMS HSM
Created by Guest
Created on Feb 7, 2019

ACEROJOB in IDGACERO not filled for HSM recall, IDGACSSC exit

We are using IGDACSSC SMS exit for retrieving information about the recalls done by HSM. During the recalled data set allocation our IGDACSSC module gets control and we read the IGDACERO control block. The ACEROJOB variable is blank for recall (we get the same behavior with ACS routines for recall, variable &JOB is also blank in that case). We are aware that this behavior is properly documented in SMS documentation (jobname is not populated in RECALL environment), that is why we are opening the enhancement request. Reason why we would like to be able to retrieve the name of the job which initiated the recall is that we have an object in CA Vantage which is supposed to show that job name, and this field is always empty. For CA Disk, we already have the value.

Idea priority Medium