FileName (CFN)

The FileName (CFN) parameter specifies the name of a data set or file that contains configuration parameters for an apply request.

Attributes

This parameter has the following attributes:

Attribute

Value

Section

[Configuration]

Abbreviation

CFN

Required?

No

Valid values

  • A fully qualified data set name or a DD name

  • None

    Indicates that there is no configuration file (High-speed Apply Engine uses default values)

Default values

SYSIN

Related topics

BindTuning-parameters

FileName-EFN

FileName-DFN

FileName

Mainframe batch job

Usage

This parameter is frequently specified as an override in the apply request. If you do not specify this parameter in the request, the High-speed Apply Engine attempts to locate a file name, data set name, or DD name with the default value.

Because this parameter accepts a value of None, High-speed Apply Engine ignores any file, data set, or a DD statement with a name of 'none' (regardless of uppercase or lowercase characters).

For the configuration file, when you do not specify a file name, High-speed Apply Engine uses the default configuration file name (apeconfig.ini).

For mainframe targets, you can specify either a data set name or a DD name, as follows:

  • If you specify a name that is longer than eight characters, High-speed Apply Engine treats it as a fully qualified data set name. The data set must already be allocated and cataloged.

  • If you specify a name that is eight characters or fewer, High-speed Apply Engine treats it as a DD name. The DD name must refer to a DD statement in the same apply request. If the character string is not a valid DD name, High-speed Apply Engine treats it as a data set name.

    For the configuration file, you can use the DD statement to refer to multiple configuration files. For more information, see Multiple configuration files for DB2 on mainframe targets.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*