Newsgroups: bit.listserv.sas-l
Date:         Thu, 5 Nov 1992 09:30:20 PST
Reply-To:     Thomas M Skinner <Thomas_M_Skinner@CCM.HF.INTEL.COM>
From:         Thomas M Skinner <Thomas_M_Skinner@CCM.HF.INTEL.COM>
Subject:      Re: Usage Notes and ZAPS
Comments: To: SAS-L@uga.cc.uga.edu

Dear SAS-Lers,                                          Nov. 5, 1992
                                                        Folsom, California
                                                        Sunny, High of 75

An unknown lister writes:

>It is not clear what role Ms. Muller has at her site.  At our site, the
>official SAS consultant has systems programmer authority; she can apply zaps.
>She is not a heavy SAS user.  The users tend to discover problems, get zap
>numbers from SAS, and request installation of the zaps.
  >Please, assuming TSNEWS-L is a SAS tech support list, publish its full name
>so that I can subscribe.
  >Usage notes: Ugh!  A complete copy is useless--too big to pick up.
>-Since it
>is a SAS dataset, I picked only the obs for MVS and 6.07, then printed it in
>batch and routed that around my section.  It would be nice to run ZyIndex
>against it, but many things would be nice and there is so little time...

Reply:  Two SI administered lists are available for reporting problems and
zaps.  The first is a news facility to alert the users and SAS consultants of
problems.  The second is for use by users and consultants to report possible
bugs to SI.


TSNEWS-L is a listserv, however this list is maintained by SAS Institute, and
is run for the purpose of posting technical bulletins, such as bug and zap
announcements; new product and release information; etc.

Here's the address for TSNEWS-L

LISTSERV@VM.SAS.COM

The TSNEWS-L requires the following text in the body of the message:

SUBSCRIBE TSNEWS-L your name

This is to be typed in the leftmost column.  The subject should be SASTS-L
Subscription.

You cannot post on this list, and the mailing from SAS are infrequent, but you
should receive confirnmation within a day or so.


EMITS: This is the Electronic Mail Interface to Technical Support at SAS.
This facility was created for reporting bugs and other difficulties to  SAS.

Here's the address for EMITS:

SUPPORT@SAS.COM

The EMITS system is a little different:

This requires that "EMITS" be placed in the subject field.

Also, registration requires use of "./" commands and requires that you specify
the SAS site that you are at.


./register=your name here
./company=your company or institution
./site=xxxxxxxxxxxx <- Your site number (available in most logs)
./phone=(xxx) xxx-xxxx

./help

All of these line begin in column 1.  Fill in your name, phone number, etc.

The command "./help" will send you instructions on how to report problems to
SAS.  You'll also receive a registration number in the reply.

Your systems folks should be copied on all corespondence to and from SI. This
is very important if you receive a reply with a tracking number.  They may
need to know so that they can apply a ZAP if recommended.  It is often usefull
to capture and attach any log listings that may be useful to SI in debugging
or identifying the problem.

You indicate you are on MVS w/ release 6.07...
As far as using the USAGE NOTES:  There is a little known CLIST for executing
an AF facility known as "SUPPORT".  It seems most sites I've been to do not
make this publicly available - much to my dismay.  The system is much like
SAS/ASSIST but is part of base SAS.  It includes FSVIEW by keywords, and AF-
like search routines...USE IT!  Contact your systems folks for access.

Happy Listing!

Intel-Insider,
Tom Skinner

==============================================================================
T.M. Skinner                  Internet: Thomas_M_Skinner@ccm.hf.intel.com
Sr. SAS Technical Support         Mail: 1900 Prairie City Rd. MS FM1-102
Intel Corporation                       Folsom, CA 95630
==============================================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Subject: (no subject given)