connect DS8100 linux
Hi; We have z/vm v5r2 running suze v10 as a guest. Defined in ds8100 eckd mode fibber connection. The question wee need to reconfigure the ds8100 to reclaim big portion of it in oreder to allocate big FBA disk to be used by linux. Can any body help in this issue?? Tarek
Re: Using LBYONLY
On Friday, 03/06/2009 at 12:47 EST, Schuh, Richard rsc...@visa.com wrote: Ah, but I do have a point. The REJECT * LOGON does not allow the same type of override that is allowed by other rules. In this, there is inconsistency. Actually, I have two points. The second is that, if LOGON is viewed as a process that is being controlled by the rule, then REJECT * LOGON should control all forms of logging the user on. After all, the same code is used to create the virtual machine. I was given 50 lashes with a wet noodle here when I previously proposed that if you have LOGON BY authority to a user you should be able to - LOGON to the user - XAUTOLOG the user - Use FOR - Use SEND (even if not the secuser) - be the SECUSER or OBSERVER Except that I would not allow SET SECUSER/OBSERVER, SEND or FOR if the user was logged on or someone else is the secuser. Unlike the privileged versions of those commands, serial access to the user ID would be enforced. Alan Altmark z/VM Development IBM Endicott
Re: Must be Friday: Mainframe USBs!
On Sun, Mar 08, 2009 at 02:10:24PM -0400, Richard Troth wrote: ECKD (today) is an IBM hardware solution for a software problem. Originally, CKD exposed not only counts and keys (thus the acronym) but more significantly tracks and records. NO ONE but MVS (and TPF) has a firm requirement for that. What I mean is that CP and VSE can at least tolerate a lack of tracks and records. (They can run from IPL to shutdown on things like SAN.) More significantly, CMS, Linux, and Solaris (or UTS or AIX or USS) explicitly THROW AWAY the track and record semantics that our precious storage subsystems worked so hard to present on the channel. They can't use it! They just care about the data on the disk, not its geometry. Are you implying VSE VSAM KSDS files do not utilize CKD architecture and/or there is no net performance advantage to that in this day and age? Maybe I need to look at the effort to migrate to 3370... -- May the LORD God bless you exceedingly abundantly! Dave Craig - - - - - - - - - - - - - - - - - - - - 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' --from _Nightfall_ by Asimov/Silverberg
Re: Must be Friday: Mainframe USBs!
Hello, I am not sure that he implied that but the FBA idea was FORCEd from VSE because MVS/OS could not handle it. Removing FBA would make VSE more z/OS like. 3310, 3370, 9336 are all FBA. FBA eliminated the conversion problem, and IMHO was faster access. Migration to larger devices was just done. I believe the S36, S38, and the AS400 all use FBA. z/VM virtual Disk is VFB-512. Why not FBA? Oh, seems to me that some of the older high strength CPU's used FBA devices to hold the microcode. Ed Martin Aultman Health Foundation 330-588-4723 ext 40441 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David L. Craig Sent: Monday, March 09, 2009 10:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! On Sun, Mar 08, 2009 at 02:10:24PM -0400, Richard Troth wrote: ECKD (today) is an IBM hardware solution for a software problem. Originally, CKD exposed not only counts and keys (thus the acronym) but more significantly tracks and records. NO ONE but MVS (and TPF) has a firm requirement for that. What I mean is that CP and VSE can at least tolerate a lack of tracks and records. (They can run from IPL to shutdown on things like SAN.) More significantly, CMS, Linux, and Solaris (or UTS or AIX or USS) explicitly THROW AWAY the track and record semantics that our precious storage subsystems worked so hard to present on the channel. They can't use it! They just care about the data on the disk, not its geometry. Are you implying VSE VSAM KSDS files do not utilize CKD architecture and/or there is no net performance advantage to that in this day and age? Maybe I need to look at the effort to migrate to 3370... -- May the LORD God bless you exceedingly abundantly! Dave Craig - - - - - - - - - - - - - - - - - - - - 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' --from _Nightfall_ by Asimov/Silverberg
Re: Using LBYONLY
I did not wield one of those noodles :-) Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Sunday, March 08, 2009 10:20 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Using LBYONLY On Friday, 03/06/2009 at 12:47 EST, Schuh, Richard rsc...@visa.com wrote: Ah, but I do have a point. The REJECT * LOGON does not allow the same type of override that is allowed by other rules. In this, there is inconsistency. Actually, I have two points. The second is that, if LOGON is viewed as a process that is being controlled by the rule, then REJECT * LOGON should control all forms of logging the user on. After all, the same code is used to create the virtual machine. I was given 50 lashes with a wet noodle here when I previously proposed that if you have LOGON BY authority to a user you should be able to - LOGON to the user - XAUTOLOG the user - Use FOR - Use SEND (even if not the secuser) - be the SECUSER or OBSERVER Except that I would not allow SET SECUSER/OBSERVER, SEND or FOR if the user was logged on or someone else is the secuser. Unlike the privileged versions of those commands, serial access to the user ID would be enforced. Alan Altmark z/VM Development IBM Endicott
Re: Must be Friday: Mainframe USBs!
Which ones would those have been? Our 360/50 used punched mylar cards. Any kind of disk that was available at the time would have been physically too large to fit in the frame :-) Regards, Richard Schuh Why not FBA? Oh, seems to me that some of the older high strength CPU's used FBA devices to hold the microcode. Ed Martin Aultman Health Foundation 330-588-4723 ext 40441
Re: Using LBYONLY
On Friday, 03/06/2009 at 03:31 EST, Bob Bolch b...@zenoroad.com wrote: It?s perfectly fine to discuss the way things ?should be? ?vs- the way things ?are?, but when a design is more than 20 years old, as in this case, then the way it works now is, by definition, the way it should be. Making some changes is just too painful. I think that we must continually assess the somewhat, uh, arcane nature of VM commands. By default, I believe that the ability for UserX to bring UserY onto the system should not be restricted by the particular mechanism used, even though you should be able to exert control over a particular mechanism if desired. A good example is communications. Should I have to protect MSG, WNG, MSGNOH, SMSG, COUPLE, NICDEF, IUCV, VMCF, ADRSPACE PERMIT, shared R/W DCSS, and shared mdisk separately? I don't like that. It's a never-ending quest to discover what new interfaces have been added, and it is a terribly large hammer to swing to enable mandatory access controls in your ESM. I much prefer to be able to protect an activity rather than a command or interface, but we are stuck with history for the nonce. Alan Altmark z/VM Development IBM Endicott
Re: Must be Friday: Mainframe USBs!
I believe that the 3090 or something similar. It has been awhile since the CE and I talked about devices. Ed Martin Aultman Health Foundation 330-588-4723 ext 40441 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Monday, March 09, 2009 11:22 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! Which ones would those have been? Our 360/50 used punched mylar cards. Any kind of disk that was available at the time would have been physically too large to fit in the frame :-) Regards, Richard Schuh Why not FBA? Oh, seems to me that some of the older high strength CPU's used FBA devices to hold the microcode. Ed Martin Aultman Health Foundation 330-588-4723 ext 40441
Re: Must be Friday: Mainframe USBs!
I'll take What are 3090s? for $100, Alex. As I recall, their VM-lite hypervisor (was it already called PR/SM?) used 3310s. I don't think 308x's did, but I'm not sure. Don't get me started about the time the outsourcing company I worked for agreed to migrate a 9370 VM/VSE customer onto a 3090 system, with no consideration of, no awareness of, 9336s not being CKD devices. Nick L'Ardent On 3/9/2009 10:22 AM, Schuh, Richard wrote: Which ones would those have been? Our 360/50 used punched mylar cards. Any kind of disk that was available at the time would have been physically too large to fit in the frame :-) Why not FBA? Oh, seems to me that some of the older high strength CPU's used FBA devices to hold the microcode.
Re: Using LBYONLY
And if we do not discuss the way things should be vs. the way they are, there will never be any progress. We will always be mired in the past and become, dare I say it, dinosaurs. Even T-Rex was only around for about 3 million years - a very short time in geological terms (the Cretaceous Period, the one in which T-Rex lived, lasted about 80 million years). Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Monday, March 09, 2009 8:24 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Using LBYONLY On Friday, 03/06/2009 at 03:31 EST, Bob Bolch b...@zenoroad.com wrote: It?s perfectly fine to discuss the way things ?should be? ?vs- the way things ?are?, but when a design is more than 20 years old, as in this case, then the way it works now is, by definition, the way it should be. Making some changes is just too painful. I think that we must continually assess the somewhat, uh, arcane nature of VM commands. By default, I believe that the ability for UserX to bring UserY onto the system should not be restricted by the particular mechanism used, even though you should be able to exert control over a particular mechanism if desired. A good example is communications. Should I have to protect MSG, WNG, MSGNOH, SMSG, COUPLE, NICDEF, IUCV, VMCF, ADRSPACE PERMIT, shared R/W DCSS, and shared mdisk separately? I don't like that. It's a never-ending quest to discover what new interfaces have been added, and it is a terribly large hammer to swing to enable mandatory access controls in your ESM. I much prefer to be able to protect an activity rather than a command or interface, but we are stuck with history for the nonce. Alan Altmark z/VM Development IBM Endicott
FW: Estimated speed/duplex values for virtual NICs
Based on packet delivery being a memory-to-memory operation with diag2a8, I'm leaning toward just inserting an estimated value of 10Gbit/sec per interface for the speed estimate reported by dladm. Does anyone else have a better value or an idea of how to measure this value? Further, does VSWITCH support generating BCI (backward congestion indicator) frames? If so, I'll just hard-code the media speed value at 100Gbit and enable the BCI support in the OpenSolaris stack and let it negotiate down.
Re: Must be Friday: Mainframe USBs!
The 308x had a FBA device for the support processor to use. Wasn't customer accessible, though. I remember helping a CE replace one once when it failed on a 3081D. Messy. The MAP ran for tens of pages. On 3/9/09 11:42 AM, Edward M Martin emar...@aultman.com wrote: I believe that the 3090 or something similar. It has been awhile since the CE and I talked about devices.
Re: Must be Friday: Mainframe USBs!
The 3090 had a complete 4331 for a support processor. Jeffry A. Kennedy Certco,Inc jkenn...@certcoinc.com 608-270-2385 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Edward M Martin Sent: Monday, March 09, 2009 10:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! I believe that the 3090 or something similar. It has been awhile since the CE and I talked about devices. Ed Martin Aultman Health Foundation 330-588-4723 ext 40441 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Monday, March 09, 2009 11:22 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! Which ones would those have been? Our 360/50 used punched mylar cards. Any kind of disk that was available at the time would have been physically too large to fit in the frame :-) Regards, Richard Schuh Why not FBA? Oh, seems to me that some of the older high strength CPU's used FBA devices to hold the microcode. Ed Martin Aultman Health Foundation 330-588-4723 ext 40441
Re: Must be Friday: Mainframe USBs!
Shall I plead a tiny bit for CKD? - VSAM has the ability to store (replicate?) the lowest level index set in front of the track where the data reside. This to avoid seek, the idea was that the higher level index blocks would be buffered in storage. But, who cares/who has time nowadays to get that last bit of performance improvement. - our own beloved VM has one function not working on FBA... Please guess The x-link part of CSE needs CKD. The locking mechanism doesn't need Reserve/Release. With one, complex, I/O the XLINK SW is able to test if a cylinder is free for e.g. a R/W LINK and if so, mark it as being used. Kind of TestAndSwap. Impossible on FBA I've been told. 2009/3/9 David L. Craig d...@radix.net On Sun, Mar 08, 2009 at 02:10:24PM -0400, Richard Troth wrote: ECKD (today) is an IBM hardware solution for a software problem. Originally, CKD exposed not only counts and keys (thus the acronym) but more significantly tracks and records. NO ONE but MVS (and TPF) has a firm requirement for that. What I mean is that CP and VSE can at least tolerate a lack of tracks and records. (They can run from IPL to shutdown on things like SAN.) More significantly, CMS, Linux, and Solaris (or UTS or AIX or USS) explicitly THROW AWAY the track and record semantics that our precious storage subsystems worked so hard to present on the channel. They can't use it! They just care about the data on the disk, not its geometry. Are you implying VSE VSAM KSDS files do not utilize CKD architecture and/or there is no net performance advantage to that in this day and age? Maybe I need to look at the effort to migrate to 3370... -- May the LORD God bless you exceedingly abundantly! Dave Craig - - - - - - - - - - - - - - - - - - - - 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' --from _Nightfall_ by Asimov/Silverberg -- Kris Buelens, IBM Belgium, VM customer support
Re: Must be Friday: Mainframe USBs!
That seems to imply that the x-link part of CSE can't be on FCP attached drives... I thought I've read that z/VM can be installed entirely on FCP attached drives. But I didn't read that much in detail if there were functions that wouldn't work in that world. Perhaps a future release would address that issue? Tom Duerbusch THD Consulting Kris Buelens kris.buel...@gmail.com 3/9/2009 1:15 PM Shall I plead a tiny bit for CKD? - VSAM has the ability to store (replicate?) the lowest level index set in front of the track where the data reside. This to avoid seek, the idea was that the higher level index blocks would be buffered in storage. But, who cares/who has time nowadays to get that last bit of performance improvement. - our own beloved VM has one function not working on FBA... Please guess The x-link part of CSE needs CKD. The locking mechanism doesn't need Reserve/Release. With one, complex, I/O the XLINK SW is able to test if a cylinder is free for e.g. a R/W LINK and if so, mark it as being used. Kind of TestAndSwap. Impossible on FBA I've been told. 2009/3/9 David L. Craig d...@radix.net On Sun, Mar 08, 2009 at 02:10:24PM -0400, Richard Troth wrote: ECKD (today) is an IBM hardware solution for a software problem. Originally, CKD exposed not only counts and keys (thus the acronym) but more significantly tracks and records. NO ONE but MVS (and TPF) has a firm requirement for that. What I mean is that CP and VSE can at least tolerate a lack of tracks and records. (They can run from IPL to shutdown on things like SAN.) More significantly, CMS, Linux, and Solaris (or UTS or AIX or USS) explicitly THROW AWAY the track and record semantics that our precious storage subsystems worked so hard to present on the channel. They can't use it! They just care about the data on the disk, not its geometry. Are you implying VSE VSAM KSDS files do not utilize CKD architecture and/or there is no net performance advantage to that in this day and age? Maybe I need to look at the effort to migrate to 3370... -- May the LORD God bless you exceedingly abundantly! Dave Craig - - - - - - - - - - - - - - - - - - - - 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' --from _Nightfall_ by Asimov/Silverberg -- Kris Buelens, IBM Belgium, VM customer support
Re: Must be Friday: Mainframe USBs!
In the distant past, we had a device called a Fast Paging Unit attached to our 4381. This had many large boards each containing many dozens of small memory chips. It was channel attached and emulated a partial 3380. We allocated it to HPO swapping ala Vista's USB ReadyBoost. Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Jeff Kennedy Sent: Monday, March 09, 2009 12:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! The 3090 had a complete 4331 for a support processor. Jeffry A. Kennedy Certco,Inc jkenn...@certcoinc.com 608-270-2385 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Edward M Martin Sent: Monday, March 09, 2009 10:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! I believe that the 3090 or something similar. It has been awhile since the CE and I talked about devices. Ed Martin Aultman Health Foundation 330-588-4723 ext 40441 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Monday, March 09, 2009 11:22 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! Which ones would those have been? Our 360/50 used punched mylar cards. Any kind of disk that was available at the time would have been physically too large to fit in the frame :-) Regards, Richard Schuh Why not FBA? Oh, seems to me that some of the older high strength CPU's used FBA devices to hold the microcode. Ed Martin Aultman Health Foundation 330-588-4723 ext 40441 This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.
Re: Must be Friday: Mainframe USBs!
Ah, but which impossibilities are they working to turn into realities? Regards, Richard Schuh Impossible is just hyperbole for No one ever did the work. See that faint glow on the distant horizon? That's the visible energy given off by elves turning the Impossible into Reality. Alan Altmark z/VM Development IBM Endicott
Re: FW: Estimated speed/duplex values for virtual NICs
On Monday, 03/09/2009 at 12:09 EDT, David Boyes dbo...@sinenomine.net wrote: Further, does VSWITCH support generating BCI (backward congestion indicator) frames? Never heard of it. Whatever they are, the VSWITCH doesn't generate them or cause them to be generated. Alan Altmark z/VM Development IBM Endicott
Re: FW: Estimated speed/duplex values for virtual NICs
FWIW, The channel bonding stuff (SuSE 10) seems to also care about speed/duplex values and can't get them from a dedicated OSA either. It complains and goes on its merry way: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full Marcy
Re: Must be Friday: Mainframe USBs!
I remember having a 3370 (I think) replaced on a 4331. The CE said the reason the MAP ran for so many pages was that the Head and Drive assembly (HDA) was the most expensive part of the drive, so the Diagnostic floppy would exhaustively test every component before it failed the Head and Drive Assembly. He was pretty sure it was the HDA and arrived with one, which was left to acclimatize (I think it needed 4 hours) while he ran through the MAP. Glorious days, Dave Wade G4UGM Illegitimi Non Carborundum -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: 09 March 2009 15:47 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! The 308x had a FBA device for the support processor to use. Wasn't customer accessible, though. I remember helping a CE replace one once when it failed on a 3081D. Messy. The MAP ran for tens of pages. On 3/9/09 11:42 AM, Edward M Martin emar...@aultman.com wrote: I believe that the 3090 or something similar. It has been awhile since the CE and I talked about devices.
Re: Must be Friday: Mainframe USBs!
I haven't experienced a failure of an HDA since the days the airline only allowed VM to have 3380-A04 and -B04 devices that were hand-me-downs from MVS and TPF. It took a week of 7 HDA failures during the 5 day work week, all housing critical data, before they finally bought new DASD for VM. I think most of the replacement HDAs were cannibalized from devices sitting on the loading dock waiting for someone to haul them away. One died less than an hour after we finished a restore. No big deal, it only took 6.5 hours to do that restore.. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Dave Wade Sent: Monday, March 09, 2009 4:27 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! I remember having a 3370 (I think) replaced on a 4331. The CE said the reason the MAP ran for so many pages was that the Head and Drive assembly (HDA) was the most expensive part of the drive, so the Diagnostic floppy would exhaustively test every component before it failed the Head and Drive Assembly. He was pretty sure it was the HDA and arrived with one, which was left to acclimatize (I think it needed 4 hours) while he ran through the MAP. Glorious days, Dave Wade G4UGM Illegitimi Non Carborundum -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: 09 March 2009 15:47 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! The 308x had a FBA device for the support processor to use. Wasn't customer accessible, though. I remember helping a CE replace one once when it failed on a 3081D. Messy. The MAP ran for tens of pages. On 3/9/09 11:42 AM, Edward M Martin emar...@aultman.com wrote: I believe that the 3090 or something similar. It has been awhile since the CE and I talked about devices.
Re: Must be Friday: Mainframe USBs!
I could have written the exact the same story - just need to strike the and TPF words and the word airline.. Ah if only we had this IBMVM list back then, we could have commiserated together. The most fun was losing the volume with the directory on a Friday afternoon. Nowadays, none of that fun. Just microcode !! Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Monday, March 09, 2009 4:45 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Must be Friday: Mainframe USBs! I haven't experienced a failure of an HDA since the days the airline only allowed VM to have 3380-A04 and -B04 devices that were hand-me-downs from MVS and TPF. It took a week of 7 HDA failures during the 5 day work week, all housing critical data, before they finally bought new DASD for VM. I think most of the replacement HDAs were cannibalized from devices sitting on the loading dock waiting for someone to haul them away. One died less than an hour after we finished a restore. No big deal, it only took 6.5 hours to do that restore.. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Dave Wade Sent: Monday, March 09, 2009 4:27 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! I remember having a 3370 (I think) replaced on a 4331. The CE said the reason the MAP ran for so many pages was that the Head and Drive assembly (HDA) was the most expensive part of the drive, so the Diagnostic floppy would exhaustively test every component before it failed the Head and Drive Assembly. He was pretty sure it was the HDA and arrived with one, which was left to acclimatize (I think it needed 4 hours) while he ran through the MAP. Glorious days, Dave Wade G4UGM Illegitimi Non Carborundum -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: 09 March 2009 15:47 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! The 308x had a FBA device for the support processor to use. Wasn't customer accessible, though. I remember helping a CE replace one once when it failed on a 3081D. Messy. The MAP ran for tens of pages. On 3/9/09 11:42 AM, Edward M Martin emar...@aultman.com wrote: I believe that the 3090 or something similar. It has been awhile since the CE and I talked about devices.
Re: Must be Friday: Mainframe USBs!
I don't miss the bad old days. From someone who has seen the bad old days for 42 years, Mar. 6, 1967. Jim Marcy Cortes wrote: I could have written the exact the same story - just need to strike the and TPF words and the word airline.. Ah if only we had this IBMVM list back then, we could have commiserated together. The most fun was losing the volume with the directory on a Friday afternoon. =20 =20 Nowadays, none of that fun. Just microcode !!=20 Marcy=20 This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. =20 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Monday, March 09, 2009 4:45 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Must be Friday: Mainframe USBs! I haven't experienced a failure of an HDA since the days the airline only allowed VM to have 3380-A04 and -B04 devices that were hand-me-downs from MVS and TPF. It took a week of 7 HDA failures during the 5 day work week, all housing critical data, before they finally bought new DASD for VM. I think most of the replacement HDAs were cannibalized from devices sitting on the loading dock waiting for someone to haul them away. One died less than an hour after we finished a restore. No big deal, it only took 6.5 hours to do that restore..=20 =20 Regards,=20 Richard Schuh=20 =20 =20 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Dave Wade Sent: Monday, March 09, 2009 4:27 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! =09 =09 I remember having a 3370 (I think) replaced on a 4331. The CE said the reason the MAP ran for so many pages was that the Head and Drive assembly (HDA) was the most expensive part of the drive, so the Diagnostic floppy would exhaustively test every component before it failed the Head and Drive Assembly. He was pretty sure it was the HDA and arrived with one, which was left to acclimatize (I think it needed 4 hours) while he ran through the MAP.=20 =20 Glorious days, =20 =20 Dave Wade G4UGM Illegitimi Non Carborundum =20 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: 09 March 2009 15:47 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Must be Friday: Mainframe USBs! =20 The 308x had a FBA device for the support processor to use. Wasn't customer accessible, though.=20 =09 I remember helping a CE replace one once when it failed on a 3081D. Messy. The MAP ran for tens of pages.=20 =09 =09 On 3/9/09 11:42 AM, Edward M Martin emar...@aultman.com wrote: I believe that the 3090 or something similar. It has been awhile since the CE and I talked about devices. -- Jim Bohnsack Cornell University (972) 596-6377 home/office (972) 342-5823 cell jab...@cornell.edu
