>SET /LOWER=TI:
>ACD LINK TI: TO NUMBER CLE$EMACS
>SET /DEF=[137,10]
>@NETGEN
>;
>; =====================================================================
>;  NET - RSX-11M-PLUS CEX System Generation Procedure
>;        Started at 06:31:24 on 08-JUN-2019
>; =====================================================================
>;
>; Copyright (c) 1996,1997,1998 by Mentec, Inc., U.S.A.
>; All rights reserved
>;
>; Generate a CEX System, Version 04.06, for your RSX-11M-PLUS target system.
>;
>; The following CEX Products may be generated
>;	DECnet
>;
>; The distribution kits must be up  to  the  current  patch  level.   If
>; necessary, you should stop the  generation  and  apply  the  necessary
>; patches.
>;
>; The logical device name LB: should already be assigned to  the  device
>; which contains the library files for the system  you  are  generating.
>; These files are EXELIB.OLB, EXEMC.MLB,  RSXMAC.SML,  SYSLIB.OLB and
>; NOANSLIB.OLB for RSX-11M-PLUS and 11SLIB.OLB for RSX-11S.
>;
>; The logical device names IN:, OU:, LS: and MP: should not be  assigned
>; to any devices before starting the generation.  These  logical  device
>; names are used by NETGEN to refer to various  disks  used  during  the
>; generation.
>;
>;
>; <EOS>  Do you want to:
>*        <RET>-Continue, E-Exit [S]: 
>;
>;
>; ====================================================================
>;  NETGEN Disk contains NO DECNET AUTOPATCH corrections
>; ====================================================================
>;
>; =====================================================================
>;  NET - Section  1 - General Initialization
>; =====================================================================
>;
>* 01.00 Do you want to see the NETGEN notes/cautions [D=N]? [Y/N]: Y
>;
>; Note the following:
>; -------------------
>;
>; . If you have not already performed a SYSGEN for your  target  system,
>;   you must do so before continuing.
>;
>; . The  privileged  tasks  generated  during  NETGEN  use configuration
>;   dependent  parameters  produced  by  SYSGEN.   For  RSX-11M/S/M-PLUS
>;   systems, the RSXMC.MAC file and the RSX11M.STB (or RSX11S.STB)  file
>;   for the target system are necessary.   If they are  not  already  on
>;   the target device under the proper UIC, NETGEN will move  them  from
>;   the user's system device to the target device.
>;
>; . If your target device contains useful files, it is recommended  that
>;   you back it up before  continuing,  as  the  device  will  be  write
>;   enabled during the NETGEN sequence.
>;
>; . The proper system libraries for the target system  must  be  on  the
>;   logical device LB: under the UIC [system-group-number,1] while you
>;   are performing your NETGEN.  These libraries are:
>;
>;        EXELIB.OLB, EXEMC.MLB, RSXMAC.SML, and SYSLIB.OLB.
>;
>;   In addition, for an RSX-11S NETGEN, the 11SLIB.OLB file is required.
>;   In addition, for an RSX-11M-PLUS NETGEN,  the NOANSLIB.OLB  file  is
>;   required.
>;
>; . If your target system supports the Queue Manager (QMG), and you wish
>;   to generate network tasks which may use  this  facility,  the  Queue
>;   Manager object library must be  on  the  logical  device  LB:  under
>;   UIC [1,24] while you are performing your NETGEN.  This file is:
>;
>;	QMG.OLB
>;
>; . If you wish to generate network tasks which require support for  RMS
>;   file  access, you must have the RMS files on your logical LB: device
>;   prior  to  performing  your NETGEN. NETGEN will look for these files
>;   under the UIC determined by sysgen. The following are the files that
>;   NETGEN will look for:
>;
>;	RMSLIB.OLB, RMS11X.ODL and RMS12X.ODL.
>;	RMSRES.TSK and RMSRES.STB (if resident libraries are supported).
>;
>; . If  your  target  system  supports a Memory Resident or a Supervisor
>;   Mode  FCS  library,  and  you  wish  the  network  tasks to use this
>;   library,  the  FCS  library  files must be on the logical device LB:
>;   under  UIC  [1,1]  while you are performing your NETGEN. These files
>;   are:
>;
>;	FCSRES.TSK and FCSRES.STB (Memory resident FCS library files).
>;	FCSFSL.TSK and FCSFSL.STB (Supervisor Mode FCS library files).
>;
>; . The following installed tasks are required on your host system while
>;   you are performing your NETGEN:
>;
>;	PIP, LBR, and MAC for RSX-11M/S/M-PLUS NETGENs.
>;
>;   If these tasks are not already installed, and you are logged in as a
>;   privileged user, NETGEN will install them automatically.  If TKB and
>;   and  MAC  are  installed,  you may want to remove them and reinstall
>;   them with an increment of 3000. to 15000. bytes so the build section
>;   of NETGEN will run faster.
>;
>; . The following installed tasks are required on your host system while
>;   you are performing your NETGEN, under the following conditions:
>;
>;	LOA and UNL if device drivers require loading.
>;	MOU and DMO if disks require mounting.
>;	UFD if the required UICs do not already exist.
>;
>;   If these tasks are not already installed, and you are logged in as a
>;   privileged user, NETGEN will install them automatically.
>;
>; . NETGEN  will  not work with the small indirect command processor. If
>;   you  have  rebuilt  the indirect command processor and specified the
>;   ODL  for  the small indirect command processor, you must install the
>;   indirect  command  processor  that  was provided as output from your
>;   SYSGEN.
>;
>; . If  you  are  generating  more than one network onto the same target
>;   disk,  the  network  help  file ([1,2]NETHLP.ULB) and  the  language
>;   libraries  ([1,1]NETFOR.OLB and [1,1]NETLIB.MLB)  will  be  replaced
>;   each  time  NETGEN  is run.  You may want to save these files before
>;   doing  the next NETGEN. This is of particular interest if one of the
>;   networks  is  for  RSX-11S  and  the other network is for RSX-11M or
>;   RSX-11M-PLUS.
>;
>; . For questions that can be answered YES or  NO,  the  default  is  NO
>;   unless  otherwise  specified.   For questions with   defaults,   the
>;   default is  produced  by  pressing  a  carriage  return  (<RET>)  in
>;   response to the  question.
>;
>; . Additional explanatory text for each question  may  be  obtained  by
>;   hitting the ESCAPE key.
>;
>; . Unless otherwise specified, it is possible to interrupt a series  of
>;   questions by typing <CTRL/Z>.  You will then be  given  the  options
>;   of either restarting the section from the top, temporarily  stopping
>;   the generation, or terminating the generation.
>;
>* 02.00 Target system device [dduu, D=SY:] [S]: 
>* 03.00 Listing/map device [dduu, D=None] [S]: 
>* 04.00 UIC Group Code for NETGEN output [O R:1-377 D:5]: 
>;
>; Checking for required tasks and UICs.
>;
>* 05.00 Do you want to perform a component mode generation [D=N]? [Y/N]: N
>;
>; Saved responses were  detected.   These were compiled on 27-DEC-2018  at
>; 10:54:21 with a User ID of "".
>;
>; An earlier set  of  saved  responses  was  compiled  on  10-JUL-2016  at
>; 21:43:00 with a User ID of "Frodo PDP-11/83 Routing NETGEN".
>;
>* 06.01 Do you wish to use the later set of saved responses [D=N]? [Y/N]: 
>* 06.02 Do you wish to use the earlier set of saved responses [D=N]? [Y/N]: 
>; 07.00 User ID to be used to identify your new responses
>*       [D=None] [S R:0.-30.]: 11/70 Area Routing w/ IP dev
>* 08.00 Is this generation to be a dry run [D=N]? [Y/N]: N
>* 09.00 Do you want a standard function network [D=N]? [Y/N]: Y
>* 11.00 Should old files be deleted [D=N]? [Y/N]: N
>;
>; <EOS>  Do you want to:
>*        <RET>-Continue, R-Repeat section, P-Pause, E-Exit [S]: 
>;
>; =====================================================================
>;  NET - Section  2 - Define the target system
>; =====================================================================
>;
>* 01.00 Use the RSXMC.MAC on SY:[005,010] [D=N]? [Y/N]: 
>* 02.00 RSXMC.MAC location (ddu:[g,m], D=SY:[011,010]) [S]: 
>;
>; SY00:[011,010]RSXMC.MAC is being copied to SY:[005,010]RSXMC.MAC
>;
>; SY:[005,010]RSXMC.MAC is being scanned to define your target system.
>; This may take up to several minutes.
>;
>; The target is an RSX-11M-PLUS system, with...
>;	A 20K-Executive
>;	Kernel data space enabled
>;	Extended memory support (more than 124K words of memory)
>;	Multi-user protection
>;	Extended instruction set (EIS)
>;	Powerfail recovery support
>;	Dynamic task checkpoint allocation
>;	PLAS support
>;	Queue Manager (QMG) support
>* 03.00 Use the RSX11M.STB on SY:[005,054] [D=N]? [Y/N]: 
>* 04.00 RSX11M.STB location (ddu:[g,m], D=SY00:[001,054]) [S]: 
>;
>; SY00:[001,054]RSX11M.STB is being copied to SY:[005,054]RSX11M.STB
>;
>;
>; Checking for required library files and tasks.
>;
>* 05.00 Should tasks link to the Supervisor Mode FCS library [D=N]? [Y/N]: Y
>;
>; The DECnet CEX Product will be generated.
>;
>; Routing or non-routing nodes can be generated from your distribution kit.
>;
>;
>; <EOS>  Do you want to:
>*        <RET>-Continue, R-Repeat section, P-Pause, E-Exit [S]: 
>;
>;
>; =====================================================================
>;  NET - Section  3 - Define the system lines
>; =====================================================================
>;
>* 01.00 Device Driver Process name [<RET>=Done] [S R:0-3]: UNA
>* 02.00 How many UNA controllers are there [D R:1.-16. D:1.]: 
>;
>* 03.01 CSR address for UNA-0 [O R:160000-177777 D:174510]: 
>* 03.02 Vector address for UNA-0 [O R:0-774 D:120]: 
>* 03.03 Device priority for UNA-0 [O R:4-6 D:5]: 
>;
>* 04.07 Set the state for UNA-0 ON when loading the network [D=N]? [Y/N]: 
>;
>* 01.00 Device Driver Process name [<RET>=Done] [S R:0-3]: IP
>;
>; Warning - IP is not a supported Device Driver Process
>;
>* 01.01 Do you have a user written IP Device Driver [D=N]? [Y/N]: Y
>;
>; The following files are necessary.
>;
>; 1. The object module for the device driver (IP.OBJ) must be moved  to
>;    SY:[005,024].
>;
>; 2. The line table descriptor files (IP.DAT, IPLN.DAT, and IPST.DAT)
>;    must be moved to SY:[005,054].
>;
>; If these files have not yet been moved, you should pause and move them
>; at this time.
>;
>* 01.02 Is the IP a multiplexing device [D=N]? [Y/N]: Y
>* 01.03 Maximum number of lines per controller [D R:1.-64. D:8.]: 
>* 01.04 Is the IP a synchronous device [D=N]? [Y/N]: N
>* 01.06 Is the IP a Direct Memory Access device [D=N]? [Y/N]: N
>* 01.07 Does the IP Device Driver run at device priority[D=N]? [Y/N]: N
>* 01.08 Does the IP need software Line Protocol support [D=N]? [Y/N]: N
>* 01.09 Maintain network management counters for the IP [D=N]? [Y/N]: N
>* 01.11 Does IP require a Unit CSR [D=N]? [Y/N]: N
>* 01.13 Does IP require a seperate modem CSR [D=N]? [Y/N]: N
>;
>* 02.00 How many IP controllers are there [D R:1.-16. D:1.]: 1
>* 02.03 Will all the IP lines run at the same line speed [D=N]? [Y/N]: Y
>* 02.04 Line speed for the IP [D R:110.-9600. D:9600.]: 9600.
>* 02.05 Will all IP lines run as FULL duplex lines [D=N]? [Y/N]: Y
>;
>* 03.00 Number of lines used on IP-0 [D R:1.-8. D:1.]: 2
>* 03.01 CSR address for IP-0 [O R:160000-177777 D:177777]: 177574
>* 03.02 Vector address for IP-0 [O R:0-774 D:0]: 0
>* 03.03 Device priority for IP-0 [O R:4-6 D:5]: 5
>;
>* 04.02 Is IP-0-0 a DL11-E or equivalent device [D=N]? [Y/N]: N
>* 04.05 Will IP-0-0 use modem signal monitoring [D=N]? [Y/N]: N
>* 05.00 Is IP-0-0 multipoint [D=N]? [Y/N]: N
>;
>* 04.02 Is IP-0-1 a DL11-E or equivalent device [D=N]? [Y/N]: N
>* 04.05 Will IP-0-1 use modem signal monitoring [D=N]? [Y/N]: N
>* 05.00 Is IP-0-1 multipoint [D=N]? [Y/N]: N
>;
>* 01.00 Device Driver Process name [<RET>=Done] [S R:0-3]: 
>;
>;
>; <EOS>  Do you want to:
>*        <RET>-Continue, R-Repeat section, P-Pause, E-Exit [S]: 
>;
>;
>; =====================================================================
>;  NET - Section  4 - Define the CEX System
>; =====================================================================
>;
>; Creating build files for AUX, the CEX Auxillary routine.
>;
>; Creating build files for STCRC, the CRC16 calculation routine.
>;
>* 03.00 Does the target system have a KG-11 [D=N]? [Y/N]: 
>;
>; Creating build files for CETAB, the CEX configuration tables.
>;
>; Creating build files for the DDMs, the device driver modules.
>;
>;	UNA
>;	IP
>;
>;
>; <EOS>  Do you want to:
>*        <RET>-Continue, R-Repeat section, P-Pause, E-Exit [S]: 
>;
>;
>; =====================================================================
>;  NET - Section  5 - Define the Comm Exec Support Components
>; =====================================================================
>;
>; Creating build files for NTINIT, the network initializer.
>;
>; Creating build files for NTL, the network loader.
>;
>; Creating build files for MLD, the general microcode loader.
>;
>; Creating build files for EVL/EVC, the event logger and collector.
>;
>; EVL will use 6. event buffers.
>;
>; =====================================================================
>;  NET - Section  6 - Define the System Management Utilities
>; =====================================================================
>;
>; Creating build files for NCP, the network control program.
>;
>; Creating build files for NMVACP  and  NMDRV,  the  Network  Management
>; Volatile ACP and driver.
>;
>; Creating build files for CFE, the configuration file editor.
>;
>; Creating build files for NDA, the network dump analyzer.
>;
>; Creating build files for VNP, the virtual network control program.
>;
>; Creating build files for LOO, the loop test sender task.
>;
>; Creating build files for EVF, the event file interpreter program.
>;
>;
>; =====================================================================
>;  NET - Section  7 - Define the CEX Products
>; =====================================================================
>;
>; Questions concerning the following CEX Products will now be asked.
>;
>;	DECnet
>;
>;
>; =====================================================================
>;  DEC - DECnet CEX Product Generation Procedure
>;        Starting questions at 06:43:55 on 08-JUN-2019
>; =====================================================================
>;
>; Copyright (c) 1996,1997,1998 by Mentec, Inc., U.S.A.
>; All rights reserved
>;
>; Generate the DECnet CEX Product for your RSX-11M-PLUS target
>; System.
>;
>; =====================================================================
>;  DEC - Section  1 - Define the target and remote nodes
>; =====================================================================
>;
>* 01.00 What is the target node name [S R:0-6]: RSX11M
>* 02.00 What is the target node address [S R:0.-8.]: 30.12
>* 03.00 Target node ID [D=None] [S R:0.-32.]: PiDP-11/70 HECnet
>* 04.00 Do you want to generate a routing node [D=N]? [Y/N]: Y
>* 04.01 Do you want to generate a level 2 routing node [D=N]? [Y/N]: Y
>* 05.00 Highest node number in this area [D R:12.-1023. D:12.]: 15.
>* 05.01 Highest area number in network [D R:30.-63. D:30.]: 63.
>;
>; Extended  network  support for network command terminals and products
>; layered on DECnet, will be included.
>;
>* 07.00 Remote node name [<RET>=Done] [S R:0-6]: 
>;
>; The DECnet MACRO user library and FORTRAN/COBOL/BASIC+2  library  will
>; be included.
>;
>; The DECnet MACRO user library will  be  placed  on  your  target  disk
>; as "SY:[1,1]NETLIB.MLB".
>;
>; The DECnet FORTRAN/COBOL/BASIC+2 object library will be placed on your
>; target disk  as "SY:[1,1]NETFOR.OLB".
>;
>; If necessary, please move them to  the  library  disk  (LB:)  on  your
>; target system, if this is different from your target disk (SY:).
>;
>;
>; <EOS>  Do you want to:
>*        <RET>-Continue, R-Repeat section, P-Pause, E-Exit [S]: 
>;
>;
>; =====================================================================
>;  DEC - Section  2 - Define the DECnet Communications Components
>; =====================================================================
>;
>; Creating build files for XPT, the routing process.
>;
>; Creating build files for RCP, the routing event processing task.
>;
>; Creating build files for ECL, the network services process and driver.
>;
>; Creating build files for NETACP, the network services ACP.
>;
>; NETACP will be checkpointable.
>;
>; Creating build files for EPM, the Ethernet protocol manager process.
>;
>; =====================================================================
>;  DEC - Section  3 - Define the DECnet Network Management Components
>; =====================================================================
>;
>; Creating build files for NICE, the  network  information  and  control
>; server task.
>;
>; Creating build files for EVR, the network event receiver task.
>;
>; Creating build files for NTD, the node state display task.
>;
>; Creating build files for NTDEMO, the node state display server task.
>;
>; Creating build files for LIN, the link watcher task.
>;
>; Creating build files for MIR, the loop test mirror task.
>;
>; Creating build files for NVP, the network connect verification task.
>;
>; Creating build files for SCP, the node name server control task.
>;
>; Creating build files for NNC, the node name collector task.
>;
>; Creating build files for NNS, the node name server.
>;
>;
>; =====================================================================
>;  DEC - Section  4 - Define the DECnet Satellite Support Components
>; =====================================================================
>;
>* 02.00 Do you want the Satellite Support Components [D=N]? [Y/N]: Y
>;
>; Creating build files  for  DLL,  the  down-line  system  loader,  host
>; component.
>;
>; Creating  build  files  for  DUM,  the  up-line  system  dumper,  host
>; component.
>;
>; Creating  build files  for  CCR,  the  console carrier requester, host
>; component.
>;
>; Creating  build  files  for  HLD,  the  down-line  task  loader,  host
>; component.
>;
>; HLD will support 4 simultaneous incoming connections.
>;
>; To generate  the HLD database which describes the tasks  to  down-line
>; load, you may execute the HLDDAT.CMD command  procedure  at  any  time
>; after your network generation is complete.  This command file will  be
>; located as follows.
>;
>;	SY:[005,001]HLDDAT.CMD
>;
>;
>; <EOS>  Do you want to:
>*        <RET>-Continue, R-Repeat section, P-Pause, E-Exit [S]: 
>;
>;
>; =====================================================================
>;  DEC - Section  5 - Define the DECnet File Utilities
>; =====================================================================
>;
>; Creating build files  for  NFT, the network file access user task.
>;
>; Creating  build  files  for  FTS,  the  network  file  access  spooler
>; user task.
>;
>; Creating build files for FAL, the network file access server.
>;
>; FAL will support RMS file access.
>; FAL will be a multi-copy object.
>; FAL will not be overlaid.
>; FAL will use the memory resident RMS library.
>; FAL user data buffer size will be 2048 bytes.
>;
>; Creating build files for  MCM,  the  network  command  or  batch  file
>; submission server.
>;
>; MCM requests will be queued to BATCH.
>;
>; =====================================================================
>;  DEC - Section  6 - Define the DECnet Terminal and Control Utilities
>; =====================================================================
>;
>; Creating build files for RMT and RMTACP, the remote  network  terminal
>; task and ACP.
>;
>; The maximum number of simultaneous RMT users is 4.
>;
>; Creating build files for HT: and RMHACP, the remote  network  terminal
>; driver and ACP.
>;
>; RMHACP will support 4 simultaneous incoming connections.
>; HTDRV will support 4 HT: units.
>;
>; Creating build files for NCT, the network command terminal server
>;
>; Creating  build  files  for  RTH,  the  network  command terminal host
>; support.
>;
>; Creating build files for TLK, the remote talk user task.
>;
>; Creating build files for LSN, the remote talk server task.
>;
>; Creating build files for PHO, the inter-terminal conversation utility.
>;
>; Creating build files for LAT/LCP, the Local Area Transport terminal
>; service process and LAT Control Program
>;
>; Creating build files for TCL, the remote task control server task.
>;
>;
>; =====================================================================
>;  DEC - DECnet CEX Product Generation Procedure
>;        DECnet question/answer section completed at 06:46:41 on 08-JUN-2019
>; =====================================================================
>;
>;
>; =====================================================================
>;  NET - Section  8 - Complete the CEX System Definitions
>; =====================================================================
>;
>; Creating build files for DLX, the Direct Line Access process.
>;
>* 02.00 What is the Large Data Buffer (LDB) size [D R:576.-1484. D:576.]: 
>;
>; <EOS>  Do you want to:
>*        <RET>-Continue, R-Repeat section, P-Pause, E-Exit [S]: 
>;
>;
>; =====================================================================
>;  NET - Section  9 - Build the CEX System at 06:48:24 on 08-JUN-2019
>; =====================================================================
>;
>; All questions have now been asked and the selected components will now
>; be built.  This may take from one to three  hours,  depending  on  the
>; selection of components and the system you are running on.
>;
>;
>SET /UIC=[1,2]
>PIP OU:[1,2]NETHLP.ULB=IN:[1,2]NETHLPD.HLP
>PIP OU:[1,2]NETHLP.ULB/PU/NM
>SET /UIC=[005,024]
>;
>PIP OU:[5,54]/NV=IN:[3,54]RSXVEC.STB
>PIP OU:[5,54]/NV/CO=IN:[131,54]AUX.TSK
>PIP OU:[5,54]/NV=IN:[131,54]AUX.STB
>TKB @OU:[5,24]STCRCBLD.CMD
>MAC @OU:[5,24]CETABASM.CMD
>TKB @OU:[5,24]CETABBLD.CMD
>PIP OU:[5,54]/NV/CO=IN:[132,54]NTINIT.TSK
>PIP OU:[5,54]/NV/CO=IN:[132,54]NTL.TSK
>PIP OU:[5,54]/NV/CO=IN:[132,54]MLD.TSK
>PIP OU:[5,54]/NV=IN:[132,54]MLD.STB
>MAC @OU:[5,24]EVLASM.CMD
>TKB @OU:[5,24]EVLBLD.CMD
>PIP OU:[5,54]/NV=IN:[131,24]EVL.DAT
>TKB @OU:[5,24]EVCBLD.CMD
>PIP OU:[5,54]/NV/CO=IN:[135,54]NCPFSL.TSK
>MAC @OU:[5,24]NMVACPASM.CMD
>TKB @OU:[5,24]NMVACPBLD.CMD
>PIP OU:[5,54]/NV/CO=IN:[135,54]NMVACP.TSK
>PIP OU:[5,54]/NV=IN:[135,54]NMVACP.STB
>PIP OU:[5,54]/NV/CO=IN:[132,54]CFEFSL.TSK
>PIP OU:[5,54]/NV/CO=IN:[141,54]NDA.TSK
>PIP OU:[5,54]/NV/CO=IN:[132,54]VNP.TSK
>PIP OU:[5,54]/NV/CO=IN:[135,54]LOO.TSK
>PIP OU:[5,54]/NV=IN:[135,54]LOO.STB
>PIP OU:[5,54]/NV/CO=IN:[135,54]EVFFSL.TSK
>MAC @OU:[5,24]DLXASM.CMD
>TKB @OU:[5,24]DLXBLD.CMD
>PIP OU:[5,54]DLX.DAT/NV=IN:[131,24]DLX.DAT
>;
>TKB @OU:[5,24]UNABLD.CMD
>PIP OU:[5,54]/NV=IN:[131,24]UNA.DAT
>PIP OU:[5,54]/NV/CO=IN:[131,54]UNAMC.TSK
>PIP OU:[5,54]/NV/CO=IN:[131,54]DDHAR.TSK,DDHAR.STB
>TKB @OU:[5,24]IPBLD.CMD
>SET /UIC=[1,1]
>PIP OU:[1,1]NETLIB.MLB/NV=IN:[1,10]NETLIBU.MLB
>LBR OU:[1,1]NETFOR.OBS=IN:[133,24]DAPFOR/EX
>LBR OU:[1,1]NETTMP.OBS=IN:[133,24]DAPTRC/EX
>LBR OU:[1,1]NETFOR/CO:1:320.:192.=IN:[134,24]NETFOR.OLB
>LBR OU:[1,1]NETFOR/IN=OU:[1,1]NETFOR.OBS
>LBR OU:[1,1]NETFOR/IN/-EP=OU:[1,1]NETTMP.OBS
>LBR OU:[1,1]NETFOR/DG:$MBLUN:$ASTBL:$ASTLU
Entry points deleted:
$MBLUN
$ASTBL
$ASTLU

