Re: Problem with HSM Recalls
Tom asked off-list whether this problem had been resolved. Alas it has not. It would appear that we have very old datasets with very small blocksizes which were migrated from 3380s. Our h/w vendor tells us that we cannot re-configure a single volume to 3380 without configuring an entire array. That is not going to happen. Fortunately the user has decided to proceed without the data. It was being migrated off of the mainframe so it is questionable whether it is actually needed. The suggestion to use daoption(relblk) failed as the data is not FB. All other options failed due to track capacity exceeded. We may ask our DR provider to configure a 3380 at our next test and attempt to recover this data. Thank You, Dave O'Brien NIH Contractor From: O'Brien, David W. (NIH/CIT) [C] Sent: Tuesday, September 20, 2011 2:20 PM To: 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.com] Sent: 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 The data was migrated in the early 90's, I don't see how the current track capacity could be exceeded. Of course no one is here who is knowledgeable of what was done. I'm open to suggestions. Continuing with the assumption that the error is caused because the blocksize is very small so that not as many blocks can fit on a track as were on the original 3380, have you tried telling HRECALL to recall the data logically, without trying to recall track images? I looked in DFSMShsm Managing Your Own Data and I see DAOPTION(RELBLK) for non-SMS data sets. Perhaps that will help. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Problem with HSM Recalls
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 hardware error message should precede this message or be found in the DFSMShsm job log SYSMSG data set. 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 output device. Attempting to recover the backup with a rename results in 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 one is here who is knowledgeable of what was done. I'm open to suggestions. TIA, Dave O'Brien -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
3380/3390 conflict? Might have to define a mod-3 in 3380 compat mode. Check the ICKDSF manuals HTH, snip 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 hardware error message should precede this message or be found in the DFSMShsm job log SYSMSG data set. 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 output device. Attempting to recover the backup with a rename results in 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 one is here who is knowledgeable of what was done. I'm open to suggestions. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
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 to over-ride it. HTH's ddk /// 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 hardware error message should precede this message or be found in the DFSMShsm job log SYSMSG data set. 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 output device. Attempting to recover the backup with a rename results in 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 one is here who is knowledgeable of what was done. I'm open to suggestions. TIA, Dave O'Brien This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
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 Cacciari IBM Italia S.p.A. Sede Legale: Circonvallazione Idroscalo - 20090 Segrate (MI) Cap. Soc. euro 384.747.048,00 C. F. e Reg. Imprese MI 01442240030 - Partita IVA 10914660153 Società soggetta all?attività di direzione e coordinamento di International Business Machines Corporation (Salvo che sia diversamente indicato sopra / Unless stated otherwise above) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
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 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 to over-ride it. HTH's ddk /// 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 hardware error message should precede this message or be found in the DFSMShsm job log SYSMSG data set. 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 output device. Attempting to recover the backup with a rename results in 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 one is here who is knowledgeable of what was done. I'm open to suggestions. TIA, Dave O'Brien This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
Thanks Allan, I'll look into the possible 3390 compatibility issue. I had discounted it since the devtype that shows up in listcat is the same as for recalls that are working. -Original Message- From: Staller, Allan [mailto:allan.stal...@kbmg.com] Sent: Tuesday, September 20, 2011 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, snip 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 hardware error message should precede this message or be found in the DFSMShsm job log SYSMSG data set. 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 output device. Attempting to recover the backup with a rename results in 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 one is here who is knowledgeable of what was done. I'm open to suggestions. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
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 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 output device. Attempting to recover the backup with a rename results in 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 one is here who is knowledgeable of what was done. I'm open to suggestions. If the data set originally resided on a 3380 and it has a very small blocksize, you might see this. For example, if it has a blocksize of 80, a 3380 track will hold 83 blocks but a 3390 will only hold 78. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
Tom, Allan, I'm getting the following trying to test your suggestions: INSTALL UNIT(1091) VFY(NW1091) SETMODE(3380) ICK00700I DEVICE INFORMATION FOR 1091 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 2105 STORAGE CONTROL DESCRIPTOR = E8 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 1091 NED=002105. .HTC.65.00045342 ICK03091I EXISTING VOLUME SERIAL READ = NW1091 ICK31054I DEVICE NOT SUPPORTED FOR THE SPECIFIED FUNCTION ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 11:12:5709/20/11 Am I missing something or is this a no-go given my hardware? The address 1091 is currently a 3390 mod-3 on a HDS 9990V marketed by Oracle/Sun/STK. Thanks, Dave O'Brien -Original 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 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 output device. Attempting to recover the backup with a rename results in 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 one is here who is knowledgeable of what was done. I'm open to suggestions. If the data set originally resided on a 3380 and it has a very small blocksize, you might see this. For example, if it has a blocksize of 80, a 3380 track will hold 83 blocks but a 3390 will only hold 78. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
Looks like you need to use the INSTALL command, not the INIT command. See 2.1.1.3 Setting an IBM 3390 to 3380 track compatibility mode in GC35-0033-25 (ICKDSF R17 dated 12-14-02) Al Staller | Z Systems Programmer | KBM Group | (Tel) 972 664 3565 | allan.stal...@kbmg.com -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 test your suggestions: INSTALL UNIT(1091) VFY(NW1091) SETMODE(3380) ICK00700I DEVICE INFORMATION FOR 1091 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 2105 STORAGE CONTROL DESCRIPTOR = E8 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 1091 NED=002105. .HTC.65.00045342 ICK03091I EXISTING VOLUME SERIAL READ = NW1091 ICK31054I DEVICE NOT SUPPORTED FOR THE SPECIFIED FUNCTION ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 11:12:5709/20/11 Am I missing something or is this a no-go given my hardware? The address 1091 is currently a 3390 mod-3 on a HDS 9990V marketed by Oracle/Sun/STK. Thanks, Dave O'Brien -Original 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 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 output device. Attempting to recover the backup with a rename results in 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 one is here who is knowledgeable of what was done. I'm open to suggestions. If the data set originally resided on a 3380 and it has a very small blocksize, you might see this. For example, if it has a blocksize of 80, a 3380 track will hold 83 blocks but a 3390 will only hold 78. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
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. - ICK00700I DEVICE INFORMATION FOR 1091 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 2105 STORAGE CONTROL DESCRIPTOR = E8 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 1091 NED=002105. .HTC.65.00045342 ICK03091I EXISTING VOLUME SERIAL READ = NW1091 ICK31054I DEVICE NOT SUPPORTED FOR THE SPECIFIED FUNCTION ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 11:12:5709/20/11 Am I missing something or is this a no-go given my hardware? The address 1091 is currently a 3390 mod-3 on a HDS 9990V marketed by Oracle/Sun/STK. Thanks, Dave O'Brien -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
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 command, not the INIT command. See 2.1.1.3 Setting an IBM 3390 to 3380 track compatibility mode in GC35-0033-25 (ICKDSF R17 dated 12-14-02) Al Staller | Z Systems Programmer | KBM Group | (Tel) 972 664 3565 | allan.stal...@kbmg.com -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 test your suggestions: INSTALL UNIT(1091) VFY(NW1091) SETMODE(3380) ICK00700I DEVICE INFORMATION FOR 1091 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 2105 STORAGE CONTROL DESCRIPTOR = E8 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 1091 NED=002105. .HTC.65.00045342 ICK03091I EXISTING VOLUME SERIAL READ = NW1091 ICK31054I DEVICE NOT SUPPORTED FOR THE SPECIFIED FUNCTION ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 11:12:5709/20/11 Am I missing something or is this a no-go given my hardware? The address 1091 is currently a 3390 mod-3 on a HDS 9990V marketed by Oracle/Sun/STK. Thanks, Dave O'Brien -Original 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 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 output device. Attempting to recover the backup with a rename results in 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 one is here who is knowledgeable of what was done. I'm open to suggestions. If the data set originally resided on a 3380 and it has a very small blocksize, you might see this. For example, if it has a blocksize of 80, a 3380 track will hold 83 blocks but a 3390 will only hold 78. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
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).. Not sure if this will work, but it's worth a try After that I would go to IBM and/or Oracle... HTH, snip I'm getting the following trying to test your suggestions: INSTALL UNIT(1091) VFY(NW1091) SETMODE(3380) ICK00700I DEVICE INFORMATION FOR 1091 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 2105 STORAGE CONTROL DESCRIPTOR = E8 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 1091 NED=002105. .HTC.65.00045342 ICK03091I EXISTING VOLUME SERIAL READ = NW1091 ICK31054I DEVICE NOT SUPPORTED FOR THE SPECIFIED FUNCTION ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 11:12:5709/20/11 /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem with HSM Recalls
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).. Not sure if this will work, but it's worth a try After that I would go to IBM and/or Oracle... HTH, snip I'm getting the following trying to test your suggestions: INSTALL UNIT(1091) VFY(NW1091) SETMODE(3380) ICK00700I DEVICE INFORMATION FOR 1091 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 2105 STORAGE CONTROL DESCRIPTOR = E8 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 1091 NED=002105. .HTC.65.00045342 ICK03091I EXISTING VOLUME SERIAL READ = NW1091 ICK31054I DEVICE NOT SUPPORTED FOR THE SPECIFIED FUNCTION ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 11:12:5709/20/11 /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
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 The data was migrated in the early 90's, I don't see how the current track capacity could be exceeded. Of course no one is here who is knowledgeable of what was done. I'm open to suggestions. Continuing with the assumption that the error is caused because the blocksize is very small so that not as many blocks can fit on a track as were on the original 3380, have you tried telling HRECALL to recall the data logically, without trying to recall track images? I looked in DFSMShsm Managing Your Own Data and I see DAOPTION(RELBLK) for non-SMS data sets. Perhaps that will help. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
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.com] Sent: 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 The data was migrated in the early 90's, I don't see how the current track capacity could be exceeded. Of course no one is here who is knowledgeable of what was done. I'm open to suggestions. Continuing with the assumption that the error is caused because the blocksize is very small so that not as many blocks can fit on a track as were on the original 3380, have you tried telling HRECALL to recall the data logically, without trying to recall track images? I looked in DFSMShsm Managing Your Own Data and I see DAOPTION(RELBLK) for non-SMS data sets. Perhaps that will help. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
