Table 67 Operational parameters
Parameter |
Description |
---|---|
AMNAME |
Name of the Control-D Compressed Dataset Access Method subsystem. The name must be four characters in length. BMC recommends that you use the same name as that specified in the SSNAME IOA installation parameter so that the same subsystem can be used for the Control-M Event Manager (CMEM) subsystem, the Control-O subsystem, and the Control-D Compressed Dataset Access Method subsystem. If not specified, the name defaults to the SSNAME specified in the IOA installation parameters. Whether the subsystem can be dynamically defined is controlled by the IOA Installation SSALLOC parameter. |
Note: The value of AMNAME must be unique among all the existing IOA installations that may run on one system. |
|
DAYTIMED |
Start time of the Control‑D work day.
The format is: DAYTIMED=+hhmm or DAYTIMED=-hhmm where:
The DAYTIMED parameter specifies to Control‑D when a new work day begins. For example, if DAYTIMED is set to +1000, the hours between midnight and 10:00 a.m. are considered as part of the work day of the previous date, that is, 6:00 A.M. on February 10th, is in the work day of February 9th. Most sites set DAYTIMED between +0900 and +1400. Every day at the specified time, the monitor performs a series of procedures that starts a new day under Control‑D. One of these important procedures cleans the Active Missions file of missions that finished executing OK, or with an execution date range that has expired. For more information, see the Control‑D and Control‑V chapter in the INCONTROL for z/OS Administrator Guide. |
CTDMON# |
The number of parallel Control‑D monitors, including generic monitors, that can work concurrently on the same Active Missions file. The reason for activating more than one monitor is speed of decollation. One Control‑D monitor can decollate one job at a time.
If a large number of sysouts must be processed in a very short time, more than one Control‑D monitor can be opened. Each monitor decollates in parallel to the others. Every additional Control‑D monitor is named by changing the last character of the Control‑D procedure. For example:
The main Control‑D monitor activates and controls all the other monitors. |
ESCAPCL |
Escape class for printouts directed to Generic classes. It must be different than the Generic class. When the GENCLAS option is activated, Control‑D reads every output that appears on the spool in one of the Generic Decollation classes (the GENCLAS parameter), even if it is printed by the Control‑D monitor. Therefore, it is important to direct outputs printed by Control‑D away from Generic Decollation classes, even if the user requested it by mistake. In such cases, the output is routed to the ESCAPCL.
|
GENJOBM |
Threshold of QUEUE size (number of jobs in the generic class in the JES spool) to stop a secondary Control-D monitor.
|
GENJOBX |
Threshold of QUEUE size (number of jobs in the generic class in the JES spool) to start a secondary Control-D monitor.
|
INTERVLD |
Sleeping interval of the Control‑D monitor. The monitor is dormant most of the time. It "wakes up" after each specified interval and determines which tasks it must carry out. The format for INTERVLD is HHMMSSth, where:
Leading zeros may be omitted. For example, three seconds, 00000300, may be specified as 300.
The value for INTERVLD should be specified according to the computer model. Its value can also be modified using an operator command. For information, see the Control‑D and Control‑V chapter in the INCONTROL for z/OS Administrator Guide. |
INTERVLG |
Interval between GENERIC queue size tests. Control-D can automatically change the number of active Control-D decollation monitors based on the number of JOBs in the JES spool that are waiting for decollation in the generic class. You can define a threshold for the number of JOBs in the spool that will be checked by the main monitor. If the number of JOBs in the spool is low (less than the GENJOBM parameter), the main monitor will stop one of the secondary monitors. If the number is too high (more than the GENJOBX parameter), the main monitor will activate a new decollation monitor. GENJOBX should be higher than GENJOBM. For the feature to work properly, we recommend defining the same set of generic classes in the GENCLASS parameter for all Control-D monitors. If the INTERVLG, GENJOBM, or GENJOBX parameter is not defined or is set to zero, or if the GENERIC process is not active, this feature is not activated. The format for INTERVLG is HHMMSSth, where:
Leading zeros may be omitted. For example, 5 minutes, 00050000, may be specified as 50000.
The value for INTERVLG should be specified according to the computer model. |
NONSWAPD |
Control‑D should be non‑swappable for performance reasons. Otherwise, Control‑D may be swapped out on each interval, which can slow down the monitor.
Valid values are:
|
Note: Sites with logically partitioned 3090/ES9000 machines should implement non-swappability by using PPT entries and setting the NONSWAPM parameter to N in CTMPARM (if Control‑M is installed) and CTDPARM. |
|
OUTGRP |
This parameter identifies each chunk that Control‑D sends to the spool in a unique way. For additional information about this parameter, see the Control‑D and Control‑V chapter in the INCONTROL for z/OS Administrator Guide.
Valid values are:
|
PRTMON# |
Number of Printers Control monitors that are activated under Control‑D. One Printers Control monitor is usually sufficient, since it can handle approximately 20 printing missions concurrently. The number of concurrent printing missions can be specified in Wish WD2618. If your data center is printing on several printers concurrently, an additional Printers Control monitor may be required. When counting printers, count only main computer printers that print large volumes of paper. Do not count remote printers.
Every additional monitor is named by changing the last character of the Control‑D Print Monitor procedure. For example, if PRTMON# is set to 3, the following monitors are automatically activated: CTDPRINT, CTDPRIN2, and CTDPRIN3. |
PRNTCLS |
Global Printing Class override. When specified, Control‑D prints all printing mission reports output to the specified class. At JES2 sites, leave PRNTCLS blank (null) during installation. At JES3 sites, this class is mandatory and must be reserved for Control‑D printing, meaning, no other source should print on this class. For more information, see Step 7 – JES3 considerations (optional). |
SMF |
SMF records to be generated for accounting purposes.
Valid values are:
Control‑D can generate SMF records containing the number of lines and pages printed for each user, report or job. This permits accounting based on usage by end users, as opposed to standard accounting by job name. SMF record data can be controlled by User Exit CTDX006. |
STATD |
Whether to generate statistical data about Control‑D usage. Some Control‑D reports depend on the availability of this statistical data.
Valid values are:
|
BKPUTIL |
The type of backup and restore product that is in use at the data center: Valid values are:
|
DFLTRST |
Default name of a restore mission to be used when the user does not designate a specific restore mission name on a report restore request. If optional Wish WD0499 is applied, the Restore window is not displayed and the name of the restore mission is obtained from this installation parameter.
|
BKPJOBST |
When the BACKUP or migration job is ready for submission, Control-D can submit the job. The BKPJOBST parameter controls whether the job is submitted or not submitted.
Valid values are:
|
RSTJOBST |
When the RESTORE job is ready for submission, Control-D can submit the job. The RSTJOBST parameter controls whether the job is submitted or not submitted.
Valid values are:
|
GENOTFND |
If the GENCLAS parameter was not specified, ignore this parameter. If output classes are specified in the GENCLAS parameter, they are constantly monitored by Control‑D. When non‑held output appears on one of the specified classes, Control‑D attempts to match the job name of the output with the job names specified in all scheduled Generic decollation missions. If no mission is found with a job name that matches the job name of the spool output, the GENOTFND installation parameter determines how Control‑D handles the output file.
Valid values are:
|
Note: This parameter replaces the JES3ESC and GENDEL parameters from previous versions, which are no longer in use. Check your previous specification for this parameter to determine the required value for GENOTFND. |
Parent Topic |