QDIOSYNC trace

The QDIOSYNC trace is not a traditional trace in which output is generated based on specific events. Instead, the QDIOSYNC trace freezes and captures (logs) OSA-Express2 or later diagnostic data in a timely manner. In addition to or instead of using the hardware management console (HMC) to manually capture the diagnostic data, you can arm the OSA-Express2 or later adapter to automatically capture diagnostic data when one of the following conditions occurs:

The adapter detects an unexpected loss of host connectivity. Unexpected loss of host connectivity occurs when the adapter receives an unexpected halt signal from the host or when the host is unresponsive to OSA requests. An unexpected halt signal includes VTAM® InOp traps (for example, ISTLLCIE InOpCode 101).
The adapter receives a CAPTURE signal from the host. A CAPTURE signal is sent by the host when one of the following conditions occurs:
- The VTAM-supplied message processing facility (MPF) exit (IUTLLCMP) is driven.
- Either the VTAM or TCP/IP functional recovery routine (FRR) is driven with ABEND06F. ABEND06F is the result of a SLIP PER trap that specifies ACTION=RECOVERY.
  Restriction: The SLIP must be a SLIP PER trap to specify ACTION=RECOVERY.

When arming an OSA-Express2 or later adapter for QDIOSYNC, you can specify an optional filter that alters what type of diagnostic data that the adapter collects. This filtering reduces the overall amount of diagnostic data collected and therefore decreases the likelihood that pertinent data is lost.

Arming an OSA-Express2 or later adapter has no effect on the host or OSA-Express2 or later performance. However, using a PER-type SLIP trap generally increases host CPU utilization.