Hello All,

Recently discovered that an ADRDSSU DUMP job ignores datasets from the INCLUDE 
selection if the source is migrated.
Looked at the documentation to find that there isn't a keyword I can use to 
force it to consider MIGRATx datasets too.

Is this ideal, or is there a case for an RFE here?
Think of a case where there's an SMS class that deletes datasets left untouched 
for a year or so.
But there's a backup job for a dataset (in that class) that runs daily.
In the case where the job hasn't run for a week or so, the dataset gets 
migrated, the backup job just completes without any warning (maybe?) about the 
exclusion of migrated datasets.
So one may be led to believe the dataset is being backed up when it is not, and 
then after a year, it's totally gone...


- Vignesh
Mainframe Infrastructure

Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670


Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to