Customizing Control-M

#JNFMS

#JNFRT

#ONSPLOC

#SYSMS

#SYSRT

$GDFREQU

AECACHL

AJFABAR

AJFSHARE

AJFSIZE

AJFTYPE

AJFTHRSH

APIMSTSO

ARCHFBA

ARCPRI#

ARCRET

ARCSEC#

ARCSPCT

ARCUNIT

ARCXOUTP

ARMELMNT

ATTSOEXT

ATTSOTSZ

ATTSYSOT

AUTOTAPE

CALNFND

CMEMREQ#

CNTERCMP

CNTERCRD

COPJS1ST

COPMEM2O

CRSPREFX

CTGFORC

CTMPLEX

CTRB4INC

CYC2X15

DAYTIMEM

DBGMCS

DEFSTEP

DELOVRER

DELOVRUN

DLRECALI

DLSCPRU

DOCUT

DUEINCHK

DWNLDERR

EDITOVRL

EMPTYTBL

EXCLURBC

EMUSDLY

ENHNJE

EXSTPRNG

FORCE#RT

FORCE#WI

FORCERBC

FORCETBL

FRCOKOPT

FREESPAC

FRMAXWT

GDFORWRD

HCDELAYT

HCHECKER

HCJDAYS

HCJINTRV

HCMINTRV

HCPINTRV

HCTINTRV

HIST

HLDCLAS

IGNDOSYS

IGNIGD17

IGNQTMGR

INTERVALM

INUSE#RT

INUSE#WI

JNMATORD

JOBREJRC

JOBSUBST

JRNL

JSCAN

LASTSTEP

M622RC4

MAXACTIV

MAXCCOK

MAXJBHLD

MJES262W

MSEL250I

MSGCPRES

MULJESPP

MULTISUB

MULTJOBS

MVBO

MXJINBOR

NEWDAY#W

NEWDAYIM

NOJOBRC4

NONSWAPM

OPTGDLVL

OPTKPLVL

OPTLINDR

OPTMODE

OPTMVLID

OVERJCLM

PFMINT

PFMSMF

PROCNAMM

PRTCLAS

PSEUDOON

QRSPREFX

RBCMAXWT

RECENA

RECLEVEL

RECLRQST

RELHLDJ

REPDELJ

RESETORC

RESETPRY

REUSAPPL

REUSTIME

SAPI

SCHPREVD

SDSB

SCRECALL

SPYWAIT

STENT#

STIGNCPU

STOPORDR

SUBBY

SUBRDRP#

SUBWRTP#

SYACTPR#

SYACTRLV

TBLDELJB

TBLRECHK

1

2

3

AJFABAR

Whether to load the AJF above the bar.

Valid values are:

• Y (Yes) – Load AJF above the bar.

• N (No) – Load AJF below the bar.

• A (Auto) – AJF location is automatically selected by Control-M. Default.

AJFSHARE

Whether to allocate the AJF as a shared memory object. This parameter is relevant when the AJF is loaded above the bar.

Valid values are:

• Y (Yes) – Allocate the AJF as a shared memory object. Default

• N (No) – Allocate the AJF as a non-shared memory object.

AUTOTAPE

(WM2744)

This option enables Control‑M tape drive resources to be automatically assigned, based on usage statistics, overriding tape drive resource allocations specified in the RESOURCE parameter of the job scheduling definition. If this option is not set, the statistics are not tracked.

• Mandatory

Valid values are:

• Y – ControlM automatically tracks usage of and assigns ControlM tape drive resources.

• N – ControlM does not automatically track usage of and assign ControlM tape drive resources. Default.

For more information about the Automatic Tape Adjustment facility, see the Control‑M chapter of the INCONTROL for z/OSAdministrator Guide.

CMEMREQ#

The maximum number of CMEM requests processed in each Control-M interval.

When there is a very large number of CMEM requests, the overhead involved in processing them can cause the performance of Control-M to be seriously degraded to such an extent that Control-M cannot process any other work. You can use this parameter to limit the number of CMEM requests that Control-M will process in each Control-M interval, enabling all Control-M functions to continue to perform properly.

• Valid values are: 0 through 99.

• Default: 20

CTMPLEX

Whether to activate the CTMPLEX facility, that is, run the Control‑M monitor in Sysplex mode.

For full information on this parameter, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

If you change the value for this parameter from N to Y, you must also perform all the steps related to CTMPLEX to activate this change. This avoids unpredictable results.

DBGMCS

Whether to trace MCS $GD commands.

• Mandatory

Valid values are:

• Y (Yes) – MCS $GD commands are traced.

• N (No) – MCS $GD commands are not traced. Default.

$GD commands are the communication mechanism used by local and remote NJE nodes to obtain the statuses of NJE jobs. These commands are issued only when extended NJE tracking support is activated.

The DBGMCS parameter enables the Control‑M administrator to turn this display on or off. The following considerations are important:

• Tracing MCS $GD commands may involve high overhead.

• When there are many NJE jobs, the console may be flooded with messages if the trace is active.

BMC recommends that you set DBGMCS to Y only when requested to do so by BMC Customer Support.

For more information about extended NJE tracking support, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

FORCE#RT

(WM3233)

The number of times Control‑M retries a FORCEJOB or CONNECT DIRECT request that fails.

This parameter is only effective if a positive value has been specified for the FORCE#WI parameter (described in this table).

• Mandatory

Valid values are:

• 0 – ControlM continues to try to execute the request until it succeeds, or until the ControlM monitor terminates, whichever occurs first. Default.

• nnn – ControlM continues to try to execute the request until it succeeds, or until nnn attempts have been made, or until the ControlM monitor terminates, whichever occurs first.

FORCE#WI

(WM3233)

Whether Control‑M retries a FORCEJOB or CONNECT DIRECT request that fails, and if so, the frequency of retries.

• Mandatory

Valid values are:

• 0 – ControlM does not retry to execute the request. Default.

• nnn – ControlM continues to try to execute the request every nnn ControlM intervals.

HLDCLAS

The automatic held output class to which Control‑M sends the MSGCLASS output of the job.

For more information about the HLDCLAS parameter, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

INTERVLM

Sleeping interval of Control‑M monitor.

• Mandatory

For full information on this parameter, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

MAXJBHLD

(WM3254)

The maximum number of jobs that are put into Held status by the Automatic Recovery feature

• Mandatory

• Maximum value: 255

• Default: 1

If you set a value for this parameter greater than zero and a subtask of a Control-M monitor job abends and message CTM114E is issued, the job is put into Held status and the CTM183E message is issued. If the number of jobs put into Held status after subtask abends is equal to the value set for this parameter, the job is not put into Held status, and the CTM184E message is issued.

This parameter can be used together with IBM’s ARM feature to automatically restart the Control-M monitor if it abends.

NONSWAPM

Whether to make the Control‑M monitor non-swappable.

• Mandatory

For full information on customizing this parameter, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

PFMINT

Control‑M performance data is accumulated and written to SMF at given time intervals. This parameter sets the time interval, in minutes, at which the SMF records are written. If the interval is set to 0 or 1440 then one SMF record is written during Control‑M Newday processing.

