HDTenEightyP/NetNews huggingface dataset:
Newsgroups: bit.listserv.vm-util
Date:         Fri, 11 Dec 1992 21:50:20 EST
From:         Paul Russell <PRUSSELL@IUBVM.BITNET>
Subject:      Re: XXENCODE and XXDECODE
              11 Dec 1992 18:14:25 GMT from <pg@SANITAS.STORTEK.COM>

<PREACH ON>
This is supposed to be a technical forum for questions and answers about
VM utilities/applications/etc, not a forum for flame wars between the
bigotted proponents of various assorted operating systems.  If you don't
have a legitimate question, or a legitimate answer to same, please have
the common sense and courtesy not to waste my time with your "my os is
better than your os" drivel.  No one os does everything well, and anyone
who contends that theirs does is either a fool or a charlatan.
<PREACH OFF>
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: University at Albany Computing Services
X-Acknowledge-To: <BEC@ALBANY>
Newsgroups: bit.listserv.vm-util
Date:         Mon, 14 Dec 1992 13:36:18 EST
From:         Ben Chi <BEC@ALBANY.BITNET>
Subject:      Re: Placing Data from seperate files into 1 BY COLUMN !
              14 Dec 1992 16:41:34 GMT from <SYSDMCKE@VM.UWP.EDU>

On Mon, 14 Dec 1992 16:41:34 GMT <SYSDMCKE@VM.UWP.EDU> said:
>  I am trying to piece together 3 seperate files with XEDIT.  The problem,
>I would like the added by column, rather than by line.
>Does anyone know an easy way to do this ?

We have here a macro, OVLY XEDIT, whose help text says:

   OVLY facilitates the combining of two files in a side-by-side manner.
   Specifically, it overlays the file currently being edited, starting at
   the current line and at a specified column with the contents of all or
   a portion of another file.  Either a specified range of columns can be
   overlaid, or the entire remainder of each line starting at the
   specified colunm (specify "*").  Either a specified number of lines can
   be overlaid, or the entire remainder of the current file (specify "*").

   Regarding the file containing the overlay text, either the entire file
   or only that portion starting at a specified line and/or that portion
   starting at a specified column and ending at a specified column can be
   used.

   Because of the large number of parameters required, a menu is presented
   for their entry.  The menu is redisplayed with diagnostic messages if
   any parameters are in error.

To get a copy, TELL LISTSERV AT ALBANY GET OVLY XEDIT FSV .
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.vm-util
Date:         Mon, 14 Dec 1992 12:55:00 EST
From:         Bob Fowles 814-865-4774 <RBF@PSUVM.BITNET>
Subject:      Re: Placing Data from seperate files into 1 BY COLUMN !

1. You might be able to get them all in one file and then use the xedit
   MERGE command.

2. You can do it in a pipeline using SPEC and OVERLAY.

   Bob Fowles, Center for Academic Computing, Penn State
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sos-data
Date:         Tue, 15 Dec 1992 16:34:32 EST
Reply-To:     TIF@NIHCU.BITNET
From:         TIF@NIHCU.BITNET
Subject:      Unemployment data by State

December 15, 1992

Dear Jim:

I am responding to your request of December 7, 1992 regarding the
availability of unemployment rates by state from 1940 to the
present.

According to a description provided to the National Archives by
the agency, the Bureau of Labor Statistics, Office of Survey
Processing, Division of Federal-State Monthly Surveys, provides
the Division of Local Area Unemployment Statistics (LAUS) with
data processing services for the production of official State and
sub-state LAUS estimates as well as for benchmarked annual LAUS
estimates or intermittant estimates as required.  The office
maintains the LAUS Official Estimates Data Base.  The data base
is used in the production of the various publications in hard
copy or microfiche formats for all States, District of Columbia,
Puerto Rico, and some 5,000 sub-state areas, as well as to
furnish LAUS official time series estimates from 1976 to date to
the LABSTAT data base.

