Health checks generate the following messages.
Reason:
The CA Deliver processes application work the requests using PRBTASKS. Because these requests are from multiple address spaces and can occur concurrently, work request queues are maintained in CSA. Typically, CA Deliver must be able to keep the queue size under 100.
A large number of queued requests indicates that something is degrading CA Deliver performance. A common cause is delayed access to the CA Deliver database or checkpoint data sets. Verify that a long term reserve is not occurring on the CA Deliver checkpoint or database volumes.
Action:
Notify the systems programmer of this condition and verify that a long-term reserve is not occurring on the CA Deliver checkpoint or database volumes. You can also increase the CA Deliver PRBTASKS parameter up to a maximum of 16.
Changing this parameter requires the CA Deliver started task to be cycled. CA Deliver continues processing.
Reason:
Informational message stating that the requests from application address spaces are not experiencing any delays.
Action:
None.
Reason:
The CA Deliver HDETAIL option allows clients to implement station tracking for all reports processed by this CA Deliver database. This feature has a high overhead and can be used only for a small CA Deliver database. When this option is turned on, database space usage rapidly grows and jobs running in pre-spool mode experience delays as the history records are created for each recipient of the report.
Action:
Contact the administrator responsible for this CA Deliver database. Determine if HDETAIL was intentionally turned on. Also verify that the two Deliver JES exits have been installed. If all of these conditions have not been met, set HDETAIL=NO in the RMOPARMS data set and cycle the RMOSTC task CA Deliver continues processing.
Reason:
Informational message. Collecting detail history incurs additional overhead and database space; most clients do not require this option. Turning off history detail does not stop basic history from be collected on the CA Deliver database. Basic history includes Date, Time, Job ID, pages and lines for each report and bundle.
Action:
Contact the administrator responsible if you want to turn on this option.
Reason:
The CA Deliver checkpoint data set is more than 80% full. The checkpoint usage is high.
Action:
Monitor the checkpoint so that the number of active entries does not exceed the capacity of the checkpoint. Run the RMOCPMAP utility to determine how the checkpoint space is being used and if it is sufficient for your needs. If the checkpoint size is sufficient for your needs, RMOGRW08 from CAI.CVDEJCL can be run to identify reports that can be deactivated. Then RMORAP is used to deactivate the reports freeing space for use. If the number of entries approaches the capacity of the checkpoint, use the RMODBASE utility MAKECKPT control statement to expand the size of the checkpoint or copy the checkpoint to a new data set.
Note: The number of bytes used per checkpoint varies. On average the checkpoint data set has the approximate capacity for 5000 non-bundled report entries per cylinder, or 2,500 bundled report entries per cylinder. The numbers are less if reports are part of multiple bundles.
Reason:
Informational message. Checkpoint usage is within normal limits.
Action:
The checkpoint data set is not experiencing a capacity problem.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|