Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!sharkey!cfctech!teemc!glc!jeffpc!jeff From: jeff@jeffpc.eds.com (Jeff Trim) Newsgroups: news.groups Subject: VMSNET.COBOL ( Re: Call for Discussion: alt.cobol) Keywords: Give them to VMSNET Message-ID: <5@jeffpc.eds.com> Date: 3 Dec 89 06:22:15 GMT References: <5301@garfield.MUN.EDU> <1989Nov25.193310.20967@world.std.com> <43327@bu-cs.BU.EDU> Reply-To: jeff@jeffpc.UUCP (Jeff Trim) Organization: jeffpc.eds.com - Rochester Hills, Michigan - U.S.A. Lines: 28 In article <43327@bu-cs.BU.EDU> ckd@bu-pub.bu.edu (Christopher Davis) writes: >I... I.... I've .... um.... programmed.... in.... well... um.... COBOL. > >[Well, there goes that engagement to Barry's daughter. :-] > >Yeah, I'd read alt.cobol (or comp.lang.cobol). I'd even post to it, though >I can't claim any sort of divine knowledge of the darned thing. Ummm to be honest I didn't like the idea of VMSNET when it was first proposed but you know maybe they can take over some of these groups that don't work under UNIX (ala alt.cobol) and move them to: vmsnet.cobol COBOL is typically found on VMS-ish OS's anyway and since the heirarchy is starting out they can easily go over to 'vmsnet' - that way the readership will grow and 'alt' will get smaller. Folks on VMS talk alot about COBOL so it could be a good match. What does everyone else think? Might even add some creedence to the 'vmsnet' heirarchy. - Jeff -- INET: jeff@jeffpc.eds.com UUCP: [ uunet, teemc ]!{edsews, glc}!jeffpc!jeff Disclaimer: Don't blame anyone else but me -- I said it. Brought to you by Super Global Mega Corp .com