Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!ncsuvx!jck
From: jck@ncsuvx.ncsu.edu (Chuck Kesler)
Newsgroups: comp.sys.amiga
Subject: Re: ARexx postings in comp.lang.rexx
Message-ID: <3089@ncsuvx.ncsu.edu>
Date: 1 Jun 89 12:43:04 GMT
References: <8905312036.AA29886@terra.oscs.montana.edu>
Reply-To: jck@ncsuvx.ncsu.edu (Chuck Kesler)
Organization: NCSU Computing Center
Lines: 27

In article <8905312036.AA29886@terra.oscs.montana.edu> iphwk@TERRA.OSCS.MONTANA.EDU (Bill Kinnersley) writes:
>I believe your information about REXXLIST being intended solely for IBM
>mainframes is mistaken.  Here is the official description of REXXLIST
>taken from the file LISTSERV.GROUPS at BITNIC: 
>
>  List: REXXLIST@UCF1VM
>  Coordinator: LISTSERV Editor (EDITOR@UCF1VM)
>  Peers: UGA
>    THE REXX (STANDARDS) DIGEST: Discussion group for the REXX language,
>    with an emphasis on coding standards.
>

Well, I'm not sure who thought up that, but I'm basing my statement on 
practice.  Just about every posting to Rexxlist is VM specific.  Also,
every header comes with a From: name of 'VM/SP Rexx Discussion List' or
some such (can't check exactly because our machine is down right now).  
The key there is the VM/SP.

This is probably a problem that the people gatewaying Bitnet mailing lists
and Usenet news should deal with.  After all, if most people who read
comp.lang.rexx are using Unix boxes, then they probably wouldn't care to 
read about VM specific Rexx issues.  The gateway between comp.lang.rexx
and Rexxlist is probably inappropriate.  It would probably be better
gatewayed with a comp.lang.rexx.vm.  But then, the gateway doesn't work
all of the time, so maybe the that point is moot.

-Chuck