In a recent note, Gilbert Saint-Flour said:
> Date: Tue, 31 Jan 2006 09:36:17 -0500
>
> We are currently converting a large number of VSE JCL streams to a z/OS
> 1.6 environment with HSM. These VSE job streams include hundreds of
> Databack (a Macro4 product) COPY and RESTORE steps which are converted
> to DFSMSdss. We currently add an IDCAMS DELETE step before each COPY
> or RESTORE to delete the output data sets and prevent COPY and RESTORE
> from failing if the target data set exists already (see example below).
> IDCAMS DELETE will NOT RECALL migrated data sets.
>
> Would it be a good idea to remove the IDCAMS DELETE steps and specify
> REPLACEUNCONDITIONAL instead?
>
TSO DELETE at least is smart in this respect. It won't RECALL a
migrated data set merely to delete it (Likewise ISPF DSLIST).
In the Bad Old Days it wasn't so nice, and I habitually coded
in EXECs:
address 'TSO' 'HDELETE' DSName
address 'TSO' 'DELETE' DSName
(I don't recall whether HSM requests were processed FIFO, or whether
I needed to do HDELETE WAIT to resolve a race.)
Related thought on automatic RECALL: in DSLIST I enter Info or Browse
on several data sets of which some are migrated. On entering END on
each, I get "WAITING FOR RECALL" on the next. Wouldn't it be nice
if the RECALLs were performed concurrently with my think latency?
-- 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
