
{
{      The purpose of this request is to define a local NAD and its
{ attributes.  One directive is required for each local NAD.
{
{ DEFINE_LOCAL_NAD, DEFLN(
{      nad, n: name = $required
{      address, a: integer 1..0FF(16) = $required
{      trunk_control_unit_0, tcu0: name = $optional
{      trunk_control_unit_1, tcu1: name = $optional
{      trunk_control_unit_2, tcu2: name = $optional
{      trunk_control_unit_3, tcu3: name = $optional
{      tcu_access_code_0, tac0: integer 0..0FFFF(16) = 0
{      tcu_access_code_1, tac1: integer 0..0FFFF(16) = 0
{      tcu_access_code_2, tac2: integer 0..0FFFF(16) = 0
{      tcu_access_code_3, tac3: integer 0..0FFFF(16) = 0
{      pp_drivers, pd: integer 1..2 = 1
{      perform_auto_reload, par: boolean = TRUE
{      reload_threshold, rt: integer 1..99 = 10
{      dump_disposition, dd: key DISCARD,SAVE_LAST,SAVE_ALL = DISCARD
{      maximum_connections, mc: integer 2..127 = 35
{      maximum_nad_entries, mne: integer 2..127 = 25
{      send_queue_limit, sql: integer 1..127 = 2
{      receive_queue_limit, rql: integer 1..127 = 2
{      monitor_trace, mt: integer 0..31 = 0
{      trunk_trace, tt: integer 0..31 = 0
{      device_trace, dt: integer 0..31 = 0)
{
{ nad:  This parameter is used to uniquely identify a local NAD
{   for this configuration file.  This name must match the name of
{   a NAD that is defined in the PHYSICAL_CONFIGURATION_UTILITY.
{   The actual verification of the name is done when the system
{   task activates the configuration.
{
{ address:  This parameter specifies the physical network
{   address of the local NAD.
{
{ trunk_control_unit_0(1,2,3):  These parameters uniquely identify
{   the trunks that are attached to each trunk control unit of this
{   local NAD.
{
{ tcu_access_code_0(1,2,3):  These parameters specify the software access
{   codes, which are used to control routing between the NADs.  Each
{   access code corresponds to the matching trunk control unit.  The
{   parameter values should normally be left set to zero.  See the 380-170 NAD
{   Hardware Reference Manual for further information on NAD access codes.
{
{ pp_drivers: This parameter specifies the number of pp drivers to drive
{   the local NAD.  For performance purposes (especially with 2XPP, i.e.
{   810 or 830 class machines) the site may wish to specify two PP drivers
{   to drive a local NAD.  If the PP utilization is a concern, then this
{   parameter should be set to 1 for each local NAD.
{
{ perform_auto_reload:  This parameter specifies whether the access
{   method is supposed to reload the NAD microcode when an
{   unrecoverable error condition is encountered.
{
{ reload_threshold:  This parameter specifies the number of microcode
{   reloads the access method should allow before declaring the device
{   unusable.  This parameter is not meaningful if the 'par' parameter
{   is FALSE.
{
{ dump_disposition:  This parameter specifies what disposition the access
{   method should use to dispose of the dump file that is generated
{   by the auto reload processing.  If DISCARD, the dump file will be
{   discarded.  If SAVE_LAST, the dump will be saved on a disk
{   file.  Only the most recent copy for this local NAD will be
{   preserved.  If SAVE_ALL, all dumps associated with this local NAD
{   will be preserved on disk until the reload threshold is reached or
{   cycle 999 has been used.  This parameter is not meaningful if
{   the 'par' parameter is FALSE.
{
{      Note - a file ($system.rhfam.nad_dumps.nad, where 'nad' is the name
{             of the local NAD) is created for each NAD dump performed.  Each
{             dump is an individual cycle of the file.
{
{ The remaining parameters are used to tailor the NAD microcode load.
{ These parameters are not meaningful if the 'par' parameter is FALSE.
{ A further explanation of these parameters can be obtained in Appendix
{ E in the 380-170 NAD Hardware Reference Manual (see references).
{
{ WARNING:
{   Changing any of the following parameters will probably impact the
{   performance of the NAD.
{
{ maximum_connections:  The purpose of this parameter is to define
{   the maximum number of concurrent connections that can be active
{   in this NAD at any instant.
{
{ maximum_nad_entries:  The purpose of this parameter is to define the
{   maximum number of remote NADs that this NAD can communicate with.
{
{ send_queue_limit:  The purpose of this parameter is to define the
{   maximum number of messages a connection may have queued, waiting
{   to be sent to the destination NAD, in this NAD.
{
{ receive_queue_limit:  The purpose of this parameter is to define the
{   the maximum number of messages a connection may have queued,
{   waiting to be received by the local host, in this NAD.
{
{ monitor_trace:  The purpose of this parameter is to define the number
{   of 32-word buffers to be used for the monitor trace.  A value of
{   zero means the trace is disabled.
{
{ trunk_trace:  The purpose of this parameter is to define the number
{   of 32-word buffers to be used for the trunk trace.  A value of
{   zero means the trace is disabled.
{
{ device_trace:  The purpose of this parameter is to define the number
{   of 32-word buffers to be used for the device trace.  A value of
{   zero means the trace is disabled.
{
