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 SMP/E
Created by Guest
Created on Apr 4, 2022

z/OSMF Software Update tasks needs to wait for migrated datasets to be recalled instead of abend

z/OSMF Software Update tasks needs to wait for migrated datasets to be recalled instead of abend right away when it finds a dataset it needs, to be migrated.

Idea priority Medium
  • Guest
    Reply
    |
    May 12, 2023

    I vote +1 for this idea, and the reasons for it are already mentioned: our SMP/e environments are also migrated by CA-Disk, causing the z/OSMF REXX to fail.

    We initially thought the failure was related to the WAITFORDSN-parameter within SMP/e, which is used for the same purpose.

    So now basically we must first create an other process, outside of z/OSMF (!), to recall all datasets.
    This is something that should be dealt with by the software, not by 'man'.

    1 reply
  • Guest
    Reply
    |
    Aug 26, 2022
    Thank you for the information. From the error screen capture you provided I can see you are using CA-Disk for data set migration. My understand is that there is an issue specifically with how CA Disk interacts with an application in TSO which led Software Update to stop the update process when it detects data sets being recalled by CA-Disk. The same problem does not occur for data sets migrated using IBM DFSMShsm. In any case, we will look further into the CA-Disk and z/OSMF Software Update interaction and consider enhancements and fixes to address this issue with CA-Disk in the future. Thank you.
  • Guest
    Reply
    |
    Jun 14, 2022

    The error looks like this:

  • Guest
    Reply
    |
    Jun 13, 2022

    In our case datasets containing the SMP/E global-, target- and dlib zones will be migrated if not used for some time. When we started using SWU, the recall request was issued of course, but the z/OSMF SWU dialog did not wait for that recall to finish but it immediately abended.

  • Guest
    Reply
    |
    Jun 2, 2022
    Thank you for your submission. However, can you please provide more information? What data sets are migrated that you wish Software Update to wait for recall?