Use CA SYSVIEW to monitor the health checks generated for CA PMO.
Business Value:
Health checks alert you to conditions that could prevent CA PMO from providing the best performance optimization, if uncorrected, and they guide you in addressing the problem.
Additional Considerations:
The following health checks are provided for CA PMO:
Ensures that the managed list is big enough to provide the best performance for directory searches of LNKLST members with CA PMO.
Ensures that CA PMO is adequately assisting LNKLST searches.
Ensures that there are enough entries for private libraries.
More Information:
See "CA PMO Health Checks" in the CA PMO Systems Programmer Guide.
Use the XCF Enhanced Data Transmission in place of control file when using a single sysplex.
Business Value:
The XCF will be used in place of the control file within a single sysplex to eliminate unnecessary control file I/O. Whereas each PMO must read the control file to determine if any other CA PMO system has updates, XCF messages can drive PMO with update information using an Event Driven Architecture. Updates reflected by the XCF implementation provide for increased performance.
More Information:
For more information see "Determine the Multiple System Communication Path (Optional)" in the CA PMO Installation Guide.
Allow CA PMO to generate LLA refreshes for link list members.
Business Value:
When LLA manages the link list libraries, LLA must be refreshed when a library is updated to ensure that LLA has the correct information. CA PMO can automatically generate selective LLA refreshes following link list updates.
More Information:
For more information, see "Handling LNKLST Updates" in the CA PMO Systems Programmer Guide.
If you are using the PMO/XCF component, you need to specify the group name that will be used by CA PMO in the sysplex. It is required to be different from other groups defined in the sysplex. If the default value (PMOXCFGP) is not acceptable, it is recommended to include PMO in your own group name.
Business Value:
Specifying the group name that is used by other products in the sysplex may cause that CA PMO will accept XCF messages from different products. This will result in error messages issued from CA PMO Also the PMO/XCF Update Messages will be sent to other products that use the same Group name. This may lead to unexpected results.
Additional Considerations:
The group name must be eight characters long, padded on the right with blanks if necessary; the valid characters are A-Z, 0-9, and national characters ($, # and @). To avoid using the names IBM uses for its XCF groups, do not begin group names with the letters A through I or the character string SYS. Also, do not use the name UNDESIG, which is reserved for use by the system programmer in your installation.
More Information:
For more information, see "Specifying Parameters" in the CA PMO Systems Programmer Guide.
To optimize sysplex functionality and enable event driven communications use both the XCF and control file.
Business Value:
To save I/O processing time and to better communicate with event driven communications, use the XCF for CA PMO systems running on the same sysplex. To allow for CA PMO systems to share updates across sysplex’s, use the control file for one PMO on each sysplex.
More Information:
For more information see "Determine the Multiple System Communication Path (Optional)" in the CA PMO Installation Guide.
Use the SMF system ID to simplify CA PMO parameters.
Business Value:
The four character SMF system ID may be used to specify that a parameter only applies to a specific system. This simplifies the task of configuring CA PMO in a multiple system environment. Because you have fewer parameters, the resulting configuration is less complex and easier to manage.
More Information:
For more information, see "Parameter Syntax" in the CA PMO Systems Programmer Guide.
|
Copyright © 2011 CA.
All rights reserved.
|
|