You can temporarily change this parameter using the Control‑M PERFDATA command. The PFMINT parameter is reset to the value in the CTMPARM member when the Control‑M monitor is restarted. For more information on the PERFDATA command, see the INCONTROL for z/OS Administrator Guide.

• Valid Values: 0-1440

• Default: 1440

PFMSMF

Specifies the SMF record type used for Control‑M performance monitoring. Choose an SMF record type number which is not already in use at your installation. If the value is set to 0 no SMF records are created.

• Valid Values: 0, 128-255

• Default: 157

AJFSIZE

Maximum number of records in the Active Jobs file (AJF).

• Mandatory

• Maximum: 10000000 (records)

For more information, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

AJFTYPE

Type of AJF file.

• Mandatory

Valid values:

• B - BASIC (Default)

• L - LARGE

• E - EXTENDED

The Active Jobs file (AJF) must be created using a DSNTYPE of BASIC, LARGE or EXTENDED through the AJFTYPE parameter. If the site’s AJFSIZE will not exceed 2,000,000 records (65,535 tracks) in the foreseeable future, then choose an AJFTYPE of BASIC (default), otherwise, an AJFTYPE of LARGE or EXTENDED must be chosen.

Consult the IBM manual, DFSMS: Using Data Sets, for the meaning of these various allocation types and how to choose the appropriate value.

AJFTHRSH

(WM2095)

Active Jobs file utilization threshold. When the threshold is reached, the Control‑M Monitor starts informing the operator about Active Jobs file utilization.

• Mandatory

• Maximum: 99%

• Default: 90%

HIST

Whether to activate the History Jobs file option.

For full information on this parameter, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

JRNL

Whether to activate the AJF Journaling option.

For full information on this parameter, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

REUSAPPL

AJF Space Reuse Application parameter prefix.

Specifies the prefix of the application parameter in the Job Schedule Definition, for jobs to be handled by AJF Space Reuse Facility.

Valid value is a string not longer than 8 characters. The default value is blank, which means that all jobs may be processed by the AJF Space Reuse Facility (if the value of the REUSTIME parameter is not zero).

For further information see the discussion of the Active Jobs File Space Reuse Facility in the INCONTROL for z/OS AdministratorGuide.

DAYTIMEM

The start time of the work day at your site.

For full information on this parameter, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

FRMAXWT

For Smart Tables where KEEP JOBS UNTIL REMOVED is set to Y, this parameter controls whether Control-M New Day processing or AJF Compress forces Smart Table completion when the MAXWAIT of all its jobs (and the Smart Table itself) has expired.

The Force Smart Table Completion process is the same process as occurs when a Smart Table job with END-TABLE Y finishes. For additional information, see END-TABLE: Post–Processing Parameter in the Control-M for z/OS User Guide.

Valid values are:

• Y – Control-M New Day processing or AJF Compress forces Smart Table completion when the MAXWAIT of all its jobs (and the Smart Table itself) has expired. Default

• N – Control-M New Day processing or AJF Compress does not force Smart Table completion when the MAXWAIT of all its jobs (and the Smart Table itself) has expired.

NEWDAY#W

After Control-M monitor issues the message "CTM113I Control-M MONITOR monitor name NEWDAY PROCESSING STARTED", it waits for a number of Control‑M sleeping intervals (this parameter) for the New Day started task to start executing. If the New Day procedure does not start to execute, the "CTML03W NEW DAY PROCEDURE NOT DETECTED" message is issued, followed by the CTML06W REPLY 'R' FOR RESUME OR 'E' FOR END message.

For example, if the Control-M sleeping interval is 3 seconds, and the default value of 30 is used, the monitor waits 90 seconds for the Newday started task to start executing.

• Default: 30

For more information, see the INCONTROL of z/OS Administrator Guide for details.

NEWDAYIM

(WM3666)

Whether to activate the New Day in memory facility. This shortens the New Day procedure by performing all compress processing using the monitor’s copy of the AJF.

Valid values are:

• Y – The New Day procedure does not read the AJF from DASD. The New Day procedure copies the AJF from the Control-M monitor's address space (using the cross- memory facility). After compressing the AJF, the New Day procedure copies the compressed AJF back to the Control-M monitor's address space. Default.

• N – The New Day procedure and Control-M monitor always read the AJF from DASD.

PROCNAMM

Name of the Control‑M New Day procedure, a started task that Control‑M invokes once a day to perform New Day functions.

If left blank, this parameter defaults to xxxTDAY, where xxx is the value of PROCPRFM.

For more information, see the INCONTROL for z/OS Administrator Guide.

CALNFND

(WM0738)

Whether to stop the ordering process if a "Calendar Not Found" error occurs during the job ordering process.

• Mandatory

Valid values are:

• Y – Stop the ordering process if a Calendar Not Found error occurs.

• N – Continue ordering the next job even if a Calendar Not Found error occurs. Default.

CNTERCMP

(WM2517)

Whether to continue ordering the next job if a Compress error occurs during the ordering process.

• Mandatory

Valid values are:

• Y – Activate this option.

• N – Do not activate this option. Default.

CNTERCRD

Whether to continue ordering if a Cards Error (Scheduling) occurs during the job ordering process, or if a job scheduling table (member) is not found.

• Mandatory

Valid values are:

• Y – Continue ordering the next job even if a cards error occurs or a job scheduling table cannot be found during ordering of a job.

• N – Do not continue. Default.

CTGFORC

(WM0983)

The operation that should be performed when Control‑M is to execute a Control‑D Category as specified in D-CAT field.

• Mandatory

Valid values are:

• Y – Force ControlD Category. Default.

• N – Order ControlD Category.

EMPTYTBL

Whether an empty SMART table, meaning a SMART Table Entity with no jobs, can be ordered.

• Mandatory

Valid values are:

• Y – An empty SMART table can be ordered.

• N – An empty SMART table cannot be ordered. Default.

EXCLURBC

Exclude RBCs are rule-based calendars that specify the days that jobs will NOT be ordered. To specify an Exclude RBC, an exclamation mark (!) must be added as a prefix when defining a Table level RBC, or as a prefix to the RBC name when referring to a Control-M (CTM) level RBC.

Before turning the value of EXCLURBC from N to Y, the user must ensure that regular (Include) RBCs that are defined at the Table level and all RBCs defined at the CTM level do not have an “!” character prefix. For more information, see the Control-M for z/OS User Guide.

• Mandatory

Valid values are:

• Y – Any TABLE level RBC that is defined with a name starting with an “!” prefix, or any CTM level RBC that is referenced with "!" as the first character, is processed as an Exclude RBC.

• N – All RBCs are processed as regular (Include) RBCs, even those that are defined or referenced with the “!” prefix. The "!" will be treated as a regular character. Default.

FORCERBC

Whether, when forcing or ordering a job belonging to a SMART table, to insert a RBC value into the job definition on the AJF. Under normal circumstances, since the job is forced, the job definition would not contain a RBC value.

Valid values are:

• Y – Sets a RBC value in the job definition according to the following criteria:

  • If the job's scheduling definition refers to a rule-based calendar, the first of these calendars is used.

  • If the job's scheduling definition does not contain a rule-based calendar, the first scheduling calendar defined in the SMART Table Entity to which the job belongs is used.

  • If the job's scheduling definition refers to a rule-based calendar '*', the first scheduling calendar defined in the SMART Table Entity is used.

