Conference 7.286::digital

    John thats partly a good idea.  But, the person needs to be taught
    the dec culture and how to use the information.
    example is askenet notesfile.  If the person just went in there
    and asked the question [i've done it before when all other sources
    exhasted], an answer will come out.
    There are notes edequate files.  There's the Dick Best list for
    listing product managers and responcible engineers.
    Maybe jsut a leaflet pointing to the places that have this information.
    Then maybe a short lesson on how to ask for information.
    Example is when I have to go a a witch hunt for equipement.  I may
    call a group and ask if they have it.  If I stopped at NO, then
    it would take forever to get the equipment.  But, if I also ask
    them if they knew someone I should contact, I immediately expand
    my data base on who to call.  If they don't know,  I ask one more
    question....Who do you think I could call that would know?
    {I'm a pain when I'm out hunting..]
    
    Nowq there's the Sales update to tell about products,
    The Digital Technical Journal that comes out periodically explaining
    technology and products,
    The Internal Guide to Digital Oganizations EL-ENGS-OM
    this book deals with Digital philosophy, resources, and processes,
    written specifically for new people, but a good guide for oldies.
    All managers and their funtions are listed alone with their phone
    numbers and mailstops.  I can't imagine not haveing this book.
    There's the Dick Best list for product owners/supporters/managers,etc.
    There's the Engineering newsletter.
    need more?
    But, the person needs to know or ask for it.  I guess, I blame Mr.
    Dot Zero's manager for not providing the *initial* orientation.
    ed
    
    

     re .0,.1:

     I agree with .0 -- while .1 is right about there being bunches of
     different manuals, etc. around, they're not the most effective things.
     You shouldn't need to carry a "survival guide" that's more than a
     single looseleaf.

     Funny you should ask. How does something like...

	Chapter 1	Why Survival?	(Introduction)
	Chapter 2	Easynotes	(Using, plus getting your own list)
	Chapter 3	Corporate VTX	(Using, plus list, plus setting up
					 your own access)
	Chapter 4	Internal Kits and Licenses
					(How to get kits directory, etc.)
	Chapter 5	ELF		(Using, plus setting up your own)
	Chapter 6	ADS		(Automatic Distribution, plus list
					 of all publication codes and
					 VMS/Ultrix/MS-Dos docset codes)
	Chapter 7	SSDs, Cover Letters and Forms
					(Finding and using Software Services
					 Descriptions)
	Chapter 8	Your Own Node	(Other basics about setting up your
					 own node -- picking a name, filling
					 out forms, setting up printer queues
					 to LPS40s, etc.)
	Chapter 9	The Phone	(Corporate Hotline List)
	Chapter 10	Using DOCUMENT	(Get started with DOCUMENT with less
					 than 10 pages of documentation to
					 have to read)
	Appendix A	Easynotes Conferences
					(EASYNOTES.LIS listing)
	Appendix B	EASYnet Kits	(KITSDIR.DOC listing)
	Appendix C	Internal PAKs	(SIXPAK (VTX internal PAK distribution
					 application) user's guide)

     Well, I just finished the first revision of one of these for our area.
     Curiously enough, it's titled

	"The Digital SWS Field Survival Guide"

     I'm making some fixes in the current revision. If there is sufficient
     interest, I'll post a pointer to it?

     /peters

    I've been in SWS for 7 years and could still use a copy of 
    your 'survival guide'...

Excellent outline.  May I suggest another chapter on acronyms?  There is, I
believe, a dictinary available, though it's been my experience that with
each new job a new list has to be developed.

Betty

    re: .2
    
    PLEASE post a pointer!  I'd like to get this included in our District
    NEWS function as a permanent feature!
    
    Thanks!
    
    -- Russ

RE: .1

>    There are notes edequate files.  There's the Dick Best list for
>    listing product managers and responcible engineers.
    
>    There's the Dick Best list for product owners/supporters/managers,etc.
>    There's the Engineering newsletter.
    
Where do you get these?

John

RE: .6, .7 
    
    >> Where do you get these?
    
    
The "Option/Module List" is a book that contains information
about Digital's currently active option-level, systems-level,
and module-level parts.  This list is maintained by Dick Best
and the Chief Engineer's Office (CEO) and is often referred to
as the "Dick Best List".  The list includes software, hardware,
and services part numbers.    

The information, which is listed by part number, includes:
	- the part description
	- what higher assembly the part is used on
	- the product technology category
	- the names of the following responsible individuals:
		* Engineering Manager
		* Design Engineer
		* Product Manager
		* Maintainability Engineer (that is, CSSE rep)
		* Manufacturing Engineer
	- the major supplier (that is, the manufacturing location)
	- the "status" of the part (such as, in design, in volume,
	  maintenance-only, etc).

The generally useful version of the report is called the Edited List.
The Edited list contains parts that are in design, or being built, or
that are obsolete but still maintained.  This report is DIGITAL 
CONFIDENTIAL, which means that it is distributed only to those employees
who have a need to know the information in their jobs.

Parts that are in "conceptual design phase", in "obsolete phase", or
which have been specifically set hidden are NOT included in the Edited
List.  These are available in the Complete List, however.  Note that
the complete list is DIGITAL RESTRICTED DISTRIBUTION, and the majority
of employees do not have access to it.

The edited list comprises two parts: the Hardware Section and the Software
Section.  Employees may request either, or both.

A quarterly subscription fee will be cross-charged to your cost center.
The rates are as follows:

	Edited List		$350/quarter
	Edited List - Hardware	$200/quarter
	Edited List - Software	$200/quarter
	Microfiche/Full Edited	$300/quarter
           
The full Edited List is also available on CD-ROM, at $250/quarter.
This CDROM contains all the software required to access the on-line
version of the list.  You must have an RRD50 CD Reader or equivalent.

To subscribe, send mail to MILPND::CEODIST.  Give your name, badge number,
mailstop, and your job responsibility.  Please obtain approval from
your cost center manager before sending in your request.

Note that the Microfiche is available at all the Reprographics centers
that we know of, and the hardcopy is available in most site libraries.

Requests for further information can be sent to David Crowley at
MILPND::CROWLEY.
    
The ENGINEERING NEWSLETTER is also published by the Chief Engineer's
Office.   Send name and mailstop to MILPND::MAGAZU.    

Every employee who needs to interact with Engineering should have
a copy of the book called,

	1988-89 INTERNAL GUIDE TO DIGITAL ORGANIZATIONS.

This book contains a description of almost every engineering group
in the company, and includes the name and phone number of the manager.

In recent years, the scope of the book has expanded beyond Engineering
(it used to be called "...Guide to Engineering"), but it is not
quite comprehensive yet.  Show your copy to your boss, and have
him/her submit a group description for next year's issue.

It can be ordered from Standards and Methods in Chelmsford via
one of the following methods:
	- in VTX, find "SMC" and order it on-line.
	- email to JOKUR::SMC (give name/badge/loc/cc)
	- snailmail to CTS1-2/D4
	- DTN: 287-3724

>      <<< Note 817.2 by SVBEV::VECRUMBA "Infinitely deep bag of tricks" >>>
>                       -< A "survival guide", Hmmmm... >-


 >     Well, I just finished the first revision of one of these for our area.
 >    Curiously enough, it's titled

 >	"The Digital SWS Field Survival Guide"

 Sounds good. There's a similar one for Engineering. It's called the

	"Software Engineering manaul"

 Here's the contents of the '88 edition which are probably relevent to 
 non Engineering groups too:

 Chapter 1	Perspectives on Digital  (philosophy, culture, directions)
 Chapter 2	Digital Organisations
 Chapter 3	Software Development tools
 Chapter 4	Overview of the Phase review process
 Chapter 5	Project management
   ...    (various Engineering chapters about coding and Phase review process)
 Appendix G	Resources information (documentation and notes conferences)

	Craig

>              <<< Note 817.0 by KYOA::MIANO "Who are the METS?" >>>
>            -< A source of information for New [Field] Employees? >-

A great idea. A similar concept is being debated in the GRADUATES notes 
conference. Interesting how two people can have the same idea in different 
places at nearly the same time. This same topic was brought up in the 
Graduates conf only 6 days before the topic here was started ....

Craig.

 p.s. The IT conf I refer to is the conference for Industrial Trainees on
      placement within Digital UK.

             <<< VOGON::DISK$JB:[NOTES$LIBRARY]GRADUATES.NOTE;5 >>>
                     -< The Official Graduates Conference >-
================================================================================
Note 56.0              Alternate Prospectus for new Grads.             2 replies
JANUS::BHARRISON "Partly Animal ...."              37 lines  Thu 11-May-89 11:39
--------------------------------------------------------------------------------
    
    After a meating with Ken Chamberlain, Dave Brash and a few of the
    more recent graduates, it has been decided to produce an alternate
    'prospectus' for this years incoming graduates. This is to be part
    of their induction procedure.
    
    What is to be in this document, is the useful info about digital
    and Reading that is only learned by bitter experience.

    ....

    Brynn.   (JANUS::BHARRISON)

================================================================================
Note 56.1              Alternate Prospectus for new Grads.                1 of 2
MARVIN::COCKBURN "Made in Scotland"                55 lines  Thu 11-May-89 12:29
--------------------------------------------------------------------------------
>           <<< Note 56.0 by JANUS::BHARRISON "Partly Animal ...." >>>
>                    -< Alternate Prospectus for new Grads. >-

Hi Brynn,
	This sounds like a good idea - this notesfile has been a bit dead
recently, people have been fairly quiet of late.
    
A lot of the things you suggest for the document are available by looking
in the Reading notesfile, but I agree it would be handy to save new hires
looking for info like this if it was organised into a leaflet or somesuch.

Anyway, I've been thinking it would be an idea to replace both the Graduates
conference and the IT's conf with one which was entitled NEW_TO_DEC

This would cover not only Grads and IT's but new hires generally, contractors
and so on. A first place to look for the person wanting an introduction to
life in the Company.

Most of the function of this notesfile (such as ESPP etc) can be carried out
in, say the UK_DIGITAL notesfile or others. But some of the info here could
be transferred to NEW_TO_DEC. Similarly with the IT conf - a lot of the topics
are duplicated elsewhere.

If there was a conference like this it would provide an extension to the
documentation you're thinking of handing out at the induction and would
provide a focal point for information. It would even be an idea if one of
the grads went along to the induction and introduced themselves so that
new hires would have a face to identify behind the mail messages and
conference announcements for events coming up and chances for new hires
to meet one another.

	Comments?
			Craig.

Re: .10

> Sounds good. There's a similar one for Engineering. It's called the
>
>	"Software Engineering manaul"

The publication mentioned is not in any way comparable to what is discussed
earlier.  The correct publication is called something like "The Guide to 
Digital Internal Organizations".  (It is mentioned in another note.)

The "Software Engineering Manual" is only a how-to book for producing 
quality software.  It is applicable to anyone who writes software, whether 
in Engineering or not.

Engineering does a whole lot more than software.  Producing hardware 
involves lots of different types of engineering.

jb

    
    
    	Could someone tell me where I can get a copy of the
    Software Engineering Manual?
    
    Tom Gallo
    

    for a copy of the Software Engineering Manual.

    Better yet, if you have access to the Corporate VTX Library, order
    it from SMC using SMC VTX.   SMC prefers VTX orders to JOKUR::SMC
    orders today.
                                                                          
    Spawning out of here, typing VTX SMC at your $ prompt, and using the 
    keyword search function (PF1-7) EL-EN571-00<cr> of SMC VTX should
    have your document ordered in less than a minute and you back in Notes
    doing Next Unseen.                      
    

re: .15

Most field employees can't do what you just suggested.  Why?  They are in
captive accounts that do nothing but run a certain OA package that most of
us software types hate.

For me to access your VTX screen from a notes conference,  I must exit the 
conference, exit NOTES, hit return to get back to the BA menu, type VTX,
(PF1-7) SMC, (PF1-7) EL-EN571-00, order the doc, (PF1-.) to exit VTX,
type NOTES to get back into NOTES, then finally, OPEN <my_conference>.

To send mail to JOKUR::SMC, all I have to do is type SEND, enter JOKUR::SMC
when mail askes who to send to, enter my subject, and my message.  After
I send the message, I'm right back where I was in the conference.  Guess which
way most people are going to do it...

Your suggestion makes perfect sense on a workstation, where I can simply create
another terminal window, (or use an inactive one), and then VTX ...

Bob

    re: .16
    
>For me to access your VTX screen from a notes conference,  I must exit the 
>conference, exit NOTES, hit return to get back to the BA menu, type VTX,
>(PF1-7) SMC, (PF1-7) EL-EN571-00, order the doc, (PF1-.) to exit VTX,
>type NOTES to get back into NOTES, then finally, OPEN <my_conference>.
    
    Is there some reason you can't SPAWN from Notes and use VTX in the
    subprocess?
    

	SPAWNing will not work if your account does not permit sub-jobs.
	Lots of A1 accounts don't.

				Alfred

re: .17

.18 has most of it right.  Most of our layered products (I think this includes
NOTES V2), now check the captive flag and won't let you SPAWN if it is set.

It get's even worse in a future release of VMS.  If you manage to get to DCL
in any way, shape, or form, and the captive flag is set, your process gets
deleted.  How's that for user-hostile?

Unfortunately, some of Digital's policies are a lot like U.S. laws; they
are geared to the lowest common denominator.  So, intelligent people get
treated like fluff-chicks, (don't ask...I heard it from a teenager) who
can't even find the 'any key'.

Bob

        So, if you think that SMC's ordering mechanism is too cumbersome.
        (even though it can be complete in a matter of seconds), then why
        don't you sit down and write them a letter.... :-)
        
        q
        

The ordering mechanism isn't too slow.  It's the #$%^&* OA product combined with
overworked machines that make things difficult.  I'm glad that the alternate
ordering method exists.  They just shouldn't hold their breath waiting for
everyone to switch over to the VTX method.

Bob

Can we get back to the subject please?

    A good sourse of information for new-hires is a program called
    "Introduction to Digital for Engineering"; a 2 day course designed
    for engineers and any technical professional whose job it is to
    support the efforts within Digital's engineering environment.  This
    includes just about everyone!
    
    I am the program manager for this program which has been offered
    throughout the company for the past 5 years.  It focuses on the
    following areas:
    
      o  Digital history
      o  Digital Culture
      o  Digital Organizations/Structure
      o  Products and Product Strategy
      o  Engineering Process (Phase Review)
      o  Quality
      o  Professional and Personal Development for Technical Professionals
          
    The response to this program has been very good.  Unfortunately,
    many recent hires (16 months and less) haven't heard of the program!
    
    Participants receive a copy of the program workbook, the "Internal
    Guide to Digital Organizations, Software Eng Manual, and an assortment
    of other handout and information about company resources.
    
    Our group, Engineering Quality Technology (ZKO2), is making a serious
    effort to get the word out about this program.  The NOTESFILE is
    an ideal place!
    
    Information about the program schedule, cost, availability, etc..
    can be obtained by contacting Debbie Barrett at 381-1338, SIVA::BARRETT
    
    
    Rick Elmer

        RE: .23 -- I recently took Rick's course (I've been at Digital for
        over 5 years, and I wasn't the "senior" employee there), and I
        recommend it to anyone who has the opportunity to take it. 
        
        Tom

    My apologies for making you wait...


    Revision 2 of the Survival Guide is now available:

	Chapter 1	Why Survival?	(Introduction)
	Chapter 2	Easynotes	(Using, plus getting your own list,
    					NOTES user guide and etiquette)
	Chapter 3	Corporate VTX	(Using, plus list, plus setting up
					 your own access)
	Chapter 4	Internal Kits and Licenses
					(How to get kits directory, etc.)
	Chapter 5	ELF		(Using, plus setting up your own)
	Chapter 6	ADS		(Automatic Distribution, plus list
					 of all publication codes and
					 VMS/Ultrix/MS-Dos docset codes)
	Chapter 7	SSDs, Cover Letters and Forms
					(Finding and using Software Services
					 Descriptions)
	Chapter 8	Your Own Node	(Other basics about setting up your
					 own node -- picking a name, filling
					 out forms, setting up printer queues
					 to LPS40s, etc.)
	Chapter 9	The Phone	(Corporate Hotline List)
	Chapter 10	Using DOCUMENT	(Get started with DOCUMENT with less
					 than 10 pages of documentation to
					 have to read)
	Appendix A	Easynotes Conferences
					(EASYNOTES.LIS listing)
	Appendix B	EASYnet Kits	(KITSDIR.DOC listing)
	Appendix C	Internal PAKs	(SIXPAK (VTX internal PAK distribution
					 application) user's guide)

    A copy is available on SUBWAY in:

    	SUBWAY""::DISK$D7:[SWSTOOLS.DOC]SG.LN03 as before, along with the

    	SIXPAK$USER_GUIDE.LN03/PS (Appendix C)

    The master copy (source, styles, etc.) of this revision of the Survival
    Guide is in:

    	SVBEV""::DUA0:[SG.V020]*.*

    If you would like to make additions/changes, let me know so I can
    incorporate your "enhancements" in the next version.

    My apologies for not adding change bars for this revision. (Will be done
    for next revision.)

    Please mail comments and suggestions to me at SVBEV::VECRUMBA.



    /Peters

    SVBEV was off the air from 2:00am until 10:00am this morning. My
    apologies if this caused any inconvenience.

    /petes

    Version 2.1 of the SWS Field Survival Guide is now available. My thanks
    to those who have expressed interest in using it in their own areas and
    encouraged its becoming more generic.

    The guide (generated for my area -- more about that later) can be found
    in:

    	SUBWAY""::DISK$D7:[SWSTOOLS.DOC]SG.LN03 as before, along with the
    	SIXPAK$USER_GUIDE.LN03,PS (Appendix C)

    If you already have a copy of the guide, you do not need to reprint
    the SIXPAK user's guide. It has not changed since the last release.

    The master copy (source, styles, etc.) of this revision of the Survival
    Guide is in:

    	SVBEV""::DUA0:[SG.V021]*.*

    I have marked changes with change bars. The primary changes are:

    -	VTX infobases alphabetized according to description.
    -   Added more ADS codes tables.
    -   Area codes on hotlines corrected (508 area), CSC numbers broken
    	out and products supported by each CSC listed.
    -	Added "Network File Copy (FTSV)" and "Virtual Terminal Sessions"
	(for LAT terminals) sections.
    -	Added DOCUMENT commands to "SDML Commands" section.
    -	Added "Monitoring Conferences" section (ENOTES, AVN).

    Most important, while the tables may "look" pretty much the same, their
    generation is now fully automated with the exception of a few questions
    and VTX SAVEs. (At last count, 732 lines of DCL just to copy files and
    run extraction/formatting programs!) The lists I update this way are:

    -	EASYNOTES.LIS (Appendix A), also table of all EASYNOTES.LIS
	copies maintained on the network
    -	Corporate VTX infobases, also now alphabetized according to description
    -	KITSDIR.DOC kits directory (Appendix B)
    -   ADS product, operating system, media, and publication codes
    -	LPS20/40 Printserver directory - generated by selecting DECNET area(s)
    -	ELF kit and server locations (V1 ELF)
    -	SSD directory contents

    I have also added a local setup section for specifying location (like
    facility or geographic area), local contact, and tools (e.g., "CONFS",
    "KITS") node and directory.

    I'll try and make the "tools" procedures available in the next week or
    so once I figure out how to make their propagation as painless as
    possible.

    I'd greatly appreciate feedback -- even wishlist additions. ;-)


    Best regards,
    Peters

re .-1:

Error alert!!

In discussing ENOTES, one of the ENOTES EXTRACT qualifiers was omitted from
the command line. The example for extracting all unseen notes into seperate
files should be:
                                  +++++++
    $ enotes extract */class=daily/update/unseen/seen/output="!AS-!6%D.TXT"
                                  +++++++

If you don't specify /update, then ENOTES trusts the "unseen" counter in your
notebook, which of course was set to _zero_ the last time you looked at all
the unseen notes!

/petes

I've made a first cut at making the tools mentioned in the Survival Guide
available "out of the context" of our local cluster. These tools are:

	confs		- search easynotes.lis, easynotes_upd.lis for
			  string, or type out entire file
	kits		- search kitsdir.doc for string, or type out entire
			  file
	doc2mate	- convert Document LN03 output (8 bit characters) to
			  7-bit equivalents to allow printing to LN03's
			  attached to DECmate printer port (only 7 bits passed
			  to printer)
	ssd_doc		- THIS IS A FIELD TEST VERSION
			  A general find/copy/format utility for Document
			  format SSD files, also works with local user files
			  (interactive command file)

They may be found in SVBEV""::DUA1:[TOOLS.SG...], contents follow. The
asterisks indicate files in need of regular TLC:

	DUA1:[TOOLS.SG]COM.DIR;1                  (RWE,RWE,RE,RE)
	DUA1:[TOOLS.SG]DOC.DIR;1                  (RWE,RWE,RE,RE)
	DUA1:[TOOLS.SG]EXE.DIR;1                  (RWE,RWE,RE,RE)
	DUA1:[TOOLS.SG]SRC.DIR;1                  (RWE,RWE,RE,RE)
	DUA1:[TOOLS.SG]SSD.DIR;1                  (RWE,RWE,RE,RE)
	DUA1:[TOOLS.SG.COM]CONFS.COM;9            (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.COM]DOC2MATE.COM;19        (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.COM]KITS.COM;6             (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.COM]SGTOOLS.COM;4          (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.COM]SSD_DOC.COM;25         (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.COM]SSD_DOC_XREF.COM;7     (RWED,RWED,RE,RE)
     *  DUA1:[TOOLS.SG.DOC]EASYNOTES.LIS;1        (RWED,RWED,RE,RE)
     *	DUA1:[TOOLS.SG.DOC]EASYNOTES_UPD.LIS;1    (RWED,RWED,RE,RE)
     *	DUA1:[TOOLS.SG.DOC]KITSDIR.DOC;1          (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.EXE]DOC2MATE.EXE;1         (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.SRC]ASCDEF.BAS;18          (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.SRC]DOC2MATE.BAS;5         (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.SRC]DOC2MATE.OBJ;1         (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.SSD]DOC$DESIGNS.DAT;8      (RWED,RWED,RE,RE)
     *	DUA1:[TOOLS.SG.SSD]SSD_XREF.TXT;1         (RWED,RWED,RE,RE)
	DUA1:[TOOLS.SG.SSD]TEX$SSD.DESIGN;5       (RWED,RWED,RE,RE)

It's assumed that the file maintainer receives the monthly EASYNOTES list
and weekly updates, and that these are extracted into the appropriate
files. KITSDIR.DOC needs to be copied periodically manually (or batch job).
Finally, ssd_doc_xref needs to be executed periodically (more on that later).

You *must* set up the same directory structure under whatever you choose as
your root:

                    SG tools root = wherever
                                |
          +---------------------+---------------------+
          |          |          |          |          |
        [.COM]     [.EXE]     [.SRC]     [.DOC]     [.SSD]
            |
            = location of "SGTOOLS.COM" command file

To set up the logicals and symbols for the tools, all the user needs to do
is add
	@dev:[wherever-the-tools-are.COM]SGTOOLS

to their login.com file.

(The logicals are SG$TOOLS_subdirectory-name, for example,  "SG$TOOLS_COM")

You will note that this *differs* from the Survival Guide, which specifies
POINTER.COM. This is the name of the file on the SUBWAY:: cluster, which also
sets up a whole other set of "stuff".

The ssd_doc procedure needed modifications to remove some local dependencies
and to allow more user discretion in copying and formatting files. Because I
will be on vacation, I decided to make it available "as is" rather than further
delay the other tools. The ssd_doc_xref procedure is used to produce a
SSD number --> SSD file name cross reference to use when selecting an SSD
by number. You need to periodically run this to keep this cross-reference up
to date.

Good luck!!


Best regards,
Peters

P.S. SVBEV is a lowly MicroVAX II, so please try and be gentle to it. File
copies after midnight would be greatly appreciated.

    Version 2.1 formatted output is still on SUBWAY as before:

    	SUBWAY""::DISK$D7:[SWSTOOLS.DOC]SG.LN03 as before, along with the
    	SIXPAK$USER_GUIDE.LN03,PS (Appendix C)

    	(the error noted has been corrected)

    The master (source) copy on SVBEV have moved, however, to:

    	SVBEV""::DISK$SG:[SG.V021]*.*

    (actually DUA1). The logical should avoid any future inconveniences.

    /petes

    Version 2.2 of the Survival Guide is now available. Changes:

    	- ELF chapter redone for version 2 (VTX based) ELF

        - VAXPAX (European service descriptions and service delivery
    	  software toolkits) chapter added

        - SIXPAK (internal license PAKS) user manual appendix dropped

        - DTN/direct inward dial appendix added

    it is available in:

    	SUBWAY""::DISK$D7:[SWSTOOLS.DOC]SG.LN03

    The master source copies will shortly be available for customization
    after some house-cleaning.

    As always, feel free to pass it on.

    /Petes

    Version 2.2a of the Survival Guide is now available. All "volatile"
    information has been updated, and all volatile information tables
    are now clearly marked with an "as of" date.

    This version contains internal enhancements for improved customization
    and version management as well as minor corrections:

    	-  new contact for EASYNOTES.LIS mail update, newly restarted
    	-  additional document types for V1.2 of DOCUMENT

    The guide is available in both LN03 and Postscript formats, in:

    	SVBEV""::DISK$SG:[SG.V022A]SG.LN03 and
    	SVBEV""::DISK$SG:[SG.V022A]SG.PS

    A copy of Matias Krempel's information guide is also available in the
    same directory (plain ASCII format):

    	SVBEV""::DISK$SG:[SG.V022A]HOW_TO_GET_INFORMATION_IN_DIGITAL.TXT

    Table of contents (asterisked, [*], items are automated volatile updates,
    sub-items, -..., are tables):

    Chapter
    -------
    1	Introduction ("Why Survival?")
    	- Resources
    2	EASYnotes
    	- EASYNOTES.LIS locations [*]
    	- NOTES Commands
    	- "Smiley Faces"
    	- NOTES documentation locations
    3	EASYnet Corporate VTX
    	- Corporate VTX files for Corporate VTX installation
    	- Corporate VTX infobases and keywords, sorted by description [*]
    4	ELF (Employee Locator Facility, V2)
    	- FIND syntax, ELF_FIND (DCL interface)
    	- ELF server locations [*]
    5	Internal Kits and Licenses
    6	ADS (Automated/automatic Distribution System)
    	- ADS Publication Codes [*]
    	- ADS Software Codes (subset: VMS, ULTRIX, DECWindows, PC) [*]
    	- ADS Media Codes [*]
    	- ADS Software Group Codes [*]
    	- ADS Operating System Codes (full list) [*]
    7	Hotline Support
    	- U.S. Technical Support Numbers
    8	Software Service Descriptions, Cover Letters, Forms
    	- Directory of Service Descriptions [*]
    	- Directory of Forms [*]
    9	VAXPAX Consultancy Kits
    	- Request Code/Kit Listing [*]
    10	Using DOCUMENT
    	- DOCUMENT Styles
    	- DOCUMENT Output Types
    	- Basic DOCUMENT Tags (enough to get started)
    11	Setting up your own network node
    	- LPS20/40 Printserver Nodes (by DECnet Area) [*]

    Appendix
    --------
    A	EASYNOTES.LIS [*] - NOTES conferences listing
    B	KITSDIR.DOC [*]   - Kits location directory
    C	DTN.LIS [*]       - DTN code listings for major sites

    ----
    "This note may be freely forwarded or re-posted within Digital"


    Best regards,
    Peters

    If anyone tried to copy the S.G. last night, SVBEV was temporarily
    unavailable because of a brain relocation/transplant/defragmentation
    operation. (All disks moved to another GPX at another site.)

    My apologies for any inconvenience.

    Best regards,
    Peters

    Version 2.3 of the Survival Guide is now available. This is the first
    "General EIS Release." As usual, all the volatile information has been
    updated. Changes for this version include:

	- network location included in guide (LN03/ANSI and Postscript copies)
	- "SG tools" made public; access procedure included
	- feedback NOTES conference started and announced
	- automatic distribution listing enhanced
	- Printservers by DECnet area replaced (for general release) by
	  Printservers by site

    The guide is available in both LN03/ANSI and Postscript formats, in:

    	SVBEV""::DISK$SG:[SG.V023]SG.LN03    (looks better)
    	SVBEV""::DISK$SG:[SG.V023]SG.PS

    A notes conference has been started to better gather feedback. In NOTES,

    	ADD ENTRY SVBEV::SURVIVAL_GUIDE  (or 33099::SURVIVAL_GUIDE)


    Best regards,
    Peters

    SVBEV is currently unavailable. I'm about 125 miles from the office
    today; I expect to have it up this evening. My apologies.
    
    /Peters

    If you get a copy of the Survival Guide over the network, please
    register yourself in the (SVBEV::)SURVIVAL_GUIDE notes conference. This
    will give me a better idea of the audience and how to target the SG. It
    will also get your name on the Survival Guide mailing interest list.

    /Peters