I am running a batch script in a DB2 CLP environment and have encountered a timing problem occasionally during batch processing. This only happens on 2000 Server: the script will skip commands intermittently...e.g. a 'db2start' command will not be run...it is completely skipped...I originally thought this to be a DB2 issue, but after testing on other environments, I concluded that it must be 2k Server...Has anyone ever seen this behaviour? If so, how can it be fixed? Any and all advice is appreciated.
Thanks,
Eric
Thanks,
Eric