Valid for
Extract
Description
Use FILERESOLVE
to alter the rules for processing wildcard file and table entries. By default, wildcard FILE
entries are processed each time the wildcard rule is satisfied. If incorrect syntax is entered in the FILE
parameter, this can lead to ABEND
conditions after startup parameters have been processed.
Replicat also processes file lists with wildcards, but it does so dynamically and the default value of FILERESOLVE
DYNAMIC
can only be altered for Extract.
Default
DYNAMIC
Syntax
FILERESOLVE {DYNAMIC | IMMEDIATE | BOTH}
DYNAMIC
Wildcard FILE
entries are processed each time the wildcard rule is satisfied.
IMMEDIATE
Existing files or tables that satisfy the wildcard definition are processed at startup.
BOTH
Files existing at startup are processed at that time, and files created after startup are processed when encountered.
Examples
Consider the following scenario. $DATA1
.DAT
.FILE1
exists when Extract starts, and $DATA1
.DAT
.FILE2
is created after startup.The following example results only in extraction from FILE1
. In addition, the list of files to which the wildcard applies is immediately available in the report.
FILERESOLVE IMMEDIATE FILE $DATA1.DAT.*
In this case, the file list for $DATA1.DAT.*
is resolved immediately, and future additions to this list are ignored.
The following example results in the extraction from both TABLE1
and TABLE2
. However, the FILE
parameter is not resolved until a record for TABLE1
or TABLE2
is encountered. Therefore, the MAP
statement is not checked for validity until that point.
FILERESOLVE DYNAMIC TABLE $DAT1.DAT.*, TARGET $DATA2.DAT.TEMPLATE, COLMAP (COL1 = COL2);
In the following example, if TABLE1
exists at runtime, but TABLE2
does not, the MAP
for TABLE1
is checked for syntax immediately, and TABLE2
will still be picked up.
FILERESOLVE BOTH TABLE $DATA1.DAT.*, TARGET $DATA2.DAT.TEMPLATE, COLMAP (COL1 = COL2);