QUSER owns IFS but is *EXCLUDED form that object ... any ideas

Our system operations group has been "working" with the security
settings on our i5.



Now we have a situation that goes like this:



Job running under QUSER

Job creates file

Job uses CPYTOSTMF or CPYTOIMPF to change format and copy to IFS folder

Job swaps users

Job changes permission of copied file to allow public access

Job swaps back to QUSER



This work fine for years.



Now the file in IFS folder

Ower: QUSER

Authority: *PUBLIC *RX

QUSER *EXCLUDED



Weird!



Any suggestion where to look for the problem?



I looked at authorities from the root to the end folder. QUSER is not
excluded anywhere on the path.



Thanks!

Bill Blalock



_____________

The information contained in this message is proprietary and/or confidential. If you are not the
intended recipient, please: (i) delete the message and all copies; (ii) do not disclose,
distribute or use the message in any manner; and (iii) notify the sender immediately. In addition,
please be aware that any message addressed to our domain is subject to archiving and review by
persons other than the intended recipient. Thank you.
_____________