Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site osu-eddie.UUCP
Path: utzoo!watmath!clyde!cbosgd!osu-eddie!sutter
From: sutter@osu-eddie.UUCP
Newsgroups: net.news.group
Subject: net.vms - big YES
Message-ID: <612@osu-eddie.UUCP>
Date: Mon, 16-Sep-85 15:19:33 EDT
Article-I.D.: osu-eddi.612
Posted: Mon Sep 16 15:19:33 1985
Date-Received: Tue, 17-Sep-85 05:53:53 EDT
Sender: sutter@osu-eddie.UUCP
Organization: OSU Instruction & Research Computer Center
Lines: 27

From: sutter (Bob Sutterfield)

I am a regular reader of fa.info-vax, and an infrequent poster.  It is
frequently of some considerable benefit to me.  For instance, when a new
release of VMS comes out, I watch the transients die down before I install
it myself (eg: math lib bugs in 4.2, with subsequent fix info).  Although I
can reasonably easily post to it, and obviously very easily read it, I would
prefer faster turnaround than having my postings go to a CSnet-ARPAnet
gateway, then wait for the mail to reach info-vax@wherever (I can never
remember where), then wait for the one-way ARPAnet-to-Usenet gateway to barf
the mail onto the Usenet, then wait for Usenet mail to propagate it back to
me so that I know if the original posting went out OK.  If I am anxiously
awaiting a response, it can be @i(quite) frustrating.

So, I would vote heartily YES in favor of a net.vms group.  Even better if
it were really two-way gatewayed with info-vax and/or info-vms.  I think
that several of the other Ohio State University VMS site managers feel the
same way, but don't necessarily read net.news.group as much as fa.info-vax.
-- 
Human:	   Bob Sutterfield
	   Facilities Management Division
	   The Ohio State University Instruction & Research Computer Center
Workplace: Ohio Cooperative Extension Service, Computer Management Group
           OCES VAX System Manager/Programmer (VMS)
Mail:	   ...cbosgd!osu-eddie!sutter.UUCP
  or:	   sutter@ohio-state.CSNET
MaBell:	   (614) 422 - 9034