-------------------<snip>------------------
Thank you for improving my understanding.
But still ...
It appears that the consensus of this thread is that in the absence
of the NONVSAM option, IDCAMS converts a DELETE request for a migrated
data set to HDELETE. If IDCAMS doesn't know whether the migrator is
HSM, FDRABR, or some other product, how does it know what component
to issue the converted DELETE to?
--------------------<unsnip>---------------------
I would estimate, with absolutely NO facts to back my estimate, that
rather than issuing a true "HDELETE" command, that IDCAMS is using smoe
sort of subsystem interface call. That being the case, a mnigrator,
whether HSM, ABR or whatever, would also accept the request via the same
mechanism. As for knowing whether the target is a VSAM cluster or a
non-VSAM dataset, what difference does it make, as long as the
"migrator" can locate the name, and thus the data to be deleted?
-------------------<snip>-----------------------
If the interfaces are compatible and, as I still believe, the migrator
must know the VSAM-ness in order to perform the deletion without recall,
it could as well return that characteristic in response to an HLIST or
equivalent API query. There's considerable value in avoiding recall
of an entire data set in order to obtain one bit of information.
--------------------<unsnip>--------------------
All things considered, what difference does it make? You're still going
to need to HRECALL (or equivalent) that dataset before you can do
anything with the contents; we don't, as yet, have a direct I/O
interface to the migrated form.
HSM and ABR do excellent jobs of storage management; let the "black box"
do what it does best. :-)
----------------------------------------------------------------------
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
