RE: V5R3 IFS Bug??

[Mark Phippard <MarkP@xxxxxxxxxxxxxxx>]

midrange-l-bounces@xxxxxxxxxxxx wrote on 12/14/2004 11:02:48 PM:

> Mark:
> 
> Sorry for late response... got a couple days off. First thing I missed 
until 
> reading your latest was "...it has NEVER worked this way before". 
Getting to the point:
> 
> And it isn't any different in V5R3, AFAIK.

You probably jumped in late, because you missed stuff.

1)  I am not talking about the archive bit.  This is a new V5R3-specific 
flag called *ALWSAV on the CHGATR command. 

2)  I am not the only one experiencing this, it came to me from my 
customers.

3)  All QNTC objects have this value set to *NO automatically, and it is 
not possible to change it with CHGATR.  If you try, you get CPFA0AD - 
Function not supported by file system.

The issue is that this is essentially a "fake" attribute and when you 
copy/move an object from QNTC up to the IFS it brings the fake attribute 
with it (it is likely a real attribute in the IFS).  If you were to create 
a new object in the IFS, the default would be *YES, I think that copying 
objects from QNTC to the IFS should do the same.

Finally, as I said, if you were to create a new object in the IFS with 
this attribute set to *YES.  Then move the object to QNTC, and then move 
it back to the IFS, the attribute changes to *NO.  In my opinion, that is 
a good example of the general underlying problem.

Mark 

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services 
powered by MessageLabs. 
_____________________________________________________________________________