Previous Topic

Next Topic

Book Contents

Book Index

Auto-Archive

Determines whether SYSDATA (job output) must be archived.

NOTE: The parameter is displayed only if Control-R is selected.

Additional information

Description

Usage

Optional

Format

Check box.

When this check box is selected, job output is archived.

When this check box is cleared, job output is not archived. In this case, Control‑R cannot restart the job, and SYSDATA viewing under Control‑M for z/OS is not possible.

When the Auto-Archive check box is selected, the sub-parameters described below can also be specified.

Variable Support

None

Alternate names

  • Control‑M/EM Utilities: AUTOARCH
  • Control-M Report: AUTO ARCHIVE
  • Control‑M/Server Utilities: (none)
  • Control‑M for z/OS Utilities: AUTOARC
  • Control‑M for z/OS: AUTO‑ARCHIVE
  • Control‑M/EM API:
  • auto_archive
  • sys_db
  • arch_max_days
  • arch_max_runs

Computer specific information

The Auto-Archive parameter is relevant only for jobs to be run in z/OS environments or OpenVMS computers.

Sub-parameters

SYS DB

A check box

If this check box is selected, a single data set is used for archiving the SYSDATA of all jobs until it is full. When the first archive data set is full, another SYSDATA data set is allocated and used. BMC Software recommends this method.

If this check box is cleared, a separate data set is created for the SYSDATA of each job run.

Max Days...

A number from 00 through 99.

Indicates the maximum number of days to retain the SYSDATA archive data set for jobs that ended NOTOK.

Max Runs...

Indicates the maximum number of job runs to retains the SYSDATA archive data set for jobs that ended NOTOK. Valid values:

  • a number from 00 through 99
  • blank (there is no maximum number of job runs)

The Auto-Archive parameter enables you to decide whether to archive job output (SYSDATA). SYSDATA refers to all information in the job log, the expanded JCL (job script), and to the output messages of the job.

While archiving SYSDATA is normally desirable, it might not be desirable for cyclic jobs, started tasks, or frequently repeated jobs that do not require restart.

BMC Software recommends that you select the SYSDB check box. BMC Software does not recommend creating a separate data set for each run because:

When archiving SYSDATA, BMC Software recommends that value 99 not be specified for the Keep Active for parameter for cyclic jobs or started tasks. Otherwise, these jobs, which are never automatically deleted from the Active Jobs database, can cause the disk to fill up with unnecessary archived SYSDATA.

NOTE: Specified parameters take effect only during execution of the New Day procedure (CONTDAY) or the Control‑M CTMCAJF utility. Therefore, it is possible to find more generations of the same job than the current value of Maximum reruns.

Whenever a job is deleted from the Active Jobs database and does not reside in the History file, its SYSDATA is deleted regardless of Maximum reruns and Keep Active for.

The Keep Active for and Maximum reruns parameters define retention criteria for the archived SYSDATA of jobs that ended NOTOK. Defaults for these parameters are defined using Control-M/Restart installation parameters. Keep Active for and Maximum reruns values in a job definition are used to override the Control‑M/Restart defaults. If both parameters are specified, retention is limited by the parameter that is satisfied first.

Parent Topic

Actions parameters