MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » August 2014

RE: Another heads up on a restore



fixed

Trevor,

I agree that your suggestion is best practice, but that does not in my view
absolve IBM of having the restore operate in a predictable manner, in this
case a complete recovery of a system. It almost sounds like they can't
find an easy fix so IBM is just bailing on the problem.

Rob: I would not only enter a change request with IBM but also put it on
the COMMON request list as well. That way (in theory anyway) the CAAC will
have an opportunity to evaluate it.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Briggs, Trevor (TBriggs2)
Sent: Tuesday, August 12, 2014 9:22 AM
To: Midrange Systems Technical Discussion
Subject: RE: Another heads up on a restore

Surely this is a simple matter of putting all your changes to
system-supplied objects (which this can be classed as) into a CL program.
This is the same CL program you would run after doing an OS upgrade.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Tuesday, August 12, 2014 8:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: Another heads up on a restore

I just submitted a DCR that this is BS.
Suggested an exit on SAVSYS, and on RSTAUT, that IBM do this themselves.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/12/2014 08:08 AM
Subject: Re: Another heads up on a restore
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



IBM owns up to this issue. They just say it's the customer's problem to

solve.
http://www-01.ibm.com/support/docview.wss?uid=nas8N1017745


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: rob@xxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Date: 08/11/2014 03:03 PM
Subject: Another heads up on a restore
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



If you secure certain commands with authorization lists they are going
to
be a little messed up on a restore.

Old system:
Object . . . . . . . : STRDBGSVR
Library . . . . . : QSYS
Object type . . . . : *CMD
Object secured by authorization list . . . . . . . . . . . . :
SYSTEMS
Object
User Group Authority
*PUBLIC *AUTL
...

After restore
Object . . . . . . . : STRDBGSVR
Library . . . . . : QSYS
Object type . . . . : *CMD
Object secured by authorization list . . . . . . . . . . . . : *NONE
Object
User Group Authority
*PUBLIC *AUTL
...


How *PUBLIC can have the authority of *AUTL when there is no longer an
authorization list associated to it is a little baffling.

7.1

On old system do WRKAUTL SYSTEMS, take option 8 to see objects in it.
Page


down to QSYS. I think only QSYS was affected.


Rob Berendt





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact