Re: DASD Problems
Thanks to all for your suggestions and comments on our recent DASD problem. The problem turned out to be just as Hitachi had originally said, a definition screw up on my part. ( What? You're surprised? ;) ) In defining the control units in the IOCP I had: CTL70CNTLUNIT CUNUMBR=7001,PATH=(70,71),UNITADD=((00,256)),* CUADD=0,UNIT=2105 CTL71CNTLUNIT CUNUMBR=7101,PATH=(72,73),UNITADD=((00,256)),* CUADD=1,UNIT=2105 When I should have had: CTL70CNTLUNIT CUNUMBR=7001,PATH=(70,71),UNITADD=((00,256)),* CUADD=0,UNIT=2105 CTL71CNTLUNIT CUNUMBR=7101,PATH=(72,73),UNITADD=((00,256)),* CUADD=0,UNIT=2105 Small mistake, big consequences. A BIG, BIG thank you to Raymond Noal and Sergio (Ed) Castro of Hitachi for their help in chasing down the cause of the problem, and finding a resolution for us. Now if we can only get our Quality Assurance people to okay production use... Peter The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: DASD Problems
Ok, now it's tomorrow. * * 9970 SEEN BY ALL LPARS * CHPID 80,81,82,83; CU 1100-1103; DEV 1100-12FF * * SHARED ESCON CHANNELS TO 9970 E9970M CHPID PATH=80,PCHID=164,TYPE=CNC, * SHARED HDS 9970 ALL LPARS CHPID PATH=81,PCHID=174,TYPE=CNC, * SHARED HDS 9970 ALL LPARS CHPID PATH=82,PCHID=165,TYPE=CNC, * SHARED HDS 9970 ALL LPARS CHPID PATH=83,PCHID=175,TYPE=CNC, * SHARED HDS 9970 ALL LPARS * ** 1100-11FF: HDS 9970 * CNTLUNIT CUNUMBR=1100,PATH=(80,81),UNIT=3990,UNITADD=((00,256)), * CUADD=0 CNTLUNIT CUNUMBR=1101,PATH=(82,83),UNIT=3990,UNITADD=((00,256)), * CUADD=0 * ** 1200-12FF: HDS 9970 CNTLUNIT CUNUMBR=1102,PATH=(80,81),UNIT=3990,UNITADD=((00,256)), * CUADD=1 CNTLUNIT CUNUMBR=1103,PATH=(82,83),UNIT=3990,UNITADD=((00,256)), * CUADD=1 * * 1100-12FF: HDS 9970 * IODEVICE ADDRESS=(1100,256),UNIT=3390,CUNUMBR=(1100,1101) IODEVICE ADDRESS=(1200,256),UNIT=3390,CUNUMBR=(1102,1103) * * ** 400-4FF: HDS 9970 CNTLUNIT CUNUMBR=400,PATH=(80,81),UNIT=3990,UNITADD=((00,256)), * CUADD=5 CNTLUNIT CUNUMBR=401,PATH=(82,83),UNIT=3990,UNITADD=((00,256)), * CUADD=5 * *400-4FF: HDS 9970 * IODEVICE ADDRESS=(400,256),UNIT=3390,CUNUMBR=(400,401) * ICKDSF ICK030E DEFINE INPUT DEVICE: FN FT FM, CONSOLE, OR READER CONSOLE CONSOLE ICK031E DEFINE OUTPUT DEVICE: FN FT FM, CONSOLE, OR PRINTER CONSOLE CONSOLE ICKDSF - CMS/XA/ESA DEVICE SUPPORT FACILITIES 17.0TIME: 15:02:24 08/30/07 PAGE 1 ENTER INPUT COMMAND: init unit(440) nvfy volid(TST440) INIT UNIT(440) NVFY VOLID(TST440) ICK00700I DEVICE INFORMATION FOR 0440 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = E9 DEVICE DESCRIPTOR = 0C ADDITIONAL DEVICE INFORMATION = 4A001B35 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00703I DEVICE IS OPERATED AS A MINIDISK ICK00091I 0440 NED= 2105. .HTC.14.00033015 ICK091I 0440 NED= 2105. .HTC.14.00033015 ICK003D REPLY U TO ALTER VOLUME 0440 CONTENTS, ELSE T U U ICK31061I 0440 VTOC INDEX CREATION SUCCESSFUL: VOLUME IS IN INDEX FORMAT ICK061I 0440 VTOC INDEX CREATION SUCCESSFUL: VOLUME IS IN INDEX FORMAT ICK01317I VTOC-INDEX IS LOCATED AT CCHH=X' 0002' AND IS 1 TRACKS. ICK01314I VTOC IS LOCATED AT CCHH=X' 0001' AND IS 1 TRACKS. ICK1I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 15:04:0008/30/07 ENTER INPUT COMMAND: END END ICK2I ICKDSF PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12 READY(00012); T=0.04/0.06 15:04:17 -- Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer . Israel Police National HQ. Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308
Re: DASD Problems
Hi David, The results for an Install: install unit(7000) INSTALL UNIT(7000) ICK00700I DEVICE INFORMATION FOR 7000 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = E9 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A001B35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 7000 NED= 2105. .HTC.14.00023257 ICK091I 7000 NED= 2105. .HTC.14.00023257 ICK31054I DEVICE NOT SUPPORTED FOR THE SPECIFIED FUNCTION ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 09:36:1908/30/07 Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: August 29, 2007 17:25 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DASD Problems ENTER INPUT COMMAND: CPVOL LABEL UNIT(7000) VOLID(NU7000) NOVFY That I/O error is worrisome. You might try the DSF INSTALL command to ensure that the volume really IS OK. Try INSTALL UNIT(7000) CPVOL FORMAT UNIT(7000) NVFY VOLID(NU7000) The INSTALL will take a LONG time (3-4 hours ... go get dinner) but it does media verification and the following CPVOL FORMAT should actually write on everything and label the volume. If you still get errors, then I'd say you have a media problem. ICK04000I DEVICE IS IN SIMPLEX STATE Ah, memories of 3990 dual copy mode. This just says that the unit you specified is not part of a dual copy pair. Think of it as RAID1 for 3390s. Unless you have real 3390s and real 3990s, you probably won't ever see the paired version. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: DASD Problems
Hi Stephen, The local Hitachi mainframe expert recently retired, so the people we have been dealing with are less experienced with these things. A learning process for all of us, I think. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Frazier Sent: August 29, 2007 15:49 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DASD Problems Ask Hitachi how the drive should be defined. They made the drives. They should know what is needed in the IOCP. [EMAIL PROTECTED] wrote: Hitachi says it is a problem with our definition of the drives. Seems unlikely to me, but it beats me what the problem is. So, does anyone have any ideas? Peter -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: DASD Problems
Hi Alan, Using CMS format was a left-field idea after ICKDSF failed to initialise the volume. What you didn't see is that after running a successful DDR copy of an old used volume, with DITTO I could see data on relative track 1. CMS format wiped that data away. Here's the end of a CPFMTXA run: FORMATTING OF CYLINDER 3338 ENDED AT: 09:43:07 ICK10710I I/O ERROR OCCURRED ON DEVICE 7000 CSW = EACCF8 0E400050 CCW = 05EB6F9C 4050 FILEMASK = 18 SENSE = 00090401 8000 0500 0100 69544C03 00F10F00 4CE2 ICK13010I ALLOCATION MAP NOT UPDATED CYLINDER ALLOCATION CURRENTLY IS AS FOLLOWS: TYPE START ENDTOTAL - ---- PERM 0 3338 3339 Try as we might, nothing seems able to write on relative track 0, although we seem to be able to write on every other track. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: August 29, 2007 17:54 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DASD Problems On Wednesday, 08/29/2007 at 02:24 EDT, [EMAIL PROTECTED] wrote: We are trying to get a Hitachi Lightning 9970V DASD unit working. We can attach the drives, CMS format them (with errors, but they appear to be formatted), do DDR copies to them (no errors). The one thing we can't do is write a label on them. When we run ICKDSF on the volumes we get: CMS FORMAT? With errors? What errors? Your DITTO from below shows that the volume has NOT been formatted by CMS FORMAT as he doesn't write IPL on the volume. INIT UNIT(7000) NVFY VOLID(NU7000) ... ICK10710I I/O ERROR OCCURRED ON DEVICE 7000 ICK31006I VOLUME LABEL CREATION FAILED ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 HCPERP6321I DASD 7000 AN OPERATION WAS TERMINATED BECAUSE RECORD HCPERP6321I 03 WAS NOT FOUND HCPERP6300I SENSE DATA FORMAT = 00 MSG CODE = 00 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = 86 HCPERP6302I SEEK ADDRESS = HCPERP6303I SENSE = 00090401 4000 8600 0100 61495C03 That sense code says record 3 on cyl 0 was not found. HCPDAS537A DASD 7000 THE LABEL COULD NOT BE READ Re-format the volume. Try using cpfmtxa to format it instead of CMS. Alan Altmark z/VM Development IBM Endicott The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: DASD Problems
Hi Shimon, Thanks for the IOCP listing. Three differences stand out: 1) We are defining the control units as device type 2105, whereas you are using 3990. 2) You have a PCHID parameter on your CHPID statements that out IOCP does not have. 3) You are using 3390-9s where we have 3390-3s defined. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Shimon Lebowitz Sent: August 30, 2007 08:03 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DASD Problems Ok, now it's tomorrow. * * 9970 SEEN BY ALL LPARS * CHPID 80,81,82,83; CU 1100-1103; DEV 1100-12FF * * SHARED ESCON CHANNELS TO 9970 E9970M CHPID PATH=80,PCHID=164,TYPE=CNC, * SHARED HDS 9970 ALL LPARS CHPID PATH=81,PCHID=174,TYPE=CNC, * SHARED HDS 9970 ALL LPARS CHPID PATH=82,PCHID=165,TYPE=CNC, * SHARED HDS 9970 ALL LPARS CHPID PATH=83,PCHID=175,TYPE=CNC, * SHARED HDS 9970 ALL LPARS * ** 1100-11FF: HDS 9970 * CNTLUNIT CUNUMBR=1100,PATH=(80,81),UNIT=3990,UNITADD=((00,256)), * CUADD=0 CNTLUNIT CUNUMBR=1101,PATH=(82,83),UNIT=3990,UNITADD=((00,256)), * CUADD=0 * ** 1200-12FF: HDS 9970 CNTLUNIT CUNUMBR=1102,PATH=(80,81),UNIT=3990,UNITADD=((00,256)), * CUADD=1 CNTLUNIT CUNUMBR=1103,PATH=(82,83),UNIT=3990,UNITADD=((00,256)), * CUADD=1 * * 1100-12FF: HDS 9970 * IODEVICE ADDRESS=(1100,256),UNIT=3390,CUNUMBR=(1100,1101) IODEVICE ADDRESS=(1200,256),UNIT=3390,CUNUMBR=(1102,1103) * * ** 400-4FF: HDS 9970 CNTLUNIT CUNUMBR=400,PATH=(80,81),UNIT=3990,UNITADD=((00,256)), * CUADD=5 CNTLUNIT CUNUMBR=401,PATH=(82,83),UNIT=3990,UNITADD=((00,256)), * CUADD=5 * *400-4FF: HDS 9970 * IODEVICE ADDRESS=(400,256),UNIT=3390,CUNUMBR=(400,401) * ICKDSF ICK030E DEFINE INPUT DEVICE: FN FT FM, CONSOLE, OR READER CONSOLE CONSOLE ICK031E DEFINE OUTPUT DEVICE: FN FT FM, CONSOLE, OR PRINTER CONSOLE CONSOLE ICKDSF - CMS/XA/ESA DEVICE SUPPORT FACILITIES 17.0TIME: 15:02:24 08/30/07 PAGE 1 ENTER INPUT COMMAND: init unit(440) nvfy volid(TST440) INIT UNIT(440) NVFY VOLID(TST440) ICK00700I DEVICE INFORMATION FOR 0440 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = E9 DEVICE DESCRIPTOR = 0C ADDITIONAL DEVICE INFORMATION = 4A001B35 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00703I DEVICE IS OPERATED AS A MINIDISK ICK00091I 0440 NED= 2105. .HTC.14.00033015 ICK091I 0440 NED= 2105. .HTC.14.00033015 ICK003D REPLY U TO ALTER VOLUME 0440 CONTENTS, ELSE T U U ICK31061I 0440 VTOC INDEX CREATION SUCCESSFUL: VOLUME IS IN INDEX FORMAT ICK061I 0440 VTOC INDEX CREATION SUCCESSFUL: VOLUME IS IN INDEX FORMAT ICK01317I VTOC-INDEX IS LOCATED AT CCHH=X' 0002' AND IS 1 TRACKS. ICK01314I VTOC IS LOCATED AT CCHH=X' 0001' AND IS 1 TRACKS. ICK1I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 15:04:0008/30/07 ENTER INPUT COMMAND: END END ICK2I ICKDSF PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12 READY(00012); T=0.04/0.06 15:04:17 -- Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer . Israel Police National HQ. Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: DASD Problems
If this is an internally raided device (like the Shark), INSTALL is not needed. I haven't used it for alot of years. The low level format function is done at install time by the CE (or at the factory). [EMAIL PROTECTED] wrote: Hi David, The results for an Install: install unit(7000) INSTALL UNIT(7000) ICK00700I DEVICE INFORMATION FOR 7000 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = E9 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A001B35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 7000 NED= 2105. .HTC.14.00023257 ICK091I 7000 NED= 2105. .HTC.14.00023257 ICK31054I DEVICE NOT SUPPORTED FOR THE SPECIFIED FUNCTION ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 09:36:1908/30/07 Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: August 29, 2007 17:25 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DASD Problems ENTER INPUT COMMAND: CPVOL LABEL UNIT(7000) VOLID(NU7000) NOVFY That I/O error is worrisome. You might try the DSF INSTALL command to ensure that the volume really IS OK. Try INSTALL UNIT(7000) CPVOL FORMAT UNIT(7000) NVFY VOLID(NU7000) The INSTALL will take a LONG time (3-4 hours ... go get dinner) but it does media verification and the following CPVOL FORMAT should actually write on everything and label the volume. If you still get errors, then I'd say you have a media problem. ICK04000I DEVICE IS IN SIMPLEX STATE Ah, memories of 3990 dual copy mode. This just says that the unit you specified is not part of a dual copy pair. Think of it as RAID1 for 3390s. Unless you have real 3390s and real 3990s, you probably won't ever see the paired version. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
Re: DASD Problems
Number 2 is specific to the z890 and z9. If you have an older machine you won't be able to specify it. The PCHID parameter provides indirection to the CHPID specification. You can specify the CHPID value that you want, you aren't tied to the hardware (that's what the PCHID value is). [EMAIL PROTECTED] wrote: Hi Shimon, Thanks for the IOCP listing. Three differences stand out: 1) We are defining the control units as device type 2105, whereas you are using 3990. 2) You have a PCHID parameter on your CHPID statements that out IOCP does not have. 3) You are using 3390-9s where we have 3390-3s defined. Peter -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
Re: DASD Problems
If this is an internally raided device (like the Shark), INSTALL is not needed. I haven't used it for alot of years. The low level format function is done at install time by the CE (or at the factory). Yes, it's not needed, but it does exercise a bunch of things that don't normally get exercised, and verifies the low-level format. Might be worth trying Shimon's defs. -- db
Re: DASD Problems
Peter, That answer from your local Hitachi people is UNACCEPTABLE!!! If they don't know then they can call someone at the Hitachi main support office and get the right answer. If they will not do that then call the Hitachi sale representative and demand that he fix the problem. Threaten to refer it to your legal department. If they will not fix it then you will replace it with a machine that will work and Hitachi will pay for all the costs involved in the replacement. The sails representative know that you legal department will contact the Hitachi legal department and he doesn't want that. The Hitachi corporate office will get it fixed if you get them involved. [EMAIL PROTECTED] wrote: Hi Stephen, The local Hitachi mainframe expert recently retired, so the people we have been dealing with are less experienced with these things. A learning process for all of us, I think. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Frazier Sent: August 29, 2007 15:49 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DASD Problems Ask Hitachi how the drive should be defined. They made the drives. They should know what is needed in the IOCP. [EMAIL PROTECTED] wrote: Hitachi says it is a problem with our definition of the drives. Seems unlikely to me, but it beats me what the problem is. So, does anyone have any ideas? Peter -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: DASD Problems
On 8/30/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 1) We are defining the control units as device type 2105, whereas you are using 3990. I would say 3990 is more likely to be correct. You cannot force the device to be a 2105 if it isn't. These are sensible devices (not my pun) that tell the OS what you have there. But there may be magic spells that IBM software does to IBM hardware in the initialization phase, and you may be messing things when not everyone found already that your were cheating. The EMC folks used to do things in the configuration to make the box appear like one or the other. I recall an event in the past where a simple firmware upgrade (with different defaults) made VSE fail to run on the device. Many of these tweaks are just there to fool SMS policies in z/OS. If anything is able to fool the system in thinking this is a 2105, then it would be there. Whether that is enough to serve as a test for going to real D/T2105 depends on your standards and your relation with EMC and/or IBM. As others said, INSTALL does not apply to modern DASD (it deals with alignment after the folks bumped the DASD off the truck). INIT is not done for VM DASD either. Rob
Re: DASD Problems
On Thursday, 08/30/2007 at 10:11 EDT, [EMAIL PROTECTED] wrote: 1) We are defining the control units as device type 2105, whereas you are using 3990. z/VM doesn't care about the UNIT= parameter in your IOCP. On z/VM 3.1, the control unit will operate as a 3990. 2) You have a PCHID parameter on your CHPID statements that out IOCP does not have. PCHIDs are not present on MP2K, so that's ok. You need to talk to Hitachi. Alan Altmark z/VM Development IBM Endicott
DASD Problems
Hi, We are trying to get a Hitachi Lightning 9970V DASD unit working. We can attach the drives, CMS format them (with errors, but they appear to be formatted), do DDR copies to them (no errors). The one thing we can't do is write a label on them. When we run ICKDSF on the volumes we get: init unit(7000) nvfy volid(nu7000) INIT UNIT(7000) NVFY VOLID(NU7000) ICK00700I DEVICE INFORMATION FOR 7000 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = E9 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A001B35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 7000 NED= 2105. .HTC.14.00023257 ICK091I 7000 NED= 2105. .HTC.14.00023257 ICK003D REPLY U TO ALTER VOLUME 7000 CONTENTS, ELSE T u U ICK10710I I/O ERROR OCCURRED ON DEVICE 7000 CSW = 762290 0E40005C CCW = 1D762220 405C FILEMASK = 18 SENSE = 00090401 1D00 0100 67094C02 00F00F00 4CE0 ICK31006I VOLUME LABEL CREATION FAILED ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 14:06:2408/29/07 HCPERP6321I DASD 7000 AN OPERATION WAS TERMINATED BECAUSE RECORD HCPERP6321I 03 WAS NOT FOUND HCPERP6300I SENSE DATA FORMAT = 00 MSG CODE = 00 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = 86 HCPERP6302I SEEK ADDRESS = HCPERP6303I SENSE = 00090401 4000 8600 0100 61495C03 HCPERP6303I 00F00F00 4CE1 HCPERP6304I IRB = 00C04017 19320650 0E50 0089 HCPERP6305I USERID = MAINT HCPERP2216I CHANNEL PATH ID = 70 HCPDAS537A DASD 7000 THE LABEL COULD NOT BE READ A DITTO disk browse shows this for the disk: DITTO/ESA for VMDB - Disk Browse CYL-HD-REC 0 00 000 Col 1 Format CHAR Volume7000 3390 Search limit * Rec Type Len 1...5...105...205...305...405...505...60 ** Begin of track Cyl:0 Hd:0 Reltrk:0 ** 0 CNT 8 DATA 8 1 CNT 8 KEY 4 IPL1 DATA24 2 CNT 8 KEY 4 IPL2 DATA 144 ... ... ** End of data on track *** ** Begin of track Cyl:0 Hd:1 Reltrk:1 ** 0 CNT 8 Which confirms the record 3 not found message. Our IOCP definition for the 9970V is: CHPID PATH=70,TYPE=CNC CHPID PATH=71,TYPE=CNC CHPID PATH=72,TYPE=CNC CHPID PATH=73,TYPE=CNC CTL70CNTLUNIT CUNUMBR=7001,PATH=(70,71),UNITADD=((00,256)),* CUADD=0,UNIT=2105 CTL71CNTLUNIT CUNUMBR=7101,PATH=(72,73),UNITADD=((00,256)),* CUADD=1,UNIT=2105 IODEVICE ADDRESS=(7000,256),CUNUMBR=(7001,7101), * UNIT=3390 Almost forgot, z/VM 3.1.0 service level 0402 running on an MP2000. ICKDSF release 17, module dated 2006-11-07. We specifically want to run as 2105 to flush out potential problems with using 2105s with VSE before we (hopefully) move to a z9. Hitachi says it is a problem with our definition of the drives. Seems unlikely to me, but it beats me what the problem is. So, does anyone have any ideas? Peter People who say they have nothing to hide, nothing to fear about providing their personal information, have no idea how information can be misapplied out of context, Ann Cavoukian Ontario Privacy Commissioner The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property
Re: DASD Problems
Peter, I am running EMC disk array, formatted with 3390-3 disks. Some of the information I saw below I don't see when I do a CPFMTXA format or ICKDSF label. I did notice that you were using the INIT function which I don't use. You could try what I have above just to get the CP format with a label and then try the ICKDSF INIT to get a VSE type VTOC written where you want it and put a VSE type label on it. The following message below I don't understand: ICK04000I DEVICE IS IN SIMPLEX STATE Just a quick look, good luck. Loren Charnley, Jr. IT Systems Engineer Family Dollar Stores, Inc. (704) 847-6961 Ext. 3327 (704) 814-3327 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, August 29, 2007 2:13 PM To: IBMVM@LISTSERV.UARK.EDU Subject: DASD Problems Hi, We are trying to get a Hitachi Lightning 9970V DASD unit working. We can attach the drives, CMS format them (with errors, but they appear to be formatted), do DDR copies to them (no errors). The one thing we can't do is write a label on them. When we run ICKDSF on the volumes we get: init unit(7000) nvfy volid(nu7000) INIT UNIT(7000) NVFY VOLID(NU7000) ICK00700I DEVICE INFORMATION FOR 7000 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = E9 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A001B35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 7000 NED= 2105. .HTC.14.00023257 ICK091I 7000 NED= 2105. .HTC.14.00023257 ICK003D REPLY U TO ALTER VOLUME 7000 CONTENTS, ELSE T u U ICK10710I I/O ERROR OCCURRED ON DEVICE 7000 CSW = 762290 0E40005C CCW = 1D762220 405C FILEMASK = 18 SENSE = 00090401 1D00 0100 67094C02 00F00F00 4CE0 ICK31006I VOLUME LABEL CREATION FAILED ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 14:06:2408/29/07 HCPERP6321I DASD 7000 AN OPERATION WAS TERMINATED BECAUSE RECORD HCPERP6321I 03 WAS NOT FOUND HCPERP6300I SENSE DATA FORMAT = 00 MSG CODE = 00 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = 86 HCPERP6302I SEEK ADDRESS = HCPERP6303I SENSE = 00090401 4000 8600 0100 61495C03 HCPERP6303I 00F00F00 4CE1 HCPERP6304I IRB = 00C04017 19320650 0E50 0089 HCPERP6305I USERID = MAINT HCPERP2216I CHANNEL PATH ID = 70 HCPDAS537A DASD 7000 THE LABEL COULD NOT BE READ A DITTO disk browse shows this for the disk: DITTO/ESA for VMDB - Disk Browse CYL-HD-REC 0 00 000 Col 1 Format CHAR Volume7000 3390 Search limit * Rec Type Len 1...5...105...205...305...405...505...60 ** Begin of track Cyl:0 Hd:0 Reltrk:0 ** 0 CNT 8 DATA 8 1 CNT 8 KEY 4 IPL1 DATA24 2 CNT 8 KEY 4 IPL2 DATA 144 ... ** End of data on track *** ** Begin of track Cyl:0 Hd:1 Reltrk:1 ** 0 CNT 8 Which confirms the record 3 not found message. Our IOCP definition for the 9970V is: CHPID PATH=70,TYPE=CNC CHPID PATH=71,TYPE=CNC CHPID PATH=72,TYPE=CNC CHPID PATH=73,TYPE=CNC CTL70CNTLUNIT CUNUMBR=7001,PATH=(70,71),UNITADD=((00,256)),* CUADD=0,UNIT=2105 CTL71CNTLUNIT CUNUMBR=7101,PATH=(72,73),UNITADD=((00,256)),* CUADD=1,UNIT=2105 IODEVICE ADDRESS=(7000,256),CUNUMBR=(7001,7101), * UNIT=3390 Almost forgot, z/VM 3.1.0 service level 0402 running on an MP2000. ICKDSF release 17, module dated 2006-11-07. We specifically want to run as 2105 to flush out potential problems with using 2105s with VSE before we (hopefully) move to a z9. Hitachi says it is a problem with our definition of the drives. Seems unlikely to me, but it beats me what the problem is. So, does anyone have any ideas? Peter People who say they have nothing to hide, nothing to fear about providing their personal information, have no idea how information can be misapplied out of context, Ann Cavoukian Ontario Privacy Commissioner The information transmitted is intended only
Re: DASD Problems
Hi Loren, I tried a CPFMTXA: cpfmtxa 7000 NU7000 Label HCPCCF6209I INVOKING ICKDSF. ICK030E DEFINE INPUT DEVICE: FN FT FM, CONSOLE, OR READER CONSOLE ICK031E DEFINE OUTPUT DEVICE: FN FT FM, CONSOLE, OR PRINTER CONSOLE ICKDSF - CMS/XA/ESA DEVICE SUPPORT FACILITIES 17.0TIME: 15:33:27 08/29/07 PAGE 1 ENTER INPUT COMMAND: CPVOL LABEL UNIT(7000) VOLID(NU7000) NOVFY ICK00700I DEVICE INFORMATION FOR 7000 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = E9 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4A001B35 TRKS/CYL = 15, # PRIMARY CYLS = 3339 ICK04000I DEVICE IS IN SIMPLEX STATE ICK00091I 7000 NED= 2105. .HTC.14.00023257 ICK091I 7000 NED= 2105. .HTC.14.00023257 ICK03090I VOLUME SERIAL = .. ICK003D REPLY U TO ALTER VOLUME 7000 CONTENTS, ELSE T U ICK03000I CPVOL REPORT FOR 7000 FOLLOWS: ICK10710I I/O ERROR OCCURRED ON DEVICE 7000 CSW = EA92E0 0E400050 CCW = 05EB6F9C 4050 FILEMASK = 18 SENSE = 00090401 8000 0500 0200 69544C03 00F10F00 4CE2 ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 15:33:3808/29/07 ENTER INPUT COMMAND: END ICK2I ICKDSF PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12 As for the Simple State message: ICK04000I DEVICE IS IN SIMPLEX STATE Explanation: The device is in simplex state and not part of a dual copy pair. System Action: Command processing continues. Operator Response: None. System Programmer Response: None. Thanks for the idea. This is a stubborn one. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of LOREN CHARNLEY Sent: August 29, 2007 15:14 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DASD Problems Peter, I am running EMC disk array, formatted with 3390-3 disks. Some of the information I saw below I don't see when I do a CPFMTXA format or ICKDSF label. I did notice that you were using the INIT function which I don't use. You could try what I have above just to get the CP format with a label and then try the ICKDSF INIT to get a VSE type VTOC written where you want it and put a VSE type label on it. The following message below I don't understand: ICK04000I DEVICE IS IN SIMPLEX STATE Just a quick look, good luck. Loren Charnley, Jr. IT Systems Engineer Family Dollar Stores, Inc. (704) 847-6961 Ext. 3327 (704) 814-3327 [EMAIL PROTECTED] The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: DASD Problems
Ask Hitachi how the drive should be defined. They made the drives. They should know what is needed in the IOCP. [EMAIL PROTECTED] wrote: Hitachi says it is a problem with our definition of the drives. Seems unlikely to me, but it beats me what the problem is. So, does anyone have any ideas? Peter -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: DASD Problems
Peter, I think that Stephen is right, contact Hitachi and make sure that the drives are set up for mainframe opsys's. When we went from a Shark to EMC, the EMC Techs did a lot to get the disks recognized by VM VSE. I would hold them to the task until such time as you have operable disks. Loren Charnley, Jr. IT Systems Engineer Family Dollar Stores, Inc. (704) 847-6961 Ext. 3327 (704) 814-3327 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Frazier Sent: Wednesday, August 29, 2007 3:49 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DASD Problems Ask Hitachi how the drive should be defined. They made the drives. They should know what is needed in the IOCP. [EMAIL PROTECTED] wrote: Hitachi says it is a problem with our definition of the drives. Seems unlikely to me, but it beats me what the problem is. So, does anyone have any ideas? Peter -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us - NOTE: This e-mail message contains PRIVILEGED and CONFIDENTIAL information and is intended only for the use of the specific individual or individuals to which it is addressed. If you are not an intended recipient of this e-mail, you are hereby notified that any unauthorized use, dissemination or copying of this e-mail or the information contained herein or attached hereto is strictly prohibited. If you receive this e-mail in error, notify the person named above by reply e-mail and please delete it. Thank you.
Re: DASD Problems
Hitachi says it is a problem with our definition of the drives. Seems unlikely to me, but it beats me what the problem is. So, does anyone have any ideas? Peter We are (still, for a short while) using a 9970, so I can look at how we do it. Tomorrow. (its after 11PM now...) Shimon -- Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer mailto:[EMAIL PROTECTED] Israel Police National HQ. http://www.poboxes.com/shimonpgp Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308
Re: DASD Problems
The following message below I don't understand: ICK04000I DEVICE IS IN SIMPLEX STATE It means the disk is NOT part of a PPRC pair, neither as primary nor as mirror. Shimon -- Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer mailto:[EMAIL PROTECTED] Israel Police National HQ. http://www.poboxes.com/shimonpgp Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308
Re: DASD Problems
Hello Peter, Just to re-enforce that Hitachi needs to look at how they have the array configured and attached. We have the EMC stuff too. I have used both CPFMTXA and ICFDSF without problems. Just a note, for the VSE stuff I use something like this INIT UNIT(755) NVFY NPRG NOMAP VSEVTOC(0,1,29) VOLID(DSK755) Ed Martin Aultman Health Foundation 330-588-4723 [EMAIL PROTECTED] ext. 40441 -Original Message-
Re: DASD Problems
ENTER INPUT COMMAND: CPVOL LABEL UNIT(7000) VOLID(NU7000) NOVFY That I/O error is worrisome. You might try the DSF INSTALL command to ensure that the volume really IS OK. Try INSTALL UNIT(7000) CPVOL FORMAT UNIT(7000) NVFY VOLID(NU7000) The INSTALL will take a LONG time (3-4 hours ... go get dinner) but it does media verification and the following CPVOL FORMAT should actually write on everything and label the volume. If you still get errors, then I'd say you have a media problem. ICK04000I DEVICE IS IN SIMPLEX STATE Ah, memories of 3990 dual copy mode. This just says that the unit you specified is not part of a dual copy pair. Think of it as RAID1 for 3390s. Unless you have real 3390s and real 3990s, you probably won't ever see the paired version.
Re: DASD Problems
ICK04000I DEVICE IS IN SIMPLEX STATE Ah, memories of 3990 dual copy mode. This just says that the unit you specified is not part of a dual copy pair. Think of it as RAID1 for 3390s. Unless you have real 3390s and real 3990s, you probably won't ever see the paired version. Why do you say that? All of our production DASD runs in HRC (Hitachi PPRC) duplex mode. We periodically suspend the HRC and run backups off the mirror copies, to reduce our backup downtime to a minimum. (At least the VM/VSE DASD). Shimon -- Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer mailto:[EMAIL PROTECTED] Israel Police National HQ. http://www.poboxes.com/shimonpgp Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308
Re: DASD Problems
On Wednesday, 08/29/2007 at 02:24 EDT, [EMAIL PROTECTED] wrote: We are trying to get a Hitachi Lightning 9970V DASD unit working. We can attach the drives, CMS format them (with errors, but they appear to be formatted), do DDR copies to them (no errors). The one thing we can't do is write a label on them. When we run ICKDSF on the volumes we get: CMS FORMAT? With errors? What errors? Your DITTO from below shows that the volume has NOT been formatted by CMS FORMAT as he doesn't write IPL on the volume. INIT UNIT(7000) NVFY VOLID(NU7000) ... ICK10710I I/O ERROR OCCURRED ON DEVICE 7000 ICK31006I VOLUME LABEL CREATION FAILED ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12 HCPERP6321I DASD 7000 AN OPERATION WAS TERMINATED BECAUSE RECORD HCPERP6321I 03 WAS NOT FOUND HCPERP6300I SENSE DATA FORMAT = 00 MSG CODE = 00 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = 86 HCPERP6302I SEEK ADDRESS = HCPERP6303I SENSE = 00090401 4000 8600 0100 61495C03 That sense code says record 3 on cyl 0 was not found. HCPDAS537A DASD 7000 THE LABEL COULD NOT BE READ Re-format the volume. Try using cpfmtxa to format it instead of CMS. Alan Altmark z/VM Development IBM Endicott
