Get the list of data sets on DASD and their information

rakaitn · New User Joined: 24 Sep 2010 Posts: 2 Location: Pune

Hello,

I need to migrate one of the mainframe applications at a shop to an emulated environment provided by Micro Focus which is going to run on Linux. As part of the migration, one of tasks is to migrate all kinds of data sets.

Is there any way (preferably a JCL) to get the list of all the data sets available on the DASD, their types and DCBs. This is required to create the catalogs in the target Linux environment.

Example:
If there are 2 sequential data sets on DASD. I need the names (both catalog & physical would be good) and DCB (Organization, Record format, Record length, Block size) etc.
For VSAM, it could be several additional information.

Thanks.
Rakesh

expat · Posted: Thu Mar 08, 2018 12:45 pm

A JCL, as you so non technically put it, does nothing other than communicate your wishes to the CPU, telling it which program and datasets you wish to play with on this occurrence.

There are many ways, ask your storage management people who will probably have access to DCOLLECT, ISMF (or whatever depending on the dataset lifecycle software in use at your shop)

You can use IEHLIST to invoke the LISTVTOC function

CSIUTIL is a REXX utility I have posted on here a few times.

So a few options for you to investigate, although given the information you have posted - I would go DCOLLECT or ISMF, although you could amend CSIUTIL to extract any further information

If you do have authority to process DCOLLECT, everything that you need to know should be in the IDCAMS manual ........ it was the last time I used it

rakaitn · New User Joined: 24 Sep 2010 Posts: 2 Location: Pune

Thank you expat for your response.

I will try to explore the options you suggested.

And I mentioned to suggest a JCL because, I was hoping to get something which can be edited and run in batch mode.

Willy Jensen · Posted: Thu Mar 08, 2018 2:15 pm

My personal favorite for VTOC listings is the VTOC program from Use [URL] BBCode for External Links file 112. It is a TSO command and can run in TSO batch.

Pete Wilson · Posted: Sat Jun 09, 2018 10:42 pm

I don't understand what you're really trying to achieve here. You say you have to 'migrate mainframe applications' to an emulated environment. I assume the 'mainframe' is an IBM Mainframe running Z/OS? And what is the 'emulated' platform going to be that runs under Linux, will that also be Z/OS? This is fairly fundamental information you need to provide. Also, when you say you're going to 'migrate' the application does that mean you want to take all the datasets with their data contents across to the new platform?

If you want to take all the datasets and contents then the simplest way is to backup all the datasets on the source system with something like DFDSS (ADRDSSU) or FDRDSF, send the backups to the new environment through FTP and then simply restore the datasets from the backups. The restore will create the datasets with all the original attributes and data content, and catalog them into the usercatalogs you have defined on the new environment.

There are other considerations such as the SMS configuration that need to be defined before any of the above can happen.