Using Message Tracing
The procedure for using message tracing is as follows:
1.Enable message tracing.
2.Run the user program or generate NSARPA activity (for example, use NFT or FTP to copy a file). If you are debugging a user NetIPC program, use the NSINF P command to get the program's Global Socket Descriptor (GSDs).
3.When the program or activity terminates, halt tracing by running BRTRC.
4.Format and examine the trace file using FMTRC. If you are debugging a user NetIPC program, examine the socket level trace records for the program's GSDs. If you are debugging a program that used DS/1000IV Compatible Services, format RTR messages.
5.If you suspect a link problem, run tracing at two nodes and examine the network trace records at both ends of the link for symmetry.
NSTRC Scheduling
,N[ETWORK ]
[XQ,]NSTRC[,traceFile][,errorLog][,recordLength] ,S[OCKET] ,B[OTH]
traceFile | File to which you want NSTRC to write the trace records. |
| While NSTRC is executing, it writes the trace records to its |
| VMA partition. NSTRC writes to the partition in a circular |
| manner; if NSTRC has filled the partition, it overwrites the |
| earliest records. NSTRC uses approximately onefourth of the |
| trace file for accounting. For each remaining page in the |
| partition, NSTRC can write 10 trace records. Therefore, if |
| NSTRC's VMA partition is n pages long, NSTRC can write |
| approximately ( n * 3/4) * 10 trace records before it |
| must overwrite previous records. If you enter the name of an |
| existing file, NSTRC overwrites the existing file. If you use the |
| default traceFile and it already exists, NSTRC prints an |
| error message and terminates. |
| Default: NS_TRACE.TRC in the current working directory. |
errorLog | Device (file or device LU) to which you want NSTRC to report |
| runtime errors. |
| Default: local LU 1 (scheduling terminal). |
recordLength | The trace record length, in bytes. For network level tracing, the |
| trace record size is approximately the total size of all protocol |
| headers. If a message has more bytes than recordLength, |
| NSTRC truncates the message. |
| Range: 48 to 120 bytes. |
| Default: 60 bytes. |
144 Maintenance Utilities