FileNameModel


The FileNameModel parameter defines the file name that the High-speed Apply Engine uses to store information about conflicts that you specify as deferred. You can use symbolic variables as part of the file name. 

Attributes

This parameter has the following attributes:

Attribute

Value

Section

[ConflictFile]

Abbreviation

None

Required?

No

Valid values

  • Text, symbolic variables, or both. Specify variables in uppercase.
  • The name must resolve to a maximum length of 44 characters.

    This parameter supports GDG and PDS data set names.

Default value

&SYSUID..BMCAPT.&REQUESTID..D&DATE..T&TIME.

Usage

You can use symbolic variables, character strings, or a combination of both as the value of the FileNameModel parameter. For an example of the file-name model, see ConflictFile-parameters.

In some circumstances, you might need to re-apply SQL statements that have been previously written to a conflict file. If you do, remember to ensure that the name of the former conflict file (now being read as the input file) is different than the name of the current conflict file.

Symbolic variables for the FileNameModel parameter describes the symbolic variables available for High-speed Apply Engine. The variables that you specify are replaced with actual values when you run an apply request. They are resolved according to standard substitution rules.

Important

If the value for SingleFile is set to No, the agent ID will be appended to the name. For more information, see SingleFile.

Symbolic variables have the following format:

  • All variables require an ampersand (&) prefix.
  • Qualifiers in the model are separated by a period.
  • If necessary for substitution, use a trailing period to delimit the variable name.
  • The resulting name must be less than or equal to 44 characters long.
  • Date and time variables must be prefixed by an alphabetic character.

You must specify the variables in uppercase. You can specify character strings in lowercase or mixed case if you enclose the value of FileNameModel in quotation marks.

Variable

Description

&REQUESTID

The job ID assigned by the system when the apply request is processed

&DATE

The current date in the format yyyyddd, where

  • yyyy is the year
  • ddd is the numeric day (001 to 366)

    When the &DATE variable is part of the file name model, you must include an alphabetic prefix (for example, D&DATE).

&DBSERVER

The SSID of the current Db2 subsystem

You can specify either &DBSERVER, or &SSID. High-speed Apply Engine determines this value from the SSID parameter

&JOBNAME

The batch job name for the apply request

&SSID

The subsystem ID (SSID) of the target Db2 subsystem

&SYSUID

The user ID associated with the apply request

&TIME

The current time in the format hhmmss, where:

  • hh is the hour
  • mm is the minute
  • ss is the second

When the &TIME variable as part of the file name model, you must include an alphabetic prefix (for example, T&TIME).

The High-speed Apply Engine supports the following additional data set naming conventions in the FileNameModel parameter:

  • Generation data group (GDG)

    Define the GDG base data set before you execute High-speed Apply Engine. For multiple conflict files (multiple agents), define a GDG base for each file (agent) before you execute High-speed Apply Engine. A typical GDG model name is shown in the following sample:

    &SYSUID..BASENAME..D&DATE..T&TIME.MIGR(+1)
  • Partitioned data set (PDS) member names

    High-speed Apply Engine does not support PDS data sets for multiple conflict files. A typical PDS model name is shown in the following sample:

    &SYSUID..BASENAME..D&DATE..T&TIME.MIGR(WKLY01)

 

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