Although the LAUS, as well as a number of other data series, were
authorized by an act of July 7, 1930 (29 USC 2) mandating BLS to
prepare "full and complete statistics of the volume and changes
in employment ...," we do not know from the information submitted
by the Bureau whether or not the data are maintained back through
1930.

The LAUS records are currently in the custody of the Bureau of
Labor Statistics.  If you are interested in these data, please
contact Karen Nunley, Bureau of Labor Statistics, Division of
Administrative Services, Room 2057, 441 G Street, NW, Washington,
DC  20212.  The telephone number is (202) 523-1468.  The 'Federal
Data Base Finder' by Matthew Lesko (1990, Kensington MD:
Information USA) lists Gloria Green (202) 523-1959 as a contact
for questions regarding the subject matter of these data.


Sincerely,



THEODORE J. HULL
Archives Specialist, Archival Services Branch
Center for Electronic Records

(202) 501-5579
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sos-data
Date:         Tue, 15 Dec 1992 16:31:36 EST
Reply-To:     TIF@NIHCU.BITNET
From:         TIF@NIHCU.BITNET
Subject: Re: NLRB Data

December 15, 1992

Dear Ms. Czarnocki:

I am responding to your inquiry of December 15, 1992 regarding
the availability of the Records of the National Labor Relations
Board (Record Group 25) posted on SOS-DATA.  You are specifically
interested in information about union certification/
decertification practices.

Under the National Labor Relations Act of 1935 (29 U.S.C. 167),
and later amendments, NLRB has two principal functions:
preventing and remedying unfair labor practives by employers and
labor organizations or their agents, and conducting secret ballot
elections among employees in appropriate collective bargaining
units to determine whether or not they desire to be represented
by a labor organization in bargaining with their employers about
their wages, hours, and working conditions.  The agency also
conducts secret ballot elections among employees who have been
 by a union-security agreement to determine whether or not
agreements.  If the latter two responsibilities are what you are
referring to when you request information about union
certification/decertification practices, then textual (paper)
records at the National Archives or at NLRB may be useful to your
research.

The primary reference units for the records of the NLRB at the
National Archives are the Civil Reference Branch (NNRC) and the
Suitland Reference Branch (NNRR), Textual Reference Division
(NNR).  These units can be contacted by writing them at the
National Archives, Washington DC 20408.  The telephone number for
NNRC is (202) 501-5425.  The telephone number for NNRR is (301)
763-7410.

You may wish to contact the NLRB directly with your question.
For further information, contact the Information Division,
National Labor Relations Board, 1717 Pennsylvania Avenue, NW,
Washington, DC 20570.  The telephone number is (202) 632-4950.
As NLRB is a regionally disbursed agency, with 33 field offices
across the United States, you may wish to contact the closest
field office for information.  I believe that would be the office
in Albany, New York.  The address is Clinton Ave. at N. Pearl
St., Albany, NY 12207.  The telephone number is (518) 472-2215.

I hope this information is useful.

Sincerely,


THEODORE J. HULL
Archives Specialist, Archival Services Branch
Center for Electronic Records
(202) 501-5579
From: BFU@NIHCU.BITNET (Roger Burns)
Newsgroups: bit.listserv.sos-data
Subject: Re: Unemployment data by State
Date: 16 Dec 92 13:58:22 GMT
Reply-To: Roger Burns <BFU@NIHCU.BITNET>
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU

> The LAUS records are currently in the custody of the Bureau of
> Labor Statistics.  If you are interested in these data, please
> contact Karen Nunley, Bureau of Labor Statistics, Division of
> Administrative Services, Room 2057, 441 G Street, NW, Washington,
> DC  20212.  The telephone number is (202) 523-1468.  The 'Federal
> Data Base Finder' by Matthew Lesko (1990, Kensington MD:
> Information USA) lists Gloria Green (202) 523-1959 as a contact
> for questions regarding the subject matter of these data.

The Bureau of Labor Statistics has moved to another building.
The Division of Administrative Services can be reached at Room 2645,
2 Massachusetts Avenue, NE, Washington, DC 20212, telephone (202) 606-6007.
The LAUS office can be reached at Room 4675 at the same address,
telephone (202) 606-6376.


