1  –  IP_INTERFACE

    Directs PEdriver to start using the specified IP interface.

    Format

      START IP_INTERFACE  ipinterface

1.1  –  Parameter

 ipinterface[,...]

    Includes specific IP interfaces, which you can use wildcards to
    specify.

    o  Use the /EXCLUDE qualifier to exclude IP interfaces.

    o  Use the SHOW IP_INTERFACE command to display IP interfaces.

1.2  –  Qualifiers

1.2.1    /EXCLUDE

       /EXCLUDE=(ipinterface[,...])

    Excludes specific IP interface, which you can use wildcards
    to specify. Use the SHOW IP_INTERFACE command to display IP
    interface names.

1.3  –  Example

  SCACP> START IP_INTERFACE WE0

      This command starts PEdriver on the IP interface WE0.

2  –  LAN_DEVICE

    Directs PEdriver to start using the specified LAN device. The
    original (and still supported) way to start PEdriver on a LAN
    device is SYS$EXAMPLES:LAVC$START_BUS.

    Format

      START LAN_DEVICE  landevicename

2.1  –  Parameter

 landevicename[,...]

    Includes specific LAN devices, which you can use wildcards to
    specify.

    Use the /EXCLUDE qualifier to exclude LAN devices.

    Use the SHOW LAN_DEVICE command to display device names.

2.2  –  Qualifiers

2.2.1    /EXCLUDE

       /EXCLUDE=(landevicename[,...])

    Excludes specific LAN devices, which you can use wildcards to
    specify.

    Use the SHOW LAN_DEVICE command to display device names.

3  –  Example

  SCACP> START LAN_DEVICE EWA

      This command starts PEdriver on the LAN device EWA.

4  –  TRACE

    Starts or resumes PEdriver tracing, optionally setting tracing
    options.

                                   NOTE

       This command is reserved for use by HP Services and OpenVMS
       Engineering only. Trace commands, their qualifiers, and
       output are subject to change from release to release.

    Format

      START TRACE  nodename

4.1  –  Parameter

 nodename[,...]

    Includes information about communications with specific nodes,
    which you can use wildcards to specify. Each node name can be
    accompanied by optional qualifiers to specify local and remote
    device names.

    If no local or remote device name is specified, the VC and all
    channels associated with the specified node are included.

    Use the SHOW CHANNEL command to display node names and local and
    remote device names.

4.2  –  Qualifiers

4.2.1    /AFTER

       /AFTER=n

    After the trace stop condition has been satisfied, continues
    tracing for n events, and then stops. If you do not specify
    /AFTER, tracing does not continue after the trace stop event.
    n can be any value between 0 and FFFFFFF.

4.2.2    /DEFAULT

    Sets the trace context back to the default settings, which are:

           channelname=*
           /AFTER=0
           /EVENT=default settings
           /STOP
           /SIZE=512

4.2.3    /EVENT

       /EVENT=(event1[,...])

    Enables tracing on specific events, which you can use wildcards
    to specify. The default is a subset of the events, which includes
    most errors and state changes.

    Use the SHOW TRACE/CONTEXT command to display event names.

4.2.4    /EXCLUDE

       /EXCLUDE=(landevicename/IPinterface[,...])

    Excludes specific LAN devices/IP interfaces, which you can use
    wildcards to specify.

    Use the SHOW LAN_DEVICE/SHOW IP_INTERFACE command to display
    device names.

4.2.5    /LOCAL_DEVICE

       /LOCAL_DEVICE=(landevicename/IPinterface[,...])

    Includes specific LAN devices that identify the local end of
    the channel. You can use wildcards to specify LAN devices/IP
    interfaces.

    Use the SHOW LAN_DEVICE/SHOW IP_INTERFACE command to display
    device names.

4.2.6    /REMOTE_DEVICE

       /REMOTE_DEVICE=(landevicename/IPinterface[,...])

    Includes specific LAN devices that identify the remote end of
    the channel. You can use wildcards to specify LAN devices/IP
    interfaces.

    Use the SHOW LAN_DEVICE/SHOW IP_INTERFACE command to display
    device names.

4.2.7    /STOP

       /STOP=(event[,...])

    Stops tracing on specific events, which you can use wildcards to
    specify. The default is to stop no events.

    Use the SHOW TRACE/CONTEXT command to display event names.

4.2.8    /SIZE

       /SIZE=n

    Specifies a trace buffer size of n bytes to be used by PEdriver
    for each trace buffer: one for global PEdriver use, one for each
    selected channel, and one for each selected VC. n can be any
    value between 0 and FFFFFFF.

4.3  –  Examples

    1.SCACP> START TRACE/EVENT=CC_STATE/SIZE=2000

      The command in this example changes the Trace Channel Control
      layer state with a 2000-byte trace buffer.

    2.SCACP> START TRACE/EVENT=ALL NODE10,NODE20

      The command in this example traces all events but only for the
      NODE10 and NODE20 channels.