In a recent note, R.S. said: > Date: Wed, 24 Jan 2007 16:42:40 +0100 > > This is something I fight against. Sometimes the dataset is never > opened. For example it is kind of "exception report". In case of no > exceptions the dataset remains "untouched". It cannot be backed up due > to invalid DSORG, so it will *never* be migrated or deleted according to > mgmt class parameters. It occupies the best DASD space. > But you can't print or view that exception report because of the invalid attributes; DSORG, RECFM, whatever.
ISTR an era when HSM refused to migrate a PDS with no members. At z/OS 1.7 there is no such problem; I just created an empty PDS, migrated it (primary) and recalled it. HSM performed extent reduction and truncation, which might not always be desirable. Migrating or backing up a data set with incomplete attributes ought to be a trivial operation: HSM should make a memorandum in the Migration Catalog with the available attributes and scratch the data set. Later, when the data set is allocated, HSM could emulate the recall by allocating with the saved attributes, and a putative open for output will complete the description or fail with Sx13. How does HSM deal with migrating a data set allocated with a full set of valid attributes but never opened, so the extents contain data invalid for the DSORG, etc. Again, my philosophy is that DS1LSTAR should be preemptive: if HSM were to stop copying at DS1LSTAR it would never perceive any problem. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
