ALL About TSK files
These TSK files are pure text files and contain an entry for every action within the form:
with = T, D, P, I, V (Table structure, Data, Primary key, Index, View)
= C, I, E (Create, Import, Export),
= xeq, ok, err
For the first time, R3load reads a TSK file completely, closes the file, renames it during a TSK.bck (for example, SAPSDIC.TSK.bck) and opens the TSK file for writing. After each execution an entry of the action is written with the corresponding status.
If all actions are processed, or if the unprocessed actions might be written back to the TSK file after an error, the TSK.bck file is deleted. During start-up, if R3load also finds a TSK.bck addition to a TSK file , it terminates immediately with a corresponding error message, as this either means an R3load process is running and is processing this request, or that a significant error has already occurred (possibly with a core dump) which will not be eliminated during the restart, but requires user intervention (for example, a full filing system , corrupt files after disk crash) When the error has been eliminated you want to merge the TSK file and therefore the TSK.bck file before or during the restart of the R3load.
There are several options available to do this:
o Manual: The TSK file contains current entries for all objects that are processed. The bck file contains entries for all objects, however, the status could also be outdated. When you merge both the files, the entries missing within the TSK file must be manually transferred from the bck file. You must then rename the bck file.
o Call R3load with the extra option '-merge_bck' (in this case, all missing entries are set to the status 'err'). This consolidates the TSK file and also the bck file and the R3load for the export or
import is started. If the R3load processes are started by the MigrationMonitor, you'll configure the extra R3load option within the *_monitor_cmd.properties file.
o As of a particular patch level in Release 6.40, the R3load contains the choice '-merge_only'. If you call the R3load with the choice '-merge_only , only the TSK file and therefore the bck file are
merged, but the export or import isn't started. You can use the choice 'R3load -h' to see whether the R3load contains the choice '-merge_only'.
These TSK files are pure text files and contain an entry for every action within the form:
with = T, D, P, I, V (Table structure, Data, Primary key, Index, View)
= C, I, E (Create, Import, Export),
= xeq, ok, err
For the first time, R3load reads a TSK file completely, closes the file, renames it during a TSK.bck (for example, SAPSDIC.TSK.bck) and opens the TSK file for writing. After each execution an entry of the action is written with the corresponding status.
If all actions are processed, or if the unprocessed actions might be written back to the TSK file after an error, the TSK.bck file is deleted. During start-up, if R3load also finds a TSK.bck addition to a TSK file , it terminates immediately with a corresponding error message, as this either means an R3load process is running and is processing this request, or that a significant error has already occurred (possibly with a core dump) which will not be eliminated during the restart, but requires user intervention (for example, a full filing system , corrupt files after disk crash) When the error has been eliminated you want to merge the TSK file and therefore the TSK.bck file before or during the restart of the R3load.
There are several options available to do this:
o Manual: The TSK file contains current entries for all objects that are processed. The bck file contains entries for all objects, however, the status could also be outdated. When you merge both the files, the entries missing within the TSK file must be manually transferred from the bck file. You must then rename the bck file.
o Call R3load with the extra option '-merge_bck' (in this case, all missing entries are set to the status 'err'). This consolidates the TSK file and also the bck file and the R3load for the export or
import is started. If the R3load processes are started by the MigrationMonitor, you'll configure the extra R3load option within the *_monitor_cmd.properties file.
o As of a particular patch level in Release 6.40, the R3load contains the choice '-merge_only'. If you call the R3load with the choice '-merge_only , only the TSK file and therefore the bck file are
merged, but the export or import isn't started. You can use the choice 'R3load -h' to see whether the R3load contains the choice '-merge_only'.
