|
This situation is triggered when the apply queue percent
full as determined by the IMS apply server has reached a
warning level. The apply queue percent full is the percentage
of the target (apply) cache in use (queue depth), computed as
(Current Cache Size/Maximum Cache Size)*100 and rounded down
to the nearest whole integer.
The Apply Queue Percent Full attribute is
displayed in the IMS Apply Server Details table view and the
Apply Queue Percent Full circular gauge view of the IMS
Replication Details workspace.
|
The apply queue percent full may be higher than expected
due to the following conditions:
- Replication is restarted and there is a large amount of
pending source updates to be processed. The apply queue
percent full should return to a normal level when the
backlog is processed.
- The occurrence of a large high volume batch (BMP or Batch
DL/I) window or a peak update period. The apply queue percent
full should return to a normal level when the number of
source updates to be processed has dropped and the servers
have a chance to catch up.
- The apply cache is too small.
Possible user actions are:
- Set the apply cache to 2G (the current max) and restart
replication.
- If the cache was already at 2G, you may need to restart
replication several times until the volume reduces as the
apply server will do a controlled stop of replication when
the apply cache limit is reached.
- If the subscription allows, consider increasing the
apply PSB number for the subscription to increase
parallelism. This may require IMS pool space and DFSPZPxx
member changes. Replication must be stopped to make this
change. If the subscription doesn't qualify for parallel
apply, consider creating 2 subscriptions, one with DBDs
that qualify for parallel apply and another with the DBDs
that do not qualify for parallel apply.
|
Copyright IBM Corp. 2011 All Rights Reserved
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM
Corp. Contact IBM
|
|
|