The following examples are intended to aid the user in gathering diagnostic information when required. Please refer to the IBM VSE/ESA Diagnosis Tools manual for detailed information

To trace I/O activity for a device in a VSE/ESA system, use the SDIO PROC, which is a standard IBM PROC in IJSYSRS.SYSLIB used for starting an IO/SIO Trace. Typical SDIO PROC statements follow:

The following example will trace 2 devices (320 and 321) and write the output to tape 280

// EXEC PROC=SDIO,UNIT=('320 321'),OUTPUT=('CCWD=256'),TAPE=280

The following example will trace a single device (320) and write the output to printer 00E  (printer output is not recommended)

// EXEC PROC=SDIO,UNIT=320,OUTPUT=('CCWD=256'),PRINTER=00E

To assist Bus-Tech Customer Support, submit a job to run the  SDIO PROC with parameters similar to the above examples. Tracing TCP/IP connections generally requires tracing a pair of subchannel addresses for each connection being analyzed. Tracing SNA connections requires tracing a single subchannel address for each VTAM PU being analyzed.

Note that the SDIO PROC actually traces 2 events: SIO and IO interrupts.

If you need to start SDAID from the AR console instead of using the SDIO PROC in a partition, you need to start each trace type one at a time (SIO and IO) and provide the unit addresses and type of output (tape or printer). The following example traces 2 subchannels and writes the output to a tape drive. Note the caps indicate what you type on the console.

SDAID

OUTDEV T=280  (output to tape address 280)

TRACE IO UNIT=(320 321) OUTP=CCWD=256    (specify the unit(s) traced and trace data for an IO trace)

TRACE SIO UNIT=(320,321),OUTP=CCWD=256 (specify the unit(s) traced and trace data for an SIO trace)

READY             (at this point, the trace is set up, but not yet running)

STRTSD            ( this command activates the trace or reactivates it after a STOPSD command)

at this point you should recreate the problem being traced

STOPSD            ( this command will pause tracing until a STRTSD command to issued - rarely used)

ENDSD              ( this command ends all tracing and closes the output device)

The following sample PROC shows how to print the SDAID trace from tape 280:

// EXEC DOSVSDMP

4                                  (in respose to prompt - print sdaid tape)

280                              ( in response to address of sdaid tape)

1                                   (file number - note: each STOPSD creates a separate file - rarely used)

SDAID traces may be quite large. We recommend that you spool the print output to the POWER LST queue. You can then retrieve it and download the file to a PC where it can be compressed using a utility such as PKZIP, and uploaded to our FTP site on the Internet. We would prefer receiving the trace this way, instead of by FAX or regular mail, if at all possible.

Alternatively, if the failure occurs infrequently, you should investigate using the BUFFER output option of SDAID. Again, please refer to the IBM VSE/ESA Diagnosis Tools manual.