×
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.
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.
From:
"Jim Franz" <franz400@xxxxxxxxxxxx>
To:
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date:
08/18/2008 02:20 PM
Subject:
Re: Can't open some file members after upgrade to 6.1
I would suggest you be proactive, and run a
DSPFD FILE(YOURLIB/*ALL) TYPE(*ATR) OUTPUT(*PRINT) FILEATR(*PF)
to print or an outfile & check your other files.
check these values
Allow read operation . . . . . . . . . . . : Yes
Allow write operation . . . . . . . . . . . : Yes
Allow update operation . . . . . . . . . . : ALWUPD *YES
Allow delete operation . . . . . . . . . . : ALWDLT *YES
Your deleting and recreate of the earlier files would default all these
values to Y.
There could be some rule now enforced when files open that was not
enforced
before.
03 -- File capabilities will not allow open. The file's
capabilities conflict with the requested access.
Jim Franz
midrange.com
