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 Functionality already exists
Workspace z/OS
Categories DFSMS DSS
Created by Guest
Created on Nov 30, 2023

DUMP Full list datset who were on the volume

Once upon a time, with DFDSS when you do Dump full you can only do a restore full.

Since many years, you are able to restore a dataset unless the dump was full.

The problem is that you never had the list of dataset contained on the dump full.

Obviously you can do a logical restore with a typrun norun to read the DUMP volume and have the list of dataset contained on the dump volume, but the less expensive effort and efficient should be that at the beginning of the DUMP, DFDSS do a list of datset contained on the volume.

Additionnaly, if during the DUMP Full, DFDSS can be interfaced with UIM to give a chance to the customer to keep the list for formatting to upload to disaster site, it will be perfect.

If on UIM exit, if customer can have dataset information like creation date, dsorg etc ... it will be better.

Thanks.

Idea priority Low
  • Guest
    Reply
    |
    Mar 6, 2024

    Hello,

    Sorry but i don't want to know how to do the list in another way, i have already found another solution to circumvent the problem.

    I need that DFDSS list who files were dumped during a physical dump. The best way is that DFDSS list files during the process. DFDSS should list the files dumped and not to add some steps to keep this informations. Because DFDSS is a tools used for backup and other function, it is normal that DFDSS list files treated and not use another process in another way. If you have two steps you have no argument to said that the file was on the dasd during the list and not after. My problem and request is only with a physical full dump. I think it is not so difficult to change DFDSS to do the list a dataset dumped during a physical DUMP.

  • Guest
    Reply
    |
    Feb 15, 2024
    Thank you for your request. This functionality already exists in a few forms:
    - One can perform an ADRDSSU PRINT of the VTOC, or an IEHLIST of the volume prior to the back up to obtain this information..Recommended if one is managing their own backups.
    - As mentioned, a TYPRUN=NORUN logical data set of the volume prior to the backup being performed
    - It its typical to perform a TYRUN=NORUN physical data set restore of a fulll volume dump image to determine what data sets are on the volume.
    - As for the application interface of a full volume dump operation, we offer EIOPTION06 where we present the blocks we write to the dump data set. Using this exit and our ADRTAPB macro, one can determine the VTOC tracks and obtain the information programatically.