in reply to System call

It seems to me that there is no reason to use system to call your perl script. Just set local values for @ARGV and call do:
# instead of system perl... { local @ARGV = ("G:/PUB_HLTH/blah/blah", "G:/PUB_HLTH/blah/blah2"); do '20_October_2004_K.pl'; }
I do not know whether this will fix your problem, but it might. You don't seem to close the file, and if you have a series of several different processes that open and append to the file without closing it, they may be stepping on each others' toes (although as each process exits, it should implicitly close the file).

Caution: Contents may have been coded under pressure.

Replies are listed 'Best First'.
Re^2: System call
by Win (Novice) on Dec 22, 2004 at 10:40 UTC
    I have fixed the problem now. But I am interested to know whether there would be advantages to using this method that I don't know about.
      You would have fewer processes running (so less resources are consumed), and any global variables from the master script would be visible in the auxiliary script.

      Caution: Contents may have been coded under pressure.