Library /sys$common/syshlp/HELPLIB.HLB  —  LANCP  SET  DEVICE  Qualifiers (General)

1    /ALL

    Sets data for all LAN devices. If you specify a device name, all
    matching LAN devices are selected, for example: E to select all
    Ethernet devices, F for FDDI, I for Token Ring, EW to select all
    Ethernet PCI Tulip devices.

2    /DEVICE_SPECIFIC

       /DEVICE_SPECIFIC=(FUNCTION="xxxx",VALUE=(n1,n2,n3...n16))
       /NODEVICE_SPECIFIC

    Allows some device-specific parameters to be adjusted. These
    are useful for debug purposes or for experiments while doing
    performance measurements. Like other LANCP commands which affect
    devices, this command requires SYSPRV privilege.

    Specify the negated qualifer to clear all device-specific
    parameter data.

    These functions are described in a text file on the system,
    SYS$HELP:LAN_COUNTERS_AND_FUNCTIONS.TXT.

3    /DLL

       /DLL or MOPDLL=(enable-option, exclusive-option, size-option,
       knownclientsonly-option)

    Provides the MOP downline load service settings for the device.

    Note that defaults apply to creation of an entry in the device
    database. If an existing entry is being modified, fields not
    specified remain unchanged.

    You can specify the following keywords with this qualifier:

    o  enable-option

             ENABLE
             DISABLE (default)

       Specify ENABLE or DISABLE to indicate that MOP downline load
       service should be enabled or disabled for the device.

    o  exclusive-option

             EXCLUSIVE
             NOEXCLUSIVE (default)

       Specify EXCLUSIVE to indicate that no other provider of MOP
       downline load service is allowed on the specified LAN device
       at the same time as LANACP. Specify NOEXCLUSIVE to indicate
       that the LAN MOP downline load service can coexist with other
       implementations (in particular, the DECnet Phase IV and DECnet
       Plus implementations that include MOP support).

       Note that when you select NOEXCLUSIVE, LANACP responds only
       to MOP downline load requests directed to nodes defined in the
       LAN node database.

    o  size-option

             SIZE=value

       Use SIZE=value to specify the size in bytes of the file data
       portion of each downline load message. The permitted range
       is 246 to 1482 bytes. The default value is 246 bytes, which
       should allow any client to load properly. Note that some
       clients may not support the larger size.

       The recommended size for better load performance and less
       server overhead is the largest size that results in successful
       loads of all clients. The 1482 value is derived from the
       maximum packet size for CSMA/CD (Ethernet) of 1518 bytes less
       the 802e header and CRC (26 bytes) and MOP protocol overhead
       (10 bytes).

       You can override the size on a per-node basis. See the SET
       NODE commands for details.

    o  knownclientsonly-option

             KNOWNCLIENTSONLY
             NOKNOWNCLIENTSONLY (default)

       Specify KNOWNCLIENTSONLY to indicate that MOP downline
       load requests should be serviced only for clients defined
       in the LAN permanent node database. When you select
       NOKNOWNCLIENTSONLY, LANACP searches the LAN$DLL directory
       for any images requested by clients that are not defined in
       the LAN node database.

       Note that this option is not available when NOEXCLUSIVE mode
       has been selected. When NOEXCLUSIVE mode is selected, LANACP
       services MOP downline load requests only for clients defined
       in the LAN node database.

4    /MAX_BUFFERS

       /MAX_BUFFERS=value

    Sets the maximum number of receive buffers to be allocated and
    used by the LAN driver for the LAN device.

5    /MIN_BUFFERS

       /MIN_BUFFERS=value

    Sets the minimum number of receive buffers to be allocated and
    used by the LAN driver for the LAN device.

6    /PERMANENT

       /PERMANENT (SET DEVICE only)

    Updates the device entries in the LAN volatile device database
    with any data currently set in the permanent database. This
    allows you to update the volatile database after changing data
    in the permanent database, rather than repeating the commands for
    each updated entry to apply the changes to the volatile database.

7    /TAG

       /TAG=value

    Specifies the IEEE 802.1Q tag for the VLAN device.
    value is the IEEE 802.IQ tag number.

8    /TRACE

       /TRACE=size-option, mask-option, stop-option
       /NOTRACE

    Provides the LAN driver trace settings for the device. By
    default, most LAN drivers do tracing of error conditions and
    state changes. Tracing is controlled by an event mask that
    selects the events to trace, a stop mask that specifies when
    to stop tracing, and the size of the trace buffer.

    You can change tracing settings at any time. The LAN driver
    allocates the trace buffer from non-paged pool. You can calculate
    the amount of pool needed by multiplying the number of entries by
    the size of each entry, 32-bytes.

    The impact of tracing on the system is negligible for error
    and state change events, more significant when all events are
    selected, and very significant when full packet tracing is
    enabled.

    The command SHOW DEVICE/TRACE displays trace results as well as
    the trace mask.

    You can specify the following keywords with this qualifier:

    o  size-option

             SIZE=value

       Use SIZE=value to specify the size of the trace buffer in
       entries, each 32 bytes. The default is 2048 entries. The
       permitted range is 256 to 1000000.

       The size MOD 3 encodes the amount of packet data to include,
       either 35 bytes, 66 bytes, 97 bytes, or the entire packet.

    o  mask-option

             MASK=(value1,value2)

       Use MASK=(value1,value2) to specify the trace mask to select
       which type of entries should be collected in the trace
       buffer. The first 32 bits consist of events common to most
       LAN drivers. The second 32 bits consist of events specific to
       the LAN driver for the specified device.

    o  stop-option

             STOP=(value1,value2)

       Use STOP=(value1,value2) to specify the trace mask to select
       which type of entries should stop tracing. When a trace entry
       is made that matches one of the bits in the stop mask, the
       trace mask is cleared so that you can look at the trace data
       accumulated so far.

9    /UPDATE

       /UPDATE (DEFINE DEVICE only)

    Adds LAN devices that are not currently in the LAN permanent
    device database to that database. The initial entry for the
    device uses default values for all parameters. To update the
    permanent database with current information from the volatile
    database, use the DEFINE DEVICE command with the /VOLATILE
    qualifier. You can combine the /UPDATE and /VOLATILE qualifiers
    in a single DEFINE DEVICE command.

10    /UPDATE

       /UPDATE (SET DEVICE only)

    Adds LAN devices that are not currently in the LAN volatile
    device database to that database. The initial entry for the
    device uses default values for all parameters. To update the
    volatile database with current information from the permanent
    database, use the SET DEVICE command with the /PERMANENT
    qualifier. You can combine the /UPDATE and /PERMANENT qualifiers
    in a single SET DEVICE command.

11    /VLAN_DEVICE

       /VLAN_DEVICE=device-name
       /NOVLAN_DEVICE

    Specifies the physical LAN device that is to host the VLAN
    device. The /NOVLAN_DEVICE qualifier requests deactivation of
    the VLAN device.

    When deactivating the VLAN device, the device-name is not
    required because the VLAN driver knows which device is hosting
    the VLAN device.

    Note that a VLAN device cannot be deactivated if any applications
    continue to use the device.

12    /VOLATILE

       /VOLATILE (DEFINE DEVICE only)

    Updates the device entries in the LAN permanent device database
    with any data currently set in the volatile database. This allows
    you to update the permanent database after changing data in the
    volatile database, rather than repeating the commands for each
    updated entry to apply the changes to the permanent database.
Close Help