As a USER, the new ASSIGN functionality greatly simplifies adjusting which file is being read when repeating the same ddck in a project.
Such simplicity does not yet exist, however, when doing variations on the input file.
For the case of a single ddck (not reused), one can currently:
Create multiple config files, changing only the file that is being read. Then run the list of configs.
Create multiple ddcks, changing only the file that is being read. Then use changeDdckFile variations.
Prepare all files and associated logical units. Then use the variation to say which logical unit to read from (details below).
Case 2 is similar to the case for which DDCK AS and ASSIGN were original introduced.
For case 3, one could use something like:
ddck entries:
As a USER, the new ASSIGN functionality greatly simplifies adjusting which file is being read when repeating the same ddck in a project. Such simplicity does not yet exist, however, when doing variations on the input file.
For the case of a single ddck (not reused), one can currently:
Case 2 is similar to the case for which DDCK AS and ASSIGN were original introduced.
For case 3, one could use something like: ddck entries:
config usage:
variation inputFileVariation unitReaderUsed unitReader1 unitReader2 unitReader3
It would be great if this could be simplified further. Maybe to something like (config only):
This latter option would then vary only the path of the given assign statement:
ASSIGN "..\file1.csv" unitReader1