103 lines
6.5 KiB
HTML
103 lines
6.5 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Recovery details" />
|
||
|
|
<meta name="abstract" content="These are some details you should refer to concerning the console recovery action." />
|
||
|
|
<meta name="description" content="These are some details you should refer to concerning the console recovery action." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrconsoletakeoverandrecover.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrtakeoverdetails.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrfunctions6521.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="recoverydetails" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Recovery details</title>
|
||
|
|
</head>
|
||
|
|
<body id="recoverydetails"><a name="recoverydetails"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Recovery details</h1>
|
||
|
|
<div><p>These are some details you should refer to concerning the console
|
||
|
|
recovery action. </p>
|
||
|
|
<div class="section"><ul><li>The recovery of the console using a device with the same console connectivity
|
||
|
|
is directly tied to the take over option. If you do not want take over capability
|
||
|
|
but do want recovery from loss of the console, you must still enable the take
|
||
|
|
over option.</li>
|
||
|
|
<li>Console recovery utilizes the take over function. Recovery can be from
|
||
|
|
the same device or another device of the same connectivity. For example,
|
||
|
|
if you are using Operations Console LAN and have multiple PCs set up to be
|
||
|
|
the console and the existing console fails you can use the take over function
|
||
|
|
from the same PC, after correcting the reason for the failure, or from another
|
||
|
|
PC. Regardless of what the former console was doing, the new console will
|
||
|
|
be in the same job, at the same step, as the original console would have been.
|
||
|
|
The job continues even though the console was not operational. Using a directly
|
||
|
|
attached console to recover a loss of a LAN-connected console doesn't fit
|
||
|
|
this scenario</li>
|
||
|
|
<li>The recoverability of the console using a different console connectivity
|
||
|
|
provides additional options for the user. If you have a backup console plan
|
||
|
|
that involves the need for a change in the console mode, consider the following: <ul><li>It is recommended that for ease of adapting recovery that you place all
|
||
|
|
console supporting adapters for use by the same IOP. This reduces the number
|
||
|
|
of steps necessary to accomplish a recovery. </li>
|
||
|
|
<li>The console mode change can be immediate depending on the method used
|
||
|
|
to make the change. Examples would be: <ul><li>Using DST or SST to change the console mode would allow the console to
|
||
|
|
change only at the next IPL. Following this action with a force DST (function
|
||
|
|
21) using the control panel or LPAR menu may not always work either.</li>
|
||
|
|
<li>Changing tags in the LPAR environment will also require an IPL to cause
|
||
|
|
a change of the console.</li>
|
||
|
|
<li>However, using the console service functions (65+21), forces the system
|
||
|
|
to do this search and activates the appropriate hardware and tasks and is
|
||
|
|
immediate.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Supporting hardware for each console type you want to use for recovery
|
||
|
|
must be available at the time of recovery. For example, if you want a local
|
||
|
|
console directly attached to be able to recover a local console on a network,
|
||
|
|
both adapter cards must be located in their respective locations or be properly
|
||
|
|
tagged for logical partitions. For this to be completed the user would also
|
||
|
|
have to change the console mode, either using an available menu or using the
|
||
|
|
console service functions (65+21). <p>In order to accomplish a recovery using
|
||
|
|
a different console mode you must set the new console mode <strong>before</strong> attempting
|
||
|
|
the take over. This means that either the supporting hardware must already
|
||
|
|
be available, including any logical partition tagging, or you have to move
|
||
|
|
supporting hardware, physically or logically, before attempting the recovery.
|
||
|
|
Then, you will have to use one of the methods to change the console mode
|
||
|
|
to the desired setting. You can use an existing workstation and SST, if available,
|
||
|
|
the native macro, or the console service functions (65+21).</p>
|
||
|
|
<p>For additional
|
||
|
|
information on console service functions, see the section: <a href="rzajrfunctions6521.htm">Using the console service functions (65+21)</a>.</p>
|
||
|
|
</li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />In V5R4, a D-mode IPL the take over function, one console device
|
||
|
|
taking over for another, is now supported. <p>If you change the console mode
|
||
|
|
value during a D-mode IPL, for example using 65+21, you should be able to
|
||
|
|
connect another device as long as the new console mode has supporting hardware
|
||
|
|
and a device.</p>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajrconsoletakeoverandrecover.htm" title="Use these functions to take control of another console device.">Take over or recover an Operations Console connection</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzajrtakeoverdetails.htm" title="These are some facts you should remember concerning the console take over function.">Take over details</a></div>
|
||
|
|
<div><a href="rzajrfunctions6521.htm" title="The emergency console recovery functions and their uses">Using the console service functions (65+21)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|