Hi bakunin thanks for your time.
Your second approach will do the trick and I will suggest this to my manager. I will then try to schedule all three process is a resonable way 1.) creation of file test3 by black-box-script 2.) chmod of test3 by cronjob 3.) pick-up of modified file tes3 by SAP-Job

However I have done some more searching and was thinking of using a sticky-bit approach but unfortunately this does not seem to work for me either.

This is my situation:
-rwsrwxrwx 1 dmadmin dmadmin 15 Mar 19 11:03 change.sh
-rw-r--r-- 1 dmadmin dmadmin 5 Mar 19 10:53 test3

Where test3 is the file in question and change.sh is a script to change the mod of test3 by the user dmadmin. So in change.sh you will find something like:

Code:

#! /bin/ksh
chmod 777 test3

My understanding of the sticky bit:

Code:

chmod u+s change.sh

is that if I set the sticky-bit any user can now execute change.sh as the orginal user of the script (dmadmin) itself having all the permissions and should be able to change the mode of test3 to 777.

However if I run change.sh as a different user (otheruser in this case) I get the following error message:

/apps/otheruser > change.sh
chmod: can't change test3: Not owner


We're on HP-UX.

Thanks for the help