At 20:58 -0500 on 10/10/2012, Mike Schwab wrote about Re: DFHSM
Recalls and Tape:
When it HSM finishes a recall, it checks the que in order for any
recall on the same tape. When it reaches the end of the que, it
unmounts the tape, and starts recalling the first waiting dataset on
the que. Haven't done as massive a quantity as 10,000 though.
No sorting of any kind, just checking the que DSN against the list on
the mounted tape.
So you are saying that as it reads the tape (after it has recalled a
file from the tape) it sees the next file on the tape and checks if
it is on the queue. It then either recalls the file (if it is on the
queue) or reads the tape to the next file and does the queue check
again.
From your "no sort" comment, I assume that it does not order the
queue based on restore tape volume but just runs the full queue until
it finds the dataset name or reaches the end of the queue. If the
latter it seems inefficient since if the queue was ordered by volume
serial number it could stop the scan once it reached an entry on a
different tape.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