• N - Does not set any RBC value for the forced job. Default.

FORCETBL

Whether, when the name specified in a FORCE command is the name of both a SMART table and a job within that SMART table, the SMART table is forced.

• Mandatory

The FORCE command can force both SMART tables and individual jobs, according to the following principles:

• If a job is named in a FORCE command, that job is forced.

• If a SMART table is named in a FORCE command, that SMART table is forced.

• If the name specified in a FORCE command is the name of both a SMART table and a job within that SMART table
  — when this parameter (FORCETBL) is set to N, which is the default, the job is forced
  — when this parameter (FORCETBL) is set to Y, the SMART table is forced

Valid values are:

• Y – The SMART table is forced.

• N – The SMART table is not forced. Default.

FREESPAC

(WM2047)

An (optional) value that causes extra space in the Active Jobs file to be preserved for each and every job during the ordering process. This space can later be used by the Active Environment Zoom screen (Screen 3.Z) to add more data to the job.

• Mandatory

• Maximum: 1024 (bytes)

• Default: 150 (bytes)

Exercise caution when setting the value for this parameter, since the size of the job may affect Control‑M performance, and most importantly, may increase I/O time every time the job is to be read or written. On the other hand, you can use this parameter to reserve enough space to enable users to add more information to the job in the Active Environment Zoom screen (Screen 3.Z), such as IN Conditions, OUT Conditions, Shouts and Notes.

GDFORWRD

Whether, when the TIME ZONE parameter is set in a job definition and the New Day procedure runs, the current working day or the next working day is assigned to the job.

• Mandatory

Valid values are:

• Y – The next day is assigned as the working day of the job. Default.

• N – The current working day is assigned as the working day of the job.

For more information on the Time Zone feature, see the Control‑M chapter of the INCONTROL for z/OS Administrator Guide.

JOBREJRC

When this parameter is set to Y, if one of the jobs is rejected by an exit (user or security exit), the ordering process terminates with RC=8.

If the job is part of a SMART table, ordering the SMART table fails.

Valid values are:

• Y - Activate feature as described above.

• N - Return code is not changed and the SMART table is not cancelled if job is rejected by an exit. Default.

LDCAEORD

The LDCAEORD (LoaD Cached AutoEdit variables at ORDer time) allows AutoEdit variables, which have been loaded in the Control-M cache, to be resolved at order time. (The AECACHL parameter points to the cached AutoEdit variables.)

• Mandatory

Valid values:

• Y – resolve the cached AutoEdit variables at order time.

• N – do not resolve the cached AutoEdit variables at order time. Default.

Caution: Setting the LDCAEORD parameter to Y might slow the job ordering process.

MXJINBOR

The MXJINBOR (MaXimum Jobs IN Bulk Order) determines how many jobs are included in bulk ordering.

• Mandatory

Valid values are:

Numeric values from 0 to 99999.

The default is 300.

0 means that bulk ordering is disabled.

NOJOBRC4

The completion code returned when the ordering process results in no jobs being ordered.

• Mandatory

Valid values are:

• Y – The ordering process sets the return code to 4 when no jobs are ordered.

• N – The ordering process sets the return code to 0 when no jobs are ordered. Default.

PSEUDOON

Whether to globally change the Adjust Condition field in SMART Table Entity definitions.

Valid values are:

• Y – Causes Control-M to treat any SMART Table Entity whose Adjust Condition field has the value of Y as though the field were specified with a value of D.

• N – The value of the Adjust Condition field is not changed. Default.

RESETORC

Whether to reset the completion code to 0 when CNTERCRD=Y.

• Mandatory

Valid values are:

• Y – Reset the completion code to 0 when CNTERCRD=Y

• N – Do not change the resulting completion code. Default.

DUEINCHK

Whether to check the DUE-IN time of a job before selecting the job for submission.

If a check is to be performed, that is, if the DUEINCHK parameter is set to Y, the job is not selected if, according to its average elapsed time, it will not finish before its DUE-OUT time.

• Mandatory

Valid values are:

• Y – Check DUE-OUT time of the job before selecting the job.

• N – Do not check DUE-OUT time of the job. Default.

IGNQTMGR

(WM3392)

Whether QUIESTIME commands are to affect both jobs and SMART tables, or only jobs.

• Mandatory

Valid values are:

• Y – QUIESTIME affects only jobs.

• N – QUIESTIME affects both jobs and SMART tables. Default

For more information on QUIESTIME, see the description of setting a planned shutdown time in the Control‑M chapter of the INCONTROL for z/OS Administrator Guide.

MAXACTIV

(WM3668)

Limits the number of active jobs in Control-M.

• Valid values are: 0 through 999999

• Default: 0 (no limitation)

Use of this parameter is functionally equivalent to defining a quantitative resource, such as an Initiator resource, with a total quantity specified in the parameter’s value, and assigning every Control‑M job 1 unit of the resource. Using this parameter, rather than resources, lowers the Control-M monitor’s computer utilization by decreasing the number of tracked Control-M jobs waiting in the JES input queue. See the section about the Control-M monitor and JES considerations in the INCONTROL for z/OS Administrator Guide for recommendations on how to use this parameter.

This parameter does not consider SMART Table Entities, started tasks, NJE jobs, on-spool jobs, and dummy jobs as active jobs.

TBLRECHK (WM2699)

Before selecting a job belonging to an Active SMART Table for submission, a decision must be made whether to re-check some of the SMART Table parameter. The decision is based on the TBLRECHK parameter.

• Mandatory

Valid values are:

• C – If any IN CONDITIONS defined in the SMART Table definition were added or deleted since the SMART Table became Active, then first rechecks all the run time criteria of the SMART Table before checking the job parameters. If any of the SMART Table run time criteria are not satisfied, then the SMART Table status is reset from Active to Wait Schedule, and none of jobs of this SMART TABLE will be eligible for running.

• Y – The same as ‘C’ option. Exists for compatibility with previous versions.

• T – Before selecting a job belonging to an Active SMART Table for submission, recheck the FROM TIME / UNTIL TIME limitations defined in the SMART Table definition. If these limitations are not satisfied, then do not select a job for submission. In any case (whether FROM TIME/UNTIL TIME limitations are satisfied or not), the SMART Table remains in Active status.

• A – Works as ‘C’ and ‘T’ together. Such as if any IN CONDITIONS defined in the SMART Table definition were added or deleted, rechecks all run time criteria of the SMART Table (including FROM TIME/UNTIL TIME) and resets the status of the SMART Table back to Wait Schedule if any run time criteria are not satisfied. If no changes occurred with the IN CONDITIONS defined in the SMART Table definition, then rechecks only FROM TIME/UNTIL TIME limitations, defined in the SMART Table definition, and keeps the SMART Table in Active status even when the FROM TIME/UNTIL TIME limitations are not satisfied.

• N – Do not check the SMART Table parameters once the SMART Table is active. The selection process of the jobs belonging to the Active SMART Table, only checks the job run time criteria. Default.

#ONSPLOC

(WM0868)

Number of attempts to locate an on-spool job before passing the job from the Submit subtask to the Status subtask.

