Previous Topic

Next Topic

Book Contents

Book Index

Minimum number of tracks

Minimum number of free partitioned data set tracks required by the library specified for the Partition Data Set parameter.

NOTE: This parameter is available for z/OS jobs only.

Additional information

Description

Usage

Mandatory, if a value is specified for the Partition Data set parameter.

Format

A positive 3-digit number (leading zeros are required)

Variable Name

None

Alternate names

  • Control‑M/EM Utilities: MIN
  • Control-M Report: MIN PDS TRAC
  • Control-M/Server Utilities: (none)
  • Control‑M for z/OS: MINIMUM
  • Control-M/EM API: min_pds_tracks

The Partition Data Set parameter specifies a library, and the Minimum number of tracks parameter specifies the minimum number of free tracks required by that library.

The Minimum number of tracks and Partition Data set parameters are always used together and are never used with other Basic Scheduling parameters

When to use

The Minimum number of tracks and Partition Data set parameters are intended for use in jobs and started tasks that compress, clean, and/or enlarge libraries. They are also specified for tasks that issue a warning message to the IOA Log file if the minimum number of free tracks is not available.

If Minimum number of tracks and Partition Data Set parameters are defined for a job, the scheduling of the job is not related to or depends on any date criteria. Instead, the job is scheduled if the actual number of free tracks available in the specified library is below the specified minimum at time of daily job ordering. The job or started task can then compress, clean, or enlarge the library (or issue the appropriate warning).

NOTE: Minimum number of tracks does not work with PDSE-type libraries because they always appear to be 100 percent full. Minimum number of tracks only checks current extents.

Parent Topic

Scheduling Parameters