Skip to content
CA Deliverâ„¢ - 14.0
Documentation powered by DocOps

Initialization Parameters

Last update June 12, 2015

As an administrator, you can use a set of parameters that initialize CA Deliver when you start the started task. This section describes these initialization parameters and presents them in alphabetical order.

You define initialization parameters in the data set named RMOPARMS.

You define the RMOPARMS data set in the start procedure JCL by specifying a DD statement named RMOPARMS. The RMOPARMS data set contains fixed, 80-byte records (blocked or unblocked).

Sample member RMOPARMS in data set CAI.CVDEOPTN contains default initialization parameters.

CA Deliver reads the information in positions 1 to 71 of the records in RMOPARMS. Information in positions 72 to 80 is ignored so you can use these positions for other purposes (for example, to contain sequence numbers).

Initialization Parameter Syntax

Syntax

parameter=value

where:

  • parameter
    Defines the initialization parameter.
  • value
    Defines the value to be assigned to the initialization parameter.

Syntax Rules

When specifying initialization parameters, do the following:

  1. Specify one initialization parameter for each record.
  2. Do not insert blank spaces between the initialization parameter and the equal sign or between the equal sign and the parameter value. The following is an example of a valid statement:

    ARCH1=DIRECT

  3. Continue an initialization parameter statement onto the next record by doing one of the following:
    • Move the statement so that its last character extends past column 71.
      In this case, CA Deliver looks for the remainder of the statement in column 1 of the next record.
    • Insert a comma at the end of the record to be continued and enter the remainder of the statement in the next record.
      Leading blanks in the next record are ignored.

Inserting Initialization Parameter Comments

To insert a record-long comment in RMOPARMS, enter an asterisk (*) in the first column. Characters after the asterisk are ignored.

To insert an inline comment, enter a space at the end of the initialization parameter statement.

Note: Characters after the space are ignored.

JOBCLSL Initialization Parameter

The JOBCLSL initialization parameter is required. You must specify a value for this parameter for CA Deliver to operate properly.

BNDLMOUT, Attributes, and the First Report in a Bundle

The initialization parameter BNDLMOUT works this way:

  • If you set this parameter to NO or use the default for the started task, the attributes used to print a bundle (except for carriage control attributes) are obtained from the first report in the bundle that is written. 
    All the reports in the bundle are consequently printed with the same attributes.
  • If you set this parameter to YES for batch bundling only, each report is printed with its own attributes except for destination and class.
Important: To accomplish this individual printing, a new DD statement is allocated and used whenever any attribute changes thereby generating several SYSOUT DD statements for the bundle. To ensure that the SYSOUT DD statements print together, an OUTPUT JCL statement is dynamically created with the GROUPID parameter and is referenced by the DD statements.

If a bundle distribution identifier is not defined in the bundle definition attributes, then the distribution identifier for the first distribution point in the bundle is used.

Bundle Output Task and the BOT Initialization Parameter

The BOT (Bundle Output Task) initialization parameter is a subtask of the started task that periodically scans the active bundle queue for bundles that are ready to print. The time period between scan actions is specified by the BNDLSCAN initialization parameter.

When CA Deliver runs on multiple operating systems in an installation, a bundle output task normally executes under CA Deliver on each operating system. BOT specifies whether the bundle output task is initially started. Also, operator commands are provided to start and stop the bundle output task.

Running BOT on multiple operating systems that share the same database can affect performance.

You can choose to not run the bundle output task on an operating system.

If a bundle is defined with JOB statements, the bundle output task submits a batch job to compose and print the bundle. The job that is submitted corresponds to skeleton JCL member RMOJCLB.

You can achieve parallel processing by submitting separate batch jobs to comprise the bundles. If no JOB statements are defined for a bundle, it is printed directly by the bundle output task.

Was this helpful?

Please log in to post comments.