Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
$JDDETAILS - Display details summary of jobs z/OS JES2 Commands SA32-0990-00 |
|
FunctionTo display resource, sampling, and wait statistics for the JES2 address space being monitored. This command should be used to determine if a resource problem is impacting JES2. The first part of the display contains statistics on the major JES2 resources. The second part displays JES2 CPU sampling statistics. High sample counts with a status other than ACTIVE or IDLE might indicate a problem. The final section is the MVS™ wait table. The main task should not enter long MVS WAITs after initialization. Typically, waits indicate some resource that was not immediately available to JES2. The resource usage and CPU statistics are reset at the beginning of every hour. To view statistics for previous intervals use the $JD HISTORY command. Because the sampling is done without serialization, it is possible, in rare stations, that PCE and exit information in the wait table are inconsistent. It is also possible that the high and low utilization numbers might not reflect the highest and lowest actual utilization if the utilization spikes for a period of time shorter than the 1–second sampling interval . The $JDDETAILS command allows subscripts. Syntax>>-$JD--DETAILS--+--------------------+------------------------>< '-(--+-RESOURCE-+--)-' +-MAIN-----+ +-WAIT-----+ +-ERROR----+ '-STORAGE--' Authority RequiredThis command requires display authority. The description of the $T RDRnn command explains how to ensure that the authority of the appropriate MVS system command group is assigned. This command requires read security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide, SA32-0991. Processing ConsiderationsThe following
restrictions apply to all monitor commands. They:
The $JDDETAILS command supports subscripts
to limit the information that is being returned. If no subscript is
provided, JES2 will display all the information. The valid subscripts
are:
ScopeSingle Member. The response to this command will be a display of information about this member only. MessagesExamples
The WT-COUNT in the above $HASP9106 response is the number of distinct times this MVS wait was encountered. The SM-COUNT is the number of times the sampling task sampled this wait. For the first wait, it has a wait count of 4 and a sample count of 13. It waited an average of 3 sample intervals at this wait. The sample interval is about 1/20 of a second; therefore, this MVS wait lasted on average 3/20 of a second each of the 4 times it was encountered. In the MVS wait table, the PCE column can
contain one of the following:
In the MVS wait table, the XIT column can
contain one of the following:
|
Copyright IBM Corporation 1990, 2014
|