When an on-spool job is handled by the Submit subtask of Control‑M, an attempt is made to locate it on spool in Hold status. If it is found in Hold status, Control‑M first releases it, then passes it to the Status subtask. If it is not found in Hold status, the job is passed immediately to the Status subtask without releasing it.

• Mandatory

• Maximum: 9999

• Default: 5

AECACHL

Name of a partitioned data set member (PDS), pointed to by the DAGLOBAL DD statement in the Control‑M monitor, which includes a list of AutoEdit Global members that are to be loaded into the AutoEdit Cache of the Control‑M monitor.

Using the AutoEdit cache dramatically improves Control‑M monitor performance, by eliminating the need to read AutoEdit members for each and every job.

By default, this parameter has no value, which means no AutoEdit caching is performed.

A sample member can be found in the CACHLST member in the Control‑M PARM member, which also contains instructions how to specify a list of the AutoEdit members that are to be loaded into the cache.

As an alternative, you can name the PDS using the following modify command:

F CONTROLM,AECACHE=RELOAD(member_name)

For more information about the Control‑M AutoEdit Cache and about this modify command, see the Control‑M chapter of the INCONTROL for z/OS Administrator Guide.

CTRB4INC

(WM2776)

By default, Control‑M inserts the Control‑M/Restart (or Control‑M/Analyzer) step immediately before the first EXEC or INCLUDE JCL statement.

This parameter governs where Control‑M inserts the Control‑M/Restart (or Control‑M/Analyzer) step when an INCLUDE JCL statement is found before the first EXEC JCL statement.

• Mandatory

Valid values are:

• Y – ControlM inserts the ControlM/Restart (or ControlM/Analyzer) step before the first EXEC statement or before the INCLUDE statement if the INCLUDE statement precedes the first EXEC statement. Default.

• N – ControlM always inserts the ControlM/Restart (or ControlM/Analyzer) step before the first EXEC statement.

INUSE#RT

(WM2354)

The number of job submission retries that should be attempted when the JCL member is in use.

• Mandatory

• Valid values: 00 through 99

• Default: 5

INUSE#RT, in conjunction with the following parameter, INUSE#WI, takes effect in Control‑M when the submission of a job fails because the JCL member is in use, either because the member is being edited, or because the partition data set is compressed. Control‑M issues a message to the IOA Log that the job was not submitted, and assigns the job a status of NOTOK.

JCOROPT

Specifies whether Control-M automatically adds the 32-character user portion to the Job Correlator in the jobs that it submits.

The Job Correlator field in JES2 jobs has 64 characters, of which the first 32 are assigned by JES2 itself. The last 32 characters is user data that can be set by the user or the application submitting the job (with the UJOBCORR keyword in the JOB JCL statement).

The data can then be used by JES2 interfaces, such as SDSF and JES2 operator commands, to access all jobs with matching correlator values (for example, in SDSF all jobs with matching correlator values can be displayed together).

For started tasks, Control-M adds the Job Correlator value to the UJOBCORR parameter in the start command.

The Job Correlator values added by Control-M can be overridden by JES2 exits that are invoked at later stages in the job submission process. It is up to the customer to ensure that the values added by Control-M are not overridden.

Valid values are:

• NONE – do not add a Job Correlator value

• ADD – add a Job Correlator value only if the job does not already have a UJOBCORR value in its JOB JCL card. The value will only be added to jobs submitted to the local MAS (Multi-Access Spool) (but not NJE jobs), and only if all the members of the local MAS are at the correct JES2 level (2.1 and above). Default.

• REPL – add a Job Correlator for all jobs, replacing the UJOBCORR value in the job’s JOB JCL card, if it already exists. The value will only be added to jobs submitted to the local MAS (but not NJE jobs), and only if all the members of the local MAS are at the correct JES2 level (2.1 and above).

• ADDF (“force add”) – add a Job Correlator value only if the job does not already have a UJOBCORR value in its JOB JCL card. The value will be added to all jobs submitted by Control-M, including NJE jobs, and even if not all MAS members are at the correct JES2 level.

• REPLF (“force replace”) – add a Job Correlator for all jobs, replacing the UJOBCORR value in the job’s JOB JCL card if it already exists. The value will be added to all jobs submitted by Control-M, including NJE jobs, and even if not all MAS members are at the correct JES2 level.

  When the ADDF or REPLF options are specified, it is the customer’s responsibility to ensure that all the systems on which Control-M can submit jobs, must support the UJOBCORR keyword.

After changing the value of this parameter, the Control-M JCL Verify and IOA Online monitors must be recycled for the change to take effect. The Control-M monitor must either be recycled or the Control-M NEWPARM monitor command must be issued.

JCORVAL

Controls the contents of the Job Correlator field that the Control-M adds to jobs. Format: 1-32 character string.

The value can contain AutoEdit variables, which are resolved at job submission time. After variable resolution, all ‘-' characters are replaced by underscores (‘_’). All other characters that are not alphanumeric or @,#,$,_ are replaced by $. If the first character is numeric, it is replaced by $. Truncation from the end will occur if the total length after resolution exceeds 32 characters. If the final result string is null, it will be replaced by the default value:

CTM_%%$SCHDTAB%%._%%ORDERID

AutoEdit variables in the JCORVAL value are only resolved, for each job, during job submission time. Any changes in the variable values that might occur after the job is submitted will not be reflected in the job’s Job Correlator value.

After changing the value of this parameter, the Control-M JCL Verify and IOA Online monitors must be recycled for the change to take effect. The Control-M monitor must either be recycled or the Control-M NEWPARM monitor command must be issued.

JNMATORD

Specifies whether Control-M predicts the JOBNAME during order time. Mandatory. Valid values are:

• Y - Control-M predicts the JOBNAME when the job is ordered.

  Note that when the job is submitted, the JOBNAME might be updated to the actual job name assigned by JES.

• N - Control-M determines the JOBNAME when the job is submitted. Default.

  Selecting Y for the JNMATORD parameter, enables a Control-M/EM user to select the Job Name option for the EM Statistics field in the Control-M/Server configuration dialog box. Selecting the Job Name option for EM Statistics provides access for the ordered job to Control-M/EM job statistics based on the JOBNAME.

MAXJCL

Specifies the maximum size (in lines) of jobs that can be submitted by Control-M.

Valid values (lines): 0-9999999

Default: 0 (no limit)

MSGCPRES

Whether Control‑M creates an additional copy of the JES SYSDATA file (JESDS) by adding appropriate OUTPUT statements to a job, or by changing its MSGCLASS to HLDCLAS.

The option implemented by this parameter used to be implemented through the CTMX002O sample Submit Exit.

• Mandatory

Valid values are:

• Y – ControlM adds the following two additional OUTPUT statements to the job:

  Copy

  //DEFAULT OUTPUT JESDS=ALL,CLASS=*         
  //JESDS   OUTPUT JESDS=ALL,CLASS=hldclas

  where hldclas is the Control-M reserved held class defined by the CTMPARM Installation parameter HLDCLAS.

If the first INCLUDE JCL statement precedes the first EXEC statement in the job and the CTRB4INC parameter is set to Y (see CTRB4INC section), the statements are added before the first INCLUDE JCL statement. Otherwise, the statements are added before the first EXEC statement.

