ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzajr_5.4.0.1/rzajrscenariotakeover3.htm

77 lines
5.0 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="Scenario: Recovery of a console requiring a new console mode setting" />
<meta name="abstract" content="There may be cases in which you may have to change the console mode in order to recover from a console error. An example of this might be the loss of your network during normal operations." />
<meta name="description" content="There may be cases in which you may have to change the console mode in order to recover from a console error. An example of this might be the loss of your network during normal operations." />
<meta name="DC.Relation" scheme="URI" content="rzajrconsolescenarios.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="scenariotakeover3" />
<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>Scenario: Recovery of a console requiring a new console mode setting</title>
</head>
<body id="scenariotakeover3"><a name="scenariotakeover3"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Scenario: Recovery of a console requiring a new console mode setting</h1>
<div><p>There may be cases in which you may have to change the console
mode in order to recover from a console error. An example of this might be
the loss of your network during normal operations.</p>
<div class="section"><p>The console mode could be changed using one of several methods,
which include:</p>
<ul><li>DST or SST menus (delayed)</li>
<li>Native macros (delayed)</li>
<li>Console Service Functions (65+21) (Immediate)</li>
</ul>
</div>
<div class="section"><p>Only the console service functions (65+21) method will automatically
take down the old connection and activate all the resources for the new choice.
The other two methods may require manual steps to activate the appropriate
resources for the new console. These changes also require that the associated
resources be available in a state where they can be used. For example, you
are using Operations Console LAN and the network fails, the console was in
use by your logical partition and you do not have an asynchronous communications
card on the IOP tagged for the console. You would have to either move a card
or change the IOP tagging to allow a directly attached console to work. If
the change is not required immediately, you could also wait for the change
to take affect during the next IPL in which case a newly tagged IOP would
allow the directly attached console to connect. In this example, however,
we are attempting to change the console's connectivity and use another device
right now. The recommended method for immediate change is the console service
functions (65+21) method. Once that has been successfully performed, the
user must sign on again. Since this scenario is from LAN to directly attached
console the new console would not get the special signon screen or the Console
Information Status screen since it is the only valid console after the console
mode change. When the network problem is fixed, the LAN connected devices
would go directly to the Console Information Status screen and would not be
able to take control as the console without changing the console mode back
to LAN. Take over is not available when a device is directly connected as
the console since only one connection of this type is allowed by the server.</p>
</div>
<div class="section"><p>Another consideration for choosing the method to change the console
mode will be the availability of another workstation. If you are installing
using the console then the only method available to you is the console service
functions (65+21).</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajrconsolescenarios.htm" title="The following scenarios will help you understand the take over and recovery options.">Scenarios</a></div>
</div>
</div>
</body>
</html>