You can use component tracing to gather information for diagnosis when recreating prior problems related to the z/OS® NFS client. To do so, follow these steps:

1. Have an operator issue a TRACE CT command, as described in Starting component tracing for the z/OS NFS client. Specify individual trace options on the command, or OPTIONS=All to include all trace types.
2. Recreate the reported problem. After the problem is recreated, disable tracing with the following command at the operator console:

   TRACE CT,OFF,COMP=MVSNFSC

   which will convert the NFS server to MIN state of tracing.
3. Create an MVS™ dump
   To create a dump of the an NFS client address space and associated data space, enter the following command at the operator console:

   DUMP COMM=(any dump description title you choose)

   In response to operator message *nn IEE094D SPECIFY OPERAND(S) FOR DUMP COMMAND, reply with:

   R nn,JOBNAME=(MVSNFSC),DSPNAME=('MVSNFSC'.NFSCTRDS),CONT 
   R nn,SDATA=(LPA,CSA,ALLNUC,GRSQ,LSQA,SWA,PSA,SQA,TRT,RGN,SUM)

   To include NFS component trace records in an SVC dump, specify the associated data space name 'MVSNFSC'.NFSCTRDS on the MVS DUMP command. The value of MVSNFSC represents the client's procedure name.

   You can now use the IPCS command CTRACE COMP(MVSNFSC) FULL to look at the trace records, where the default data set has been set to a captured dump data set. NFS provides both IPCS exits and format tables to facilitate this activity.