- Article Type: General
- Product: Aleph
- Product Version: 20
We're working on a script to automatically ftp & load files from YBP. We're anticipating that there will typically be 1-3 files to load. We're planning to do the load with p_file_90.
We were hoping to do this along the lines of:
ftp file A
load file A (batch queue)
ftp file B
load file B (batch queue)
ftp file C
load file C (batch queue)
The reason I wanted to submit these to the batch queue, instead of simply running them from the script, was so the next file could be ftp'd immediately. From your response, it sounds like this will work, but the load job will begin immediately, even if the previous job in the queue has not finished running.
Is it OK to run multiple instances of p_file_90 run simultaneously? Or do we need to rework this so that they run from the script in sequence?
There can be problems with running jobs simultaneously, but you could try it....
The problems have to do with the jobs writing to a file with the same name.
If you give the Report file for each job a different name, that will prevent a conflict there. But the p_file_90 file-01 step writes a file.1 work file and the file-02 step writes a file.2 file. These could conflict.
I think it is better to create a script which does the ftp and load for each file in sequence. (This presumes that the ftp can be included in a script OK.)
- Article last edited: 10/8/2013