.                                Installing NEWS.                                ---------------  N The following  section  describe  the necessary  steps  to install  NEWS  on aN system. Note that where possible these steps should be performed  in the orderK as given in this text. It is necessary to do each stage in the order below.    A. Installing NEWS files ------------------------  N 1. Load *.C,  *.H,  *.HLP,  *.CLD,  *.OPT  and NEWSBUILD.COM  files  into  theN    directory  dev:[dir.NEWS_SRC].   This set of files  corresponds  to the SRCN    backup  saveset  of the  distribution.   The  directory  name  NEWS_SRC  is>    critical when using the supplied DCL NEWSBUILD.COM routine.  N 2. Create  the directory  dev:[dir.NEWS_BUILD].   This is where  the NEWSBUILDJ    procedure will put the object files and libraries needed to build NEWS.  N 3. Create  the directory  dev:[dir.NEWS_DIST].   Load the DIST backup  saveset    into this directory.   N 4. Create the directory dev:[dir.NEWS_DOC].   Load the DOC backup saveset into    this directory.     B. Compiling and Linking NEWS  -----------------------------   N One command procedure  performs  both the compile and link phases of NEWS. TheN procedure works on the revision date-time of the file to determine whether any, files require re-compilation before linking.  , 1.  Execute the NEWSBUILD command procedure:  B     $ SET def dev:[dir.NEWS_SRC]   ! This is critical to NEWSBUILD0     $ @NEWSBUILD [tcp-transport] [force] [debug]           tcp-transport:  N [ONE] #                         M [ULTINET]                          C [MU]                         W [IN]%                         U [CXSOCKETS] "                         UCXQ [IOS]                            E [XOS]]           force:          COMPILE                          LINKG                         <empty string> - as required by date/time check   D         debug:          DEBUG   - compile and link with DEBUG optionF                         NODEBUG - compile and link with NODEBUG optionG                         <empty string> - compile and link both versions   N    This procedure creates a new set of .EXE files in the NEWS_DIST  directory.6    which are used in the following installation steps.     C. NEWS Accounts ----------------  N 1. Add  an account  for  a NEWS  manager  (NEWSMGR  if you'd  like  a usernameN    suggestion).   This account is used to execute the housekeeping  batch jobsN    (such as NEWSSKIM if you are using it).  It is also used as the account forN    the network feeds to adjacent  NEWS sites, and therefore  should have proxyN    entries to adjacent  DECnet nodes' NEWS manager  accounts  if more than one+    node will be running NEWS on the DECnet.   N 2. The account  normally  requires  SYSPRV  to execute  some  of the functionsN    associated with the 'housekeeping' batch jobs.  The account may also need aN    reasonable  disk quota if you are anticipating  a large  amount  of networkN    news flowing through  your system,  and you make this account  own the newsN    posting  directories.   For a full feed, you can expect to use about 25,000,    VMS blocks per day of NEWS that you keep.     D. Logical Names ----------------  N It is intended  that  much  of the local  tailoring  of NEWS  is performed  byN logical  name translations.   For this reason  the logical  name structure  isD important when installing NEWS - please read this section carefully.  O >>  NOTE:  It is important that these names be defined before running NEWS for   >>         the first time.                             N 1. The distribution set includes  the  file  NEWS_STARTUP.COM_TEMPLATE,  which0    should be modified for use at the local site.      Description of names:  N      NEWS_ROOT,  NEWS_DEVICE  (REQUIRED  for server nodes) Both names point toN      the news files root directory.   Both must be defined  in EXEC mode.  TheN      news data files  are placed  in a tree descending  from this root - i.e. N      newsgroup   `aus.wanted'   has   text   files   residing   in  the   areaN      NEWS_DEVICE:[AUS.WANTED].   The Index files  and Help file are placed  in.      the NEWS_ROOT directory for server nodes.  N      NEWS_MGR_ID (REQUIRED for server nodes) Translates to the identifier nameN      which must be granted to any users who require  the management  functionsN      of NEWS (delete  newsgroup,  create  newsgroup,  etc).   The name must beI      defined in EXEC mode to stop unauthorized users tinkering with NEWS.   N      NEWS_ADDRESS  (REQUIRED)  Translates  to the internet address of the hostN      node.  This is typically  of the form node.site.domain.   The address  isN      used to generate the Internet-format  "From" address in all postings from      this node.   N      NEWS_NODE (OPTIONAL)  Translates  to the local node name.  This is made aN      logical  name to allow a cluster  to operate  as a single  logical  node,N      using a cluster alias.  All nodes in a cluster  should use the same valueN      of NEWS_NODE.   This logical  name is also used in the "Path:"  header as      the local node name.   N      NEWS_PATHNAME  (OPTIONAL)  This is the name of the local node used in theN      Path header.  For uucp sites this is the uucp node name.  For other sites"      it is the node address value.  N      NEWS_ORGANIZATION  (or NEWS_ORGANISATION)  (OPTIONAL)  Translates  to theN      name  of the organisation.   This  is to help  in identifying  the personN      posting  the message  to other users on the net.  Users may use a process6      level logical name to override this system value.  N      NEWS_TIMEZONE  (REQUIRED) Translates  to the local timezone code.  If notN      defined then NEWS will assume (incorrectly in almost all cases!) that the      local timezone is "GMT".   N      NEWS_MANAGER,  NEWS_MANAGER_DEV  (REQUIRED  for server nodes) This is theN      work directory of the NEWSMGR account.  All temporary  files used in newsN      maintenance  are placed here.  NEWS_MANAGER_DEV  is the equivalent  area,#      defined as a concealed device.   N      NEWS_CACHE  (OPTIONAL)  This logical name is used to trigger  caching  ofN      message Ids in a global section to improve effiency  of the nntp server. N      If you use this feature you'll also have to create the associated  global
      section.   N      USENET  (REQUIRED  for server  nodes)  This is a mail alias for the localN      news manager.   As above,  this may either  be a logical  name  or a mail      forwarding address.  N      NEWSMAIL,  RNEWS (OPTIONAL)  These are mail address aliases to allow thisN      node to communicate  to adjacent  NEWS nodes.  They should be defined  asN      the username of the NEWS manager account.  An alternative  is to use MAILN      management utilities to add add an entry for the addresses "NEWSMAIL" andM      "RNEWS" with a forwarding address to the NEWS manager account (NEWSMGR).   N      NEWS_HELPLIB  (OPTIONAL)  NEWS will by default search for the online helpN      file, NEWS.HLB, in the areas NEWS_ROOT:  and SYS$HELP:  (in that order). N      If you wish to place the NEWS.HLB  file in some other area,  then use theH      logical name NEWS_HELPLIB to define the full name of the help file.  N      NEWS_NETPOST,  and NEWS_NONETPOST.   When  either  of these  logicals  isN      defined,  their  translation  is interpreted  as  an  identifier.   UsersN      holding  the identifier  may (may not) post to network  newsgroups.   ForN      example, if NEWS_NETPOST  is defined as NETPOST, then users must hold theN      NETPOST identifier to post to network wide groups.  If NEWS_NONETPOST  isN      defined as NOPOST, then users holding the NOPOST identifier  may not post      to network groups.   N      NEWS_NNTP_LOG.  If this logical is defined, the NNTP server will log eachN      access to the file specified.  For example if NEWS_NNTP_LOG is defined asN      NEWS_MANAGER:NNTP_SERVER.LOG, then all NNTP accesses would be appended to"      NEWS_MANAGER:NNTP_SERVER.LOG.  N      NEWS_NNTP_PROTOCOL and NEWS_NNTP_SERVER are used by NEWS in a client onlyN      configuration  to determine  the  internet  address  of the  remote  NNTP4      client, and what TCP/IP protocol is to be used.  N      NEWS_STOP.   If this logical is defined  (/EXEC in the SYSTEM table) then      NEWS will shut down.   N      NNTP_DISK_DANGER  and NNTP_DISK.   If the available  disk  blocks  on theN      device  NNTP_DISK   falls  below  the  number  of  blocks  specified   byN      NNTP_DISK_DANGER,  then  new  connections  to the  nntp  server  will  be      rejected.  N      NNTP_SCRATCH.   If this  logical  is defined,  then  it must  point  to aN      directory  that will be used by the nntp  server  for creating  temporary      files.   N      NEWS_USAGE_LOG  (OPTIONAL)  If defined as a system logical  name (in EXECN      mode) as the name of a file, then a usage log of NEWS will be placed into      that file.      E. Global DCL Symbols  ---------------------   < 1. In the system login command script add a symbol for NEWS: 	$ NEWS :== $ location:NEWS    2. Install NEWS.EXE   N    Copy NEWS.EXE to the location as specified  by the DCL symbol for NEWS with8    world RE access.  Then install the image with SYSPRV:  , 	$ COPY NEWS.EXE location:NEWS.EXE/PROT=W:RE
 	$ INSTALL; 	INSTALL> ADD location:NEWS.EXE/OPEN/HEAD/SHARE/PRIV=SYSPRV  	INSTALL> EXIT  N    SYSPRV  is required  to ensure  that users  who post news items  end up NOTN    owning  the actual  news text files,  and also is required  to successfullyN    initialize  the indexed files on the first-time  execution  of the program.7    For most of the time NEWS runs with SYSPRV disabled.      F. Initial Environment ----------------------  7 If you are configuring NEWS with a local database then:   N 1. Using AUTHORIZE,  create the news management  identifier  (the value of theN    logical name NEWS_MGR_ID), and grant the identifier to the user(s) who will-    be responsible for the management of NEWS.   N    Note that  the NEWSMGR  (news  management)  account  must  be granted  thisH    identifier in order to correctly process incoming network news feeds.  N 2. Create  the  directories  that  have  been  defined  by the  logical  namesN    NEWS_MANAGER  and NEWS_ROOT.   Ensure  that the directories  are group  and    world accessible.  N    Optionally: Add a propagation ACL to the NEWS_ROOT directory to allow those<    users whom you wish to use news to access the item files.    H 3. Copy NEWS.HLB to NEWS_ROOT: and allow world read access to this file.  N >> Note that for the installation  of the NNTP client systems  NEWS_ROOT:  mayN >> not be defined, or in any case you may wish to place this file elsewhere onN >> the system.  You may optionally  place NEWS.HLB in the system help area, asN >> SYS$HELP:NEWS.HLB,  or use the system  level logical  name NEWS_HELPLIB  to< >> point to another location where you have placed NEWS.HLB.    ; If you are configuring NEWS as a diskless NNTP Client then:   J 1. Copy NEWS.HLB to SYS$HELP:NEWS.HLB and allow world access to this file.  N    Note that for the installation you may wish to place this file elsewhere onN    the system.   You may  optionally  use  a the  system  level  logical  nameA    NEWS_HELPLIB to point to where you have placed NEWS.HLB.  i.e.   4       $ DEFINE/SYSTEM NEWS_HELPLIB dev:[dir]NEWS.HLB    N If you  have  turned  on NNTP  message  Id caching:  i.e.   you  have  defined NEWS_CACHE in the setp above.    	How to create the cache :
 	$ mcr sysgen & 	create news_root:news.cache/size=1400 	$ set proc/priv=sysgbl 
 	$ run cachem  	Z ! to reset the cache      G. NEWS Control Files  ---------------------   N There are several  control  files used by NEWS -- these files should  be read,N and then edited  to match  the local  site requirements.   Each file  contains3 comments as to the function and format of the file.   N 1. NEWS.SYS  Read (and then EDIT) file NEWS.SYS.   This file determines  whichN    newsgroups  you will accept, and which newsgroups  your network  neighboursN    will  accept.   The  edited  version  of  NEWS.SYS   should  be  copied  toN    NEWS_MANAGER:.   Include  the  entries  "local",   "junk",  "control"   andN    "to.<node>"  (where <node>  is the value of NEWS_NODE)  in the local node's    filter set.  N 2. NEWS.SYSD  may be used to define the distributions  accepted by the systems4    defined in NEWS.SYS.  The format of this file is:   	system:dist1,dist2,...  	system1:dist1,dist2,...N 3. NEWS.DISTRIBUTION  Read (and then EDIT)  the file NEWS.DISTRIBUTION.   ThisN    file determines  how news is distributed  through your node.  If you are anN    'end- node' for NEWS, then this file should  be empty,  otherwise  the fileN    must be defined.  The edited version of NEWS.DISTRIBUTION  should be copied    to NEWS_MANAGER:.  N 4. NEWS.ALIASES Read (and then EDIT) the file NEWS.ALIASES.  This file definesN    local aliases  for newsgroups.   If you wish to define local aliases,  editJ    this file and copy the edited version to NEWS_MANAGER: as NEWS.ALIASES.  N 5. MAILPATHS  Read (and then EDIT) the file MAILPATHS.   This file defines theN    internet addresses of ALL moderators for moderated newsgroups.   The edited<    version of MAILPATHS.  should be copied to NEWS_MANAGER:.  N 6. NEWSSKIM.COM  Read NEWSSKIM.COM,  and modify it to suit your requirements. N    See comments  in the code.  Then copy the edited  file to news_root.   ThisN    file is responsible  for the collection  and distribution  of news items to    remote sites.  N 7. NEWS_ADDRESS.CNF  Read this file,  and also read the file ADD_TRANSFORM.C. N    If you are using a local PMDF mail handler,  then the default action may beN    suitable.  Otherwise  you will  need  to edit  this  file,  and copy  it to%    NEWS_MANAGER: as NEWS_ADDRESS.CNF.   N 8. NEWS_POST.DEFAULTS Read this file and decide if it is relevant.  If so then6    edit the file and place a copy it to NEWS_MANAGER:.  N 9. NEWS_POST.CC  Read  this  file,  and  decide  if  it  is  relevant.   WhereN    unmoderated  newsgroups are fed from a mailing list, then postings into theN    newsgroup  may not be sent back to the central mailing  list address.   YouN    can place entries into this file to force cross mailings  of local postingsN    back to the mailing list address.  If necessary, edit this file and copy itN    to NEWS_MANAGER:  as NEWS_POST.CC.   If not required  then do not copy  the"    file to the NEWS_MANAGER: area.  N 10.NNTP_ACCESS.NEWS  Read this file, and decide if it is relevant.   This fileN    determines  what systems may access your NNTP server.   If necessary,  editN    this  file   and  copy   it  to  NEWS_ROOT:.    (That's   NEWS_ROOT:,   not    NEWS_MANAGER:.)  N 11.NEWS_POST.DEFAULTS  Read this file and decide  if you want to use it.  ThisN    file  allows  you to specify  the default  values  for some  of the articleN    headers based on what newsgroup an article is being posted to.  If you want:    to use this file, edit it and copy it to NEWS_MANAGER:.  N 12.NEWSRC.TEMPLATE This file will be used as the default NEWSRC file if a userN    has no NEWSRC  file.   If you want to use this file, edit it and copy it to    NEWS_MANAGER:.   N 13.NEWS.CLASSES This file may be used for defining site specific classes.  The    format of the file is:    	classname group,group,...  N    Classname  is the name of the class that all the groups  should  be entered    into. For example:    	$classes class.*   N    would enter all groups  under  "class"  into the groups  $CLASSES.   If you7    decide to use this file, put it under NEWS_MANAGER:.      H. First Time Execution of NEWS  -------------------------------   N 1. Once ALL the above steps have been completed, login to an account which has?    SYSPRV and has the NEWS_MGR_ID identifier, and run NEWS.EXE.   N    The first time execution  will create the files: NEWS_ROOT:NEWS.GROUPS  andN    news_root:news.items,    and    also    create    the    authority    file,    news_manager:news.license.   N This almost  completes  the installation  of NEWS - the remaining  task is theN creation of the necessary newsgroups.  Use the CREATE/LOCAL command and createN the newsgroups  "control"  and "junk".  If you are on the USENET news network,N obtain a copy of the most recent "checkgroups"  posting relevant  to your areaN of the USENET.   Examine the newsgroup  names in this posting and add the rootN names (e.g.   "net"  from "net.wombats")  of the relevant  newsgroups  to yourN local  acceptance  filter  in news_manager:news.sys.   Once news.sys  has beenN edited, pass this checkgroups  posting  to NEWS by using the ADD command  withN the /EXECUTE  qualifier.   This will automatically  load the local  NEWS files' with the applicable network newsgroups.    u( I. Upgrading from Previous NEWS Versions( ----------------------------------------   V5.9 - V6.0 Upgrade   N The only change  in V6.0 over V5.9 is a change  in a previously  unused  fieldN within  the news.groups  indexed  file as the first used news item number  (toN speed up the NNTP Server code).   When installing  NEWS V6.0 install  the NEWSN program  first, and perform  a SKIM pass.  Then install  the NNTP server  codeN following the completion  of the SKIM pass.  This is optional, and if not doneN in this order  then the NNTP server  will lie about  the first  used news itemN number  in each newsgroup  (which  is exactly  what Unix versions  of the NNTP server currently do!).     V5.8 - V5.9 Upgradei  N There were no changes to the NEWS file in this version,  so that no particular upgrade actions were required.     V5.7 - V5.8 Upgrade_  N The first time NEWS V5.8 is executed  on a system which has been running  NEWSN V5.2 through  V5.7,  then NEWS will  attempt  to perform  the upgrade  to V5.8N automatically.   Note that this upgrade  phase  requires  that the local  NEWSN manager account execute the upgrade,  so ensure that this account is the first account to use V5.8.  N The automatic  upgrade  converts  the file  news_root:newsgroups.v50  to a newN internal  record  format,  and saves the new format  as news_root:news.groups.N Similarly    the    file    news_root:newsitems.v50     is    converted     toN news_root:news.items.   While  this conversion  is being  performed  NEWS willN display it's progress on the screen.  The conversion  phase completes with theN display of the advice to delete the .v50 files.  Following this the upgrade is	 complete.   N If  you  were  running   NEWS  V5.4  or  NEWS  V5.6  then   delete   the  file news_root:history.dat.     J. Installing NNTP Servers --------------------------  N There are three node types with respect  to NEWS NNTP: Server nodes, where theN node acts as a server for remote clients, Client-only  nodes, which access oneN or more server nodes over NNTP, and Server/Client nodes, where some newsgroupsN are served from remote NNTP servers, and this node also acts as an NNTP server for remote client nodes.   NNTP Access File  N For NNTP servers you may wish to set up an access permission file.  By defaultN any remote system is allowed  to connect  to the NNTP service.   Access can be+ restricted using an access permission file.n  N The access file is news_root:nntp_access.news.   If this file exists, the NNTPN server will consult  this file before  accepting  a remote  client  connection request.  N The format  of this  access  file  is one entry  per line  (with  the  commentN delimiter character  as '#').  Each line contains up to four fields, delimited
 by blanks:  % 	a - 	remote host name (or "default")u  & 	b - 	read / transfer permission field. 		      read	   # read and transfer permission4 		      xfr	   #  no read - transfer only permission5  		      noread	   #  no read, no transfer permission + 		(the minimum abbreviation is 1 character)n   	c - 	post permission field. 		    post	   #  post access/ 		    nopost 	   #  no post access    [default]s+ 		(the minimum abbreviation is 1 character)E   	d - 	newsgroup access listeF                 This is a comma separated list. Access is granted onlyA                 to those newsgroups listed in the entry. WildcardnC                 characters '*' and '%' and '?' are supported in thetD                 list, and specific negation, using the '!' character?                 prefix, is also supported. There is an implicit B                 inclusion of sub-newsgroups within each entry. ForF                 example the entry "wombat" will match against "wombat"F                 and also "wombat.singles", "wombat.hairy.wild", and so                 on.s   For example:      ?   alpha   read    nopost  *           # read access, all groups M   beta    read    post    *,!alpha    # read and post to all but alpha groupssJ   gamma   xfr     post    *           # read, transfer, post to all groups   default read    nopost  *   N The relevant  line in the permissions  file is selected  using the remote hostN name.  The NNTP driver code has support for identification  of the remote host name and remote user;s  E o	For the DECNET single channel driver, the remote user is retrieved eC using the logical name translations of SYS$REM_NODE and SYS$REM_ID.   I o	For the DECNET multi channel driver the remote host name is set to the sL value "DECNET", and the remote user to "NNTP". I have yet to check that the B NCP connection block holds the correct remote task identification.  D o	For the CMU-TEK , Multinet and WIN TCP drivers the remote host is E correctly passed to the server, but the remote user is passed as the S constant value "NNTP"A  N As well as the permissions,  the NEWS access.news  individual newsgroup accessN lists are now supported by the NNTP server process.   The remote user and hostN names are used to look up the access.news file before allowing the NNTP serverN access to a restricted newsgroup.   This behaviour is consistent with the NEWS% definition of a restricted newsgroup.o     NNTP  Installation  N To install  the NNTP NEWS servers,  then  follow  the steps  as shown  for the network types below.  N You can check  the operation  of the NNTP  server  by running  the NNTP_CLIENTN program (this program  implements  an interactive  interface  to a remote NNTPN server).   Running  NNTP_CLIENT  and  specifying  the  remote  node  name  andN transport protocol should initiate an interactive session with the remote NNTPN server.   The welcome  message  should appear,  and you should  then obtain  aN reasonable  response to the "HELP" command.  The "QUIT" command will exit from the remote server.  N Once NNTP is installed on the server and client newsgroups  can then be set asN NNTP-served newsgroups (see the documentation on the SET command for details).     Common Logical Name EnvironmentA   NEWS_GMT_OFFSETa  N NNTP uses the value  of this logical  name to convert  from local  time to theN equivalent  GMT time.  The format of the number is a signed timestring  in VMS delta time format.  J For example, Canberra, Australia, is 10 hours ahead of GMT. The following ( logical name definitions are equivalent:-   $ DEFINE/SYSTEM NEWS_GMT_OFFSET "+10:00:00" ,   $ DEFINE/SYSTEM NEWS_GMT_OFFSET "10:00:00")   $ DEFINE/SYSTEM NEWS_GMT_OFFSET "10:00"l&   $ DEFINE/SYSTEM NEWS_GMT_OFFSET "10"  L [Note that you'll need to change the value of the logical name for daylight  saving.]     DECNET Server and Client Nodes  H 1.	Copy NNTP_DEC.EXE to a location accessible to the DECNET account (or H define a new account used for running NNTP in a manner analogous to the & VMS V5 network applications accounts).  ? 2.	Use the INSTALL utility to install NNTP_DEC.EXE with SYSPRV.m  I 3.	In the DECNET (or special purpose) account, create the file NNTP.COM    with the following contents:  <   $ ! NNTP.COM - executed in response to an incoming connect   $ ! to "TASK=NNTP""   $ RUN device:[directory]NNTP_DEC    N There is a variant of NNTP_DEC, called NNTP_DECM.   This program is configuredN to accept multiple incoming DECNet connections to the NNTP object, and serviceN all  such  connections   from  a  single   NNTP  process.    The  installationN instructions  are the same  as the  NNTP_DEC  instructions,  except  that  theN executable referred to in the INSTALL and NNTP.COM is NNTP_DECM.EXE.   Also toN create a permanent DECnet object, NNTP_DECM.EXE  must be installed with SYSPRV and SYSNAM.   N Note that these installation  instructions  allow remote systems to connect toN the NNTP using the task specification:  "TASK=NNTP".   This is compatible withB the task specification of the NNTP process supported under Ultrix.  eN You can connect  the NNTP executable  to a known  object  number  and name  ifN desired using object definition  within DECnet's  NCP utility (this process isN not documented here), to allow incoming connection task specification  stringsN of the form  "NNTP="  and so on.   If the remote  system  is an ANU  NEWS  VMSN system,  then the logical  name  NEWS_decnet-server-name_TASK  can be used  toA specify the required task connection string on the remote system.     + CMU TCP NNTP Server and Server/Client Nodesg  G 1.	Copy nntp_tcpcmu.exe to a location accessible to the SYSTEM account   (this example uses tcp$system).   = 2.	In sys$manager:internet.config insert the following lines:=  ;  ; Define the well-known ports we support and their serverst?  ; WKS:port:procname:imagename:status:privs:priority:queuelimitw  ;A  WKS:119:NEWSRV:TCP$NEWSRV:NETWRK:NETMBX,TMPMBX,SYSPRV,PHY_IO:4:5E  ; 3.	In sys$manager:ip_startup.com insert the following line:n  6  $ define/system tcp$newsrv tcp$system:nntp_tcpcmu.exe      + WIN TCP NNTP Server and Server/Client Nodesp  1 1.	Copy nntp_tcpwin.exe to twg$tcp:[netdist.serv]w  ? 2. 	Add the following block to twg$tcp:[netdist.etc]servers.dat   
     # NNTP     service-name    NNTP6     program         TWG$TCP:[NETDIST.SERV]:nntp_tcpwin     socket-type     SOCK_STREAM 0     socket-options  SO_ACCEPTCONN | SO_KEEPALIVE!     socket-address  AF_INET , 119l     working-set     200.     maxservers      5t     INIT            TCP_Init     LISTEN          TCP_Listen!     CONNECTED       TCP_Connected      SERVICE         Run_Programl  ; 3.	Add the following line to twg$tcp:[netdist.etc]services.t  (     NNTP    119/tcp    #NNTP NEWS Server  B 4.	Stop/Id on the INET_SERVERS process and restart it by running  #     @twg$tcp:[netdist.misc]inetservt      0 Multinet TCP NNTP Server and Server/Client Nodes  ; 1.	Copy nntp_tcpwinmultinet.exe to multinet:nntp_server.exet  3 2. 	Invoke the Multinet services configure program:        $ MULTINET CONFIG/SERVER 	Config> ADD SERVICE   t K. NEWS network Transferss -------------------------t  N This section  describes  some hints as to how to feed new postings  from a VMSN NEWS site to an adjacent non-VMS system (commonly  a Unix system).   There areN two basic approaches:  Using the NNTP network  protocol  and TCP/IP on VMS, or using a VMS/Unix mailer.   NNTP-based NEWS feedsi  N The NNTP  approach  uses  the "ihave/sendme"  protocol  described  in the NNTP4 standard.  The following changes have to be applied:  % o  Modify NEWS.SYS on the VMS system:l  P     unixnode:world,inet,arp,anu,canb,comp,sci,rec,news,misc,soc,talk,aus,alt:N:\0     NEWS_MANAGER_DEV/[IHAVE_UNIXNODE]COLLECT.IDS  N    The relevant  entry  now specifies  that  the VMS system  will  append  theN    message identifiers  to the specified  file, rather than placing the entireN    message text into the posting area (the 'N' flag in the SYS entry specifies$    message identifier transmission).  K o In the Skim command procedure on VMS, the following commands may used to c   invoke NNTP:        $ Distribute:S4     $   write sys$output "Copy items to other sites"     $   set on.     $   nntp_xmit :== $ news_manager:nntp_xmit     $Search_1:8     $   nodedir = f$search("news_manager:ihave_*.dir",2)+     $   If nodedir .eqs. "" Then goto abort A     $   node = f$parse(nodedir,,,"NAME","SYNTAX_ONLY") - "IHAVE_"d:     $   senddir = "news_manager_dev:[ihave_" + node + "];",     $   savedfiles = senddir - ";" + "*.*;*"     $   node = node + "::;"h     $Search_2:%     $   file = f$search(savedfiles,3).+     $   If file .eqs. "" Then goto search_1o$     $   on error Then goto no_copy_2!     $   nntp_xmit 'node tcp 'filew     $   delete 'file     $No_copy_2:      $   goto search_2   H o If the VMS system does not feed to additional systems then no further H changes are necessary (i.e. the VMS system is a logical end-node in the E news network topology). However if the VMS system does relay network fI batches (i.e. a routing node with respect to the NEWS network), then you eK will need to modify the configuration file  NEWS_MANAGER:NEWS.DISTRIBUTION .K to ensure that news batches are forwarded correctly through this VMS  node h to all adjacent nodes.   Mail-based NEWS feedst  N The second approach  is based on the existence  on a mail link between the two systems.  N o On the VMS system  you will need to define  two mail destinations:  newsmailN   and rnews.   These  mail destinations  are used  by the Unix  system  as theN   default  mail destination  of forwarded  news batches.   If the news managerN   username  is NEWSMGR then the following  logical names need to be defined on   the VMS system:R  $     $ DEFINE/SYSTEM NEWSMAIL NEWSMGR!     $ DEFINE/SYSTEM RNEWS NEWSMGR.  + o The VMS NEWS.SYS file requires the entry:   8     unixnode:world,inet,arp,anu,canb,comp,sci,rec,news,\     misc,soc,talk,aus,alt:BN:\.     NEWS_MANAGER_DEV/[POST_UNIXNODE]NEWS.BATCH  N   The 'B' flag indicates  the news  item  texts  are to be stored  in the postN   area, and the 'N' transmission  flags indicate that the the mail format usesN   leading 'N' characters in the mail body to delineate the news batch from the   mail headers.N  N o In the Skim command  procedure  on VMS, the following  commands  need  to be   inserted:m       $Distribute:5     $    write sys$output "Copy items to other sites"w     $    set ont     $Search_1:8     $    nodedir = f$search("news_manager:post_*.dir",1)0     $    If nodedir .eqs. "" Then goto ExitlabelA     $    node = f$parse(nodedir,,,"NAME","SYNTAX_ONLY") - "POST_"t:     $    senddir = "news_manager_dev:[post_" + node + "];"-     $    savedfiles = senddir - ";" + "*.*;*"d     $    node = node + "::;"     $Search_2:&     $    file = f$search(savedfiles,2),     $    If file .eqs. "" Then goto Search_1%     $    on error then goto No_copy_2s*     $    mail 'file' in%"""rnews@"node'"""     $    delete 'file      $No_copy_2:s     $    goto search_2  G o On the Unix system an entry needs to be inserted in the aliases file:t  !     rnews: "|/usr/lib/news/uurec"f  N Variants of these approaches  are possible, such a mailing the 'ihave' list ofN message-ids  to the unix site,  and then having  the Unix  site  respond  withN 'sendme'  control  messages  back to the VMS system  using  mail (or any otherN means of message  transfer)  as the message  transport.   The comments  in theN distributed  version of NEWS.SYS contain additional information  on how to set  up such distribution mechanisms.