Using GTF tracing for further diagnosis of catalog performance problems

You may also find the following information helpful for diagnosing catalog performance problems:

Collect GTF trace data from the User and Catalog address space for DSP,SVC=(19,20,26,48,56,99) and set the following SLIP:

SLIP SET,IF,JOBNAME=jjjjj,ACTION=TRACE,LPAMOD=(IGC0002F,xxx),
        TRDATA=(STD,REGS,
        12R?+278?,+14,                    <===CAMLST
        12R?+278?+4?,+2C,                 <===ENTRY NAME
        12R?+270?,+1C,                    <===CTGPL
        11R?+CD4?,+1000,                  <===GFL workarea
        12R?+270?+4?,+2C,                 <===ENTRY NAME
        12R?+260,+263),END                <===CATMAN RC/RSN
        Where: jjjjj = the batch jobname or TSO userid
               xxx = the offset of procedure RESMCNTL in module
                     IGC0002F which is X'71A' for all current
                     releases of DFSMS (z/OS 1.7 thru 1.10).

Now, start GTF with the following options:

TRACE=SLIP,DSP,SVCP,JOBNAMEP

when prompted for a reply, enter:

R XX,SVC=(19,20,26,48,56,99),JOBNAME=(JJJJ,CATALOG),END.

Examine the time from the start of the SVC26 until the instruction fetch entry. The time for that should be in the range of 10-15 milliseconds.

Collect GTF trace data with CCW data for the device where the Catalog resides. In the trace data you may see multiple reads to the VVDS, which is normal, or you may see continual re-reading of the same BCS record, which indicates a problem.