Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!agate!ucbvax!decwrl!polyslo!vlsi3b15!vax1.cc.lehigh.edu!sei.cmu.edu!krvw From: CHESS@YKTVMV.BITNET (David M. Chess) Newsgroups: comp.virus Subject: re: the CHRISTMA EXEC on BITNET and VNET (IBM VM/CMS) Message-ID: <0002.8907251208.AA04381@ge.sei.cmu.edu> Date: 24 Jul 89 00:00:00 GMT Sender: Virus Discussion List Lines: 19 Approved: krvw@sei.cmu.edu While I was lucky enough to be on vacation when CHRISTMA hit VNET, my impression is that (press to the contrary), VNET handled it about like BITNET did: a few nodes shut down or cold started, but most just installed and ran some filters on RSCS and local spool. Lots of human and CPU time and net bandwidth wasted, but not a system-wide shutdown. This is just an unofficial impression, of course! As far as I know, it's no harder to get a file from BITNET to VNET now than it was before CHRISTMA; the person you want to talk to on the VNET side has to be authorized with the gateway. Exactly how an IBMer gets authorized for BITNET access varies with site/division/etc. I'm authorized, for instance, and I can be sent mail from BITNET just by sending in the normal way to CHESS at YKTVMV (let's not all try this just to be sure it works, of course! Hehe). DC IBM T. J. Watson Research Center