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

What the command string being used to change the authority ?

CHGAUT

I missed a step

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

What I missed:
- At this point authorities are fine
Job copies file into another folder in IFS using COPY command

Now the QUSER *EXCLUDED has been tacked on to the permissions

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Wednesday, January 21, 2009 4:40 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: QUSER owns IFS but is *EXCLUDED form that object ... any
ideas

Hi Bill

What the command string being used to change the authority ?

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Blalock, Bill
Sent: Thursday, 22 January 2009 11:26 a.m.
To: Midrange Systems Technical Discussion
Subject: 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