Filename: NLUPDATE.TXT


                       D R A F T  V E R S I O N
                       =========  =============

Zone 73 @CrossNet(tm)
Procedure for sending Nodelist updates to the CrossNet ZC.
Updated: 03/08/93

This procedure is designed for the beginner in mind.
It is hoped that this will make nodelist updates uniform
throughout CrossNet.

Input and suggestions welcomed!

Please send comments and suggestions to Jim Rhodes, 73:200/0

---------------------------------------------------------------------

This procedure is designed to make sending weekly nodelist update
segments to the ZC quick and painless.

To start out. Use a text editor to cut out your HOST or REGION
segment out of the CROSSLST.### nodelist.  Save the segment in
a subdirectory that you plan to use for all future updates.
i.e. \CROSSLST or \NODELIST

Rename the segment NETXXXX.SEG or REGXXXX.SEG where XXX is your
HOST Net or REGION ID.

Now that you have a starting point you may want to add the following
lines to the top of the segment to make a header:

;
; NODELIST SEGMENT UPDATE FOR NETXXXX.SEG ( OR REGXXX.SEG )
;
; DATE UPDATED:
;
; CHANGES MADE:
;
;

This way when you sent your nodelist segment to your RC or ZC each
week it will be easily identified and the changes will be
clearly understood.

When a node is added, changed, or deleted from your NET or REGION.
Simply make the change in the nodelist segment and forward it to your
RC or to the ZC for inclusion in the CrossNet nodelist by Thursday
afternoon of each week.  If there are no changes it is not necessary to
send a nodelist update segment upstream.

When adding nodes, please refer to the nodelist structure posted as
NLSTRUCT.DOC in the CROSSNET.ZIP file and in the CROSSLST.###
nodelist after the actual listing of systems.

In order to avoid routing problems any system that is calling out of
their geographic area should be listed as a Pvt system.