z/OS: OSDI NET Service and GTF Tracing (Doc ID 1210051.1)

Last updated on JULY 17, 2024

Applies to:

Goal

The OSDI Net Service STC on Z/OS has the ability to generate GTF trace
records to record pertinent information that may be useful in certain debugging
situations. The Net Service an has internal trace table 32KB in size, in which it records
events for debugging purposes, but this table will wrap when full, overwriting
earlier entries in the table. With GTF trace active, the trace table entries
are written out to a GTF trace dataset as well as to the internal trace table,
creating a complete chronological history of events. The performance overhead
of generating GTF trace records is minimal.

Please note that an OSDI Net Service GTF trace is NOT the same as a SQL*NET
trace generated by setting either TRACE_LEVEL_SERVER, TRACE_LEVEL_AGENT or TRACE_LEVEL_CLIENT in the SQLNET DD card of Z/OS OSDI Servers, Gateways or Clients.

Customers may be asked by Oracle Support Services to provide a GTF trace
from the OSDI Net Service started task, in order to help resolve a problem that they have
reported to Oracle Support Services. In the majority of problems, a GTF trace will not be needed.
However, there will be a small number of problems that cannot be
resolved without a GTF trace.

This article is written with the assumption that the reader understands the fundamentals of the Z/OS operating system, particularly the GTF feature.Having read this document, the reader should be able to accomplish the generation of a GTF trace by the OSDI Net Service without requiring any further intervention by Oracle Support Services.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.