Temporary storage: Summary global statistics
Temporary storage summary global statistics are not available online.
| DFHSTUP name | Description |
|---|---|
| Put/Putq main storage requests | The number of records that application
programs wrote to main temporary storage.
|
| Get/Getq main storage requests | The number of records that application
programs obtained from main temporary storage.
|
| Current TSMAINLIMIT setting | The current limit for the amount
of storage that CICS® makes
available for data in main temporary storage.
|
| Times at TSMAINLIMIT | The number of times that main
temporary storage use attempted to exceed the limit for the amount
of storage allowed for data.
|
| Peak storage used for TSMAINLIMIT | The peak amount of storage that
was used for data in main temporary storage.
|
| Number of queues auto deleted | The number of temporary storage queues that CICS has deleted automatically by using the clean up task.
|
| Count of clean up task runs | The number of times that the clean up task, which deletes
eligible temporary storage queues automatically, has run.
|
| Put/Putq auxiliary storage requests | The number of records that application
programs wrote to auxiliary temporary storage.
|
| Get/Getq auxiliary storage requests | The number of records that application
programs obtained from auxiliary temporary storage.
|
| Peak temporary storage names in use | The peak number of temporary
storage queue names in use at any one time.
|
| Number of entries in longest queue | The peak number of items in any
one temporary storage queue, up to a maximum of 32767.
|
| Times queues created | The number of times that CICS created individual temporary
storage queues.
|
| Control interval size | The size of the VSAM unit of transmission between DASD and main storage, specified in the CONTROLINTERVALSIZE parameter in the VSAM CLUSTER definition for the temporary storage data set. In general, using large control intervals (CIs) permits more data to be transferred at one time, resulting in less system overhead. |
| Available bytes per control interval | The number of bytes available
for use in the temporary storage data set control interval.
|
| Segments per control interval | The number of segments available
in each temporary storage data set control interval.
|
| Bytes per segment | The number of bytes per segment
of the temporary storage data set.
|
| Writes more than control interval | The number of writes of records
whose length was greater than the control interval (CI) size. If the
reported value is large, increase the CI size. If the value is zero,
consider reducing the CI size until a small value is reported.
|
| Longest auxiliary temporary storage record | The size, expressed in bytes,
of the longest record written to the temporary storage data set.
|
| Number of control intervals available | The number of control intervals
(CIs) available for auxiliary temporary storage. This is the total
available space on the temporary storage data set, expressed as a
number of control intervals. This is not the space remaining at termination.
|
| Peak control intervals in use | The peak number of control intervals
(CIs) that contain active data.
|
| Times aux. storage exhausted | The number of situations where
one or more transactions might have been suspended because of a NOSPACE
condition, or might have been forced to end abnormally (by using a
HANDLE CONDITION NOSPACE command). If statistics are present for this
field, increase the size of the temporary storage data set.
|
| Number of temp. storage compressions | The number of times that the
temporary storage buffers were compressed.
|
| Temporary storage buffers | The number of temporary storage
buffers specified in the TS= system initialization parameter, or in
the overrides. The number of buffers allocated might exceed the number
requested.
|
| Buffer waits | The number of times a request
was queued because all buffers were allocated to other tasks. A buffer
wait also occurs if the required control interval is already in a
locked buffer, and therefore unavailable, even if there are other
buffers available.
|
| Peak users waiting on buffers | The peak number of requests
queued because no buffers were available.
|
| Buffer writes | The number of WRITEs to the temporary
storage data set. This includes both WRITEs required for recovery
(see Forced writes for recovery) and WRITEs required when the buffer
is needed to accommodate another control interval (CI). To minimize
input/output activity caused by the second situation, increase buffer
allocation.
|
| Forced writes for recovery | The subset of the total number
of WRITEs caused by recovery being specified for queues. This input/output
activity is not affected by buffer allocation.
|
| Buffer reads | The number of times a control
interval (CI) must be read from disk. To decrease this activity, increase
the buffer allocation.
|
| Format writes | The number of times a new control
interval (CI) was successfully written at the end of the data set
to increase the amount of available space in the data set. A formatted
write is attempted only if the current number of CIs available in
the auxiliary data set have all been used.
|
| Temporary storage strings | The number of temporary storage
strings specified in the TS= system initialization parameter, or in
the overrides. The number of strings allocated might exceed the number
requested.
|
| Peak number of strings in use | The peak number of concurrent
input/output operations. If this is significantly less than the number
specified in the system initialization table (SIT), consider reducing
the SIT value to approach this number.
|
| Times string wait occurred | The number of input/output requests
that were queued because no strings were available. If the number
of strings is the same as the number of buffers, this number is zero.
If this number is a high percentage (over 30%) of the total number
of input/output requests (for this purpose, the sum of TSGTWTN, Buffer
writes, and TSGTRDN, Buffer reads), consider increasing the number
of strings initially allocated.
|
| Peak number of users waiting on string | The peak number of input/output
requests that were queued at any one time because all strings were
in use.
|
| I/O errors on TS data set | The number of input/output errors
that occurred on the temporary storage data set. Normally, this number
should be zero. If it is not, inspect the CICS and VSAM messages to determine the cause.
|
| Shared pools defined | The number of unique shared TS queue pools defined to CICS. |
| Shared pools currently connected | The number of the shared TS pools that this CICS region is connected to. |
| Shared read requests | The number of TS READQs from the Shared TS Queue pool of TS queues. |
| Shared write requests | The number of TS WRITEQs to the Shared TS Queue pool of TS queues. |