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 |
DBMS | Db2, Db2 LUW, Oracle |
Required? | No |
Valid values |
|
Default value |
|
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.
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.
- For mainframe targets:
- 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
|
&DBSERVER |
|
&JOBNAME | The batch job name for the apply request |
&SSID | The subsystem ID (SSID) of the target Db2 subsystem This variable is not valid for Oracle and Db2 LUW targets. |
&SYSUID | The user ID associated with the apply request |
&TIME | The current time in the format hhmmss, where:
For mainframe targets, when the &TIME variable as part of the file name model, you must include an alphabetic prefix (for example, T&TIME). |
For mainframe targets, 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)