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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.