Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Example of Detecting Catalog Resource Contention z/OS DFSMS Managing Catalogs SC23-6853-00 |
|
In this example, the SYSZTIOT resource is used with the default wait time (10 minutes) and action (notification only). The information in this example also applies to the other resources to which resource contention monitoring applies (ALLOCLCK, SYSIGGV2, and SYSZVVDS). If you receive system message IEC393I notifying you that a task
or tasks is waiting on the SYSZTIOT resource, you can use the information
in the message to determine if any action is needed to resolve the
wait. Note that receiving this message does not mean that an error
or problem exists - you may not need to take any action at all. If
you cancel any of the jobs listed, consider first taking a dump of
the CAS by issuing:
To get more information about the waiting jobs, use the information
in message IEC393I as follows:
Unless specified otherwise in the IGGCATxx parmlib member, the
system, by default, lets a task wait for the SYSZTIOT task for 10
minutes before writing a SYMREC record to the logrec data set and
issuing message IEC393I. You can specify a different wait time using
the following command:
See MODIFY CATALOG Command Syntax for wait_time limits.If you specify a non-default SYSZTIOT wait time on the MODIFY command, you must respecify that value after each system IPL. A non-default value does, however, persist through restarts of the CAS task. Unless specified otherwise in the IGGCATxx parmlib member, the
only action the system takes by default is notify (writing a SYMREC
record to the logrec data set and issuing message IEC393I). You can
specify that the system also re-drive the task using the following
command:
See MODIFY CATALOG Command Syntax for action-flags ,
which can be used to specify re-drive.If you specify a re-drive action for SYSZTIOT on the MODIFY command, you must respecify that value after each system IPL. A non-default action-flags value does, however, persist through restarts of the CAS task. Additional information:
|
Copyright IBM Corporation 1990, 2014
|