|
According to the Backup and Recovery Guide, appendix D you 4) Install LIC 14) Install the operating system 29) Use GO RESTORE, option 21 Which I did. In the RSTCFG part of the GO RESTORE option 21 it restored the device descriptions and automatically created the output queues, (wrong) in the library QUSRSYS. While it hasn't yet ran the RSTLIB portion, it must have created a base QUSRSYS with step 14 was ran. And yes, the RSTAUT ran as part of step 29. And although I see the CPF3776 message when the RSTAUT was done, the flags thrown up are not for any output queues. Weird files in QTEMP and the like.
What would the slip install do different?
Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
Evan Harris <spanner@xxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 09/23/2004 03:22 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc
Fax to
Subject Re: Unload/Reload screwed up security.
Hi Rob
If it was only LIC then according to my recollection QUSRYSYS shouldn't exist as it is installed as part of the OS install. Are you sure you installed just the LIC ?
Have you tried running RSTAUT ? Have you checed RSTAUT ran ?
Sounds like the slip install instructions are what you ought to refer to for next time.
Regards Evan Harris
>We did an unload/reload following appendix D of the Backup and Recovery >Guide. We did one modification we thought to "save" time. Prior to the >downtime we preinstalled lic on the new system using the IBM CD's. Just >lic - not OS or anything else. This allowed us to initialize the disk >drives - a long running task on a 3.3TB machine. We stopped at the start >of step 14. In the past we used to use the SAVSYS to do the LIC install >but we upgraded to V5R3 after our last SAVSYS. > >We are wondering if this "time saving" step caused us numerous problems. >This is not our first unload/reload. However this is the first time we >remember numerous painful events regarding security not being restored. >Here's one scenario: >Used GO RESTORE - 21. Definitely told it to restore to a different >system, which, among other things appends ALWOBJDIF(*ALL) to all commands. >RSTCFG runs. Restores devices, automatically creates matching output >queues in QUSRSYS. >RSTLIB of QUSRSYS runs. Get numerous errors like >CPF370B Information 10 09/18/04 09:07:12.299504 QSRRSLIB > QSYS 1015 QSRRLCP2 QSYS 0091
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.