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

85 lines
5.8 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 a console is currently available" />
<meta name="abstract" content="If you know in advance that you will need a different console type you can use the current console to make the changes necessary for use with a different console." />
<meta name="description" content="If you know in advance that you will need a different console type you can use the current console to make the changes necessary for use with a different console." />
<meta name="DC.Relation" scheme="URI" content="rzajrmanageshared.htm" />
<meta name="DC.Relation" scheme="URI" content="rzajrchangeconsoletype.htm" />
<meta name="DC.Relation" scheme="URI" content="rzajractivating.htm" />
<meta name="DC.Relation" scheme="URI" content="rzajrdeactivating.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="switchconsoleavailable" />
<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 a console is currently
available</title>
</head>
<body id="switchconsoleavailable"><a name="switchconsoleavailable"><!-- --></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 a console is currently
available</h1>
<div><p>If you know in advance that you will need a different console type
you can use the current console to make the changes necessary for use with
a different console.</p>
<div class="section"><p>If the hardware resources for the targeted console type have already
been specified and configured for use as a console, making the change may
be as simple as specifying the new console mode and activating the associated
hardware resource. However, if hardware used for the targeted console type
will require allocation or configuration, you will need to use the appropriate
information in <span class="uicontrol">Change from one console type to another</span>. </p>
</div>
<div class="section"><div class="p">An example would be the planned loss of the network used by your
LAN-connected console. You will be doing some infrastructure changes requiring
more than a day. You also have the console cable already installed between
the server's asynchronous communications adapter and the PC. You can use
either DST or SST to change the console mode to a 2 for Operations Console
direct. The asynchronous communications adapter will not be active at this
time since the console mode is set for LAN so you would have to manually start
the asynchronous card with a function 66 on the control panel or remote control
panel. Once
the communications line is active you can disconnect the LAN-connected console
and create a configuration for the direct attached local console, if a configuration
doesn't already exist, and start a connection. To switch back to the LAN-connected
console you would only have to use the direct-attached console to enter either
DST or SST and change the console mode to a 3, disconnect the existing console
and restart the LAN-connected console. Since the hardware resource configuration
didn't change there isn't a need for further changes. You could deactivate
the asynchronous communications adapter manually
or just wait until the next IPL. The IPL will not start the asynchronous
communications adapter because the console mode is now set for LAN.<div class="note"><span class="notetitle">Note:</span> To
activate the new console without an IPL you could perform the console service
function of 65+21+21. Once the console mode has been updated performing the
console service function will disconnect the current console and restart the
console type you just specified. See link to console service function documents.</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="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzajractivating.htm" title="How to manually activate the asynchronous communications line for use with Operations Console.">Activate the asynchronous communications line on the server</a></div>
<div><a href="rzajrdeactivating.htm" title="Deactivate the asynchronous communications line on the server">Deactivate the asynchronous communications line on the server</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzajrchangeconsoletype.htm" title="If you already have a console connection, you can change to different types of consoles in the following ways.">Change from one console type to another</a></div>
</div>
</div>
</body>
</html>