IBM 7060-H30
While I am cleaning out my DR room... I also have an IBM 7060 H30, $1 plus shipping and packaging. Please respond to me directly. -- 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: IBM 7060-H30
While I am cleaning out my DR room... I also have an IBM 7060 H30, $1 plus shipping and packaging. And I have a H50 that's probably not even worth that much. Shane ... -- 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: IBM 7060-H30
Tracy, I was going to email you and find out where your 7060 was located, but then I looked for your web site and found out you are in Vermont. I would be interested in an H30, and it would fit in my car, but Vermont is a long way from Milwaukee. Also, there is the minor problem of z/OS software. I remember when the company I worked for had an H50, all of the IBM software cost 30K per month approximately. I believe the 7060 runs z/OS 1.5 and below. Eric Bielefeld Sr. Systems Programmer Milwaukee, Wisconsin 414-475-7434 - Original Message - From: Adams, Tracy tad...@cvps.com Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@bama.ua.edu Sent: Thursday, July 02, 2009 7:35 AM Subject: IBM 7060-H30 While I am cleaning out my DR room... I also have an IBM 7060 H30, $1 plus shipping and packaging. Please respond to me directly. -- 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: IBM 7060-H30
2009/7/2 Adams, Tracy tad...@cvps.com: While I am cleaning out my DR room... I also have an IBM 7060 H30, $1 plus shipping and packaging. Please respond to me directly. One in Florida sold on eBay just recently for US $515, with 4 serious bidders (it started at $99). Item 220436063530, and from the pictures it appears to have little or no DASD (or maybe it's the OS/2 disks that are missing). OTOH the parts value may be higher than as a running machine. Those 18 GB SSA drives are still available from IBM at roughly $5000 each! It's a great little machine, and many developers are disappointed that IBM never made a z/Arch version. Tony H. -- 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
IBM 7060 H30 network cards
We have an IBM 7060 H30 that has 4 network cards. One for OS/2, two for prodcution z/OS LPAR, and one for test z/OS LPAR. Last week we had to unplug and replug the production LPAR network cables from the H30. We did this twice. Both times the 7060's PC rebooted which as some of you might know kills the S/390 processor. We did not stop the TCP/IP stacks that were using the interface cards. Should we have stopped TCP/IP? Should we vary the even odd device addresses offline? Should we vary the even odd device address paths offline. Should something on the OS/2 side (emio device drivers) be stopped? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM 7060 H30 network cards
Had much the same configuration once, but don't ever recall any issues plugging and unplugging those cables. We did have some serious issues trying to use the 3270 controller emulation on the OS/2 NIC for console support. OS/2 would get really flakey to the point of locking up or doing very strange things. We had to use the little red reset button on more than one occasion. Since we were using internal (emulated) DASD, we considered it unacceptable for production except as a dead last resort. We did use it on our remote BR machine, but we rebooted every week or so to keep OS/2 from going bonkers. If you choose to use those emulated controllers, then I would strongly suggest weekly reboots. HTH. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Richard Pinion Sent: Wednesday, November 02, 2005 10:21 AM To: IBM-MAIN@BAMA.UA.EDU Subject: IBM 7060 H30 network cards We have an IBM 7060 H30 that has 4 network cards. One for OS/2, two for prodcution z/OS LPAR, and one for test z/OS LPAR. Last week we had to unplug and replug the production LPAR network cables from the H30. We did this twice. Both times the 7060's PC rebooted which as some of you might know kills the S/390 processor. We did not stop the TCP/IP stacks that were using the interface cards. Should we have stopped TCP/IP? Should we vary the even odd device addresses offline? Should we vary the even odd device address paths offline. Should something on the OS/2 side (emio device drivers) be stopped? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM 7060 H30 network cards
In general, it's always a good idea to at least bring down the interfaces ( on Z/OS) V TCPIP,,STOP,X before unplugging cables. I usually also bring down the subchannel addresses, and chipid's but I'm known to be overcautious. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Richard Pinion Sent: Wednesday, November 02, 2005 11:21 AM To: IBM-MAIN@BAMA.UA.EDU Subject: IBM 7060 H30 network cards We have an IBM 7060 H30 that has 4 network cards. One for OS/2, two for prodcution z/OS LPAR, and one for test z/OS LPAR. Last week we had to unplug and replug the production LPAR network cables from the H30. We did this twice. Both times the 7060's PC rebooted which as some of you might know kills the S/390 processor. We did not stop the TCP/IP stacks that were using the interface cards. Should we have stopped TCP/IP? Should we vary the even odd device addresses offline? Should we vary the even odd device address paths offline. Should something on the OS/2 side (emio device drivers) be stopped? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM 7060 H30 network cards
This is the reason when we put in our H50 we went with a third-party network device. I asked the business integrator who assisted us what his take was on it and here is his reply: Rex - You are correct - what happened to them is exactly the reason you went with the external device. If any emulated I/O is in use, a reboot of the Support Element will probably take MVS down. If they had to unplug and replug the network cable connected to the ethernet card, they should have done everything possible to stop all activity on that card prior to unplugging the cable. I'm not sure if there is a foolproof procedure, but if I had to unplug the ethernet cable I would do the following in this sequence. Stop TCP/IP. Vary offline ALL emulated devices associated with that card. Vary the path to those devices offline. Config CHPID FC offline to this LPAR. When this is complete, you might be able to unplug the ethernet without taking down OS/2. If the cable work did not cause any OS/2 problems, reverse the above procedure to get the TCP/IP connection restored. As far as I know, there is nothing they could have done from an OS/2 perspective. I know of no way to stop device drivers or anything else that may be associated with the ethernet card. HTH Rex -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Richard Pinion Sent: Wednesday, November 02, 2005 10:21 AM To: IBM-MAIN@BAMA.UA.EDU Subject: IBM 7060 H30 network cards We have an IBM 7060 H30 that has 4 network cards. One for OS/2, two for prodcution z/OS LPAR, and one for test z/OS LPAR. Last week we had to unplug and replug the production LPAR network cables from the H30. We did this twice. Both times the 7060's PC rebooted which as some of you might know kills the S/390 processor. We did not stop the TCP/IP stacks that were using the interface cards. Should we have stopped TCP/IP? Should we vary the even odd device addresses offline? Should we vary the even odd device address paths offline. Should something on the OS/2 side (emio device drivers) be stopped? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM 7060 H30 network cards
Hey thanks, that's what I needed to know!!! [EMAIL PROTECTED] 11/2/2005 1:08:10 PM This is the reason when we put in our H50 we went with a third-party network device. I asked the business integrator who assisted us what his take was on it and here is his reply: Rex - You are correct - what happened to them is exactly the reason you went with the external device. If any emulated I/O is in use, a reboot of the Support Element will probably take MVS down. If they had to unplug and replug the network cable connected to the ethernet card, they should have done everything possible to stop all activity on that card prior to unplugging the cable. I'm not sure if there is a foolproof procedure, but if I had to unplug the ethernet cable I would do the following in this sequence. Stop TCP/IP. Vary offline ALL emulated devices associated with that card. Vary the path to those devices offline. Config CHPID FC offline to this LPAR. When this is complete, you might be able to unplug the ethernet without taking down OS/2. If the cable work did not cause any OS/2 problems, reverse the above procedure to get the TCP/IP connection restored. As far as I know, there is nothing they could have done from an OS/2 perspective. I know of no way to stop device drivers or anything else that may be associated with the ethernet card. HTH Rex -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Richard Pinion Sent: Wednesday, November 02, 2005 10:21 AM To: IBM-MAIN@BAMA.UA.EDU Subject: IBM 7060 H30 network cards We have an IBM 7060 H30 that has 4 network cards. One for OS/2, two for prodcution z/OS LPAR, and one for test z/OS LPAR. Last week we had to unplug and replug the production LPAR network cables from the H30. We did this twice. Both times the 7060's PC rebooted which as some of you might know kills the S/390 processor. We did not stop the TCP/IP stacks that were using the interface cards. Should we have stopped TCP/IP? Should we vary the even odd device addresses offline? Should we vary the even odd device address paths offline. Should something on the OS/2 side (emio device drivers) be stopped? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM 7060 H30 network cards
On Wed, 2 Nov 2005 10:21:07 -0600, Richard Pinion [EMAIL PROTECTED] wrote: We have an IBM 7060 H30 that has 4 network cards. One for OS/2, two for prodcution z/OS LPAR, and one for test z/OS LPAR. Last week we had to unplug and replug the production LPAR network cables from the H30. We did this twice. Both times the 7060's PC rebooted which as some of you might know kills the S/390 processor. We did not stop the TCP/IP stacks that were using the interface cards. Should we have stopped TCP/IP? Should we vary the even odd device addresses offline? Should we vary the even odd device address paths offline. Should something on the OS/2 side (emio device drivers) be stopped? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Gee, maybe you want to get something fixed. We have a 7060 H50 with a similar setup. Can't say we unplug the Production cards much, 90% of all terminal traffic goes through them, 100% of all print traffic and 100% of all FTP. 7060's (internal) PC was last booted over a year ago (when the system was moved). The internal OS/2 is connected via a crossover cable to the OMC, which was up and down all over the place when the move occurred, the mainframe did not miss a beat. Mark -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
