Object Authority and RSTOBJ
willsher
I have a program (CL) which must be compiled with OWNER(QSECOFR) and
*OWNER authority. When I save this object using SAVOBJ I don't get any
problems. However, when I restore the object on a remote AS/400,
either the object won't restore, or I am told that 'security or format
changes' etc etc.
I suspect the key to this is that I save the object as user JIM (who
has all the authorities under the sun), but then restore it as QPGMR
(who does not usually have the authority even to smile!). Is there
anything I can do to the object to force it's restoratioin with the
same authorities as it was saved?
Jim Willsher
"There's two lanes running down this road, and whichever side you're on...
Accounts for where you want to go, or what you're running from..."
Jim Willsher <will...@sol.co.uk>
Eno Rebyc
> I have a program (CL) which must be compiled with OWNER(QSECOFR) and
> *OWNER authority. When I save this object using SAVOBJ I don't get any
> problems. However, when I restore the object on a remote AS/400,
> either the object won't restore, or I am told that 'security or format
> changes' etc etc.
>
> I suspect the key to this is that I save the object as user JIM (who
> has all the authorities under the sun), but then restore it as QPGMR
> (who does not usually have the authority even to smile!). Is there
> anything I can do to the object to force it's restoratioin with the
> same authorities as it was saved?
>
>>>>I have a program (CL) which must be compiled with OWNER(QSECOFR) and
>>>> *OWNER authority.
That sentence is the key to your problem. The object will restore; but
it'll now have a *PUBLIC authority of *EXCLUDE. You need to restore your
program on the target system with a user profile that has *ALLOBJ and
*SECADM authorities. QSECOFR would be the prime candidate here!
Good luck,
eR
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* The end crowns all; *
* And that old common arbitrator, *
* Time, will one day end it. *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-BS*-*-*-*
Mark Ford
On Sat, 09 Nov 1996 21:42:51 GMT, will...@sol.co.uk (willsher) wrote:
>I have a program (CL) which must be compiled with OWNER(QSECOFR) and
>*OWNER authority. When I save this object using SAVOBJ I don't get any
>problems. However, when I restore the object on a remote AS/400,
>either the object won't restore, or I am told that 'security or format
>changes' etc etc.
>
>I suspect the key to this is that I save the object as user JIM (who
>has all the authorities under the sun), but then restore it as QPGMR
>(who does not usually have the authority even to smile!). Is there
>anything I can do to the object to force it's restoratioin with the
>same authorities as it was saved?
>
>
>
>
>
>
>"There's two lanes running down this road, and whichever side you're on...
>Accounts for where you want to go, or what you're running from..."
>
>
>Jim Willsher <will...@sol.co.uk>
>
You need to use the ALWOBJDIF(*ALL) and MBROPT(*ALL) parameters on the
RSTOBJ command, and perform the restore from a profile with *ALLOBJ
and *SECADM rights (I believe). This will restore the object with
owner information intact, although any individual authorities granted
will be lost.
Mark.
Kevin Carroll
Eno Rebyc wrote:
>
> In article <562tt7$a...@biffo.sol.co.uk>, will...@sol.co.uk (willsher) wrote:
>
> > I have a program (CL) which must be compiled with OWNER(QSECOFR) and
> > *OWNER authority. When I save this object using SAVOBJ I don't get any
> > problems. However, when I restore the object on a remote AS/400,
> > either the object won't restore, or I am told that 'security or format
> > changes' etc etc.
> >
> > I suspect the key to this is that I save the object as user JIM (who
> > has all the authorities under the sun), but then restore it as QPGMR
> > (who does not usually have the authority even to smile!). Is there
> > anything I can do to the object to force it's restoratioin with the
> > same authorities as it was saved?
> >
>
> >>>>I have a program (CL) which must be compiled with OWNER(QSECOFR) and
> >>>> *OWNER authority.
>
> it'll now have a *PUBLIC authority of *EXCLUDE. You need to restore your
> program on the target system with a user profile that has *ALLOBJ and
> *SECADM authorities. QSECOFR would be the prime candidate here!
>
> Good luck,
> eR
>
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> * The end crowns all; *
> * And that old common arbitrator, *
> * Time, will one day end it. *
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-BS*-*-*-*
Yes! Otherwise any old hacker could swipe a program from system A and
reload it on System B! Now, at least he/she has to sign onto system B as
QSECOFR or equivalent to restore it! Not a bug! It's a feature!!!
Regards, Kevin
--
+-------------------------------------------------------------+
Kevin Carroll IT Advisor Web Page: http://www.kdc.co.nz
Email: ke...@kdc.co.nz Ph: +64-21-440 757 Fax: +64-21-660 758
K D Carroll Ltd (Information Technology Services) New Zealand