Filtering NFS ctrace records in IPCS

The z/OS® NFS Ctrace function allows you to restrict the trace records to be processed by IPCS and displayed on the trace screen. Use the CTRACE DISPLAY PARAMETERS panel, shown in Figure 1, to do so.

Use the Component field to specify whether you want trace records for the NFS server or NFS client. Specify the name of the server or client as it appears in your start procedure. The example shown in Figure 1 uses MVSNFSC as the name of the NFS client.

Use the Options field to specify any of the following:

Nothing, in which case all records will be processed and displayed.
A specific list of record types to be processed and displayed. In this case, you can use shorthand record specifications (for example, CALL, TASK_FLOW), as well as the full-length record type names. All other record types will be filtered out and not displayed. Any invalid option values are ignored. If no valid options are specified, no trace records are displayed. Figure 1 shows an example of selecting only the BUFFER and USS (that is, USS_REQUEST and USS_RETURN) record types.
The value "PANEL" to display a filtering criteria panel, which provides another method of specifying options. If the Component field specifies the name of the NFS server, then the NFS Server Filtering Criteria panel (shown in Figure 2) is displayed. If the Component field specifies the name of the NFS client, then the NFS Client Filtering Criteria panel (shown in Figure 3) is displayed.

Figure 1. CTRACE Display Parameters panel

-------------------- CTRACE DISPLAY PARAMETERS  -------------------------------
COMMAND ===>                                                                   
                                                                               
  System      ===>           (System name or blank)                            
  Component   ===> MVSNFSC   (Component name (required))                       
  Subnames    ===>                                                             
                                                                               
  GMT/LOCAL   ===> G                        (G or L, GMT is default)           
  Start time  ===>                          (mm/dd/yy,hh:mm:ss.dddddd or       
  Stop time   ===>                           mm/dd/yy,hh.mm.ss.dddddd)         
  Limit       ===> 0         Exception ===>                                    
  Report type ===> FULL      (SHort, SUmmary, Full, Tally)                     
  User exit   ===>           (Exit program name)                               
  Override source ===>                                                         
  Options         ===> USS,BUFFER                                                 
                                                                               
  To enter/verify required values, type any character                          
  Entry IDs ===>   Jobnames ===>   ASIDs ===>   OPTIONS ===>   SUBS ===>       
                                                                               
  CTRACE COMP(MVSNFSC) FULL OPTIONS((REQ,BUF))                                 
                                                                               
                                                                               
  ENTER = update CTRACE definition.  END/PF3 = return to previous panel.       
  S = start CTRACE.  R = reset all fields.

If you specify the NFS server name in the Components field and PANEL in the Options field, then the NFS Server Filtering Criteria panel is displayed:

Figure 2. NFS Server Filtering Criteria

--------------------   NFS Server Filtering Criteria   ------------------------
COMMAND ===>                                                                   
------------------------------ o p t i o n s ----------------------------------
_ FFDC        | _ SCHEDULE    | _ INFO      | _ USS_REQUEST | _ LOCK_REQUEST   
_ ENTRY       | _ DISPATCH    | _ WARNING   | _ USS_RETURN  | _ LOCK_RESUME    
_ EXIT        | _ CB_MGMT     | _ ERROR     | _ DFP_REQUEST | _ LOCK_RELEASE   
_ SUSPEND     | _ NETWORK     | _ DETAIL    | _ DFP_RETURN  |                  
_ RESUME      | _ GENERAL     | _ TRAP      | _ BUFFER      |                  
--------------------- s u p e r   o p t i o n s ------------------------------
_ CALL (ENTRY+EXIT)                            | _ DEBUG1 (FFDC+ENTRY+EXIT)    
_ TASK_FLOW (SUSPEND+RESUME+SCHEDULE+DISPATCH) | _ DEBUG2 (DEBUG1+NETWORK)     
_ LOCK (LOCK_REQUEST+LOCK_RESUME+LOCK_RELEASE) | _ DEBUG4 (DEBUG2+TASK_FLOW+   
_ USS (USS_REQUEST+USS_RETURN)                 |           GENERAL)            
_ MVS (DFP_REQUEST+DFP_RETURN)                 |                               
                                                                               
---------- s e c o n d a r y    f i l t e r i n g    c r i t e r i a ----------
MODNAME  => ________   TASKNAME  => ________    FUNCNAME   => ________________
PREQBLK  => ________   REQID     => ________    OPERATION  => ________         
-------------------------------------------------------------------------------
Batch processing  => _ (Y/N)                                                   
-------------------------------------------------------------------------------
  ENTER = update Filtering Criteria definition.                                
  END/PF3 = return to previous panel.  S = start.   R = reset all fields.

If you specify the NFS client name in the Components field and PANEL in the Options field, then the NFS Client Filtering Criteria panel is displayed:

Figure 3. NFS Client Filtering Criteria

