OSI/AS SCF Reference Manual

OSI/AS SCF Commands
OSI/AS SCF Reference Manual—424121-001
2-233
Considerations for the TRACE Command
TO file-spec
specifies the file to which trace information is to be written. The file might have
been previously created as an unstructured file with file code 830. An old file is
purged of data before the trace is initiated. If the file does not exist, SCF creates the
file with an extent size of 100 pages for the primary extent and 20 pages for
secondary extents. There are a maximum of 15 secondary extents for a maximum
file size of 400 pages. If a file larger than 400 pages is needed, use a previously
created file.
WRAP
specifies that when the trace disk file end-of-file (EOF) is reached, trace data will
wrap around to the beginning of the file and overwrite any data that is there. The
default is “NOWRAP.”
Considerations for the TRACE Command
The considerations contain information about command use that should be read before
studying the command syntax in too much detail.
PROCESS Object
•
The OSI/AS subsystem supports the TRACE command for OSI manager and TAPS
processes. For TSP processes, use the TRACE command, described in the OSI/TS
SCF Reference Manual. For NSP processes, see the SCF Reference Manual for
X25AM, the TCP/IP Configuration and Management Manual, or the SCF Reference
Manual for Multilan/TLAM (for D-series releases) or the PAM Configuration and
Management Manual (for G06 and later releases).
•
The default value for RECSIZE (128 bytes) may not be adequate to allow complete
formatting of trace records by the PTrace program. If RECSIZE is not set large
enough, the trace displays will be truncated and trace run will need to be repeated.
The RECSIZE parameter specifies the maximum size of trace record captured. The
size of trace record required for a TAPSOBJ trace depends on APS user requests and
segmenting performed by session. The maximum size of user request is 30,000
bytes but this can be reduced in some cases by adjusting the MAXCONNECTIONS
attribute. Data read from transport will never exceed 1,500 bytes but all PDUs
except data will be reassembled before moving up the stack. The maximum size a
reassembled PDU can reach is 12,000 bytes.
If any of the following keywords are selected, specify a RECSIZE from 1,000
through 4,050 bytes:
ALL (traces session connections)
L5
L5PROV
L5SM
L5USER