For the requests on the queue, in order. You may still be submitting requests when the first one gets processed.
On Sat, Oct 18, 2014 at 8:34 AM, Robert A. Rosenberg <[email protected]> wrote: > At 19:51 +0000 on 10/17/2014, Chase, John wrote about Re: HSM Recall > process: > >> An exception to the order of processing is when doing recalls from tape, >> where DFSMShsm reduces the number of mounts by doing several recalls from a >> given tape while the tape is continuously mounted. If a recall task has just >> completed a recall from a tape, it processes the highest-priority request >> that is currently on the queue for that same tape, no matter where the >> request is positioned on the queue. > > > Assuming that it has multiple recalls with the same priority on the tape is > it smart enough to do them in the order that they are on the tape (ie: File > Number Order) thus reading the tape sequentially or does it go with their > order on the queue (ie: In essence random) thus seeking back and forth on > the tape? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