----------------------   NFS Client Filtering Criteria   ---- ENTER NEW VALUES
 COMMAND ===>                                                                   
 -----------------------------------------------------------------------------  
                 O P T I O N S                |    S U P E R O P T I O N S      
 -----------------------------------------------------------------------------  
 _ FFDC        | _ NFS_REQUEST | _ CB_MGMT    | _ CALL (ENTRY, EXIT)            
 _ ENTRY       | _ NFS_RETURN  | _ BUFFER     | _ TASK_FLOW (SUSPEND, RESUME,   
 _ EXIT        | _ USS_REQUEST | _ NETWORK    |            SCHEDULE, DISPATCH)  
 _ SUSPEND     | _ USS_RETURN  | _ GENERAL    | _ USS  (USS_REQUEST, USS_RETURN)
 _ RESUME      | _ LOCK_REQUEST| _ DETAIL     | _ NFS  (NFS_REQUEST, NFS_RETURN)
 _ SCHEDULE    | _ LOCK_RESUME | _ TRAP       | _ LOCK (LOCK_REQUEST,           
 _ DISPATCH    | _ LOCK_RELEASE| _ MSG        |       LOCK_RESUME, LOCK_RELEASE)
               |               |              |       
 -------------------------------------------------------------------------------
 MODNAME  => ________     PID       => ________  FUNCNAME  => ________________  
 PREQBLK   => ________    REQID     => ________  VNOP      => ________          
 RNODE    => ________     DIRRNODE  => ________  MNTINFO   => ________          
 -------------------------------------------------------------------------------
                       Buffer Filtering Criteria                                
 BNPTR    => ________     BNFLAG    => ___       BNNUM     => ________________  
 -------------------------------------------------------------------------------
 Batch processing  => N (Y/N)  
 -------------------------------------------------------------------------------

   ENTER = update Filtering Criteria definition.                                
   END/PF3 = return to previous panel.  S = start.   R = reset all fields.

Any combination of record types can be selected on the Options and Superoptions sections of the Filtering Criteria menus by putting an X or other character before the desired option. Within those record types, further selection filtering can be done based on the following criteria (on either Filtering Criteria panel):

FUNCNAME: 1 to 16 character name of a specific z/OS NFS server or client function for which trace records are to be displayed. This will limit the display to only trace records issued from within the selected function.
Note: Because function names are mixed case, but this parameter can not be specified in mixed case in all instances, the filter function will match the names regardless of case. For example, FUNC1 will match func1, Func1, FUNC1, and so on.
If the specified name ends in an asterisk, all function names starting with the specified string will be considered a match and will be selected. For example, FUN* will match FUNC1, function2, Funny, and so on. If the asterisk is the only character specified for FUNCNAME, all function names will be considered a match. The asterisk can be specified only on the right end of the string or as the only character in the string. No other wildcard variations are supported.
MODNAME: 1 to 8 character name of the z/OS NFS server or client module for which trace records are to be displayed. This will limit the display to only trace records issued from within the selected load module.
PREQBLK: 1 to 8 hexadecimal digit number representing the address of a specific request block for which trace records are to be displayed. Note that request blocks are reused.
REQID: 1 to 8 hexadecimal digit number representing a specific request for which trace records are to be displayed.

The following fields apply only to the NFS Server Filtering Criteria panel (Figure 2):

OPERATION: Four-byte, 8-character, hexadecimal representation of the NFS V2 or V3 request, or V4 operation, for which trace records are to be displayed. For example, 0xFFFFFF60.
TASKNAME: 1 to 8 character name of the z/OS NFS server task for which trace records are to be displayed. This will limit the display to only trace records issued from within the selected task.

The following fields apply only to the NFS Client Filtering Criteria panel (Figure 3):

DIRRNODE

1 to 8 hexadecimal digit number representing the address of a specific parent directory rnode associated with the trace records to be displayed.

MNTINFO

1 to 8 hexadecimal digit number representing the address of a specific mount info block associated with the trace records to be displayed.

PID

1 to 8 hexadecimal digit number representing the process id of the z/OS NFS client process for which trace records are to be displayed.

RNODE

1 to 8 hexadecimal digit number representing the address of a specific rnode associated with the trace records to be displayed.

VNOP

1 to 8 character name of the vnode/vfs operation (for example, vn_rdwr) for which trace records are to be displayed. Only a single vnode/vfs operation name can be specified.

Buffer record types

For BUFFER record types on the client filtering panel, several additional selection criteria are available. These criteria are ignored if no buffer records are selected.

BNNUM: 1 to 16 hexadecimal digit number representing a specific buffer associated with the BUFFER trace records that are to be displayed.
BNFLAG: 3 bit flag field associated with the BUFFER trace records that are to be displayed. This value is treated as a mask for identifying buffers whose selected bits are on.
BNPTR: 1 to 8 hexadecimal digit number representing the address of a specific 8K buffer associated with the BUFFER trace records that are to be displayed.

Note:

If multiple criteria are specified, records matching any of the record type options and all of the other specified criteria are considered to be a match and are selected.
Any of these secondary options can be specified on the IPCS Ctrace Display Parameters panel OPTIONS list if one of the Filtering Criteria panels is not being used.