INFO-VAX Thu, 22 Feb 2007 Volume 2007 : Issue 105 Contents: A CEO agrees with me: Marketing! Re: Canadian OpenVMS Seminar (07.02.20) Re: Canadian OpenVMS Seminar (07.02.20) Re: EVE defined key problem. Re: EVE defined key problem. Re: How bad software planning costed Airbus $6 billion Re: Major windoze Vista account ports to OpenVMS! Re: MSA1500 on VMS? NYC area OpenVMS Update, T4/TLViz Talks 2/28/07 Re: Oracle - DST 2007 heads up OT: Quebec Health Care Virus Re: OT: Quebec Health Care Virus Re: OT: Quebec Health Care Virus RE: OT: Quebec Health Care Virus Re: Quebec Health Care Virus RE: Quebec Health Care Virus Re: SRI PersonalAlpha and OpenVMS PAK Re: They are slowly coming home to the worlds ONLY virus free OS! Re: VT320 or 420 keypad codes ---------------------------------------------------------------------- Date: Wed, 21 Feb 2007 20:04:47 -0600 From: David J Dachtera Subject: A CEO agrees with me: Marketing! Message-ID: <45DCFA3F.3D15CF61@spam.comcast.net> Seems I'm not the only one saying it. In an article on Reuters about Kraft Foods, a U.S. company, the CEO of Kraft is quoted as saying (about Kraft), "... the company needs to spend more on marketing and develop new products that go beyond extensions of existing lines". Maybe I'm not crazy after all. -- David J Dachtera dba DJE Systems http://www.djesys.com/ Unofficial OpenVMS Marketing Home Page http://www.djesys.com/vms/market/ Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/ Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/ Unofficial OpenVMS Hobbyist Support Page: http://www.djesys.com/vms/support/ ------------------------------ Date: Wed, 21 Feb 2007 20:14:13 -0600 From: David J Dachtera Subject: Re: Canadian OpenVMS Seminar (07.02.20) Message-ID: <45DCFC75.E7927721@spam.comcast.net> "n.rieck@sympatico.ca" wrote: > > Canadian OpenVMS Seminar (07.02.20) > > I won't bore you with the whole thing but here are some key Itanium > points. > > 1) there are now more Itanium CPUs installed in working system than > Alphas. > (this figure is industry-wide; not just HP) What's the breakdown? - Enterprise-class systems (GS1280 equiv.): - "Second Tier" servers (ESxx class): - "Small" servers (DSxx class): > 2) 70 companies are involved in producing Itanium systems How many produce machines that are certified to run VMS? > 3) Don't expect a quad-core Itanium2 until 2009. Reason? No chip sets > are > currently available which would be able to constantly feed data to all > 4 > cores The main reason why OpenVMS in the enterprise tier is doomed to extinction. > 4) The Itanium chip can provide RAS (Reliability, Availability, > Serviceability) while x86-64 systems currently do not. I heard one > engineer > say "Bill Gates isn't responsible for all instances of the > blue-screen-of-death; the quirkiness of x86-64 and supporting chip- > sets are > partially to blame" Not really relevant to VMS at this time since no VMS-x64. -- David J Dachtera dba DJE Systems http://www.djesys.com/ Unofficial OpenVMS Marketing Home Page http://www.djesys.com/vms/market/ Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/ Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/ Unofficial OpenVMS Hobbyist Support Page: http://www.djesys.com/vms/support/ ------------------------------ Date: 21 Feb 2007 19:22:09 -0800 From: "n.rieck@sympatico.ca" Subject: Re: Canadian OpenVMS Seminar (07.02.20) Message-ID: <1172114529.028693.72280@m58g2000cwm.googlegroups.com> Photo From the Canadian OpenVMS Seminar (07.02.20) http://www.encompasscanada.com/ That's JF standing next to Sue in the middle. (I'm wearning the black shirt and grey jacket on the far left) Neil Rieck Kitchener/Waterloo/Cambridge, Ontario, Canada. http://www3.sympatico.ca/n.rieck/ ------------------------------ Date: Wed, 21 Feb 2007 19:19:41 GMT From: Rob Brown Subject: Re: EVE defined key problem. Message-ID: On Wed, 21 Feb 2007, Fatz wrote: >> TPU MESSAGE(STR(READ_KEY)) > > DOWN > > I am indeed using an eXceed DECterm. Hmmm. What happens when you press KP2 at the DCL prompt? On a PC keyboard, the arrow keys are mapped to the numeric keypad with KP2 being DOWN, unless the numlock setting is "numbers". Does eXceed take care of this for you? Or do you need to press the numlock key? -- Rob Brown b r o w n a t g m c l d o t c o m G. Michaels Consulting Ltd. (780)438-9343 (voice) Edmonton (780)437-3367 (FAX) http://gmcl.com/ ------------------------------ Date: Wed, 21 Feb 2007 18:36:36 -0500 From: JF Mezei Subject: Re: EVE defined key problem. Message-ID: <11548$45dcd78c$cef8887a$3605@TEKSAVVY.COM> Fatz wrote: > Thanks for responding: > > Using "two" instead of "split" had no effect. Try: Command: DEFINE enter TWO as the EVE command then press the actual key you want defined. This will map the command to whatever key you have pressed, no matter what your emulator is doing. Interestingly, in your TPU$COMMAND.TPU file, you can : define_key (eve$$kt_return + "eve_two_windows", KP2, "Split window"); and when you press HELP key while in TPU, it will show "Split window" as the text for that key. But the actual command is TWO_WINDOWS (TPU is the background engine, EVE is the editor. The User interface expects EVE commands such as TWO_WINDOWS, while the TPU$COMMAND.TPU expects TPU commands hence the different syntax). You may need to : DEFINE TPU$COMMAND SYS$LOGIN:TPU$COMMAND.TPU ------------------------------ Date: 21 Feb 2007 17:27:32 -0800 From: "GeekMan" Subject: Re: How bad software planning costed Airbus $6 billion Message-ID: <1172106653.246821.146640@m58g2000cwm.googlegroups.com> ....snip... > > Anyway, XML and SOA and Web 2.0 and mashups and ... will fix all that next > time, and will cost hardly anything. It must be true, I read it in an IT > comic (same as I read about MAP and TOP and CALS and PDES and STEP and SAP > and ...). You forgot EDIF....... ------------------------------ Date: Wed, 21 Feb 2007 16:40:33 -0500 From: JF Mezei Subject: Re: Major windoze Vista account ports to OpenVMS! Message-ID: <70a67$45dcbc55$cef8887a$27810@TEKSAVVY.COM> BTW, "Vista" was listed as a major partner for VMS in Sue's Powerpoint presentations. ------------------------------ Date: Thu, 22 Feb 2007 04:38:48 GMT From: "Malcolm Dunnett" Subject: Re: MSA1500 on VMS? Message-ID: wrote in message news:1171634760.485974.32660@j27g2000cwj.googlegroups.com... | Thanks Malcolm. | Nice gotcha though - if you want to regress back to the old firmware | you've got to back everything up and start again. :o( I loaded the V7 firmware on the MSA1000 today. When I restarted the controller it kept crashing during the "scanning SCSI devices" phase. Turns out it didn't like the 4254 shelf I was using on the expansion ports ( it's not supported, but it worked with the old firmware - abeit only at 80MB/sec ). I replaced it with a newer shelf and everthing came up fine. I can't really try the active/active configuration because I can't get the 2/6 fibreswitch to work, so I only have one port. I don't have the password for the switch and there's something funny programmed into it - it won't connect to my Brocade switch. It appears theres no way to get into the switch without paying HP or Brocade to reset it ( I don't have it under service ). Anyone want to buy a 2/6 switch cheap? I'm going to replace it with a regular single fibre port. (If anyone's got one they want to trade for a switch with an unknown password I'll do that too) ------------------------------ Date: 21 Feb 2007 10:54:30 -0800 From: "Gary McCready" Subject: NYC area OpenVMS Update, T4/TLViz Talks 2/28/07 Message-ID: <1172084070.119949.327230@p10g2000cwp.googlegroups.com> The Encompass New York Metro Local User Group (NYMLUG) will host a meeting set for Wednesday, Feb. 28 featuring an OpenVMS Update talk by Stephen "Hoff" Hoffman, of HoffmanLabs, formerly of HP and a T4 (Performance Tool) talk by Steve Lieman, Trend Analyst & Performance Architect at TrendsThatMatter.com. Anyone may attend the meeting. Please see below for more detail. The talk will be hosted near the Exchange Place PATH station, Jersey City, NJ location starting at 12:00. Those who sign up will be sent directions to the meeting location on 2/26. Please sign up by by filling out an interest survey by Monday, 2/26, 7pm at http://snipurl.com/NYM0702 or http://www.surveymonkey.com/s.asp?u=549063255627 or by sending email to nymlug (-at-) mccready.com. For additional information and updates, please join the NYMLUG mailing list at http://groups.yahoo.com/group/NYMLUG/ You may also send email to Gary McCready at nymlug (-at-) mccready.com or if you have questions about the meeting or the local user group. Please note that we will probably need to limit attendance at this meeting, so please respond quickly to avoid disappointment! For more information about Encompass, an HP User Group, please visit: http://www.encompassus.org/ OpenVMS Technical Update: Information on recent and on planned OpenVMS features, platforms and capabilities. Details on OpenVMS V7.3-2, V8.3 and on the OpenVMS roadmap will be presented, as will information on Integrity servers and the Alpha product status. As time permits, Hoff will also include the latest in OpenVMS Hints and Kinks, which are a collection of OpenVMS-related details, tools and techniques you that might not have known about before. Speaker: Stephen "Hoff" Hoffman If it has to do with MicroVMS, VMS or OpenVMS or with VAX, Alpha or Integrity server or related hardware, Stephen "Hoff" Hoffman has probably worked with it. Written a book or two about it. Presented about it. Answered Ask The Wizard or ITRC or comp.os.vms questions about it. Or engineered or ported it. This ranges from work within the OpenVMS Engineering team including porting OpenVMS to Intel Itanium, to a quarter-century of continuous experience with the platform with end-user organizations, and within DIGITAL, Compaq and HP. Security, drivers, ACPs, TCP/IP and DECnet networking and DCL are all familiar territory. Hoff is now available to resolve your OpenVMS conundrums through HoffmanLabs LLC, a services and support company and HP Business Partner specializing in OpenVMS software, and VAX, Alpha and Integrity hardware. For more info on this speaker, please visit http://www.hoffmanlabs.com/ Making the Best Use of the Most Recent T4 Features & Improvements The T4 & Friends Approach to performance has been proven to be a powerful and time-saving way to tackle the most challenging VMS and EVA performance problems. There have been some important recent improvements in the latest versions of TLViz (the TimeLine visualizer) and CSVPNG (the command line tool for manipulating T4 data). Using VMS T4 data and EVA data from VEVAMON as examples, this talk will demonstrate the use of the latest Beta version of TLViz ( v.2.0), and the newest features of CSVPNG (V1.0-119) and show how these tools can help you stay on top of the most important performance issue impacting your mission critical VMS and EVA systems. There will also be a brief example of how these tools can be put to excellent use on just about any trend data that you might have obtained from other sources. Intended Audience: If you are already using a T4 & Friends approach for your system performance investigations, this session will help learn what you need to know to advance to the next level. If you are new to T4, this session will help you determine how adding a T4 approach could prove to be a useful adjunct to the performance work you are already doing. Speaker: Steve Lieman, Trend Analyst & Performance Architect at TrendsThatMatter.com Steve has been involved with the hands-on practical uses of T4 from T4's early beginnings. He has actively employed T4, TLViz & CSVPNG as essential ingredients of his performance work for VMS Engineering and now in his work with TrendsThatMatter. Steve's audio segments on T4 related subjects have been included in several of the most recent VMS Audio Update programs. Steve was a member of the OpenVMS Engineering Performance Group for 11 years and has more than 25 years of enterprise system performance management experience. Steve has been a regular speaker about T4 at the popular OpenVMS Technical Updates and he has delivered seminars and hands-on workshops on practical performance management at more than two dozen locations in the U.S, Canada, Europe, and the Pacific Rim. Steve also participated on the Transaction Processing Council in its formative years while it was developing and defining the TPC-C benchmark For more information on this speaker, please visit http://www.trendsthatmatter.com/ ------------------------------ Date: Wed, 21 Feb 2007 16:26:30 -0500 From: JF Mezei Subject: Re: Oracle - DST 2007 heads up Message-ID: <698d$45dcb90a$cef8887a$29389@TEKSAVVY.COM> Bill Gunshannon wrote: > But no one "saves" anything. You merely relocate it. That is correct. However, there are cases at some latitudes where the move may reduce peak power consumption during a peak period. North of those latitudes, it will make no difference. And since the change in DST only changes power consumption during a couple of weeks of the year, and makes 0 difference during the real peak power conmsumption (january/february when it gets really cold), then the net effect is very minimal since power utilities must still scale their power generating utilities and power import contracts to support the try peak periods when it is very cold (or very hot in summer). What this silly changes really shows is that there is no viable opposition at the goverment or media level to block such silly and useless moves, and no viable opposition that would have outlined all the IT problems that this change would have generated around the world not just in the USA. Each elected representative in a govermment must learn to be a critique and truly spend the time to learn about issues before voting on them. And especially in the USA, they should forbid the technique of hiding various decisions as part of a bigger bill. This is purely political ("such and such voted for national ID cards" when "such and such" actually voted for some military budget to sustain troups and, having not read through the bill, was unaware that it also implemented a national ID card programme. ------------------------------ Date: Wed, 21 Feb 2007 15:31:06 -0500 From: JF Mezei Subject: OT: Quebec Health Care Virus Message-ID: This came to me from an untrusted source, but appears legit. Last week, the Quebec health care system came to a grinding halt due to a virus infection. (Hey Cerner, time to start taking government ministers to lunch to get the contract to rebuild this). This has been fairly hush hush in terms of details because we are just going into an election. Notes: because of separatist philosophy, Quebec now uses "national" instead of "provincial". But it does give some insight on how a large network of Windows Pcs cane come to a grinding halt. #### First excuse my English, this is not my native language. As some people want the inside of the story, here what really happened and is still happening as the situation is still not in control. First some topology. The Quebec health computing network (RTSS) has a pyramid structure. At the top of the pyramid there is what is called the "technocentre national" it can see all ip addresses in the network. Each administrative area in Quebec as a "technocentre regional" that can see all the ip addresses of their area. Each hospital can not see other hospital as they are at the bottom of the pyramid. For an hospital to see another hospital ip address, forms has to be filled and an explicit route has to be configure for the two ip addresses to be able to see each others. The good thing of this architecture is that every hospital (and other services provider) is isolated. The bad thing is if a virus gets up to the technocentre notional it can affect the entire network and make big damage. Now some history The RTSS has been around for now almost ten years, it is still based on old technology and the network link are not good (lots of 128, 256 and 512 kbps). Which means it is hard to do remote work, like deploying patches updates and other things. There have been promises for the last five years to update the network but as it is an exclusive contract sign between the GTQ and the Quebec ministry of Health it is hard to have things moving before the end of the contract. During the past 4 years, the health ministry has put a lot of pressure on the hospital to address security in the IT, but no new money has been injected. Therefore hospitals prefer to diminish the waiting list than investing on IT that still work. Another move is for the ministry to rationalise the IT departments. That means that whenever possible software should be installed in the Technocentre regional or national instead of the hospital. This is supposed to bring scale fund saving. (This has an important part to play in this virus attacked). The Quebec health network is composed by 90 000 pcs and more than 2000 servers. The average technician per pc ration is 1/200. That explains a lot on why there are still some windows 95, 98, NT workstations. There is no specific funding for the IT and hospital have to decide either to give services or to replace PCs. And as the waiting list are closely watch by the ministry, guess what they choose. The virus attack The virus (worm) was effectively the WORM.RINBOT.C worm. The attacked started two weeks ago in a hospital somewhere in Quebec. The thing to do would have to remove this hospital from the network until the hospital has been cleaned and therefore the hospital would have been the only one contaminated. But as they are more and more application that are housed at the technocentre regional, therefore disconnecting the hospital would have mean no radiology, no lab results,... So the hospital was left on the network, has contaminated the technocentre regional that has contaminated the technocentre national that has contaminated all areas of Quebec. The worm started spreading without control in the night of the 13th of February. On the 14th of February, a national security alert has been raised. But at that time most of the routers were already out of order because that one of the thing that the worm does is a DOD attack. The security alert asked us to clean all the infected servers, windows 95, 98 and NT workstation. The virus doesn't attack XP workstations (with SP2). On the 15th the situation got really completely out of control because more and more workstations get infected and some hospitals lost completely their network connectivity. (despite the official announcement that stated that everything was fined issued on the 13th of February). So on the 15th of February desperate measures were taken. First the internet access was closed (it is only at that point that we can be sure that no information was transmitted by the virus). We still do not know what information has been transmitted by the virus during the days is was active on the network. One thing is sure is that information was exchange and that the virus was trying to contact an external site to exchange information. Second the technocentre national asked that the 90 000 pcs were rebooted during a 6 hours window from 3pm to 9pm. The measures were efficient for some areas and on the 16th the virus was less active and almost eradicated in some areas. Mail services were restored. On the 19th the internet connection to the outside world has been restored for areas that did not show virus activity. A proxy has been put in place to manage the internet traffic because up to that time internet traffic was not monitored. And we are waiting for the situation to be in control in the entire province. As for the router logs, the logs have been turned on only after the facts and when the traffic was less because it was unmanageable. What is upsetting is that the media just relay the information given but the ministry without investigating. This was a major failure in the health network as some hospitals were not able to work during three days. They had to go back to paper. Areas that had put the VOIP did not have phones. But the government is going into election and therefore nothing has to be said as it looks really bad. Hopes this will give you the information you were seeking. ######## ------------------------------ Date: 21 Feb 2007 16:47:02 -0800 From: bob@instantwhip.com Subject: Re: OT: Quebec Health Care Virus Message-ID: <1172105222.230389.258080@q2g2000cwa.googlegroups.com> I continue to be amazed at how people here continue to state the flawed fact that another solution is cheaper and better than vms ... WRONG! when you take that higher initial investment and divide it over decades of virus free 99.9999 uptime enviroment your TCO on vms wins overwhelmingly ... also, they should be using vms to save money because they are broke running a socialized healthcare system the same one Hillary Clinton and the democrats are and have been pushing for years ... look at Canadas broken system and think about that the next election ... ------------------------------ Date: 21 Feb 2007 16:50:06 -0800 From: bob@instantwhip.com Subject: Re: OT: Quebec Health Care Virus Message-ID: <1172105406.267418.31770@a75g2000cwd.googlegroups.com> and just think of the money they could be saving if they would have been on vms initially ... they could have ran for decades on vms without a problem ever ... windoze is not a 10 to 20 year solution .... anyone who signs a contract longer than 1 year with any other os than vms is plain stupid ... ------------------------------ Date: Wed, 21 Feb 2007 22:10:53 -0500 From: "Main, Kerry" Subject: RE: OT: Quebec Health Care Virus Message-ID: > -----Original Message----- > From: bob@instantwhip.com [mailto:bob@instantwhip.com]=20 > Sent: February 21, 2007 7:47 PM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: OT: Quebec Health Care Virus >=20 > I continue to be amazed at how people here continue to state > the flawed fact that another solution is cheaper and better than > vms ... >=20 > WRONG! >=20 > when you take that higher initial investment and divide it over > decades > of virus free 99.9999 uptime enviroment your TCO on vms wins > overwhelmingly ... >=20 > also, they should be using vms to save money because they are > broke running a socialized healthcare system the same one Hillary > Clinton and the democrats are and have been pushing for years ... >=20 > look at Canadas broken system and think about that the next > election ... >=20 While I certainly will not argue about your choice in OS's, Canada's health systemm is far from broken.=20 While no system is issue free, the reality is that it works very well here for most situations - likely in the order of 95%+ or better. Unfortunately, those few areas where there are issues are magnified exponentially by those who prefer the status quo. And the system is constantly eveolving to reduce those 5% issues to an even smaller number. Back to the regular scheduled program .. :-) Regards Kerry Main Senior Consultant HP Services Canada Voice: 613-592-4660 Fax: 613-591-4477 kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20 OpenVMS - the secure, multi-site OS that just works. =20 ------------------------------ Date: Wed, 21 Feb 2007 13:43:23 -0700 From: "Michael D. Ober" Subject: Re: Quebec Health Care Virus Message-ID: <45dcaef4$0$10300$815e3792@news.qwest.net> This is more an indictment of the Quebec health care system priorities than it is of Windows. When Win95 and 98 were new, viruii were rare. The fact that these versions of Windows are still in use even after their shortcomings became painfully obvious to the rest of the world is a problem within the health care system. Yes, you can easily say that VMS wouldn't have been impacted, but the upfront cost of custom programming to get VMS to do what can be frequently purchased on the open market can be a major factor in not using VMS. Yes, there may be higher continuing costs running Windows, but if the upfront cost is too high, it doesn't make any difference simply because the initial purchase won't be made. In addition, almost any decent virus scanner could have stopped this thing in its tracks, so there is the additional issue of network security management not being done. As usual, problems like this aren't technical - they're human, or in the case of government health care, political. Mike Ober. "JF Mezei" wrote in message news:d981f$45dcac0e$cef8887a$25150@TEKSAVVY.COM... > This came to me from an untrusted source, but appears legit. Last week, > the Quebec health care system came to a grinding halt due to a virus > infection. (Hey Cerner, time to start taking government ministers to lunch > to get the contract to rebuild this). This has been fairly hush hush in > terms of details because we are just going into an election. > > Notes: because of separatist philosophy, Quebec now uses "national" > instead of "provincial". > > > But it does give some insight on how a large network of Windows Pcs cane > come to a grinding halt. > > > #### > First excuse my English, this is not my native language. > > As some people want the inside of the story, here what really happened > and is still happening as the situation is still not in control. > > First some topology. > > The Quebec health computing network (RTSS) has a pyramid structure. At > the top of the pyramid there is what is called the "technocentre > national" it can see all ip addresses in the network. Each > administrative area in Quebec as a "technocentre regional" that can > see all the ip addresses of their area. > > Each hospital can not see other hospital as they are at the bottom of > the pyramid. For an hospital to see another hospital ip address, forms > has to be filled and an explicit route has to be configure for the two > ip addresses to be able to see each others. The good thing of this > architecture is that every hospital (and other services provider) is > isolated. > > The bad thing is if a virus gets up to the technocentre notional it > can affect the entire network and make big damage. > > Now some history > > The RTSS has been around for now almost ten years, it is still based > on old technology and the network link are not good (lots of 128, 256 > and 512 kbps). Which means it is hard to do remote work, like > deploying patches updates and other things. > > There have been promises for the last five years to update the network > but as it is an exclusive contract sign between the GTQ and the Quebec > ministry of Health it is hard to have things moving before the end of > the contract. > > During the past 4 years, the health ministry has put a lot of pressure > on the hospital to address security in the IT, but no new money has > been injected. Therefore hospitals prefer to diminish the waiting list > than investing on IT that still work. > > Another move is for the ministry to rationalise the IT departments. > That means that whenever possible software should be installed in the > Technocentre regional or national instead of the hospital. This is > supposed to bring scale fund saving. (This has an important part to > play in this virus attacked). > > The Quebec health network is composed by 90 000 pcs and more than 2000 > servers. The average technician per pc ration is 1/200. That explains > a lot on why there are still some windows 95, 98, NT workstations. > There is no specific funding for the IT and hospital have to decide > either to give services or to replace PCs. And as the waiting list are > closely watch by the ministry, guess what they choose. > > The virus attack > The virus (worm) was effectively the WORM.RINBOT.C worm. The attacked > started two weeks ago in a hospital somewhere in Quebec. > The thing to do would have to remove this hospital from the network > until the hospital has been cleaned and therefore the hospital would > have been the only one contaminated. > > But as they are more and more application that are housed at the > technocentre regional, therefore disconnecting the hospital would have > mean no radiology, no lab results,... > > So the hospital was left on the network, has contaminated the > technocentre regional that has contaminated the technocentre national > that has contaminated all areas of Quebec. > > The worm started spreading without control in the night of the 13th of > February. On the 14th of February, a national security alert has been > raised. But at that time most of the routers were already out of order > because that one of the thing that the worm does is a DOD attack. > The security alert asked us to clean all the infected servers, windows > 95, 98 and NT workstation. > > The virus doesn't attack XP workstations (with SP2). > On the 15th the situation got really completely out of control because > more and more workstations get infected and some hospitals lost > completely their network connectivity. (despite the official > announcement that stated that everything was fined issued on the 13th > of February). > > So on the 15th of February desperate measures were taken. > > First the internet access was closed (it is only at that point that > we can be sure that no information was transmitted by the virus). We > still do not know what information has been transmitted by the virus > during the days is was active on the network. One thing is sure is > that information was exchange and that the virus was trying to contact > an external site to exchange information. > > Second the technocentre national asked that the 90 000 pcs were > rebooted during a 6 hours window from 3pm to 9pm. > > The measures were efficient for some areas and on the 16th the virus > was less active and almost eradicated in some areas. Mail services > were restored. > > On the 19th the internet connection to the outside world has been > restored for areas that did not show virus activity. A proxy has been > put in place to manage the internet traffic because up to that time > internet traffic was not monitored. > And we are waiting for the situation to be in control in the entire > province. > > As for the router logs, the logs have been turned on only after the > facts and when the traffic was less because it was unmanageable. > > What is upsetting is that the media just relay the information given > but the ministry without investigating. > This was a major failure in the health network as some hospitals were > not able to work during three days. They had to go back to paper. > Areas that had put the VOIP did not have phones. But the government is > going into election and therefore nothing has to be said as it looks > really bad. > Hopes this will give you the information you were seeking. > ######## ------------------------------ Date: Wed, 21 Feb 2007 21:28:37 -0500 From: "Main, Kerry" Subject: RE: Quebec Health Care Virus Message-ID: > -----Original Message----- > From: Michael D. Ober [mailto:"obermd."@.alum.mit.edu.nospam]=20 > Sent: February 21, 2007 3:43 PM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: Quebec Health Care Virus >=20 > This is more an indictment of the Quebec health care system=20 > priorities than=20 > it is of Windows. When Win95 and 98 were new, viruii were=20 > rare. The fact=20 > that these versions of Windows are still in use even after their=20 > shortcomings became painfully obvious to the rest of the=20 > world is a problem=20 > within the health care system. Yes, you can easily say that=20 > VMS wouldn't=20 > have been impacted, but the upfront cost of custom=20 > programming to get VMS to=20 > do what can be frequently purchased on the open market can be=20 > a major factor=20 > in not using VMS. Yes, there may be higher continuing costs running=20 > Windows, but if the upfront cost is too high, it doesn't make=20 > any difference=20 > simply because the initial purchase won't be made. >=20 > In addition, almost any decent virus scanner could have=20 > stopped this thing=20 > in its tracks, so there is the additional issue of network security=20 > management not being done. >=20 > As usual, problems like this aren't technical - they're=20 > human, or in the=20 > case of government health care, political. >=20 > Mike Ober. >=20 Mike - I have no idea of what the issues are with this specific case, but in general, when you base a mission critical infrastructure on a platform that has 5-20 serious security patches per month released, it is highly unlikely that any amount of processes are going to be able to prevent an incident from happening at some point in the future. Keep in mind that virus scanners do not look for open security holes that are widely published on various hacker networks that exist across the Internet. Also, keep in mind that most security analysts will state that something like 50-60% of all security incidents are due to internal issues. So, while no platform, including OpenVMS, can ever state they are 100% secure, the bottom line is that some platforms are more secure by design and do not have a culture established where its Customers have become so complacent that they put up with dealing with 5-20 security patches per month. At some point, one needs to examine OS religion and put some reality back into the system.=20 Case in point: http://www.openvms.org/stories.php?story=3D07/02/16/3329759 Regards Kerry Main Senior Consultant HP Services Canada Voice: 613-592-4660 Fax: 613-591-4477 kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20 OpenVMS - the secure, multi-site OS that just works. ------------------------------ Date: 21 Feb 2007 11:58:41 -0800 From: "Wilm Boerhout" Subject: Re: SRI PersonalAlpha and OpenVMS PAK Message-ID: <1172087921.812931.70960@m58g2000cwm.googlegroups.com> On 21 feb, 02:55, heal...@aracnet.com wrote: > On a related note, what can this emulator be used for? It has been years > since I tried running OpenVMS in 96Mb, and V7.2 was barely usable. As I > recall I considered 112Mb to be the realistic minimum on an > AlphaStation 200 4/233. It runs V8.2 just fine on my laptop. Just VMS and DECwindows, no apps or databases. It can be used to check VMS' new features, test DCL procedures, test different networking configurations. It's been a while, but I compiled all SIMH (3.5 I think) emulators on the Personal Alpha, and succeeded running RSTS/E on a SIMH PDP-11. SIMH VAX compiled, but would not run. I should try with the new 3.7 I guess. Mind you, these were overnight compilations, like on mainframes in the '60s. It is not intended to be any kind of production system, but nice to have around. /Wilm ------------------------------ Date: 21 Feb 2007 19:03:47 -0800 From: "n.rieck@sympatico.ca" Subject: Re: They are slowly coming home to the worlds ONLY virus free OS! Message-ID: <1172113427.090462.151580@v33g2000cwv.googlegroups.com> On Feb 21, 6:33 am, "n.ri...@sympatico.ca" wrote: > On Feb 21, 5:52 am, "n.ri...@sympatico.ca" > wrote:> wrote in message > > [...snip...] > > Oops! > Consolidated patch kits in the Solaris world are called "patch > clusters". > (is this what they mean when they say that Sun has clustering? :-) > OK so I downloaded the Solaris-8 patch cluster (a.k.a. consolidated distribution) which was 613 MB zipped. Then I copied it to the drive of a SUN-Blade-150 (650 MHz Ultra-SPARC-II), unzipped it, did an INIT S, then started the install. The install process took a slightly more than 4 hours! Something like this on OpenVMS AS-DS20e (833 MHz) would take less than 30 minutes and I wouldn't need to be in single user mode. Neil Rieck Kitchener/Waterloo/Cambridge, Ontario, Canada. http://www3.sympatico.ca/n.rieck/ ------------------------------ Date: 21 Feb 2007 12:46:20 -0800 From: roland@logikalsolutions.com Subject: Re: VT320 or 420 keypad codes Message-ID: <1172090780.316677.17020@j27g2000cwj.googlegroups.com> On Feb 20, 7:07 am, Thomas Dickey wrote: > rol...@logikalsolutions.com wrote: > > Hello all, > > I was poking around with the KONSOLE program which comes with SuSE > > Linux 10.2 AMD64 edition and found it does a fairly descent job of > > VT420 emulation, sans the keypad codes. I found the config file, and > > odd, but when I run vttest, it doesn't. > > It's a subset of vt100 with a few of the vt220 escape codes such as ECH. > > Although vt100 is a subset of vt220 is a subset of ... vt420, > it's not reasonable to say that konsole emulates vt420. > > ftp://invisible-island.net/vttest/ > > (The keypad codes for example, are a vt100 feature) > > > the comment, and the Qt header file. Someone just didn't have the > > scan codes to enter for translation. It looks like it is completely > > doable with just a few minutes of work...anyone have a link to the > > scan codes sent back by the keypad keys? I looked at VT100.NET and > > didn't see what I needed. > > The X-term stuff shipping with this version is pretty annoying. No > > cutting and pasting with mouse and no screen printing. KONSOLE seems > > to interpret the codes coming back to the screen correctly and > > correctly handle the function keys. It just needs the mapping for the > > keypad filled out. > > xterm supports ANSI color, VT220 emulation and UTF-8 > There's an faq at > http://invisible-island.net/xterm/xterm.faq.html > ftp://invisible-island.net/xterm/ > > > Thanks, > > Roland > > -- > Thomas E. Dickeyhttp://invisible-island.netftp://invisible-island.net Thank you for your input. The xterm which comes with every version of SuSE I have tried is quite pathetic in its VT support. Yes, I've pulled down all of the modifications to get the keys mapped. Where it becomes truly pathetic is in its handling of the right margin, no matter how you tweak it, it just can't handle it correctly. Another really problem with it is lack of support for screen printing. It has hidden menu options for it, but they are perpetually greyed out. The ultimate killer is its complete lack of support for cutting and pasting with a mouse. Being able to select a screen of data and paste it into an editor or word processor is crucial. I haven't lived without this capability since that Windows 3.1 application ran on top of DOS. Having a couple of decades with this functionality, I'm not going to give it up. No, I'm not going to try the PowerTerm thing. The Windows version of that product had a hokey licensing situation and purly frustrating functionality. After years of using both Reflections and KEAterm, I want that level of quality. Konsole handles the cutting and pasting correctly. There are some escape sequences it doesn't handle currently, yet it tosses up most FMS forms for me. It also handles the dynamic screen resizing correctly. If I can get the keyboard mapped, I'll look into how much effort it is to modify the source code to handle the balance of the escape sequences correctly. Thanks, Roland ------------------------------ End of INFO-VAX 2007.105 ************************