During configuration, net$configure creates ASCII files of
    NCL commands, called NCL scripts, for each configurable
    entity.  Here are some startup scripts created by
    net$configure:

    NET$ALIAS_STARTUP.NCL            NET$APPLICATION_STARTUP.NCL
    NET$CSMACD_STARTUP.NCL           NET$DDCMP_STARTUP.NCL
    NET$DNS_CLERK_STARTUP.NCL        NET$DTSS_CLERK_STARTUP.NCL
    NET$EVENT_STARTUP.NCL            NET$FDDI_STARTUP.NCL
    NET$HDLC_STARTUP.NCL             NET$MODEM_STARTUP.NCL
    NET$MOP_CIRCUIT_STARTUP.NCL      NET$MOP_CLIENT_STARTUP.NCL
    NET$NODE_STARTUP.NCL             NET$NSP_TRANSPORT_STARTUP.NCL
    NET$OSI_TRANSPORT_STARTUP.NCL    NET$SEARCHPATH_STARTUP.NCL
    NET$SESSION_STARTUP.NCL

    As you can see, the script files are generally named as follows,
    where "entity_name" is almost always a module or entity:

    SYS$MANAGER:NET$entity_name_STARTUP.NCL

    If you need to customize the startup of network components
    further than net$configure allows, you must edit the appropriate
    script with a text editor and then execute it to save the
    changes until the next time you run net$configure.

    For example, say you wished to modify all the Event Dispatcher
    Sinks so that UIDs were no longer displayed in events.  This is
    not something you can easily configure the Event Dispatcher to
    do using net$configure.  (Refer to the DECnet-Plus Applications
    Installation and Advanced Configurations manual for more
    information regarding the script changes that net$configure can
    make.)  In order to make this change, you could add the ncl
    command "set event dispatcher sink * displayuids false" to the
    end of the SYS$MANAGER:NET$EVENT_STARTUP.NCL script, then
    re-execute that script, as in:

    NCL> @SYS$MANAGER:NET$EVENT_STARTUP.NCL

    This would make the change you requested.  However, the next
    time you run net$configure, depending upon what answers you
    provide, your customized NET$EVENT_STARTUP.NCL script could be
    replaced with a new script, essentially removing your changes.

    Before this could happen, however, net$configure would display
    a list of NCL scripts that had been manually modified and warn
    you that those customized scripts might be renamed to .NCL-OLD.
    If you then selected to have net$configure create a new
    NET$EVENT_STARTUP.NCL, you'd need to manually merge the
    customizations from the .NCL-OLD file into the new .NCL file.

    Maintaining customized scripts in this way could become
    cumbersome, so DECnet provides a method for retaining changes
    to certain scripts which users frequently customize.  DECnet
    allows you to permanently save any edits made to the following
    scripts by renaming those customized script files to local
    scripts:

    NET$EVENT_STARTUP.NCL       -> NET$EVENT_LOCAL.NCL
    NET$MOP_CLIENT_STARTUP.NCL  -> NET$MOP_CLIENT_LOCAL.NCL
    NET$APPLICATION_STARTUP.NCL -> NET$APPLICATION_LOCAL.NCL
    NET$SEARCHPATH_STARTUP.NCL  -> NET$SEARCHPATH_LOCAL.NCL

    At startup, if a NET$SEARCHPATH_LOCAL.NCL script is found, it
    is executed in lieu of the NET$SEARCHPATH_STARTUP.NCL script.
    If any local script exists for the EVENT, MOP_CLIENT, or
    APPLICATION entities, then that local script is executed
    immediately after the standard version of that script.  The
    advantage to using these local scripts is that they will remain
    unchanged when net$configure is run, even if you do choose to
    have net$configure modify the standard versions of those scripts.