: IBM-MAIN@bama.ua.edu
Subject: Re: Problem with HSM Recalls
Thanks Tom but no dice, got the following:
ARC1118I reas - 16
16The data set record format must be fixed or fixed-blocked when
using DAOPTION(RELBLK).
-Original Message-
From: Tom Marchant [mailto:m42tom-ibmm...@yahoo
: Tuesday, September 20, 2011 1:51 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Problem with HSM Recalls
On Tue, 20 Sep 2011 10:18:12 -0400, O'Brien, David W. (NIH/CIT) [C] wrote:
>ARC1001I SYSMGT.D93132.N001606 RECOVER FAILED, RC=0008, REAS=0168
>ARC1108I ERROR CATALOGING DATA SET
>
On Tue, 20 Sep 2011 10:18:12 -0400, O'Brien, David W. (NIH/CIT) [C] wrote:
>ARC1001I SYSMGT.D93132.N001606 RECOVER FAILED, RC=0008, REAS=0168
>ARC1108I ERROR CATALOGING DATA SET
>
>The data was migrated in the early 90's, I don't see how the current track
>capacity could be exceeded. Of course no
Allan,
Specifying devtype seems to have worked. Thank You.
Now I'll see if I can recall the datasets.
-Original Message-
From: Staller, Allan [mailto:allan.stal...@kbmg.com]
Sent: Tuesday, September 20, 2011 1:19 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Problem with HSM Recalls
The message text for ICK31054I DEVICE NOT SUPPORTED FOR THE SPECIFIED
FUNCTION
Will refer you to "1.1.4 Devices supported by ICKDSF"
Which indicates in table 12 that the INSTALL command is not supported on
CU type 2105
You might try INIT UNIT(1091) VFY(NW1091) ..DEVTYPE(3380)
Allan,
I did use the Install command, see first line of output.
-Original Message-
From: Staller, Allan [mailto:allan.stal...@kbmg.com]
Sent: Tuesday, September 20, 2011 11:36 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Problem with HSM Recalls
Looks like you need to use the INSTALL
Tom, Allan,
I'm getting the following trying to test your suggestions:
INSTALL UNIT(1091) VFY(NW1091) SETMODE(3380)
I would say you need to reconfigure the volume in the HDS 9990V as a 3380
first, then initialize it.
--
--Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of O'Brien, David W. (NIH/CIT) [C]
Sent: Tuesday, September 20, 2011 10:21 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Problem with HSM Recalls
Tom, Allan,
I'm getting the following trying to t
al Message-
From: Tom Marchant [mailto:m42tom-ibmm...@yahoo.com]
Sent: Tuesday, September 20, 2011 10:52 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Problem with HSM Recalls
On Tue, 20 Sep 2011 10:18:12 -0400, O'Brien, David W. (NIH/CIT) [C] wrote:
>Message ARC1001I also precedes this m
On Tue, 20 Sep 2011 10:18:12 -0400, O'Brien, David W. (NIH/CIT) [C] wrote:
>Message ARC1001I also precedes this message, giving the operation in
>process, the name of the data set, and a reason code.
>
>Reascode Meaning
>8 Direct access data records exceed the track capacity of the
>
11 10:23 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Problem with HSM Recalls
3380/3390 conflict? Might have to define a mod-3 in 3380 compat mode.
Check the ICKDSF manuals
HTH,
A recall of the first dataset listed below results in
ARC1113I I/O ERROR WRITING PRIMARY COPY
Explanation: While DFS
Thanks Darth,
I had tried unit volume parameters with the same result.
-Original Message-
From: Darth Keller [mailto:darth.kel...@assurant.com]
Sent: Tuesday, September 20, 2011 10:28 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Problem with HSM Recalls
Dave -
You didn't provid
Allan,
probably HSM is trying to restore your dataset into its original VOLUME,
and this volume is no more active in
your configuration. Try to supply a VOLSER to HSM to relocate the dataset
on another dasd.
HTH
_
Paolo C
Dave -
You didn't provide the commands you used, but based on the REAS=0168, I'd
suggest specifying the UNIT(unittype) on your command & if necessary, the
VOLUME(volser) parameter. If it was migrated from a 3380, the recall &
recover are probably still trying to use that unit type & you need
3380/3390 conflict? Might have to define a mod-3 in 3380 compat mode.
Check the ICKDSF manuals
HTH,
A recall of the first dataset listed below results in
ARC1113I I/O ERROR WRITING PRIMARY COPY
Explanation: While DFSMShsm was writing the primary copy of a data set
during a recall or recove
A recall of the first dataset listed below results in
ARC1113I I/O ERROR WRITING PRIMARY COPY
Explanation: While DFSMShsm was writing the primary copy of a data set
during a recall or recovery operation, an I/O error occurred or invalid
data was found. If an I/O error occurred an access method or
At 10:28 -0400 on 07/28/2008, Richards, Robert B. wrote about Re: HSM Recalls:
Am I missing something? You stated that you didn't agree with me and
then proceeded to agree with my premise. Stated another way: "Only
migrate when you need more free space in your volume pools. Otherwise
At 09:17 -0500 on 07/28/2008, Adams, Rick wrote about Re: HSM Recalls:
We set the exit up to not migrate any datasets smaller than 10MB for 60
days and to not migrate datasets smaller then 5MB for 400 days.
I assume this is "since last access" not "since creation" sinc
ssion List [mailto:[EMAIL PROTECTED] On
> Behalf Of Vernooy, C.P. - SPLXM
> Sent: Monday, July 28, 2008 10:06 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: HSM Recalls
>
> I don't agree.
> First, "You don't" is not an answer to the question "how do I&
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Vernooy, C.P. - SPLXM
Sent: Monday, July 28, 2008 10:06 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Recalls
I don't agree.
First, "You don't" is not an answer to the question "how do I".
&qu
cs here and are actually in agreement.
Bob
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Vernooy, C.P. - SPLXM
Sent: Monday, July 28, 2008 10:06 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Recalls
I don't agree.
First, "You don&#
datasets not migrating were so small.
This was a win-win situation for us.
ThanksRick
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Michael Wickman
Sent: Monday, July 28, 2008 7:55 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Recalls
Just
The down side of this method is that you only have one chance to determine
the size, at dataset creation
I also believe that HSM's ARCMDEXT exit is the place to decide whether to
migrate, either ML1 or ML2, or leave it spin a little longer. And the exit
certainly isn't rocket science. The SMS
> US Office of Personnel Management
> 1900 E Street NW Room: BH04L
> Washington, D.C. 20415
> Phone: (202) 606-1195
> Email: [EMAIL PROTECTED]
> ---------
>
&
Email: [EMAIL PROTECTED]
-
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Vernooy, C.P. - SPLXM
Sent: Monday, July 28, 2008 9:12 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Recalls
The down side of this method is that yo
_
>
> From: Michael Wickman [mailto:[EMAIL PROTECTED]
> Sent: Mon 7/28/2008 8:55 AM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: HSM Recalls
>
>
>
> Just curious how you select for migration base on size. Do you set
> special management class based on prima
Not HSM, selection is done by assigning SMS Management class based on size in
the SMS ACS routine.
From: Michael Wickman [mailto:[EMAIL PROTECTED]
Sent: Mon 7/28/2008 8:55 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Recalls
Just curious how you select for
mwickman at waddell dot com
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ted MacNEIL
Sent: Thursday, July 24, 2008 4:56 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: [IBM-MAIN] HSM Recalls
>We
AMA.UA.EDU
Subject: Re: HSM Recalls
There is, and it does. It starts a TCB for each file in the whole job
that needs recalling following the place where RECALL is invoked. In
each TCB it issues HRECALL for one file and WAIT's for the recall to
finish.
Beware though -- If your shop's &q
That program does not work when the DSN specified is the base GDG
name.
Thank You
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Stephen Y Odo
Sent: Friday, July 25, 2008 2:48 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Recalls
We&#x
We're using a program from the CBT tape ... I think it's from Gilbert
Saint-flour ... to do just that ...
--Stephen
Itschak Mugzach wrote:
Why don't you pre-recall files with OpenTech's Hrecall product? It will cut
a lot of job waits for you.
Itschak
--
frame Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Farley, Peter x23353
Sent: Thursday, July 24, 2008 3:20 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Recalls
There is, and it does. It starts a TCB for each file in the whole job
that needs recalling following the place where RECALL is invoke
--Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Robert A. Rosenberg
Sent: Friday, July 25, 2008 7:10 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Recalls
At 16:19 -0400 on 07/24/2008, Farley, Peter x23353 wrote about Re: HSM
Recalls:
>There is, and
At 16:19 -0400 on 07/24/2008, Farley, Peter x23353 wrote about Re: HSM Recalls:
There is, and it does. It starts a TCB for each file in the whole job
that needs recalling following the place where RECALL is invoked. In
each TCB it issues HRECALL for one file and WAIT's for the recall to
f
>We do not migrate anything smaller than 5mb since the overhead of migrating
>them and having them recalled later was greater than the cost of just leaving
>them on disk!
I mentioned this on IBM-Main many years ago.
I was told I was full of s**t.
Back then, it was any dataset a cylinder (.8 MB)
disk!
ThanksRick
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Farley, Peter x23353
Sent: Thursday, July 24, 2008 3:20 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: HSM Recalls
There is, and it does. It starts a TCB for each file in the whole
; To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: HSM Recalls
>
> there was at one time a program on cbt file 183 - RECALL, from
> Gilbert.
>
> Maybe it still works.
>
> Alex
This message and any attachments are intended only for the use of the addressee
and
may contain inform
there was at one time a program on cbt file 183 - RECALL, from Gilbert.
Maybe it still works.
Alex
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN
Normal batch allocation proceeds on a data by dataset basis and so
DFHSM recalls happen as it is detected that each GDS is migrated. If you
wish to have the recalls proceed in parallel, then you can issue HRECALL
commands for each individual GDS (the default is NOWAIT) say from TSO
in batch (probab
I have this job that calls in all generations of a dataset. This job
executes once a month and most of the generation have been migrated.
When the job starts executing is sends the request to HSM to start the
recalls. It recalls the migrated datasets one at a time. Is there a way
to make more recal
40 matches
Mail list logo
