CA CSM can mass offload (move, copy, or delete) user task output kept within CA CSM by utilizing the policy wizard. Use this functionality with either the Move or Delete policy types to ensure that the file system being used for task output does not continue to grow and use excessive DASD space. Create site policies to ensure that the operational standards and goals are adhered to.
The policy types Copy and Move can send the existing task output that is selected by the executing policy to either JES or a sequential data set. You can execute a policy immediately after it is created. You can also store policies for future usage and can trigger them manually or automatically with a CA CSM scheduling mechanism or an external scheduler.
You can select from the following types of tasks:
Include tasks that are related to products. The following task types belong to product tasks:
Include tasks that are related to setting up and configuring CA CSM. The following task types belong to housekeeping tasks:
Include audit tasks that represent tasks deleted from CA CSM and task policy tasks that are created when a task management policy executes. The following task types belong to audit tasks:
You can create archives for all tasks run daily, weekly, individually for each task, or for all of the tasks specified in one policy. You can archive tasks into sequential data sets or onto a JES spool. The exported tasks are encoded in the code page IBM-1047/103 Latin 1 (Open Systems). For example, if you do not have this code page set, you may see something similar to the following:
CA Chorus Software Manager - Release: 5.1 ÝProduction (56); 2013-02-07_10-49-48; user1¨
With the code page set, this text would look like the following:
CA Chorus Software Manager - Release: 5.1 [Production (56); 2013-02-07_10-49-48; user1]
After the execution finishes, you can view several reports that are based on output of the task execution. You can browse the reports in the output browser. The reports include the following:
Provides details about tasks that were processed (copied or deleted) during policy execution. For copied tasks, the data set into which task output was copied to is also mentioned.
(Optional) Provides details about tasks that could not be processed (copied or deleted) because they were locked at the time of processing.
Provides details about data sets created during policy execution (copy or move) and contents of those data sets (tasks copied) not applicable for deletion.
Provides general statistics for the policy, including name, type, organization, data set symbolics, and details about the execution.
Provides a log of all actions which occurred during policy execution. To enable the execution log, change the diagnostic log level to Debug.
This section contains the following topics:
|
Copyright © 2014 CA.
All rights reserved.
|
|