Extra SYSDATA files for an additional job are created in the Control‑M reserved held sysout class HLDCLAS, and the MSGCLASS of the original job remains unchanged.

• N – ControlM changes the MSGCLASS of the job without adding any OUTPUT statements. Default.

Setting this parameter to Y has the following advantages:

• Performance under ControlM is better.

• All sysout of the job pointed to by the expression SYSOUT=* remains under the original MSGCLASS; this eliminates the need to use sysout or DO SYSOUT functions to return it to the original MSGCLASS.

• The additional SYSDATA files can be automatically deleted using any automation product, such as ControlO, or any equivalent product, asynchronous to ControlM.

• The CTMX002O Submit Exit is unnecessary.

However, if you use JES3 //*ROUTE XEQ statements to route NJE jobs, you must set this parameter to N, and use the CTMX002O sample Submit Exit if necessary.

For additional tuning of the added OUTPUT statements, you can change the MSGCPRES member in the CTM PARM library. The provided MSGCPRES member contains the OUTPUT statements, as described above. Control-M performs AutoEdit resolution of the statements defined in this member.

MULTISUB

(WM3625)

Jobs submission buffering factor.

• Valid values are: 0 through 128

• Default: 0 (no buffering)

Setting this parameter enhances the Control-M submission process by using the JES spool slice window more effectively. Jobs that have been prepared for submission are accumulated before writing them into the JES internal reader. The MULTISUB parameter specifies the number of jobs that are accumulated.

For more information, see the JES2PARM Tuning Considerations section in the INCONTROL for z/OS Administrator Guide, Chapter 3 Control-M, Control-M Monitor and JES Considerations.

MULTJOBS

(WM1744)

Whether Control‑M submits to JES multiple jobs that exist in one JCL member.

• Mandatory

Valid values are:

• Y – Submit each job present in a JCL member.

• N – Submit only the first job in a JCL member. Default.

In both cases, Control‑M handles only the first job. Even if it submits the subsequent jobs, it does not perform any follow-up nor post-processing on the second and subsequent jobs.

OVERJCLM

Whether values already set in the JCL of a job can be overwritten by values inserted in the following fields of the Control‑M Job Scheduling Definition screen (Screen 2):

• SCHENV

• SYSTEM ID

• NJE NODE

Valid values are:

• Y – Values already set in JCL are overwritten.

• N – Values already set in JCL are not overwritten. Default.

• Mandatory

RECLRQST

Whether the Control-M monitor issues a DFSMSHSM RECALL request when accessing a migrated data set.

• Mandatory

Valid values are:

• Y - DFSMSHSM RECALL request issued. Default.

  The RECALL process runs asynchronously, allowing the Control-M monitor to continue submitting jobs simultaneously.

• N - DFSMSHSM RECALL request not issued. The data set is automatically restored.

  The RECALL process takes place during the OPEN process of the data set. This causes the Control-M monitor to wait for RECALL processing to finish before continuing with any further work, which may adversely affect performance. Hence, N should be specified only if DFSMSHSM RECALL requests are not supported at the site.

RELHLDJ

(WM1837)

Whether Control‑M should automatically release an on-spool job when it detects that the on-spool job is in Held status.

As explained in the preceding parameter, #ONSPLOC, when an on-spool job is found in Held status, Control‑M generally releases it before passing it to the Status subtask. However, some sites may choose to release the on-spool job manually.

• Mandatory

Valid values are:

• Y – ControlM should release an on-spool job. Default.

• N – ControlM should not release an on-spool job.

JOBSUBST

Whether to enable the Control-M Submission Substitution facility, which replaces jobs with dummy jobs or alternate jobs for testing purposes. When jobs are replaced, the post-processing statements DO SHOUT, DO MAIL, DO REMEDY, and DO REMFORCE are skipped. For more information about this facility, see Job Submission Substitution Facility.

Valid values are:

• Y – Yes, Enable Submission Substitution.

• N – No, Disable Submission Substitution facility. Default.

• S – Enable Submission Substitution facility but do not skip the DO SHOUT post-processing statement.

SUBRDRP#

Number of parallel JCL reader processes used by the Control-M monitor for reading the JCLs from the libraries and preparing them for submission.

The JCLs are then submitted by the processes defined by the SUBWRTP# parameter.

When set to 0, job submissions are serviced by the Control-M monitor using a single process that reads the JCLs, prepares them for submission, and performs the actual submission.

Valid values: 0-10
Default: 0

SUBWRTP#

Number of parallel JCL writer processes used by the Control-M monitor for writing the JCLs to JES (that is, for submitting the JCLs).

These JCLs were earlier prepared for submission by the processes defined by the SUBRDRP# parameter.

When set to 0, job submissions are serviced by the Control-M monitor using a single process that reads the JCLs, prepares them for submission, and performs the actual submission.

Valid values: 0-100
Default: 0

$GDFREQU

(WM2333)

Frequency of issuing $G D commands to a remote NJE node when the enhanced NJE support in JES2 environment is active (the ENHNJE parameter is set to Y).

The frequency is expressed in terms of Control‑M intervals.

Increasing the value of this parameter reduces the number of $G D commands. However, this may result in the information available to Control‑M as to the status of the job in a remote NJE node being less up-to-date. On the other hand, decreasing the value of the parameter may cause redundant overhead on Control‑M and the NJE lines, so BMC recommends that you do not set the value too low.

• Mandatory

• Maximum: 99, recommended only if all NJE jobs are long running jobs.

• Default: 3, meaning that ControlM issues a $GD command for an NJE job every three intervals.

#JNFMS

(WM1755)

Frequency of issuing message SPY253E (JOB NOT FOUND IN QUEUE n TIMES) when an attempt to check the status of the job failed with an indication that the job was not found.

• Mandatory

• Maximum: 999

• Default: 5

Increasing this number reduces the number of times SPY253E messages are issued. BMC recommends that you do this in cases where the setting of the #JNFRT parameter is high.

#JNFRT

(WM1754)

Number of attempts to locate a job on spool and check its status when the job is not found.

• Mandatory

• Maximum: 999

• Default: 10

Increasing this number is recommended for cases where for some reason the job cannot be found on spool for long period of time, for example, an NJE job. On the other hand, increasing this number also delays the time until Control‑M marks the job as Disappeared.

#SYSMS

(WM1764)

Frequency of issuing message JES262W.

• Mandatory

• Maximum: 999

• Default: 5, meaning that the message is issued after every five failed attempts.

Increasing this number causes fewer such messages to be issued, which is recommended if the number of retries, set by the preceding parameter, #SYSRT, is high.

#SYSRT

(WM0652)

Number of attempts to read the sysout of a job when the sysout cannot be initially read by Control‑M.

• Mandatory

• Maximum: 999

• Default: 20

Increasing this number is recommended in cases where for some reason the sysout of a job cannot be read for a long period, for example when a big sysout of a job comes back from an NJE node.

ENHNJE

(WM1883)

Whether the NJE support for JES2 is to be activated.

• Mandatory

Valid values are:

• Y – ControlM in a JES2 environment opens an MCS Console, and during execution of NJE jobs sends Status requests ($G D Command) to the remote node to check the status of the job. Default.

• N – ControlM does not activate the NJE support.

EXSTPRNG

