Re: IBMLink outages in 2012
In d9a38e3a-ca51-4033-be46-9d37265ee...@comcast.net, on 05/21/2012 at 11:24 PM, Ed Gould edgould1...@comcast.net said: I vaguely remember an IBM product (INFO-MVS) which was (if memory serves me) was a single (??) reel 6250 tape sent monthly by IBM. INFO-MVS was another product in the same family. There was also INFO-ACCESS, which let you ship dumps to IBM electronically, and to retrieve service, over SNA. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
In fkjpr71k9aqo209gi143h9g9hnuq125...@4ax.com, on 05/23/2012 at 08:54 AM, Clark Morris cfmpub...@ns.sympatico.ca said: On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it Shorthand? How is 24/7/365 shorter than 24/7? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
On Thu, May 24, 2012 at 6:18 AM, Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net wrote: In fkjpr71k9aqo209gi143h9g9hnuq125...@4ax.com, on 05/23/2012 at 08:54 AM, Clark Morris cfmpub...@ns.sympatico.ca said: On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it Shorthand? How is 24/7/365 shorter than 24/7? It's not. But it's shorter (or at least easier to remember/type/understand for most people) than 86400/365 or 31536000. And he didn't say shorthand, he said shortcut. Are we done now? -- zMan -- I've got a mainframe and I'm not afraid to use it -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
zMan zedgarhoo...@gmail.com wrote in message news:CAFO-8tqWyJKz+G7jJXvgooJ7QinzBAo=rw0+ywebrx8_jbv...@mail.gmail.com ... On Thu, May 24, 2012 at 6:18 AM, Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net wrote: In fkjpr71k9aqo209gi143h9g9hnuq125...@4ax.com, on 05/23/2012 at 08:54 AM, Clark Morris cfmpub...@ns.sympatico.ca said: On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it Shorthand? How is 24/7/365 shorter than 24/7? It's not. But it's shorter (or at least easier to remember/type/understand for most people) than 86400/365 or 31536000. And he didn't say shorthand, he said shortcut. Are we done now? -- zMan -- I've got a mainframe and I'm not afraid to use it I would like to suggest the 24/7/52 variation. It is shorter than 24/7/365 and is easier realizable in 1 year. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
Read it again. He did say both shortcut and shorthand Bill Fairchild Programmer Rocket Software 408 Chamberlain Park Lane * Franklin, TN 37069-2526 * USA t: +1.617.614.4503 * e: bfairch...@rocketsoftware.com * w: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of zMan Sent: Thursday, May 24, 2012 6:31 AM To: IBM-MAIN@bama.ua.edu Subject: Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012 On Thu, May 24, 2012 at 6:18 AM, Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net wrote: In fkjpr71k9aqo209gi143h9g9hnuq125...@4ax.com, on 05/23/2012 at 08:54 AM, Clark Morris cfmpub...@ns.sympatico.ca said: On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it Shorthand? How is 24/7/365 shorter than 24/7? It's not. But it's shorter (or at least easier to remember/type/understand for most people) than 86400/365 or 31536000. And he didn't say shorthand, he said shortcut. Are we done now? -- zMan -- I've got a mainframe and I'm not afraid to use it -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
24/7/365 appropriateness was Re: IBMLink outages in 2012
On 22 May 2012 20:04:42 -0700, in bit.listserv.ibm-main you wrote: In hj3lr7lassfuf88ovoeg000i1pp935e...@4ax.com, on 05/21/2012 at 03:51 PM, Clark Morris cfmpub...@ns.sympatico.ca said: I'm the last to see my own errors. Hopefully it was obvious I meant 24/7/365 That's no better. Either 24/7/52 or 24/365 would be approximately correct. On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it and is it the way that the general public as opposed to us professional nitpickers best understands it? Clark Morris -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
In actuality, isn't 24x7 comprehensive enough? The 24 infers that the availability is round the clock, as opposed to most operating schedules that embrace a single day shift of 8 hours (banker's hours), or a day of 14 or 16 hours. The 7 infers that availability is every day of the week, as opposed to only 5 days or 6 days as posited by many businesses. Beyond these, there is no de rigueur schedule of weeks within a year, or even days within a year that is consistently embraced across all cutures and peoples. Consequently, there is no need to stress availability for 52 or 52.(fraction) weeks and no need to stress 365 day availability. Neither of these adds clarity beyond what 24x7 or 24/7 or whatever representation you give to every hour, every day. Billy On Wed, May 23, 2012 at 7:54 AM, Clark Morris cfmpub...@ns.sympatico.cawrote: On 22 May 2012 20:04:42 -0700, in bit.listserv.ibm-main you wrote: In hj3lr7lassfuf88ovoeg000i1pp935e...@4ax.com, on 05/21/2012 at 03:51 PM, Clark Morris cfmpub...@ns.sympatico.ca said: I'm the last to see my own errors. Hopefully it was obvious I meant 24/7/365 That's no better. Either 24/7/52 or 24/365 would be approximately correct. On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it and is it the way that the general public as opposed to us professional nitpickers best understands it? Clark Morris -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
YES enough said!!! Sent from my Verizon Wireless BlackBerry -Original Message- From: Bill Ashton bill00ash...@gmail.com Sender: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Date: Wed, 23 May 2012 08:30:11 To: IBM-MAIN@bama.ua.edu Reply-to: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Subject: Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012 In actuality, isn't 24x7 comprehensive enough? The 24 infers that the availability is round the clock, as opposed to most operating schedules that embrace a single day shift of 8 hours (banker's hours), or a day of 14 or 16 hours. The 7 infers that availability is every day of the week, as opposed to only 5 days or 6 days as posited by many businesses. Beyond these, there is no de rigueur schedule of weeks within a year, or even days within a year that is consistently embraced across all cutures and peoples. Consequently, there is no need to stress availability for 52 or 52.(fraction) weeks and no need to stress 365 day availability. Neither of these adds clarity beyond what 24x7 or 24/7 or whatever representation you give to every hour, every day. Billy On Wed, May 23, 2012 at 7:54 AM, Clark Morris cfmpub...@ns.sympatico.cawrote: On 22 May 2012 20:04:42 -0700, in bit.listserv.ibm-main you wrote: In hj3lr7lassfuf88ovoeg000i1pp935e...@4ax.com, on 05/21/2012 at 03:51 PM, Clark Morris cfmpub...@ns.sympatico.ca said: I'm the last to see my own errors. Hopefully it was obvious I meant 24/7/365 That's no better. Either 24/7/52 or 24/365 would be approximately correct. On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it and is it the way that the general public as opposed to us professional nitpickers best understands it? Clark Morris -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
cfmpub...@ns.sympatico.ca (Clark Morris) writes: On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it and is it the way that the general public as opposed to us professional nitpickers best understands it? when we were doing ha/cmp in the early 90s, one of the customers we called on supported the 1-800 lookup (i.e. 1-800 got routed to dbms transaction that looked up the real number for putting the call through) had five-nines availability. the incumbent had redundant hardware ... but required system to be taken down for software maintenance ... short scheduled downtime, once a year blew the outage budget for a nearly a century. ha/cmp didn't have redundant hardware components but had replicated systems and fall-over ... so failures downtime was masked ... even rolling outages for software system maintenance w/o service impact. eventually the incumbent vendor came back and said that they could do replicated systems also ... for masking individual system downtime ... but that negated the requirement for redudant sofware. i was then asked to write a section for the corporae continuous available strategy document ... but the section got pulled after both Rochester and POK complained that they couldn't meet the objectives. past posts mentioning coining the terms disaster survivability and geographic survivability ... to differentiate from disaster/recovery when out marketing ha/cmp: http://www.garlic.com/~lynn/submain.html#available -- virtualization experience starting Jan1968, online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
And the general public, many Dilbertian managers, and even some of us professional nitpickers, think that a job running 1 hour instead of 10 is 900% faster, and that 1 is 10 times smaller than 10. 2+2 no longer = 5; now it equals chartreuse. Fortunately architects and engineers know how to use mathematically accurate and precise terminology when describing the bridges they design and build, or we would have a lot more cars falling off of collapsing bridges. Bill Fairchild Programmer Rocket Software 408 Chamberlain Park Lane * Franklin, TN 37069-2526 * USA t: +1.617.614.4503 * e: bfairch...@rocketsoftware.com * w: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Clark Morris Sent: Wednesday, May 23, 2012 6:54 AM To: IBM-MAIN@bama.ua.edu Subject: 24/7/365 appropriateness was Re: IBMLink outages in 2012 On 22 May 2012 20:04:42 -0700, in bit.listserv.ibm-main you wrote: In hj3lr7lassfuf88ovoeg000i1pp935e...@4ax.com, on 05/21/2012 at 03:51 PM, Clark Morris cfmpub...@ns.sympatico.ca said: I'm the last to see my own errors. Hopefully it was obvious I meant 24/7/365 That's no better. Either 24/7/52 or 24/365 would be approximately correct. On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it and is it the way that the general public as opposed to us professional nitpickers best understands it? Clark Morris -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
bfairch...@rocketsoftware.com (Bill Fairchild) writes: And the general public, many Dilbertian managers, and even some of us professional nitpickers, think that a job running 1 hour instead of 10 is 900% faster, and that 1 is 10 times smaller than 10. 2+2 no longer = 5; now it equals chartreuse. Fortunately architects and engineers know how to use mathematically accurate and precise terminology when describing the bridges they design and build, or we would have a lot more cars falling off of collapsing bridges. re: http://www.garlic.com/~lynn/2012g.html#29 24/7/365 appropriateness was Re: IBMLink outages in 2012 Volcker in discussion with civil engineering professor about significantly decline in infrastructure projects (as institutions skimmed funds for other purposes disappearing civil engineering jobs) resulting in universities cutting back civil engineering programs; Confidence Men, pg290: Well, I said, 'The trouble with the United States recently is we spent several decades not producing many civil engineers and producing a huge number of financial engineers. And the result is s**tty bridges and a s**tty financial system! ... snip ... old presentation by Jim Gray on availability ... scanned from paper copy that had been made on copying machine in bldg. 28, SJR http://www.garlic.com/~lynn/grayft84.pdf the point (from early 80s) was that majority of outages (scheduled and non-scheduled) had shifted from hardware to software (and human errors). (early 70s) before virtual memory announcement for 370, a copy of internal document describing the technology leaked to the press. in the wake of the following investigation, all internal copying machines were retrofitted with unique identifier (under the glass) that would appear on all copies made on that machine. for other drift ... it has been five years since Jim disappeared and cal. court recently declared him dead ... reference in (linkedin) z/VM group: http://lnkd.in/C2yn7p also archived here: http://www.garlic.com/~lynn/2012g.html#21 Closure in Disappearance of Computer Scientist -- virtualization experience starting Jan1968, online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
On Wed, May 23, 2012 at 9:20 AM, Bill Fairchild bfairch...@rocketsoftware.com wrote: And the general public, many Dilbertian managers, and even some of us professional nitpickers, think that a job running 1 hour instead of 10 is 900% faster, and that 1 is 10 times smaller than 10. 2+2 no longer = 5; now it equals chartreuse. Fortunately architects and engineers know how to use mathematically accurate and precise terminology when describing the bridges they design and build, or we would have a lot more cars falling off of collapsing bridges. Bill Fairchild http://en.wikipedia.org/wiki/List_of_bridge_failures -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
On Wed, 23 May 2012 14:20:03 +, Bill Fairchild wrote: And the general public, many Dilbertian managers, and even some of us professional nitpickers, think that a job running 1 hour instead of 10 is 900% faster, I believe that's correct usage, even as an airplane that flies from New York to Washington in one hour is 900% faster than a car that makes the trip in 10 hours. and that 1 is 10 times smaller than 10. And that's confusing or nonsensical. But see: e.g.: http://en.wikipedia.org/wiki/Markedness#Marked_and_unmarked_word_pairs http://www.springerlink.com/content/u15776721t318p8u/ Does 24/7 sometimes presume an exception for national holidays? Why is it 24/7 rather than 24x7? And why do markets display prices such as 3/$1.00 rather than $1.00/3? Is chartreuse about 50% greener than olive? Now, can we get back to our charter of discussing the appropriate use of TLAs? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: 24/7/365 appropriateness was Re: IBMLink outages in 2012
IMHO everyone here perfectly understand common (and intended) meaning of 24/7/365. While is formally inaccurate, it's still clear. The rest is as worth to discuss as USS=Unix System Services. Maybe there is official IBM meaning* of 24/7/365 or the only proper description of continuous availability ? vbg My €0.02 -- Radoslaw Skorupka Lodz, Poland W dniu 2012-05-23 16:20, Bill Fairchild pisze: And the general public, many Dilbertian managers, and even some of us professional nitpickers, think that a job running 1 hour instead of 10 is 900% faster, and that 1 is 10 times smaller than 10. 2+2 no longer = 5; now it equals chartreuse. Fortunately architects and engineers know how to use mathematically accurate and precise terminology when describing the bridges they design and build, or we would have a lot more cars falling off of collapsing bridges. Bill Fairchild Programmer Rocket Software 408 Chamberlain Park Lane * Franklin, TN 37069-2526 * USA t: +1.617.614.4503 * e: bfairch...@rocketsoftware.com * w: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Clark Morris Sent: Wednesday, May 23, 2012 6:54 AM To: IBM-MAIN@bama.ua.edu Subject: 24/7/365 appropriateness was Re: IBMLink outages in 2012 On 22 May 2012 20:04:42 -0700, in bit.listserv.ibm-main you wrote: Inhj3lr7lassfuf88ovoeg000i1pp935e...@4ax.com, on 05/21/2012 at 03:51 PM, Clark Morriscfmpub...@ns.sympatico.ca said: I'm the last to see my own errors. Hopefully it was obvious I meant 24/7/365 That's no better. Either 24/7/52 or 24/365 would be approximately correct. On a logical basis I agree with you but has the 24/7/365 shortcut for continuous availability become so pervasive that it is the shorthand way for saying it and is it the way that the general public as opposed to us professional nitpickers best understands it? Clark Morris -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2012 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.410.984 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
In hj3lr7lassfuf88ovoeg000i1pp935e...@4ax.com, on 05/21/2012 at 03:51 PM, Clark Morris cfmpub...@ns.sympatico.ca said: I'm the last to see my own errors. Hopefully it was obvious I meant 24/7/365 That's no better. Either 24/7/52 or 24/365 would be approximately correct. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
On 20 May 2012 20:18:55 -0700, in bit.listserv.ibm-main you wrote: 24/7/265? That hurts, sounds more like my tyres. I'm the last to see my own errors. Hopefully it was obvious I meant 24/7/365 (or should that be 365.24?). Clark Morris MARK DOUGLAS -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Clark Morris Sent: Monday, 21 May 2012 1:10 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IBMLink outages in 2012 On 20 May 2012 18:28:50 -0700, in bit.listserv.ibm-main you wrote: On 5/20/2012 7:33 PM, Mary Anne Matyaz wrote: Except for an 'outage' is not 'scheduled maintenance'. So they still hit 24/7 as long as they do it during a 50 some hour outage. :) MA Let me know if I missed any. Clearly we still have a way to go for 24/7. 100%, 99%, 98.4%, 97.5%, 97.4%: clearly trending in the wrong direction. The average up-time so far in 2012 is 98.46% ... not even two nines. Of course, things look far worse if you consider weekends -- when most customer scheduled outages take place -- to be 'prime time' for IBMLink availability. :-\ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN For our purposes, an outage is an outage, scheduled or not. Our requirement to IBM is clearly 24/7/365(6), for all of IBMLink, SR, ShopZ, Internet Service Retrieval, etc. Ed's right in that IBM exacerbates the problem by having the outages during most z/OS installation's prime time for maintenance. They should move these outages to 0dark30 on Thursday morning or something. In a private e-mail, I was correctly brought to task for repetitive postings comparing IBM to Microsoft. However I think I have been making my point badly. It seems that IBM feels that it is not worth the investment to bring this application (Service Link, etc.) to a 24/7/265 level of reliability and some people who I know and respect here would have this lower on the list of priorities believing there are more urgent issues. However my point is two fold, the first is that we can point to another vendor that seems to do better and that this may well cast doubts on the reliability of the z series platform. In dealing with the problem we need to determine if this is basically just a problem for z/OS support staff that doesn't affect the perception of the platform or is this something that hurts those of us who are advocating that the z series platform is the best one for our critical applications. In short is this just a techy problem or is it also an image problem within the larger organization? Clark Morris Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN * Disclaimer * The contents of this electronic message and any attachments are intended only for the addressee and may contain privileged or confidential information. They may only be used for the purposes for which they were supplied. If you are not the addressee, you are notified that any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. The privilege of confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of mistaken delivery to you. If you receive this message in error please notify the sender by return e-mail or telephone. Please note: the Department of Public Works carries out automatic software scanning, filtering and blocking of E-mails and attachments (including emails of a personal nature) for detection of viruses, malicious code, SPAM, executable programs or content it deems unacceptable. All reasonable precautions will be taken to respect the privacy of individuals in accordance with the Information Privacy Act 2009 (Qld). Personal information will only be used for official purposes, e.g. monitoring Departmental Personnel's compliance with Departmental Policies. Personal information will not be divulged or disclosed to others, unless authorised or required by Departmental Policy and/or law. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
This post should be saved and not read until Friday for the proper mind-set. I think the correct term should be 24/7/52.1775, as there are 52.1775 weeks in an average [1] year rather than 365, 366, or even 265. Bill Fairchild Programmer Rocket Software 408 Chamberlain Park Lane * Franklin, TN 37069-2526 * USA t: +1.617.614.4503 * e: bfairch...@rocketsoftware.com * w: www.rocketsoftware.com [1] averaged over a complete Gregorian calendar cycle of 400 years. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Clark Morris Sent: Monday, May 21, 2012 1:52 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IBMLink outages in 2012 On 20 May 2012 20:18:55 -0700, in bit.listserv.ibm-main you wrote: 24/7/265? That hurts, sounds more like my tyres. I'm the last to see my own errors. Hopefully it was obvious I meant 24/7/365 (or should that be 365.24?). Clark Morris MARK DOUGLAS -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Clark Morris Sent: Monday, 21 May 2012 1:10 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IBMLink outages in 2012 On 20 May 2012 18:28:50 -0700, in bit.listserv.ibm-main you wrote: On 5/20/2012 7:33 PM, Mary Anne Matyaz wrote: Except for an 'outage' is not 'scheduled maintenance'. So they still hit 24/7 as long as they do it during a 50 some hour outage. :) MA Let me know if I missed any. Clearly we still have a way to go for 24/7. 100%, 99%, 98.4%, 97.5%, 97.4%: clearly trending in the wrong direction. The average up-time so far in 2012 is 98.46% ... not even two nines. Of course, things look far worse if you consider weekends -- when most customer scheduled outages take place -- to be 'prime time' for IBMLink availability. :-\ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN For our purposes, an outage is an outage, scheduled or not. Our requirement to IBM is clearly 24/7/365(6), for all of IBMLink, SR, ShopZ, Internet Service Retrieval, etc. Ed's right in that IBM exacerbates the problem by having the outages during most z/OS installation's prime time for maintenance. They should move these outages to 0dark30 on Thursday morning or something. In a private e-mail, I was correctly brought to task for repetitive postings comparing IBM to Microsoft. However I think I have been making my point badly. It seems that IBM feels that it is not worth the investment to bring this application (Service Link, etc.) to a 24/7/265 level of reliability and some people who I know and respect here would have this lower on the list of priorities believing there are more urgent issues. However my point is two fold, the first is that we can point to another vendor that seems to do better and that this may well cast doubts on the reliability of the z series platform. In dealing with the problem we need to determine if this is basically just a problem for z/OS support staff that doesn't affect the perception of the platform or is this something that hurts those of us who are advocating that the z series platform is the best one for our critical applications. In short is this just a techy problem or is it also an image problem within the larger organization? Clark Morris Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN * Disclaimer * The contents of this electronic message and any attachments are intended only for the addressee and may contain privileged or confidential information. They may only be used for the purposes for which they were supplied. If you are not the addressee, you are notified that any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. The privilege of confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of mistaken delivery to you. If you receive this message in error please notify the sender by return e-mail or telephone. Please note: the Department of Public Works carries out automatic software scanning, filtering and blocking of E-mails and attachments (including emails of a personal nature) for detection of viruses, malicious code, SPAM, executable programs or content it deems unacceptable. All reasonable precautions will be taken to respect the privacy of individuals in accordance with the Information Privacy Act 2009 (Qld). Personal information will only be used for official purposes, e.g. monitoring Departmental Personnel's compliance with Departmental Policies. Personal information
Re: IBMLink outages in 2012
My consideration is many applications in IBMLink don't seem to merit the cost of true continuous operations. I think it is unreasonable to ask for 24/7/365(6), for all of IBMLink. We need high availability for applications that enable us to effectively support our own high availability systems. This seems to be operational support for our System z hardware and software, reporting problems electronically, researching problem databases for known solutions and open APARs, and retrieving service. ResourceLink which we use for hardware support IBM moved to a higher availability infrastructure some time ago and has made process changes to make the infrequent outages less problematic for customers. SR on the current highly available infrastructure seems to be filling the need to submit problems electronically. I didn't like SR as much when I first saw it. The community at SHARE and customers directly gave IBM very critical feedback. IBM's leaders listened and delayed the replacement of ETR by SR until many significant issues had been addressed. There are remaining bugs and opportunities to improve i.e. the double sign-in requirement for some use cases. SR is any many ways better than ETR and I now prefer it i.e. attach small files, multiple users updates on status of PMR, etc. IBM is doing OK here. IBMLink SIS is critical to us. This weekend it was fortunate that IBMLink was up early as we had a planned infrastructure outage and ran into a problem that we found in five minutes using SIS probably would have taken hours using phone support at 0400 on a Sunday. IBMLink SIS or some other tool that is highly available and lets me search in one place all System z products solutions, problems, and information is important to us. IBMLink availability for SIS has not always met our expectations. This weekend for instance it was scheduled down while we had a major quarterly infrastructure upgrade. We hit a problem that caused our daily backups to fail after deploying RSU1203 (OA38632). We were lucky and IBMLink was up early from its scheduled down time so we were able to very quickly in a few minutes determine that a fixing PTF and a workaround was available.I think IBM needs to make moving the search function improving completeness, usability, and transition to a high! availability infrastructure a priority. ShopzSeries or an equivalent facility to order and retrieve service and hold data electronically is the third leg on the stool for production support. This is an area where IBM has not met expectations and outages have occurred on a recurring basis with little or no explanation. The applications in IBMLink outside that core are conveniences and should have good availability but probably don't have a valid business case to be highly available. IBM is not meeting my expectations in terms of announcing downtime with sufficient lead time, providing access to a help desk with current availability information, and minimizing outages. I think IBM has an opportunity to showcase its own technologies in its customer faced systems that it seems to be missing. Best Regards, Sam Knutson, GEICO System z Team Leader mailto:sknut...@geico.com (office) 301.986.3574 (cell) 301.996.1318 Think big, act bold, start simple, grow fast... -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Thomas Conley Sent: Sunday, May 20, 2012 9:28 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IBMLink outages in 2012 For our purposes, an outage is an outage, scheduled or not. Our requirement to IBM is clearly 24/7/365(6), for all of IBMLink, SR, ShopZ, Internet Service Retrieval, etc. Ed's right in that IBM exacerbates the problem by having the outages during most z/OS installation's prime time for maintenance. They should move these outages to 0dark30 on Thursday morning or something. Regards, Tom Conley This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
Actually, in 24 / 7 / 365, why are days listed twice? 24 hours a day, 365 days a year would cover it (ignoring leap day). 24 hours a day, 7 days a week, 52 weeks a year covers it a more sensible way (ignoring the extra day or two past 364 days). 24 hours a day, 7 days a week, 365 weeks? What happens after the 7 years? On Mon, May 21, 2012 at 1:51 PM, Clark Morris cfmpub...@ns.sympatico.ca wrote: On 20 May 2012 20:18:55 -0700, in bit.listserv.ibm-main you wrote: 24/7/265? That hurts, sounds more like my tyres. I'm the last to see my own errors. Hopefully it was obvious I meant 24/7/365 (or should that be 365.24?). Clark Morris -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
On 21 May 2012 13:27:19 -0700, in bit.listserv.ibm-main Sam Knutson wrote: My consideration is many applications in IBMLink don't seem to merit the cost of true continuous operations. I think it is unreasonable to ask for 24/7/365(6), for all of IBMLink. As someone who has been away from the actual trouble shooting for over 20 years (I still remember my site's customer number) so I don't know what the critical functions are or what all is included in IBMLINK. From your posting below, I can see that IBMLINK covers a number of areas. I wonder how Amazon or LL Bean define what has to have virtually total availability. Similar questions arise for Apple and Microsoft. I would definitely think that problem databases require it and that frozen ones should be available for reading even when they are unavailable for update due to maintenance. I'm wondering if this is sort of like EREP was back when I was dealing with it, a necessary stepchild that seemed to not have any one group responsible for it. Possibly it would be worthwhile to identify all of the functions in IBMLINK and identify which ones need the availability. It sounds like something SHARE is well suited for. Also we need to identify the customer and IBM costs incurred by lack of availability both soft and hard. Have any of the people on this list found that the problems with IBMLINK affect the perception of the z series within their organizations and of IBM's ability to come up with appropriate products for business needs? Clark Morris We need high availability for applications that enable us to effectively support our own high availability systems. This seems to be operational support for our System z hardware and software, reporting problems electronically, researching problem databases for known solutions and open APARs, and retrieving service. ResourceLink which we use for hardware support IBM moved to a higher availability infrastructure some time ago and has made process changes to make the infrequent outages less problematic for customers. SR on the current highly available infrastructure seems to be filling the need to submit problems electronically. I didn't like SR as much when I first saw it. The community at SHARE and customers directly gave IBM very critical feedback. IBM's leaders listened and delayed the replacement of ETR by SR until many significant issues had been addressed. There are remaining bugs and opportunities to improve i.e. the double sign-in requirement for some use cases. SR is any many ways better than ETR and I now prefer it i.e. attach small files, multiple users updates on status of PMR, etc. IBM is doing OK here. IBMLink SIS is critical to us. This weekend it was fortunate that IBMLink was up early as we had a planned infrastructure outage and ran into a problem that we found in five minutes using SIS probably would have taken hours using phone support at 0400 on a Sunday. IBMLink SIS or some other tool that is highly available and lets me search in one place all System z products solutions, problems, and information is important to us. IBMLink availability for SIS has not always met our expectations. This weekend for instance it was scheduled down while we had a major quarterly infrastructure upgrade. We hit a problem that caused our daily backups to fail after deploying RSU1203 (OA38632). We were lucky and IBMLink was up early from its scheduled down time so we were able to very quickly in a few minutes determine that a fixing PTF and a workaround was available.I think IBM needs to make moving the search function improving completeness, usability, and transition to a hig! h! availability infrastructure a priority. ShopzSeries or an equivalent facility to order and retrieve service and hold data electronically is the third leg on the stool for production support. This is an area where IBM has not met expectations and outages have occurred on a recurring basis with little or no explanation. The applications in IBMLink outside that core are conveniences and should have good availability but probably don't have a valid business case to be highly available. IBM is not meeting my expectations in terms of announcing downtime with sufficient lead time, providing access to a help desk with current availability information, and minimizing outages. I think IBM has an opportunity to showcase its own technologies in its customer faced systems that it seems to be missing. Best Regards, Sam Knutson, GEICO System z Team Leader mailto:sknut...@geico.com (office) 301.986.3574 (cell) 301.996.1318 Think big, act bold, start simple, grow fast... -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Thomas Conley Sent: Sunday, May 20, 2012 9:28 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IBMLink
Re: IBMLink outages in 2012
in one place all System z products solutions, problems, and information is important to us. IBMLink availability for SIS has not always met our expectations. This weekend for instance it was scheduled down while we had a major quarterly infrastructure upgrade. We hit a problem that caused our daily backups to fail after deploying RSU1203 (OA38632). We were lucky and IBMLink was up early from its scheduled down time so we were able to very quickly in a few minutes determine that a fixing PTF and a workaround was available.I think IBM needs to make moving the search function improving completeness, usability, and transition to a hig! h! availability infrastructure a priority. ShopzSeries or an equivalent facility to order and retrieve service and hold data electronically is the third leg on the stool for production support. This is an area where IBM has not met expectations and outages have occurred on a recurring basis with little or no explanation. The applications in IBMLink outside that core are conveniences and should have good availability but probably don't have a valid business case to be highly available. IBM is not meeting my expectations in terms of announcing downtime with sufficient lead time, providing access to a help desk with current availability information, and minimizing outages. I think IBM has an opportunity to showcase its own technologies in its customer faced systems that it seems to be missing. Best Regards, Sam Knutson, GEICO System z Team Leader mailto:sknut...@geico.com (office) 301.986.3574 (cell) 301.996.1318 Think big, act bold, start simple, grow fast... -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Thomas Conley Sent: Sunday, May 20, 2012 9:28 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IBMLink outages in 2012 For our purposes, an outage is an outage, scheduled or not. Our requirement to IBM is clearly 24/7/365(6), for all of IBMLink, SR, ShopZ, Internet Service Retrieval, etc. Ed's right in that IBM exacerbates the problem by having the outages during most z/OS installation's prime time for maintenance. They should move these outages to 0dark30 on Thursday morning or something. Regards, Tom Conley This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
Except for an 'outage' is not 'scheduled maintenance'. So they still hit 24/7 as long as they do it during a 50 some hour outage. :) MA Let me know if I missed any. Clearly we still have a way to go for 24/7. 100%, 99%, 98.4%, 97.5%, 97.4%: clearly trending in the wrong direction. The average up-time so far in 2012 is 98.46% ... not even two nines. Of course, things look far worse if you consider weekends -- when most customer scheduled outages take place -- to be 'prime time' for IBMLink availability. :-\ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
On 5/20/2012 7:33 PM, Mary Anne Matyaz wrote: Except for an 'outage' is not 'scheduled maintenance'. So they still hit 24/7 as long as they do it during a 50 some hour outage. :) MA Let me know if I missed any. Clearly we still have a way to go for 24/7. 100%, 99%, 98.4%, 97.5%, 97.4%: clearly trending in the wrong direction. The average up-time so far in 2012 is 98.46% ... not even two nines. Of course, things look far worse if you consider weekends -- when most customer scheduled outages take place -- to be 'prime time' for IBMLink availability. :-\ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN For our purposes, an outage is an outage, scheduled or not. Our requirement to IBM is clearly 24/7/365(6), for all of IBMLink, SR, ShopZ, Internet Service Retrieval, etc. Ed's right in that IBM exacerbates the problem by having the outages during most z/OS installation's prime time for maintenance. They should move these outages to 0dark30 on Thursday morning or something. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
On 20 May 2012 18:28:50 -0700, in bit.listserv.ibm-main you wrote: On 5/20/2012 7:33 PM, Mary Anne Matyaz wrote: Except for an 'outage' is not 'scheduled maintenance'. So they still hit 24/7 as long as they do it during a 50 some hour outage. :) MA Let me know if I missed any. Clearly we still have a way to go for 24/7. 100%, 99%, 98.4%, 97.5%, 97.4%: clearly trending in the wrong direction. The average up-time so far in 2012 is 98.46% ... not even two nines. Of course, things look far worse if you consider weekends -- when most customer scheduled outages take place -- to be 'prime time' for IBMLink availability. :-\ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN For our purposes, an outage is an outage, scheduled or not. Our requirement to IBM is clearly 24/7/365(6), for all of IBMLink, SR, ShopZ, Internet Service Retrieval, etc. Ed's right in that IBM exacerbates the problem by having the outages during most z/OS installation's prime time for maintenance. They should move these outages to 0dark30 on Thursday morning or something. In a private e-mail, I was correctly brought to task for repetitive postings comparing IBM to Microsoft. However I think I have been making my point badly. It seems that IBM feels that it is not worth the investment to bring this application (Service Link, etc.) to a 24/7/265 level of reliability and some people who I know and respect here would have this lower on the list of priorities believing there are more urgent issues. However my point is two fold, the first is that we can point to another vendor that seems to do better and that this may well cast doubts on the reliability of the z series platform. In dealing with the problem we need to determine if this is basically just a problem for z/OS support staff that doesn't affect the perception of the platform or is this something that hurts those of us who are advocating that the z series platform is the best one for our critical applications. In short is this just a techy problem or is it also an image problem within the larger organization? Clark Morris Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
24/7/265? That hurts, sounds more like my tyres. MARK DOUGLAS -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Clark Morris Sent: Monday, 21 May 2012 1:10 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IBMLink outages in 2012 On 20 May 2012 18:28:50 -0700, in bit.listserv.ibm-main you wrote: On 5/20/2012 7:33 PM, Mary Anne Matyaz wrote: Except for an 'outage' is not 'scheduled maintenance'. So they still hit 24/7 as long as they do it during a 50 some hour outage. :) MA Let me know if I missed any. Clearly we still have a way to go for 24/7. 100%, 99%, 98.4%, 97.5%, 97.4%: clearly trending in the wrong direction. The average up-time so far in 2012 is 98.46% ... not even two nines. Of course, things look far worse if you consider weekends -- when most customer scheduled outages take place -- to be 'prime time' for IBMLink availability. :-\ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN For our purposes, an outage is an outage, scheduled or not. Our requirement to IBM is clearly 24/7/365(6), for all of IBMLink, SR, ShopZ, Internet Service Retrieval, etc. Ed's right in that IBM exacerbates the problem by having the outages during most z/OS installation's prime time for maintenance. They should move these outages to 0dark30 on Thursday morning or something. In a private e-mail, I was correctly brought to task for repetitive postings comparing IBM to Microsoft. However I think I have been making my point badly. It seems that IBM feels that it is not worth the investment to bring this application (Service Link, etc.) to a 24/7/265 level of reliability and some people who I know and respect here would have this lower on the list of priorities believing there are more urgent issues. However my point is two fold, the first is that we can point to another vendor that seems to do better and that this may well cast doubts on the reliability of the z series platform. In dealing with the problem we need to determine if this is basically just a problem for z/OS support staff that doesn't affect the perception of the platform or is this something that hurts those of us who are advocating that the z series platform is the best one for our critical applications. In short is this just a techy problem or is it also an image problem within the larger organization? Clark Morris Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN * Disclaimer * The contents of this electronic message and any attachments are intended only for the addressee and may contain privileged or confidential information. They may only be used for the purposes for which they were supplied. If you are not the addressee, you are notified that any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. The privilege of confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of mistaken delivery to you. If you receive this message in error please notify the sender by return e-mail or telephone. Please note: the Department of Public Works carries out automatic software scanning, filtering and blocking of E-mails and attachments (including emails of a personal nature) for detection of viruses, malicious code, SPAM, executable programs or content it deems unacceptable. All reasonable precautions will be taken to respect the privacy of individuals in accordance with the Information Privacy Act 2009 (Qld). Personal information will only be used for official purposes, e.g. monitoring Departmental Personnel's compliance with Departmental Policies. Personal information will not be divulged or disclosed to others, unless authorised or required by Departmental Policy and/or law. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: IBMLink outages in 2012
On 5/19/2012 8:20 PM, Pinnacle wrote: Let me know if I missed any. Clearly we still have a way to go for 24/7. 100%, 99%, 98.4%, 97.5%, 97.4%: clearly trending in the wrong direction. The average up-time so far in 2012 is 98.46% ... not even two nines. Of course, things look far worse if you consider weekends -- when most customer scheduled outages take place -- to be 'prime time' for IBMLink availability. :-\ -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