-- Roger Burns     Bureau of Labor Statistics     bfu@cu.nih.gov
                      Washington, DC 20212        bfu@nihcu.bitnet
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sos-data
Date:         Mon, 14 Dec 1992 17:04:40 EST
Reply-To:     Susan Czarnocki <IN02@MUSICB.MCGILL.CA>
From:         Susan Czarnocki <IN02@MUSICB.MCGILL.CA>
Subject:      NLRB Data

We have a researcher looking for recent National Labor Relations
Board data -- particularly union certification/de-certification
information.  Could anyone tell us where we could acquire such
data?

Thanks.
McGill University       Montreal        Canada
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: sos-data@UNCVM1.BITNET
X-VMS-To: IN%"sos-data@uncvm1"
X-VMS-Cc: CAMPBELLD
Newsgroups: bit.listserv.sos-data
Date:         Tue, 15 Dec 1992 16:46:00 CST
Reply-To:     RICHARD JENSEN <CAMPBELLD@APSU.BITNET>
From:         RICHARD JENSEN <CAMPBELLD@APSU.BITNET>
Subject:      unemployment data by states before 1976

    Unemployment data by states before 1976 is not conveniently
    available, but (depending on the validity needed) can be
    estimated.
    1. See Charles F Schwartz and Robert Graham, Personal Income by
       States since 1929 (supplement to Survey of Current Business,
       1956, reprinted by Greenwood)
 A. The usual source of unemployment estimates since 1940 is the
    monthly Current Population Survey. It uses a national sample and
    does not provide state or regional estimates.
 B. The decennial census has state breakdowns (but its national
    totals differ is 20% lower than A.)
 C. The Social Security Yearbook (and Social Security Bulletin)
    reports annual state data from Unemployment Insurance claims.
    This may be the best source, but see "The Measurement And
    Behavior of Unemployment" (Princeton UP, 1957), esp chapters by
    Parnes and Levine.
 D. The Labor Dept's Bureau of Economic Security for many years
    issued (mimeograph) a bimonthly labor market report, "Labor
    Market Developments in Major Areas" series ES-219, for 150
    metropolitan area labor markets. Estimates based on UI claims.
    These estimates can be aggregated to states (they cover 70% of
    nonfarm employment)
 E. I vaguely recall that William Bowen & Finegan, The Economics of
    Labor Force Participation (Princeton 1969) used state estimates
    --
    Richard Jensen, U of Illinois Chicago
    campbelld@apsu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.l-vmctr
Date:         Tue, 15 Dec 1992 08:15:33 EST
From:         Ron Wigmore <SYST8103@RYEVM.RYERSON.CA>
Subject:      Running A Merge/Purge

Our last Merge/Purge was done about three years ago.  We will be running
one this weekend, and I am not sure how to handle bad tapes.  Hopefully
someone out there has just run a Merge/Purge and so can readily tell me
how to correctly process bad tapes.

Some tapes are 'bad' because of incorrect dataset counts, etc., but most
simply get I/O errors when VMBACKUP trys to read the tape.  I know what
some of the volsers are, but there are probably many others among the
700 tapes that will be Merge/Purged.

Does anyone have any tips on how to minimize the length of time it will
take to do the Merge/Purge?  Given that when VMAMPU hits a bad tape, the
run will abend, will using the "FORCE" option enable the rest of the tape(s)
to be processed or are all of the files after that tape be lost?

All suggestions welcome!

Ron,,,
Newsgroups: bit.listserv.l-vmctr
From: xmas@uxa.ecn.bgu.edu (Mark A. Stevens)
Subject: Re: Running A Merge/Purge
Organization: Educational Computing Network
Date: Tue, 15 Dec 1992 16:18:41 GMT

In article <921215.081533.EST.SYST8103@RyeVm.Ryerson.Ca> Ron Wigmore <SYST8103@RYEVM.RYERSON.CA> writes:
>...
>Some tapes are 'bad' because of incorrect dataset counts, etc., but most
>simply get I/O errors when VMBACKUP trys to read the tape.  I know what
>some of the volsers are, but there are probably many others among the
>700 tapes that will be Merge/Purged.

