Hi, because FBID order takes precedence over priority. Hence, if a user issues
1000 NOWAIT type recalls and there is a single WAIT type recall at the end of
the same tape, then the Wait-type is going to be delayed until all of the
NOWAIT type recalls are processed.
The introduction of the se
us.ibm.com]
Sent: Friday, October 12, 2012 11:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM Recalls and Tape
In both a CRQ and nonCRQ environment, HSM will process all of the queued
requests from a mounted tape. But, there are some important differences.
In a nonCRQ environment, each HS
Agreed. The HSM default is to hold a tape for 5 seconds to wait for another
recall from the same tape to be queued. Either the next recall from the same
tape is coming in after 5 seconds, or it is arriving on another LPAR (in a
nonCRQ environment).
Glenn Wilcock
DFSMShsm Architect
--
In both a CRQ and nonCRQ environment, HSM will process all of the queued
requests from a mounted tape. But, there are some important differences.
In a nonCRQ environment, each HSM host has it's own queue. So, each host will
only process the queued requests on it's own queue. This requires eac
: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Robert A. Rosenberg
Sent: Thursday, October 11, 2012 8:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM Recalls and Tape
At 11:55 + on 10/11/2012, Hervey Martinez wrote about Re: DFHSM Recalls and
Tape:
>If
At 11:55 + on 10/11/2012, Hervey Martinez wrote about Re: DFHSM
Recalls and Tape:
If you have CRQ(Common Recall Queue) set up, then HSM will "look
ahead" and recall all files that are on the same tape. Also, with
CRQ, you can limit which LPARS will perform recalls and limit the
At 10:10 -0400 on 10/11/2012, O'Brien, David W. (NIH/CIT) [C] wrote
about Re: DFHSM Recalls and Tape:
Elardus,
I think you missed the distinction between submitting recalls and a
process causing recalls. At this shop it was not unusual for a user
to submit an Iefbr14 job to delete dat
Behalf Of Lizette Koehler
:>: Sent: Thursday, October 11, 2012 6:15 AM
:>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Re: DFHSM Recalls and Tape
:>:
:>: Everyone thanks so much for confirming what I was told.
:>:
:>: Where my problem arises is when a user wants to recall 500
On Thu, 11 Oct 2012 10:19:59 -0400, O'Brien, David W. (NIH/CIT) [C]
wrote:
>I think you missed the distinction between submitting recalls and a process
>causing recalls. At this shop it was not unusual for a user to submit an
>Iefbr14 job to delete datasets thereby causing the recall of any da
O'Brien
-Original Message-
From: Staller, Allan [mailto:allan.stal...@kbmg.com]
Sent: Thursday, October 11, 2012 10:15 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM Recalls and Tape
See ' SYSTEM IEFBR14_DELMIGDS(NORECALL)' in SYS1.PARMLIB(ALLOCxx). New with
z/OS 1.11 (?)
See ' SYSTEM IEFBR14_DELMIGDS(NORECALL)' in SYS1.PARMLIB(ALLOCxx). New with
z/OS 1.11 (?)
At this shop it was not unusual for a user to submit an Iefbr14 job to delete
datasets thereby causing the recall of any dataset that had been migrated.
Since the recall is serial, it would result in one
result in one tape
mount per recall.
Dave O'Brien
-Original Message-
From: Elardus Engelbrecht [mailto:elardus.engelbre...@sita.co.za]
Sent: Thursday, October 11, 2012 10:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM Recalls and Tape
O'Brien, David W. wrote:
>One
O'Brien, David W. wrote:
>One caveat, if I may. Is your user submitting 5000 Hrecalls or are they
>submitting a process which will result in 5000 recalls? The latter could
>result in 5000 tape mounts.
No. Look up on TAPEMAXRECALLTASKS and MAXRECALLTASKS. So in your example with
TAPEMAXRECALLTA
gt; Dave O'Brien
> >
> > -Original Message-
> > From: Hervey Martinez [mailto:hervey.marti...@custserv.com]
> > Sent: Thursday, October 11, 2012 7:55 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: DFHSM Recalls and Tape
> >
> > If you have CR
f
> Of Hervey Martinez
> Sent: Thursday, October 11, 2012 6:08 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DFHSM Recalls and Tape
>
> Dave,
>
> Yes I've heard that but have never seen it done without CRQ.
>
> Regards,
>
> Hervey
>
>
> -Ori
rsday, October 11, 2012 9:15 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM Recalls and Tape
Everyone thanks so much for confirming what I was told.
Where my problem arises is when a user wants to recall 5000 or more datasets.
I was concerned that the recall process would serialize it rather
ording to
> tape volume in order to minimize tape mounts with or without CRQ.
>
> Dave O'Brien
>
> -Original Message-
> From: Hervey Martinez [mailto:hervey.marti...@custserv.com]
> Sent: Thursday, October 11, 2012 7:55 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subje
: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM Recalls and Tape
Hervey,
That is not true, at least not at this shop. HSM routinely queues recalls
according to tape volume in order to minimize tape mounts with or without CRQ.
Dave O'Brien
-Original Message-
From: Hervey Martinez [mail
2012 7:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM Recalls and Tape
If you have CRQ(Common Recall Queue) set up, then HSM will "look ahead" and
recall all files that are on the same tape. Also, with CRQ, you can limit which
LPARS will perform recalls and limit them in that
pen one at a time in a FIFO
manner.
Regards,
Hervey
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Robert A. Rosenberg
Sent: Thursday, October 11, 2012 3:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHSM Recalls and Tape
At 20:5
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
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 checki
On 10/10/2012 6:27 PM, Lizette Koehler wrote:
Just want to make sure I understand what IBM told me once.
Is it true that when you have a large number of recalls (and I am talking
10,000 or more at a time) that HSM will identify which ones are on which
migration tapes and stack them accordingly
UA.EDU]
> On Behalf Of Lizette Koehler
> Sent: Wednesday, October 10, 2012 3:28 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: DFHSM Recalls and Tape
>
> Just want to make sure I understand what IBM told me once.
>
> Is it true that when you have a large number of recalls (and
Just want to make sure I understand what IBM told me once.
Is it true that when you have a large number of recalls (and I am talking
10,000 or more at a time) that HSM will identify which ones are on which
migration tapes and stack them accordingly. Or is it still a manual process of
identifyi
25 matches
Mail list logo