(WM3407)

Whether to exclude a range of steps, called the EXCLUDED STEP RANGE, in job scheduling definition statements. The EXCLUDED STEP RANGE includes all steps of a job, excluding the steps from one step to another.

• Mandatory

Valid values are:

• Y – The EXCLUDED STEP RANGE facility is activated. When EXSTPRNG=Y, a minus sign appears as the first character of the step, indicating that this is an excluded step range.

• N – The EXCLUDED STEP RANGE facility is not activated. Default.
  When EXSTPRNG=N, any STEP RANGE, regardless of its name, is processed as a regular STEP RANGE (that is, the range of steps from one step to another).

TBLDELJB

Whether deletion of a job inside a SMART Table Entity before it ran (that is, in Wait Schedule status) causes the SMART Table Entity itself to end NOTOK.

• Mandatory

Valid values are:

• N – ControlM marks the SMART Table Entity as Ended NOTOK if a job in this SMART Table Entity has been deleted before execution. Default.

• O – ControlM does not take into consideration the job that was deleted before execution when it marks how the SMART Table Entity has ended.

• C – The deletion of a Cyclic Job belonging to SMART Table, which already ran at least once, does not set the status of the corresponding table to NOTOK.

LASTSTEP

(WM3180)

Whether to assign a special meaning to the $LAST and $FIRST job step names when they are specified in ON PGMST or STEP RANGE statements.

• Mandatory

Valid values are:

• Y – Treat $LAST as the last executed job step, and treat $FIRST as the first executed job step.

• N – Assign no special meaning to $LAST and $FIRST. Default.

MAXCCOK

(WM1473)

Maximum condition code for Control‑M to mark a job as ended OK.

Every job that finishes with a condition code above the value specified in the MAXCCOK parameter is considered as ended NOTOK. BMC recommends that this value be set to either 0 or 4. Setting MAXCCOK to 4 indicates that jobs ending with warning conditions (a maximum RC of 4) are considered OK.

• Mandatory

• Valid values: Up to 4 digits

• Default: 0004

MJES262W

(WM0723)

Whether Control‑M writes the warning message JES262W ("UNSUCCESSFUL ATTEMPTS TO READ JOB DATA BY SUBSYSTEM REQUEST") to the IOA Log, in addition to issuing it to the operator.

• Mandatory

Valid values are:

• Y – ControlM should write JES262W messages to the IOA Log.

• N – ControlM should not write JES262W warning messages in the IOA Log. Default.

BMC recommends that you set this parameter to the default N, since when JES is busy, the above message may be issued several times for many jobs, which in turn may fill the IOA Log with many such messages.

SAPI

Reserved parameter.

Do not alter the default value (Y) set for this parameter unless instructed to do so by BMC Customer Support.

SDSB

Whether the IBM Spool Dataset Browse interface is used to read sysout data sets.

This interface provides significant improvements in performance in a JES2 Sysplex environment with multiple systems sharing the same spool.

• Mandatory

Valid values are:

• Y – The IBM Spool Dataset Browse interface is used. Default.

• A value of N has the same effect as a value of Y.

• F – The IBM Spool Dataset Browse interface is not used.

SPYWAIT

(WM1765)

Number of 1/100 seconds to wait in the SPY subtask when an attempt to locate a job on spool failed, and a retry is required.

• Mandatory

• Maximum: 999 (almost 10 seconds)

• Default: 100 (one second)

Increasing this parameter above the value of the regular Control‑M interval time, as set in the INTERVALM parameter, may dramatically affect the overall performance, and is not recommended in any case. When Control‑M is busy, BMC recommends that you set this parameter to no more than one second, while when Control‑M is less busy you may consider increasing it. The only disadvantage of using too low a number is that Control‑M may retry too early, wasting computer time.

COPJS1ST

Controls the order in which the DO SYSOUT F statement copies the SYSOUT datasets of a job to a file.

Valid values are:

• Y – The job's JES SYSOUT datasets (JESMSGLG, JESJCL, and JESYSMSG) are always copied first, regardless of the order in which JES writes the SYSOUT datasets to the spool.

• N – The SYSOUT datasets are copied in the order in which they were written by JES. Default.

SYACTPR#

Number of DO SYSOUT processing tasks.

• Valid values: 0–10

• Default: 0 (DO SYSOUT actions processed by the CTMSPY task)

Setting this parameter to a non-zero value enhances Control-M job tracking and post-processing, by separating the tracking of jobs from the execution of DO SYSOUT actions (multi-SPY mode). By default, job tracking and DO SYSOUT actions are performed synchronously, that is, a job's status only changes to ENDED after that job's DO SYSOUT actions are executed. This may result in delays in job tracking in a JESPLEX environment when waiting for the spool slice window. When SYACTPR# is non-zero, the DO SYSOUT actions are executed asynchronously by separate tasks, preventing this type of delay. SYACTPR# specifies the number of such tasks that can run concurrently.

ATTSOEXT

File extension for SYSOUT sent by ONPGM … DO MAIL parameter.

ATTSOTSZ

(WM3701)

The maximum size in KB of the SYSOUT that is attached to email messages when ATTSYSOT=Y.

• Maximum: 999999

• Default: 5000

When ATTSOTSZ=0, the size of the attachment is unlimited.

If the size of a job's SYSOUT exceeds the value of the ATTSOTSZ parameter, the SYSOUT will not be attached to email messages that are sent for that job.

ATTSYSOT

(WM3701)

Whether the SYSOUT of the job should be attached to email messages sent as a result of DO MAIL, DO SHOUT, or SHOUT statements.

Valid values are:

• Y – The SYSOUT of the job is attached to all email messages that are sent as result of DO MAIL, DO SHOUT, or SHOUT statements.

• N – The SYSOUT of the job is not attached to such email messages. Default.

COPMEM2O

Whether the JCL member should be copied from the MEMLIB library to the OVERLIB library, when the job ends NOTOK. JCL members of cyclic or rerun jobs (using DO RERUN) may be copied only if CYC2X15 is set to Y (see the CYC2X15 parameter below).

• Mandatory

Valid values are:

• Y – The JCL member is copied.

• N – The JCL member is not copied. Default.

CRSPREFX

When a job ends NOTOK and is holding a control resource whose prefix matches the corresponding parameter, this resource is not released by Control-M, and the job continues to hold it until it is rerun and ends OK, is FORCEd OK, or is deleted through screen 3 or NEWDAY processing.

CYC2X15

(WM2322)

Whether the Control‑M monitor should call the CTMX015 job termination exit when a cyclic job ends, or either when a DO RERUN or RESTART is performed.

• Mandatory

Valid values are:

• Y – Job termination exit is called for each cycle termination of a cyclic jobs.

• N – Job termination exit is not called when cyclic job ends. Default.

DEFSTEP

Activates the issuing of warning messages when a job step (or range of steps) referenced by the ON PGMST statement in the job definition does not match any step in the JCL of the job.

• Mandatory

Valid values are:

• Y – Issue warning messages when a job step (or range of steps) referenced by the ON PGMST statement in the job definition does not match any step in the JCL of the job.

If at least one such the warning was issued for the job, the 'Post-Processing Failed' characteristic is added to job's status in Control-M.