>PIP OU:[1,1]NETFOR.OBS;*/DE,NETTMP.OBS;*
>SET /UIC=[005,024]
>PIP OU:[005,024]/NV=IN:[137,24]NTEST.CMD
>SET /UIC=[005,054]
>PIP OU:[005,054]/NV/CO=IN:[133,54]DTS.TSK,DTR.TSK
>SET /UIC=[005,024]
>TKB @OU:[5,24]XPTBLD.CMD
>PIP OU:[5,54]XPT.DAT/NV=IN:[131,24]XPT.DAT
>TKB @OU:[5,24]RCP1BLD.CMD
>TKB @OU:[5,24]RCP2BLD.CMD
>MAC @OU:[5,24]ECLASM.CMD
>TKB @OU:[5,24]ECLBLD.CMD
>PIP OU:[5,54]ECL.DAT/NV=IN:[131,24]ECL.DAT
>PIP OU:[5,54]/NV/CO=IN:[135,54]PROXY.TSK
>TKB @OU:[5,24]NETACPBLD.CMD
>TKB @OU:[5,24]EPMBLD.CMD
>PIP OU:[5,54]/NV=IN:[131,24]EPM.DAT,EPMST.DAT
>PIP OU:[5,54]/NV/CO=IN:[135,54]NICE.TSK
>PIP OU:[5,54]/NV/CO=IN:[135,54]EVR.TSK
>PIP OU:[5,54]/NV/CO=IN:[135,54]NTD.TSK
>PIP OU:[5,54]/NV/CO=IN:[135,54]NTDEMO.TSK
>PIP OU:[5,54]/NV/CO=IN:[135,54]LIN.TSK
>PIP OU:[5,54]/NV/CO=IN:[135,54]MIR.TSK
>PIP OU:[5,54]/NV=IN:[135,54]MIR.STB
>PIP OU:[5,54]/NV/CO=IN:[132,54]NVPFSL.TSK
>PIP OU:[5,54]/NV/CO=IN:[165,54]SCPFSL.TSK
>PIP OU:[5,54]/NV/CO=IN:[161,54]NNCFSL.TSK
>PIP OU:[5,54]/NV/CO=IN:[162,54]NNDRV.TSK,NNDRV.STB,NNS.TSK,IN:[162,24]NNS.DAT
>PIP OU:[5,54]/NV/CO=IN:[135,54]DLLFSL.TSK
>PIP OU:[5,54]/NV/CO=IN:[136,54]SEC*.SYS,TER*.SYS
>PIP OU:[5,54]/NV/CO=IN:[135,54]DUM.TSK
>PIP OU:[5,54]/NV/CO=IN:[135,54]CCR.TSK
>TKB @OU:[5,24]HLDBLD.CMD
>PIP OU:[5,1]/NV=IN:[132,24]HLDDAT.CMD
>SET /UIC=[5,10]
>LBR OU:[5,10]HLDLIB/CR:1:0:64.:MAC=IN:[130,10]HLDTB.MAC
>TKB @OU:[5,24]NFTBLD.CMD
>SET /UIC=[5,24]
>MAC @OU:[5,24]FTSASM.CMD
>TKB @OU:[5,24]FTSBLD.CMD
>SET /UIC=[5,24]
>MAC @OU:[5,24]FALASM.CMD
>TKB @OU:[5,24]FALBLD.CMD
>TKB @OU:[5,24]MCMBLD.CMD
>MAC @OU:[5,24]RMTASM.CMD
>TKB @OU:[5,24]RMTBLD.CMD
>MAC @OU:[5,24]RMHACPASM.CMD
>TKB @OU:[5,24]RMHACPBLD.CMD
>PIP OU:[5,54]/NV/CO=IN:[140,54]TRXCTL.TSK
>PIP OU:[5,54]/NV/CO=IN:[140,54]TRXCOL.TSK
>TKB @OU:[5,24]NCTBLD.CMD
>PIP OU:[5,54]NCT.DAT/NV=IN:[140,24]NCT.DAT
>MAC @OU:[5,24]RTHASM.CMD
>TKB @OU:[5,24]RTHBLD.CMD
>PIP OU:[5,54]RTH.DAT/NV=IN:[140,24]RTH.DAT
>TKB @OU:[5,24]TLKBLD.CMD
>PIP OU:[5,54]/NV/CO=IN:[133,54]LSN.TSK
>PIP OU:[5,54]/NV/CO=IN:[133,54]PHONE.TSK
>SET /UIC=[1,2]
>PIP OU:[1,2]/NV=IN:[133,10]PHONEHELP.HLP
>SET /UIC=[5,24]
>PIP OU:[5,54]/NV/CO=IN:[135,54]LCPFSL.TSK
>PIP OU:[5,54]/NV/CO=IN:[131,54]LAT.TSK,LAT.STB
>PIP OU:[5,54]/NV/CO=IN:[131,54]LAT1.TSK,LAT1.STB
>PIP OU:[5,54]/NV/CO=IN:[131,54]LTD.TSK,LTD.STB
>PIP OU:[5,54]/NV/CO=IN:[131,54]LTD1.TSK,LTD1.STB
>PIP OU:[5,54]LAT.DAT/NV=IN:[131,24]LAT.DAT
>PIP OU:[5,54]LTD.DAT/NV=IN:[131,24]LTD.DAT
>MAC @OU:[5,24]TCLASM.CMD
>TKB @OU:[5,24]TCLBLD.CMD
>;
>; =====================================================================
>;  NET - Section 10 - Generation Clean Up
>; =====================================================================
>;
>; Creating NETCFG.TXT, the network configuration description file.
>; Creating NETCFE.CMD, the network configuration command file.
>; Creating NETINS.CMD, the network installation command file.
>; Creating NETREM.CMD, the network removal command file.
>;
>;
>; The network HELP file library has been placed on your target disk, as:
>;
>;	SY:[1,2]NETHLP.ULB
>;
>; This file should be moved to your target systems library device (LB:).
>;
>;
>; =====================================================================
>;  NET - RSX-11M-PLUS CEX System Generation Procedure
>;        Stopped at 06:49:04 on 08-JUN-2019
>; =====================================================================
>;
>@ <EOF>
>