Job Archiving configuration

9.0.20.000 This page provides information for creating Archive Rule files, that is, payload JSON files that you can submit when you configure Job Archiving.

The following code sample shows the available properties and objects that you can include within such a file. The rest of this page provides details about each of these properties and objects.

{
    "name": "All DS jobs",
    "description": "Collect all DS jobs",
    "maxOutputSize": 20,
    "maxOutputSizeType": "MB",
    "trimType": "Omit",
    "retention": 1,
    "retentionType": "Months",
    "isActive": true,
    "archivedType": "Log",
    "ruleParameters": [
        {
          "field": "ctm",
          "criteria": "*",
          "exceptions": [
            "fds*"
          ]
        },
        {
          "field": "jobName",
          "criteria": "A*",
          "exceptions": [
            "Ac*",
            "Ad*"
          ]
        },
        {
          "field": "jobType",
          "criteria": "Job:FileTransfer"
        },
        {
          "field": "application",
          "criteria": "*",
          "exceptions": [
            "c*"
          ]
        },
        {
          "field": "subApplication",
          "criteria": "s*",
          "exceptions": [
            "s4*"
          ]
        },
        {
          "field": "folder",
          "criteria": "*",
          "exceptions": [
            "f*"
          ]
        },
        {
          "field": "library",
          "criteria": "bmc*",
          "exceptions": [
            "bmc6*",
            "bmc7*"
          ]
        },
        {
          "field": "jobStatus",
          "criteria": "Ended OK"
        }
    ]
}

General rule settings

Start your Archive Rule file with the following general properties for the rule that you are defining:

PropertyDescription
name

A unique name for the rule

This is the only property that is required for a new rule.
It cannot be modified when updating an existing rule.

descriptionAn optional textual description of the rule
maxOutputSize

Maximum size of output to retrieve for jobs that match this rule

Valid values: 1–100

maxOutputSizeType

Unit of measurement for maximum output size

Valid values: KB, MB

trimType

What to do when retrieved job output exceeds the maximum size

Valid values:

  • Beginning — trim the excess size from the beginning of the output
  • End — trim the excess size from the end of the output
  • Omit — omit this output from the job outputs that are retrieved
retention

Amount of time to keep the data that is retrieved based on this rule in the Workload Archiving server

Valid values: any positive integer

retentionType

Unit of measurement for the retention period

Valid values: Days, Months, Years

isActive

Activity status of the rule

Valid values: true (enabled) | false (disabled)

archivedType

Type(s) of data to archive for jobs that match this rule

Valid values:

  • Log
  • Output
  • Log and Output

Rule parameters for job filtering

Under the ruleParameters object, you can define a group of rule parameters that filter jobs based on various job properties and determine which jobs to archive. These parameters are defined with the following properties:

  • field — job property by which to filter
  • criteria — filter value
  • exceptions — values to exclude from the filter

All rule parameters are optional, and the default for all criteria is "*" (ALL jobs).

The following table summarizes the guidelines for including rule parameters in an Archive Rule file:

FieldCriteriaExceptions
ctmAny string. Asterisk and question mark (* and ?) wildcards supported.One or more string, separated by commas
jobType

One of the following job types:

  • All
  • Distributed:All (all jobs on distributed-type machines)
  • Job:CommandAndScript
  • Job:FileWatcher
  • Job:Informatica
  • Job:SAP:R3
  • Job:SAP:BW
  • Job:Hadoop
  • Job:FileTransfer
  • Job:Database
  • Job:AWS

Note: In the output of the config archive:rules::get command, you might see other job types that are not supported by Control-M Automation API (from jobs that were created through Control-M). Do not include unsupported job types in your Archive Rule files. 

Not applicable
jobNameAny string. Asterisk and question mark (* and ?) wildcards supported.One or more string, separated by commas
applicationAny string. Asterisk and question mark (* and ?) wildcards supported.One or more string, separated by commas
subApplicationAny string. Asterisk and question mark (* and ?) wildcards supported.One or more string, separated by commas
folderAny string. Asterisk and question mark (* and ?) wildcards supported.One or more string, separated by commas
libraryAny string. Asterisk and question mark (* and ?) wildcards supported.One or more string, separated by commas
jobStatus

One of the following statuses:

  • All
  • Ended OK
  • Ended Not OK
Not applicable
Was this page helpful? Yes No Submitting... Thank you

Comments