Looking for Ideas

[Del]

I seem to have programmed myself into a corner...
Running under SCO Unix...
We run a batch jobstream every night.
Prior to running, I delete all the lock files to prevent the batch jobs from hanging up on a locked file, which happened many times before I finally started deleting lockfiles before kicking off the jobstream.
Problem is, when the users get in and start using the files the next day, filePro creates new lock files with read write permission for filePro only.
This is ok when running regular filePro apps, but when users run FPSQL they get errors saying permission is denied on the lockfile.  So they can't run their FPSQL reports unless they log in as root.  I don't want them logging in as root.
Why doesn't FPSQL run as filePro with access to filePro owned files like the rest of the filePro apps?  I can run dclerk on these files just fine, but FPSQL gets a permission error on the lockfile.
I don't know how to change the umask for filePro so that it will create lockfiles  with read permission for user, group and other.
I can't be going in and changing permissions on the lockfiles all the time.
I'm sure I am not the first to deal with this - what have others done about this?
Any suggestions?

Del
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20070726/f6b5c2a0/attachment.html