Performance and Maintenance Best Practices
Run Full Backups and Incremental Unloads
Run full volume backups periodically and use the
EndevorUnload/Reload utility to do incremental unloads between full volume backups. Consider performing full volume backups weekly and incremental unloads daily. In addition, data validation should be performed daily.
Full volume backups run more quickly than
Endevorfull unloads. For disaster recovery, you could restore from the full volume backup, and then add data from the incremental unload.
The Unload/Reload utility (program C1BM5000) is a backup, recovery, and file validation mechanism for
EndevorVSAM control files (Master Control File, package data sets) and their related base and delta libraries. It allows users to backup (unload), restore (reload), and/or validate the integrity of one or more
Endevorenvironments in the event of a physical device failure or site disaster.
The Unload/Reload utility creates a file from which individual elements can be retrieved should one be accidentally deleted. It also ensures that there is no loss of synchronization among the
Endevorfiles, which can occur during the full volume backups.
Use VSAM Record Level Sharing
If your site has more than 50,000 elements, use the IBM z/OS VSAM Record Level Sharing (RLS) facility to manage your
EndevorVSAM data sets to improve VSAM performance. VSAM RLS should manage all Master Control Files (MCFs), Element catalog and EINDEX, and the package data set.
Endevormaking extensive use of VSAM to maintain the control information, it can, in larger installations, incur some performance bottlenecks mainly caused by VSAM open and close processing. Using VSAM RLS can help improve overall performance.
Activate Concurrent Action Processing
Activate the Concurrent Action Processing feature to speed processing of large numbers of elements. With the Type Sequence grouping capability, the application continues to dispatch element actions from the sequenced type chain as long as the group category value matches the previous request. Available STCs will only have to wait if sequenced type requests from one group category value are still processing and there are no non-type sequenced requests to process.
If you have bulk moves of large numbers of elements in a package or batch job, it can take a long time to complete the moves. Concurrent Action Processing speeds processing of batch jobs and packages, greatly reducing processing time. This feature enables
Endevorto exploit additional capacity on z/OS platforms to simultaneously execute certain element action requests, which reduces the elapsed time it takes to process multiple actions. An increase in throughput is immediate after Concurrent Action Processing has been activated.
Endevoradministrator must activate this feature.