• N – Do not issue warning messages and do not add 'Post-Processing Failed' to job's status. Default.

DELOVRER

Whether the JCL member should be deleted from the OVERLIB library if the rerun of the job ended OK. JCL members of any cycle after the first cycle in a cyclic job may be deleted only if CYC2X15 is set to Y (see the CYC2X15 parameter above).

Valid values are:

• Y – The JCL member is deleted.

• N – The JCL member is not deleted. Default.

DELOVRUN

Whether the JCL member should be deleted from the OVERLIB library if any run of any job ended OK. JCL members of cyclic jobs may be deleted only if CYC2X15 is set to Y (see the CYC2X15 parameter above).

• Mandatory

Valid values are:

• Y – The JCL member is deleted.

• N – The JCL member is not deleted. Default.

FRCOKOPT

Whether the DO actions following codes of the form "ON PGMST ANYSTEP CODE OK" should be executed when a job is FORCEd-OK.

For further details on the operation of this parameter, see the discussion of the Force OK Confirmation window in the Control-M for z/OS User Guide.

• Mandatory

Valid values are:

• Y – DO actions following "CODE OK" are executed when job is FORCEd-OK.

• N – Such DO actions are not executed. Default.

IGNDOSYS

(WM2998)

Whether the Control‑M Monitor should ignore SYSOUT or DO SYSOUT post-processing functions when reading of the SYSDATA of the job failed.

• Mandatory

Valid values are:

• Y – Ignore SYSOUT or DO SYSOUT post-processing functions when reading of the SYSDATA of the job failed.

• N – Do not ignore SYSOUT and DO SYSOUT post-processing functions when the SYSDATA files of the job could not be read. Default.

IGNIGD17

(WM3255)

Whether the Control‑M monitor should treat the IGD17001I and IGD17101I messages as NCT2 (Not Cataloged 2) conditions.

Valid values are:

• Y – The ControlM monitor does not treat the IGD17001I and IGD17101I messages as NCT2 conditions.

• N – The ControlM monitor treats the IGD17001I and IGD17101I messages as NCT2 (Not Cataloged 2) conditions. Default.

MSEL250I

(WM1520)

Whether the Control‑M monitor should issue the SEL250I message (CONDITION cond_name {DELETED | ADDED}: OID=orderid, RUNNUMBER=run_num) when it adds or delete a condition on behalf of a job due to an OUT or DO COND statement.

• Mandatory

Valid values are:

• Y – ControlM issues the SEL250I message for each condition it adds on behalf of a job.

• N – No SEL250I message is issued. Default.

For backward compatibility, the default value of this parameter is N. However, BMC recommends that you set it to Y, which logs all condition activity in the IOA Log, thus enabling you to trace the addition and deletion of conditions if necessary.

MULJESPP

Whether Control‑M post-processes NJE jobs that were executed on both JES2 and JES3 systems.

• Mandatory

Valid values are:

• Y – ControlM post-processes jobs that were executed on both JES2 and JES3 systems.

• N – ControlM does not post-process jobs that were executed on both JES2 and JES3 systems. Default.

QRSPREFX

When a job ends NOTOK and is holding a quantitative resource whose prefix matches the corresponding parameter, this resource is not released by Control-M, and the job continues to hold it until it is rerun and ends OK, is FORCEd OK, or is deleted through screen 3 or NEWDAY processing.

SCRECALL

        (WM2998)

Whether a migrated scheduling library is recalled during the processing of a DO FORCEJOB request.

Valid values are:

• Y – The scheduling table is recalled, and Control-M tries to reorder the job in the same way as if the scheduling table is in use (see parameters FORCE#RT and FORCE#WI in the MONITOR Section).

• N – The scheduling table is not recalled, and the job is not scheduled. Default.

ARCHFBA

Whether to create the Archive file with FBA or FB record format.

• Mandatory

ARCPRI#

Non-zero primary allocation size for the sysout archive data set.

• Mandatory

ARCRET

Archive retention period in days.

ARCSEC#

Secondary allocation size for the sysout archive data set.

ARCSPCT

Allocation type for the sysout archive data set.

• Mandatory

APIMSTSO

Whether to suppress messages from the CTMAPI utility when it is invoked under TSO.

• Mandatory

Valid values are:

• Y – Suppress messages from the CTMAPI utility.

• N – Do not suppress messages from the CTMAPI utility. Default.

EDITOVRL

(WM2004)

Where a JCL Edit request is to be performed (from Control‑M/Enterprise Manager only).

• Mandatory

Valid values are:

• Y – Save the JCL Edit from ControlM/Enterprise Manager in the OVERLIB library.

• N – Save JCL Edit from ControlM/Enterprise Manager in the library from which it was read. For example, if the JCL member exists in the OVERLIB library, the JCL is saved in the OVERLIB library. Otherwise, it is saved in the MEMLIB library. Default.

SCHPREVD

(WM1350)

Whether the SAC parameter in the job/SMART table definition, which is used for conversion only, is active.

• Mandatory

Valid values are:

• Y – SAC is active.

• N – SAC is not active. Default.

STENT#

The maximum number of job occurrences that can be accumulated into a Statistics file job record.

• Valid values are: 20-200

• Default: 20

Warning: Changing this parameter to a lower value after the Statistics file is already in use may cause the statistics for the most recent job occurrences to be lost.

DWNLDERR

Action to be taken when the Control-M Application Server (CTMAS) encounters an error during the download process. Valid values are:

• EMX – Log the event in the IOA log file and exclude the problematic job from the next download. Default.

• LOG – Log the event in the IOA log file.

HCDELAYT

The minimum time interval in seconds, interpreted as a "process delay" in the Control-M Health Checker. If this parameter is set to 0 the report is not produced.

• Mandatory

• Valid values are 0-999

• Default: 030

HCHECKER

Whether Control‑M monitor should use the Health Checker interface to communicate with IBM Health Checker.

• Mandatory

Valid values are:

• Y - Health Checker interface is enabled. ControlM monitor will communicate with IBM Health Checker. Default.

• N - Health Checker interface is disabled. ControlM monitor will not communicate with IBM Health Checker.

HCJDAYS

The number of days that defines a job as "dormant."

• Mandatory

• Valid values: 1-999

• Default: 365 days

HCJINTRV

The interval of time, in hours, between checks of the "dormant" jobs in the Active Jobs file. Dormant jobs have been sitting in the Active Jobs file for more than the specified days in the HCJDAYS parameter.

• Mandatory

• Valid values: 0-999

• Default: 24 hours

HCLINTRV

The interval time, in minutes, between checks for issues in the IOALOG Index file.

If this parameter is set to 0, the check is not processed.

• Valid values are 0-9999

• Default: 0

HCLOGIDX

Threshold percentage for the level of correspondence between the IOALOG Index file and the IOA Log. A warning is issued when the IOA log is indexed below this percentage.

• Valid values are 1-99

• Default: 85%

HCMEMA16

Threshold amount of virtual storage memory (in megabytes) above the 16MB line. A warning is issued when the amount of available storage memory falls below this value.

• Valid values are 0-999

• Default: 50 MB

HCMEMB16

Threshold amount of virtual storage memory (in kilobytes) below the 16MB line. A warning is issued when the amount of available storage memory falls below this value.

• Valid values are 0-9999

• Default: 256 KB

HCMINTRV

The interval of time, in minutes, between parameter checks. Each check verifies that the parameter values in the CTMPARM member in the IOA PARM library are the same as the CTMPARM settings currently in memory.

If this parameter is set to 0, the check is not processed.

• Mandatory

• Valid values are 0-999

• Default: 30 minutes

HCPINTRV

The interval of time, in minutes, between checks for job processing delays. An exception message is produced based on internal tables, maintained by the various Control‑M subtasks (such as submitter, selector, and spyer), which determines whether a job being processed by these components is experiencing excessive delays. These delays could indicate a job is not responding (hang condition).

If this parameter is set to 0, the check is not processed.

• Mandatory

• Valid values are 0-999

• Default: 1 minute

HCSINTRV

The interval time, in minutes, between checks for issues in Control-M Monitor virtual storage consumption.

If this parameter is set to 0, the check is not processed.

• Valid values are 0-999

• Default: 3 minutes

RECENA

Activates or disables the Recovery Mode processing.

Valid values are:

• Y—Activate the Recovery Mode if the Control-M monitor terminates abnormally. Default

• N—Do not activate the Recovery Mode if the Control-M monitor terminates abnormally.

If RECENA=Y(ES), duplicate submissions and DO FORCEJOB processing are prevented, regardless of the RECLEVEL value. The parameter can be changed dynamically by NEWPARM without stopping or starting the Control-M monitor.

For more information on this parameter, see the INCONTROL for z/OS Administrator Guide.

DLRECALI

Deadline scheduling recalculation rate for internal Load-Indexes, that is, the time interval between consecutive DUE-IN/DUE-OUT recalculations.

A value of 0 (the default) means that only manual recalculations are available, using the IOA online facility (REFRESH DEADLINE) or the following operator command:

F CONTROLM,REFSCHED

Valid values: 0 – 60 minutes
Default: 0

The parameter can be changed dynamically by NEWPARM without stopping or starting the Control-M monitor.

DLSCPRU

Deadline Scheduling precision unit for internal Load-Indexes, that is, the time unit (minutes or seconds) used during deadline scheduling calculations.

Setting the precision unit to seconds assists Control-M in avoiding calculation issues that might arise from rounding the results to minutes.

Valid values: S (seconds), M (minutes)
Default: S

The parameter can be changed dynamically by NEWPARM without stopping or starting the Control-M monitor.

OPTGDLVL

Limits downward changes in Load-Index level to gradual changes of one level at a time (internal Load-Indexes only).

This helps Control-M avoid steep drops in Load-Index levels and allows Control-M to adjust the workloads gradually.

This parameter works in conjunction with OPTKPLVL.

Valid values: Y, N
Default: N

The parameter can be changed dynamically by NEWPARM without stopping or starting the Control-M monitor.

OPTKPLVL

Additional time, expressed as a number of calculation intervals (the OPTLINDR parameter), that an internal Load-Index must remain in its current level, before changing to a lower level.

The purpose of delaying the change in load level is to avoid frequent Load-Index level changes and allow Control-M to adjust the workloads gradually.

Valid values: 0 – 99 intervals
Default: 0

The parameter can be changed dynamically by NEWPARM without stopping or starting the Control-M monitor.

OPTLINDR

Interval, in seconds, between Load-Index level recalculations for Internal Load-Indexes.

It is recommended to rely on RMF information (RMF MINTIME) to avoid excessive recalculations while the system information (taken from RMF) is not updated.

Valid values: 0 – 999 (seconds)
Default: 0

Special values:

• 0: Take the interval from the RMF where the Control-M Global monitor is running.

• 999: Never refresh Load-Index levels of Internal Load Indexes. The last measured level remains in effect.

The parameter can be changed dynamically by NEWPARM without stopping or starting the Control-M monitor.

OPTMODE

Control-M Workload Optimization mode

Valid values:

• Y — Control-M Workload Optimization is enabled. Load-Indexes are calculated and used by Workload Policy rules. Default.

• N — Control-M Workload Optimization is disabled. Load-Indexes are not calculated and rules that reference Load-Indexes in Workload Policies are ignored.

• C — Calculation of Load-Indexes only. Load-Indexes are calculated, but rules that reference Load-Indexes in Workload Policies are ignored. This mode allows Load-Index calculations without impacting the submission process and should be used for testing purposes only.

For this parameter, the NEWPARM monitor command cannot be used to dynamically activate changes.

OPTMVLID

Whether to enable setting levels of MainView Alarm (MVA) Load-Indexes. The data for this type of Load-Indexes is obtained by CMEM or by Control-O from MainView Alarm Management.

Valid values:

• Y — MainView Alarm-based Load-Indexes are enabled.

• N — MainView Alarms-based Load-Indexes are disabled. Default.

RESETPRY

Maximum priority to be reset during the job submission process.

If a job's priority is equal or lower than RESETPRY, the priority is ignored and the job is considered as having the lowest possible priority, allowing it to be submitted according to its calculated DUE-IN time (the time at which it must start in order to meet its own SLA and the SLAs of its dependent jobs).

If a job's priority is higher than RESETPRY, the priority is taken into account and the job is processed accordingly.

As priority has precedence over DUE-IN, this parameter allows resetting the job's specified priority so that DUE-IN can have a greater impact, while those jobs with the highest priorities retain their original precedence.

Valid values: Any valid priority value
Default: " " — priority is not to be reset.

The parameter can be changed dynamically by NEWPARM without stopping or starting the Control-M monitor.

ARMELMNT

The name that represents Control‑M as an element of automatic restart management (ARM).

When this parameter is enabled, the operating system automatically restarts Control‑M after an unexpected failure, using ARM.

When specifying an element name, apply the following rules:

• The name can be from1 through 12 characters. ControlM appends to this name the 4-character system identifier on which the element originally registered, which makes this name unique across the Sysplex.

• Valid characters are uppercase alphabetic characters, the digits 0 through 9, and the following symbols: $, #, @ and underscore (_).

• The first character may not be a number.

• Element names that start with A through I, and SYS, are reserved for use by IBM.

Valid values are:

• N or NO or '' (Blank) – ARM for ControlM is not enabled. The operating system does not attempt to restart ControlM if it fails unexpectedly. Default.

• policy_name – Name of the ARM policy. ARM for ControlM is enabled. The operating system attempts to restart ControlM if it fails unexpectedly.

This element name must exactly match the ELEMENT and ELEMENT_NAME ARM policy parameters, or the operating system will use the default policy. For more information, see the section on ARM support in the Control‑M chapter of the INCONTROL for z/OS Administrator Guide.

DOCUT

Whether DOCU/TEXT is installed at the site.

For more information on this parameter, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

JSCAN

Whether a JOB/SCAN product is installed at the site.

For more information on this parameter, see the "Installing Control-M" chapter in the INCONTROL for z/OS Installation Guide: Installing.

M622RC4

Causes the CTMRELRS utility to end with a return code of 4, instead of a return code of 12, if message CTM622E is displayed.

Valid values are:

• Y – The utility ends with a return code of 4.

• N – The utility ends with a return code of 12. Default.

GRFSIZE

OPTLIND#

STTPSIZ