Cloud Data Manager

Running life cycle management

Before running for the first time:

  • Associate the same user ID with the Model9 z/OS agent and the life cycle management process. Running life cycle management requires the user ID to have READ access to: M9.LIFECYCLE.CLOUD.DELETEEXPIRED.

  • A life cycle management process can be associated with one resource complex only. Define a life cycle management process for each resource complex.

  • Only one life cycle management process can run simultaneously for the same resource process.

  • By default, all LPARs in a Sysplex are associated with the same resource complex, named “group-<sysplex-name>”. Running life cycle management in any LPAR will delete the expired archived data sets in the entire Sysplex.

Running for the first time:

  • The life cycle management process can be activated in “simulate” mode, meaning it will report the data sets that would have been deleted without actually deleting them.

  • During the first run, the life cycle management process will scan all archived data sets with an expiration date.

Running regularly:

  • The next time the life cycle management process will run, it will begin where the previous process ended.

  • It is recommended to run a life cycle management process every day.

Life cycle management job parameters

A sample JCL, M9LIFECY, can be found in the Model9 SAMPLIB PDS, see the installation guide for more details. The PWD parameter should point to the agent installation directory.

image32.png
Life cycle management syntax

The syntax is specified in the MAINARGS DD card.

Simulate - Default is no. When specifying yes, the job will report the data sets that should be deleted but will not delete them.

Target - The one possible value is cloud, meaning the process will be performed on the storage specified in the “objstore” parameter of the agent configuration file.

Action - The one possible action is delete-expired, meaning the process will delete expired archived data sets.