Re: Can't open some file members after upgrade to 6.1 - RESOLVED

Thanks, Chuck.

I have verified that a CPYF REPLACE(*YES) request to the problem file
which has ALWDLT(*NO) does NOT fail.

I will report this as a defect.



Michael Kirkpatrick
Western Dental Services, Inc.
Information Systems / IBM i™ Development
(
Phone:
(714) 571.3582
(
Toll free:
(800) 471.4444
7
Fax:
(714) 480.3001
*
Email:
mkirkpatrick@xxxxxxxxxxxxxxxxx
8
Web:
http://www.westerndental.com/





From:
CRPence <CRPbottle@xxxxxxxxx>
To:
midrange-l@xxxxxxxxxxxx
Date:
08/18/2008 06:42 PM
Subject:
Re: Can't open some file members after upgrade to 6.1 - RESOLVED



Hmmm... this message appeared as a new thread, so my prior message
was a response made before having read the quoted text in this message.

The ALWDLT [Allow Delete] attribute trumps authority. Thus if there
were an operation that tries to delete a record from the file.mbr, then
that operation should be prevented irrespective of the user authority.

*However* the feature of /clear/ does not honor the /allow/
attribute, because /clear/ is not a row\record operation; i.e. the clear
is against the member.data rather than any row. Since the MTU suggests
that an attempt was made to effect consistency with CPYF by changing
CPYFRMSTMF, you could verify that a CPYF REPLACE(*YES) request that
names a TOFILE() which has ALWDLT(*NO) does not fail due to that
attribute setting. In so doing, that implies the CPYFRMSTMF feature has
gone too far in its attempt to enforce the same rules as that other
utility; i.e. report that specific change in behavior as a defect.

Regards, Chuck

MKirkpatrick@xxxxxxxxxxxxxxxxx wrote:

Jim, I think you hit on it. I restored the bad file and it is
ALWDLT *NO

On the S36 BLDFILE proc, the default is NOT delete capable

My recreating of the file as you mentioned caused it to be ALWDLT
*YES and my CPYFRMSTMF worked fine.

There is some discussion of changes to authority requirements for
CPYFRMSTMF in the Memo to Users V6R1.

http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/topic/rzaq9/rzaq9.pdf

These didn't seem to apply, as I even tried my CPYFRMSTMF using the
QSECOFR profile and still got a 'Not authorized to object' message.
Just a little misleading.

Thanks for all of the responses to this issue.