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

78 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="Switching from one console type to another when the current console is not operational" />
<meta name="abstract" content="If you develop a problem with the current console, you may be able to use one of the following methods to change the console mode." />
<meta name="description" content="If you develop a problem with the current console, you may be able to use one of the following methods to change the console mode." />
<meta name="DC.Relation" scheme="URI" content="rzajrmanageshared.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="switchconsolenotoperational" />
<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>Switching from one console type to another when the current console
is not operational</title>
</head>
<body id="switchconsolenotoperational"><a name="switchconsolenotoperational"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Switching from one console type to another when the current console
is not operational</h1>
<div><p>If you develop a problem with the current console, you may be able
to use one of the following methods to change the console mode.</p>
<div class="section"><ul><li>If you are using a LAN-connected PC for the console and have another PC
set up to be the console, you might be able to use the other PC for the console
until the problem with the first console is fixed.</li>
<li>Use SST from another workstation.</li>
<li>Use the console service functions (65+21).</li>
<li>Use the appropriate native macro from another workstation. <div class="note"><span class="notetitle">Note:</span> Any hardware
allocations or configurations will have to be accomplished before connecting
with another connectivity. For example, if you are using a shared IOP in an
LPAR environment you can deallocate and allocate the resource from one partition
to another, if your hardware supports this method. If you planned for a backup
console some or all of this work may already be done. If you do not have
a backup console in place, some tasks may require one or more IPLs to get
the system into a state where you can use the new console.</div>
</li>
</ul>
</div>
<div class="section"><div class="p">Using the same configuration example above (LAN to direct) and
assuming all hardware and configurations have been done, you would disconnect
the existing console (LAN-connected); use the console service functions (65+21),
native macro, or SST from another workstation to set the console mode to a
2 for directly attached consoles, then connect the local console directly
attached. However, if you used the native macro or SST from another workstation,
you may also have to activate the asynchronous communications adapter. Using
the console service functions (65+21) or native macro OPSCONSOLE RESTART automatically
activates the adapter.<div class="note"><span class="notetitle">Note:</span> There are several console service functions (65+21)
that might be needed to recover or debug an Operations Console problem depending
on the problem, connectivity used for the current console, the target console
type, and the current state of the system.
If you are unsure of any function or recovery action contact your service
provider for assistance.</div>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajrmanageshared.htm" title="Manage multiple devices that can become consoles">Manage your multiple consoles</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<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>