Starting OSAENTA trace

You can start an OSAENTA trace in one of the following ways:

Using the V TCPIP,,OSAENTA command

V TCPIP,tcpprocname,OSAENTA,ON,PORTNAME=OSA4,IPADDR=9.1.27.2

Using the OSAENTA statement in TCPIP.PROFILE
```
OSAENTA ON PORTNAME=OSA4 IPADDR=9.1.27.2
```

Security Rule: To use any VARY command, the user must be authorized in RACF®. The OPERCMDS RACF profile for each user must have access for a resource of the form MVS™.VARY.TCPIP.OSAENTA.

Traces are placed in an internal buffer, which can then be written out using a CTRACE external writer. The MVS TRACE command must also be issued for component SYSTCPOT to activate the OSAENTA trace.

After starting OSAENTA trace, you can display the status using the Netstat command, as shown in the following example:

D TCPIP,TCPCS,NETSTAT,DEV
  DEVNAME: OSA4              DEVTYPE: MPCIPA                          
    DEVSTATUS: READY                                                  
    LNKNAME: LOSAFE            LNKTYPE: IPAQENET   LNKSTATUS: READY   
.
.
.
OSA-Express Network Traffic Analyzer Information:
  OSA PortName: OSA4              OSA DevStatus:     Ready
    OSA IntfName: EZANTAQDIO4101  OSA IntfStatus:    Ready
    OSA Speed:    1000            OSA Authorization: Logical Partition
    OSAENTA Cumulative Trace Statistics:
      DataMegs:   0                     Frames:          8
      DataBytes:  760                   FramesDiscarded: 4
      FramesLost: 0
    OSAENTA Active Trace Statistics:
      DataMegs:   0                     Frames:          8
      DataBytes:  760                   FramesDiscarded: 4
      FramesLost: 0                     TimeActive:      8
    OSAENTA Trace Settings:           Status: On
      DataMegsLimit: 1024               FramesLimit:     2147483647
      Abbrev:        224                TimeLimit:       10080
      Discard:       ALL
    OSAENTA Trace Filters:            Nofilter: ALL
      DeviceID: *
      Mac:      *
      VLANid:   *
      ETHType:  *
      IPAddr:   *
      Protocol: *
      PortNum:  *

If you are a TSO user, use the NETSTAT DEVlinks command.