z/OS Network File System Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Starting component tracing for the z/OS NFS server

z/OS Network File System Guide and Reference
SC23-6883-00

To start recording diagnostic information for the z/OS NFS server in z/OS component trace buffers, follow these steps:

  1. Decide on the trace options to use. These can be in a CTINFSnn member of SYS1.PARMLIB to be specified on the TRACE CT command, or individual options to be specified when prompted in response to the TRACE CT command. Note that if TRACEOPTS OFF is used, no other TRACEOPTS value can be specified. See z/OS MVS Initialization and Tuning Reference for further information.
  2. From the master console or another console with master authority, issue the TRACE CT command as follows:
Read syntax diagramSkip visual syntax diagram
>>-TRACE CT,ON,COMP=--mvsnfs--+----------------+---------------><
                              '-,parm=CTINFSnn-'   

where
mvsnfs
Specifies the name of the procedure in your system PROCLIB used to start up the server.
parm=CTINFSnn
Specifies that diagnostic information for the NFS server be recorded in z/OS component trace buffers using trace options specified in member CTINFSnn of SYS1.PARMLIB. To use the default trace options for the z/OS NFS server, specify parm=CTINFS00 for the default SYS1.PARMLIB member CTINFS00.
If you do not specify a CTINFSnn PARMLIB member on the CTRACE CT command, the following message will prompt you to enter trace operands:
* id ITT006A SPECIFY OPERAND(S) FOR TRACE CT COMMAND.
In response to the message, reply with the identification number id from the message, an external writer program if any to receive the records, and a trace option or options to use from the list shown later in this section. Here is the response syntax:
Read syntax diagramSkip visual syntax diagram
>>-R(eply)--id--OPTIONS=--(name,name...)------------------------>

>--+----------------------+--+-,CONT-+-------------------------><
   '-,WTR=-+-procname---+-'  '-,END--'   
           '-DISCONNECT-'                

where:
id
Specifies the identification number from the ITT006A message.
name,name...
Specifies a trace option or options for tracing NFS server records. The possible options are:
Buffer
Buffer Management (that is, BUFNODE)
CB_Mgmt
Control Block Management (creation, initialization, modification, deletion).
Detail
Detailed Trace Record. This is used for low level debug.
DFP_request
Call to MVS data set system function.
DFP_return
Return from MVS data set system function.
Dispatch
NFS Client worker thread posts results back to Cross memory thread.
Entry
Entry into a function
Error
Existing NFS Trace Error Record. This option is on by default and cannot be turned off.
Exit
Exit from a function.
FFDC
First Failure Data Capture. This option is on by default and cannot be turned off.
General
General Trace Record.
Info
Existing NFS Trace Info Record.
Lock_Release
Control Block Lock Release
Lock_Request
Control Block Lock Requests
Lock_Resume
Control block lock request resumes after lock request either succeeds or fails.
Network
Network communication related trace.
Resume
Cross memory thread receives result from NFS Client worker thread and resumes processing, or NFS worker thread receives work for processing
Schedule
Cross memory thread sends work to NFS Client worker thread and continues processing in parallel.
Suspend
Cross memory thread sends work to NFS Client worker thread and waits for result, or NFS worker thread waits for work.
Trap
For use in special temporary trap code created to aid in the analysis of a problem.
USS_request
Request issued to z/OS UNIX System Services.
USS_return
Returned from z/OS UNIX System Services request.
Warning
Existing NFS Trace Warning Record.
In addition to these basic options, you can also enter the following shorthand values to specify multiple record types:
All
All existing NFS trace records.
Call
Entry and Exit record types.
Debug1
FFDC, Entry and Exit record types.
Debug2
FFDC, Entry, Exit and Network record types.
Debug4
FFDC, Entry, Exit, Network, Suspend, Resume, Schedule, Dispatch and General record types.
Debug9
All existing NFS trace records (equal to All).
Lock
Lock_Req, Lock_Result and Lock_Release record types
MVS
DFP_Request and DFP_Return record types.
NFS
NFS_Req and NFS_Rtn record types.
Task_Flow
Suspend, Resume, Schedule and Dispatch record types.
USS
USS_Request and USS_Return record types.
Note:
  1. An option can be turned off by preceding the option value with a minus sign (for example, OPTIONS=(-GENERAL) ).
  2. Options are processed from left to right, first processing all values to turn on options and then processing all values to turn off options. Thus all options except Network can be turned on with the following options specification: OPTIONS=(ALL, -NETWORK). If an options value of " -ALL" is specified, the options revert back to a minimum trace state .
  3. A minimum trace state has been defined, which will be the default initial trace state and will also be the trace state that takes effect if "all" trace states are turned off. In this "MIN" state, ERROR and FFDC record tracing will remain active. They cannot be deactivated. Neither MIN nor -MIN can be specified in the OPTIONS list.
WTR=procname|DISCONNECT
Connects or disconnects the component trace external writer and the trace. procname identifies the name of the member that contains the source JCL that invokes the external writer. The member can be a SYS1.PROCLIB cataloged procedure or a job. The procname in the WTR parameter must match the procname in a previous TRACE CT,WTRSTART command.

WTR=DISCONNECT disconnects the writer and the trace. The component continues tracing and placing the trace records in the address-space buffer, but stops passing trace records to the external writer.

You must also specify a TRACE CT,WTRSTART or TRACE CT,WTRSTOP command to start or stop the writer.

CONT or END
Specifies that the reply continues on another line. The system reissues the same prompting message. You then can continue the reply. You can repeat any parameters on the continuation line, except END. Repeated parameters are strung together. They do not overlay each other. You must specify END to complete the response. END identifies the end of the REPLY.
Note: It is no longer necessary to use the flushctr option on the Modify command to flush the last buffer being filled to the component trace before the external writer is stopped or before a dump is taken. This function is now done automatically when the Component Trace external writer is stopped.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014