Re: RISC Disaster Recovery Disaster

Mike, 

You went off course during the 'Set Major System Options'.  Instead of
'Enable automatic configuration = 'Y', you should of had auto config to 'N'
and QIPLTYPE, (Console in debug mode) set to 2.

This way you would have received a working console and you could of continued.

The Backup and Recovery Guide documents this.

I'm not sure which chapter and verse, because the are various different
scenarios documented, such as 
        Was load source unit that failed.
        Are User ASPs present
        etc.

I believe that it is Checklist 17 in the Recovery section, but check this
as it may vary per Version/Release that you are running.




At 04:20 PM 5/15/98 PDT, you wrote:
>Hi All,
>
>Am getting ready to do a disaster recovery test up at our hot site in
Seattle, WA in July.  This will be the first test of a RISC AS/400 disaster
recovery for us.
>
>To get ready and to see how our recovery instructions needed to change, I
did a scratch install of V3R7 on a Model 40S.  The good news is that you no
longer have a backache from bending over trying to read the SRC codes to
see where it is in the process.  Almost all of the dialouge is now sent to
the system console.  That's nice!
>
>The real problems began at the point of setting the IPL Options during the
O/S load.  The Set Major Systems Options asks if you want to Enable
automatic configuration which needs to be a 'Y' option.  This creates a
DEVD for the system console and tape devices.  If you say no, the system
hangs with an SRC of A9002000 and a blank console screen....Some choice.
>
>By saying yes to enable automatic configuration, I am moving on to the
RESTORE menu to take option 21.  For a tape device in the Specify Command
Defaults screen I enter TAP01 and tell it to prompt for commands.  This is
where it goes to hell in a hand basket.....When restoring the user profiles
I get an error "TAP01 Not Available" and the restore fails.
>
>I get back to a command line and do WRKCFGSTS *CTL TAP*.  Auto config has
created DEVD's for all 16 of the 3480 tape drives and the resource names
and device names are not the same!!!!!!!!!!!!!!  We on the AS/400 side only
have 5 of these devices - what has happily been known as TAP01 through
TAP05 for many years (or at least until auto config was turned on!).  The
mainframe has the remainder of the 3480 drives assigned to it.
>
>Through the process of elimination I was able to determine that the device
TAP01 had a  DEVD created by auto config called TAP06 assigned to the
resource TAP01.  I still have to sort through the remaining 4 drives and
figure out which is which....That's not nice!
>
>Now for the $64,000,000.00:  Is this by design???????????  If it is, you
will never be able to have device naming integrity and have to manipulate
them every time they are created - to include a disaster recovery scenerio.
 <BTW>A disaster recovery site with an auditor breathing down your neck
ain't the place to find out you no longer know the device name of your
alternate IPL tape drive !!!
>
>I hope someone at IBM will take a serious look at this and offer an
explanation if not a solution to making sure the resource name TAP01 gets
assigned to an auto config created DEVD name TAP01.
>
>My next question is:  Have I missed something here????  Has anyone else
seen this and found a way around this on a RISC box???  Any comments and
ideas would be greatly appreciated.
>
>Mike Shaw
>North American Mortgage Company
>Santa Rosa, CA
>
>
>
>
>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator: david@midrange.com
>+---
>
>
Neil Clark
Barsa Consulting Group, LLC.
Tel. (914) 251 9400
Fax. (914) 251 9406


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---