|
Hello Matt, > I think that's the IFS equivalent of a lock on a file. I'd program > in a wait period when this happens and try again. That's what we do now. The files should be all unique, but checking the scripts of the testers, we found that they did some typos and other errors, e.g. they copied a file 4 times to the server. Because processing is started via a FTP Exit program, it might in fact happen that there is a lock on the file, because there might have been 4 jobs running at the same time. (Can't say it definitely, that's what i wanted to express in the initial "design" sentence :-), because there are 20 jobs sucking on a data queue for processing orders. Could scale down, but for a load test... :-) Hm, checked that, no, the two 3029 files were not affected by these errors. They were unique. -- best regards, Anton Gombkötö
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.