Logic is provided to prevent APEC from running on any system in the shared TMC environment while any of the following utilities are in use:
If any of these utilities start while APEC is scanning or if any of these utilities are running when a scan starts, APEC stops scanning until the next scheduled start time.
If the TMC has to be moved, before you start TMSINIT to establish the new location, stop TMSAPEC before running TMSINIT. If TMSAPEC is active when TMSINIT is run, unpredictable results may be obtained, for example an S130 abend or errors reading from or writing to the TMC.
The APEC subtask identifies users or jobs that have incorrectly updated volume or data set chains. Messages issued when invalid chains are discovered include the userid of the last updater of the invalid TMC record. Check the output of APEC task at regular intervals to identify the users incorrectly performing updates to the TMC.
If you share the TMC with multiple systems, APEC must be run on one system at a time to avoid possible duplicate updates.
TMSAPEC issues an enqueue for exclusive ownership of a resource, SCOPE=SYSTEMS, QNAME=TMSQNAME, RNAME=TMSAPEC or RNAME=TMSAPEC-vvvvvv-data.set.name.tmc. This resource should be GLOBALLY managed and shared by all systems sharing the TMC using either MIM or GRS. The RNAME depends on if you enabled the Unique_RNAME feature either via TMSXTEND or TMSUDSNB.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|