If you *KNOW* they are bad, do you have twins so you can mark the bad
ones in the VMARCHIVE database?

>Does anyone have any tips on how to minimize the length of time it will
>take to do the Merge/Purge?  Given that when VMAMPU hits a bad tape, the
>run will abend, will using the "FORCE" option enable the rest of the tape(s)
>to be processed or are all of the files after that tape be lost?

VMBACKUP has a tape scanning utility that looks at the tapes and builds a
report of what it finds (I've forgotten the name of it of course.)  You
could use it to scan all tapes to identify the bad ones (tape errors) and
the reports would help with identifying those which are missing DSS's
when compared with VMARCHIVE's report on DSS's and volsers (again I
forgot the name, lot of good I am.)  
-- 
Mark A. Stevens                           Phone:    708-534-0200
Systems Programmer                        Internet: xmas@uxa.ecn.bgu.edu
Educational Computing Network             BITNET:   XMAS@ECNUXA.BITNET
Board of Governors Universities           VMSHARE:  ECE/MARK
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.l-vmctr
Date:         Wed, 16 Dec 1992 11:02:12 EST
From:         Ron Wigmore <SYST8103@RYEVM.RYERSON.CA>
Subject:      Exec Error In VMBTCPY And Merge/Purge And Bad Tapes

I just used VMBTCPY for the very first time and I am getting a
REXX error (Invalid call to routine, line 230).  RXTAPIO seems to
be doing something that REXX doesn't like.  Should I be linked to
another disk aside from VMBACKUP's 192?

Also, the manual does not explain how to process/delete files during
a Merge/Purge from tapes which get I/O errors.  Does anyone have any
suggestions as to how I could delete the files from the database that
are on the tapes (16 tapes in total!) so that our users won't get the
"OFU" status when they query their files?

I think I need to do a normal Merge/Purge, skipping the BASE tapes
that give the I/O errors, and then run another Merge/Purge using the
DBONLY option after ensuring all files on the bad tapes have been purged.
I am hoping that there is an easier way since several thousand files
are involved.

We're are running VMBACKUP 5.2 on a VM/HPO Release 5 system.

Ron,,,
From: MAINT2@ERS.BITNET (Ken Koester)
Newsgroups: bit.listserv.l-vmctr
Subject: Re: Exec Error In VMBTCPY And Merge/Purge And Bad Tapes
Date: 16 Dec 92 17:42:45 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
              16 Dec 1992 11:02:12 EST from <SYST8103@RYEVM.RYER SON.CA>

On Wed, 16 Dec 1992 11:02:12 EST Ron Wigmore said:
>
>Also, the manual does not explain how to process/delete files during
>a Merge/Purge from tapes which get I/O errors.  Does anyone have any
>suggestions as to how I could delete the files from the database that
>are on the tapes (16 tapes in total!) so that our users won't get the
>"OFU" status when they query their files?
>
Mark the tapes as one of the flavors of damaged, assuming you've got a good
twin (or, if the twin is giving problems, mark it as damaged.) The MP should
work just fine.  There should be no problem with cleaning out expired files.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.l-vmctr
Date:         Wed, 16 Dec 1992 11:59:50 EST
From:         Ron Wigmore <SYST8103@RYEVM.RYERSON.CA>
Subject: Oops! Ignore My Last Question

Oops, I read the Merge/Purge section several times, but never seemed
to clue in what the PURGE option did.  You can all ignore my last
message.

Sorry for any inconvenience ...

Ron,,,
Newsgroups: bit.listserv.xmailer
From: schafer@is.rice.edu (Richard Alan Schafer)
Subject: Re:      Re: MAILER 2.10 and missing pieces...
Organization: Rice University
Date: Fri, 11 Dec 1992 21:47:42 GMT

In article <XMAILER%92121110573006@BITNIC.EDUCOM.EDU>,         Andy Hooper
<HOOPER@QUCDN.QUEENSU.CA> writes:

|> DMSDDL, the module that does the NETDATA work for SENDFILE, has an XEDIT
|> option to read directly from an XEDIT buffer. When DMSDDL was legitimized
|> in VM/ESA as the NETDATA command, it retained the XEDIT option.

Yes, I know.  I'm already using that for *reading* files coming in as netdata,
so using it for output will be no problem.  I'll probably make the default
still be punch, and require the site to change that if they are running a
mailer which can handle netdata.

Just to be sure I understand: the entire file (BSMTP envelope and all) is put
into netdata, right?  (Doing the BSMTP envelope around a NETDATA file would
be more difficult.)

-- 
Richard
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.xmailer
Date:         Sat, 19 Dec 1992 00:32:02 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: Nicknames
Comments: To: Multiple Recipients of <XMAILER@FINHUTC.BITNET>
              18 Dec 1992 15:29:20 EST from The Crosswell Mailer List
              <XMAILER@FINHUTC>

On Fri, 18 Dec 1992 15:29:20 EST Mark Bodenstein <MAB@CORNELLC> said:

>The VAX will  be going away, and I'd  like to be able to do  this on VM,
>for both BSMTP format mail and unwrapped RFC-822 format mail.
>
>Is this doable in Mailer 2.10? Is it doable in LMAIL?

With LMail you'd add a line in HOST OVERRIDE saying:

nodeid INTERBIT SMTP BSMTP NETDATA H=hostname

Note  however that  it is  not guaranteed  this will  work with  straight
RFC822 mail. LMail performs validity checking  for RFC822 mail, so if Joe
sends  mail saying  'From: Jack'  this  will be  rejected. LMail  doesn't
support the  old BITNET 2  input protocol with the  hidden '*Deliver-To:'
header (or  whatever the name  was, it  was a long  time ago) so  it also
rejects such mail  when coming from a "trusted" mailer;  if it didn't, it
would be delivering to everyone rather than just the intended recipients,
and you might even end up with a loop.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Virginia Polytechnic Institute
Newsgroups: bit.listserv.xmailer
Date:         Fri, 11 Dec 1992 16:40:26 EST
From:         Valdis Kletnieks <VALDIS@VTVM1.CC.VT.EDU>
Subject:      Whoops. Abend in MAILER 2.10

VM/XA 2.1, CMS 5.6

After making a small change to the VTVM1 MTPLATE file and re-running MG,
I copied it over to the MAILER 193 and then did the following:

TELL MAILER CMS ACC 193 C/A
TELL MAILER STOP

Mailer proceeded to restart, but after startup geve the following
messages:

12/11/92 16:17:02 MAILER069I Initializing trace table
12/11/92 16:17:02 MAILER011I 01250705 bytes of stack space.
DMSIPT141T Specification exception occurred at 024F47 in routine MAILER

This last repeated some 100,000 times before I did a FORCE/XAUTOLOG,
after which it came up and ran fine.

Anybody have an idea?  Was something mis-initialized causing the STOP
code to not work (similar to the problem 2.08 had with RELOAD)?

                                  Valdis Kletnieks
                                  Computer Systems Engineer
                                  Virginia Polytechnic Institute
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.xmailer
Date:         Fri, 11 Dec 1992 15:43:28 -0500
From:         jwagner@PRINCETON.EDU
Subject:      Re: MAILER 2.10 and missing pieces...
Comments: To: Crosswell Mailer <XMAILER@uga.cc.uga.edu>
              11 Dec 92 10:50:10 -0500. <9212111601.AA12503@Princeton.EDU>

> DMSDDL, the module that does the NETDATA work for SENDFILE, has an XEDIT
> option to read directly from an XEDIT buffer. When DMSDDL was legitimized
> in VM/ESA as the NETDATA command, it retained the XEDIT option.
>
> Andy Hooper

I wanted to do minimal damage to the current logic.  The BSMTP is created on
the fly (while punching).  The XEDIT option could be used if the BSMTP was
added to the file before punching, but it would have to be removed before
outbound logging takes place.  My code was just to verify I could send long
lines, I'm leaving the real work up to Richard.

   John
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.xmailer
Date:         Fri, 11 Dec 1992 15:41:14 -0500
From:         jwagner@PRINCETON.EDU
Subject:      Re: MAILER 2.10 and missing pieces...
Comments: To: Crosswell Mailer <XMAILER@uga.cc.uga.edu>
              10 Dec 92 22:41:13 +0200. <9212102052.AA28558@Princeton.EDU>

> BTW, am I correct to assume that the netdata mail will have the appropriate
> flag set in the file header that indicates "note" format so that
DMSDDL a.k.a.
> RECEIVE will read it into a NOTEBOOK?
>
> - Lawrence

The note bit is not set.  I don't do this so it is possible to recognize IBM
NOTEs in the reader with the RDR command.

  John
Newsgroups: bit.listserv.xmailer
From: schafer@is.rice.edu (Richard Alan Schafer)
Subject: Re:      Re: MAILER 2.10 and missing pieces...
Organization: Rice University
Date: Fri, 11 Dec 1992 21:18:50 GMT

In article <XMAILER%92121021491741@HEARN>,         "Lawrence S. Kalman"
<VSLAWR@WEIZMANN.WEIZMANN.AC.IL> writes:
>>On Thu, 10 Dec 92 14:11:56 -0500 <jwagner@PRINCETON.EDU> said:
>>An operational problem still remains with the NETDATA support and that is
the
>>question of how should local delivery by handled?  Currently it is an all or
>>nothing operation (either all in punch or all in NETDATA).  My intention is
>>to create some new exits (localp and localn) that can be used in the
SPECIALS
>>table to allow you to select a default delivery type and selectively deliver
>>the other format when required.  Does this sound like it meets your needs?
> 
>This is high on our list of requirements.  We have several antiquated servers
>which read mail via "EXECIO * CARD" and I didn't want to have to make them
>smarter as a necessary prerequisite to enabling the netdata feature.

This would be important to many people, I think.  There are many sites where
people will use other facilities in addition to RiceMail (as hard as that 
might be for me to accept :-) from time to time to handle incoming mail files.

>BTW, am I correct to assume that the netdata mail will have the appropriate
>flag set in the file header that indicates "note" format so that DMSDDL
a.k.a.
>RECEIVE will read it into a NOTEBOOK?

I almost hope this *isn't* true, although it's probably the right thing to do.
If only read NOTE files came that way, I might be able to do a better job of
dealing with the brain-dead IBM note header format that won't occasionally
confuse them with RFC822 headers which happen to have the word "at" in just
the wrong place.  Being sure that the files come with a filetype of something
other than NOTE would help.

-- 
Richard
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.xmailer
Date:         Tue, 15 Dec 1992 16:59:00 -0500
From:         jwagner@PRINCETON.EDU
Subject:      Re: MAILER 2.10 and missing pieces...
Comments: To: Crosswell Mailer <XMAILER@uga.cc.uga.edu>
              13 Dec 92 10:28:01 +0200. <9212141526.AA20135@Princeton.EDU>

> Then let me ask a question instead of trying to answer it.  We have a server
> which currently distinguishes between mail and other files by the simple
> technique of issuing RECEIVE = JUNK FILE A (NOTEBOOK ALL.  JUNK FILE and ALL
> NOTEBOOK do not exist before the command is issued.  Either ALL NOTEBOOK or
> JUNK FILE will be created by the RECEIVE  command depending on whether or not
> the file is mail.  This is because punch format files are recognized
as mail if
> the file type is either MAIL or NOTE, and netdata files are recognized based
> on the note flag in header record INMR02.   As I now understand it, a netdata
> mail file received from XMailer will break this server.  Do I have any
> alternative to modifying the logic of the server?

Adding the same check for filetype of MAIL for NETDATA format should fix your
server.  RECECIVE should put the NETDATA formatted files in JUNK FILE.

  John
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU