Utility to list all migration sizes

[Lizette Koehler]

I am in the process of writing a rexx to read a list of datasets and then display the file attributes are DFHSM knows then if they are in MIGRAT status. Otheriwse it uses LISTDSI to get the info.

Other that doing a lot of HLIST commands and trapping the output, is there a better way to do this? I have about 150,000 datasets to do this against.

Thanks

Lizette

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX

[Glenn Knickerbocker]

On 11 May 2012 12:33:29 -0700, Lizette Koehler wrote:
>Other that doing a lot of HLIST commands and trapping the output, is
>there a better way to do this?

I had a similar question this week and was directed to the Catalog Search
Interface. If your data sets share high-level qualifiers so that you can
list them in one shot using wild cards, you can get all the info from the
CSI at once. The CSI is documented in the DFSMS Managing Catalogs
manual, and there's a Rexx sample in SYS1.SAMPLIB(IGGCSIRX).

ŹR http://users.bestweb.net/~notr/zangelding.html "When there's
a nuclear attack, that's when buckets are used." --Tim Brown, IUSD

[Andreas Fischer]

the catalog search interface is very useful, but when it comes to detailed
attributes of migrated data sets, it won't help you (well at least as far
as i know). i didn't find anything but trapping the hlist output when i
had a similar task.

regards,
andi


TSO REXX Discussion List <TSO-...@VM.MARIST.EDU> schrieb am 12.05.2012
19:45:21:

[Lizette Koehler]

Basically, I will get a request from a user, I need HLQ.** on dasd for x
amount of time. In this case they will be DB2 tables (vsam linear). So I
need to have some idea of

1) How many datasets
2) How much dasd is required
3) Make sure they get migrated asap afterwards and recover any temp dasd (ha
ha) added for the duration.

The request is not an issue if the questions can be answered. So I am
trying to create a REXX/ISPF process that the users can use to produce the
answers to the first two questions.

It would be better if they could limit their requests, but sometimes that is
difficult as they do not know what tables in DB2 are going to be used.

So the cat in most cases is fairly fat.

Any other thoughts are appreciated.

Lizette

> -----Original Message-----
> From: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] On Behalf
Of
> Adrian Stern
> Sent: Sunday, May 13, 2012 9:33 AM
> To: TSO-...@VM.MARIST.EDU
> Subject: Re: [TSO-REXX] Antwort: Re: [TSO-REXX] Utility to list all
migration sizes
>

> I'm not sure the size in HSM will be very helpful since the datasets as
far as I'm aware
> are restored in as little space as possible - that may be a site parameter
but that was
> always what happened.
>
> You can perhaps search in a back-up of the volumes before the datasets
were
> migrated - that was possible at some places I've worked.
>
> What is the requirement? There may be another way of skinning the cat.

[Ron Hesketh]

Hi Lizette
If you know which tablespaces or indexspaces the datasets belong
to, you can get the size from the SYSIBM.SYSTABLEPART SPACEF column,
and SYSIBM.SYSINDEXPART . Ths assumes that the STOSPACE utility has been
run .

Regards,
Ron.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

_______________________________________________________________________________


This email has been scanned by the Bankwest Email Security System.
_______________________________________________________________________________





_______________________________________________________________________________
Unencrypted electronic mail is not secure and may not be authentic.
If you have any doubts as to the contents please telephone to confirm.

This electronic transmission including any attachments is intended only
for those to whom it is addressed. It may contain copyright material or
information that is confidential, privileged or exempt from disclosure by law.
Any claim to privilege is not waived or lost by reason of mistaken transmission
of this information. If you are not the intended recipient you must not
distribute or copy this transmission and should please notify the sender.
Your costs for doing this will be reimbursed by the sender.

We do not accept liability in connection with computer virus, data corruption,
delay, interruption, unauthorised access or unauthorised amendment.
_______________________________________________________________________________


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

[Andreas Fischer]

you might have a good reason why you want to know the size, but is that
really necessary in this case in a sms-managed environment? my approach
would be to use rexx/sql to find the dataset names for a given db2 table
and let hsm recover those datasets. all you have to do is monitor the sms
pool, but i assume this has to be done in any case. migration of data sets
also is an sms issue itself. why would you take care of that yourself when
sms can do that for you?

andi


TSO REXX Discussion List <TSO-...@VM.MARIST.EDU> schrieb am 13.05.2012
18:53:09: