|
These values should all be “1”. You may have to change “Allow a service
tool user ID…”.
Did you notice the quite detailed instructions on how to boot from a DVD
yet do 100% of your install from tape?
Much of this is from the recovery manual. However instead of skipping all
around the darn thing I laid the steps out sequentially in an effort to
ease others.
Keep in mind that I did 15 unload/reloads of IBM i 7.1 from Power 6 to
Power 8 systems following instructions with this snippet as part of them.
And I had coworkers follow them and do them on their own with me out of
the building also.
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: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/09/2018 11:21 AM
Subject: Re: QS36F file format error after migrating LPAR
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
On Mon, Apr 9, 2018 at 8:59 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
device?
Refresh my memory, did we already talk you through going into SST and
seeing if your tape device is flagged as an alternate installation
And can it also be used as an alternate IPL device?
Thanks for talking, Rob. I think I d'oh suddenly figured it out. The tape
works, it just won't boot. It's a type 21 GO SAVE.
But the source machine is a P7 and the target is P8. There's no way that's
going to work, methinks.
Arrgh. Now I have to figure out how to migrate and fix this system. No
BRMS
restore-the-system report, since it's not done with BRMS.
Is there a magic incantation to reconnect the QS36F files with their data
definitions? My head hurtz ...
--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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.