ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahc_5.4.0.1/rzahcswinstallprocess.htm

130 lines
8.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="concept" />
<meta name="DC.Title" content="Software installation process" />
<meta name="abstract" content="The software installation process has three phases: preinstallation activities, the main installation, and postinstallation activities." />
<meta name="description" content="The software installation process has three phases: preinstallation activities, the main installation, and postinstallation activities." />
<meta name="DC.Relation" scheme="URI" content="rzahcswconcepts1.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzahcswinstallprocess" />
<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>Software installation process</title>
</head>
<body id="rzahcswinstallprocess"><a name="rzahcswinstallprocess"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Software installation process</h1>
<div><p>The software installation process has three phases: preinstallation
activities, the main installation, and postinstallation activities. </p>
<p></p>
<ol><li><strong>Preinstallation activities:</strong> <p>You can do these activities
days or even a few weeks in advance. To plan and prepare your server before
you install your software, use the appropriate planning and preparation topics
to guide you through the activities that you need to do.</p>
<ul><li>Upgrading to V5R4 from either V5R2 or V5R3: <a href="rzahcchecklist.htm#rzahcchecklist">Checklist: Software upgrade or replacement readiness</a></li>
<li>Replacing Licensed Internal Code and i5/OS™ of the same version and release to
support new hardware: <a href="rzahcchecklistprepreplace.htm#rzahcchecklistprepreplace">Checklist: Software replacement</a></li>
<li>Installing V5R4 on a new server or logical partition: <a href="rzahcinstallchecklist.htm#rzahcinstallchecklist">Checklist: Software installation readiness</a></li>
</ul>
<p>These activities include verifying your order, checking the amount
of available disk space, backing up your server, and cleaning your media device.
In a software upgrade or replacement, some of the tasks are required. If you
do not perform these required tasks, you will be forced to restart the installation.</p>
</li>
<li><strong>The installation process:</strong> <p> The installation process begins
when you start performing the instructions in one of the procedural topics.
For example, to upgrade to the new release, you might have chosen automatic
installation. The automatic installation process installs the Licensed Internal
Code, the operating system (<span class="keyword">i5/OS</span>),
and licensed programs. You would have minimal interaction with the system,
except to load the optical distribution media and to monitor the system.</p>
<p>Your
only installation activity might be changing the primary language or installing
additional licensed programs. Or, perhaps you want to perform these activities
after an automatic or manual installation.</p>
</li>
<li><strong>Postinstallation activities:</strong> <p>The last step of each procedure
directs you to use a completion checklist. You might be directed to additional
steps, such as saving your system and performing installation activities on
workstations for IBM<sup>®</sup> eServer™ <span class="keyword">iSeries™ Access Family</span> products.
Other activities could include customizing your system, or setting usage limits
for user-based priced products. Before you begin production work on your system,
be sure to adequately protect your system from unauthorized use.</p>
<p>The
following figure shows an example of one type of software installation. (Your
particular installation might not include all of the topics that are shown
in this figure.) </p>
<div class="fignone" id="rzahcswinstallprocess__flowcht"><a name="rzahcswinstallprocess__flowcht"><!-- --></a><span class="figcap">Figure 1. Overview of the installation
process</span><br /><img src="rzahc501.gif" alt="Overview of Installation&#xA;Process" /><br /></div>
</li>
</ol>
<p>The procedure that you use for software installation depends on what you
plan to install. </p>
<dl class="dlexpand"><dt class="dltermexpand">Install software on a new server</dt>
<dd>If you just received a new server, the operating system and other licensed
programs might or might not be installed already.</dd>
<dt class="dltermexpand">Upgrade or replace existing software</dt>
<dd>If you are upgrading or replacing your existing <span class="keyword">OS/400<sup>®</sup></span> or <span class="keyword">i5/OS</span> software, use either the automatic
installation method or the manual installation method. <dl class="dlexpand"><dt class="dltermexpand">Automatic installation</dt>
<dd>This replaces your existing release with minimal user interaction. The
language feature code on the distribution media is installed as the primary
language on the server. The automatic installation process keeps the current
environment and system values. The process can add all nonconfigured disk
units to the system auxiliary storage pool (ASP) and retain the ASP configuration
of previously configured disk units. The automatic installation process is
recommended for use with most servers. </dd>
<dt class="dltermexpand">Manual installation</dt>
<dd>This interactively replaces your existing release by using the Work with
Licensed Programs menu. Displays that require responses appear on the console.
During a manual installation, you can change installation options. Use the
manual installation process if you are doing any of the following installation
procedures:<ul><li>Adding a disk device using mirrored protection, device parity protection,
or user auxiliary storage pools.</li>
<li>Changing the environment (<span class="keyword">i5/OS</span> or System/36™),
system values, language feature code, or configuration values.</li>
<li>Planning to use an alternate installation device when you upgrade.</li>
<li>Creating logical partitions during the installation process.</li>
<li>Using tapes created with the Save System (SAVSYS) command. (The SAVSYS
command creates tapes that are meant for recovery.)</li>
</ul>
</dd>
</dl>
</dd>
<dt class="dltermexpand">Add licensed programs</dt>
<dd>When you add additional licensed programs (in addition to those done already
in the methods mentioned above) or optional parts of licensed programs, you
use the method done through option 11 (Install licensed programs) of the Work
with Licensed Programs (LICPGM) menu. Typically you use option 11 when you
need to install a new licensed program or to replace a single licensed program.</dd>
<dt class="dltermexpand">Add or change globalization support</dt>
<dd>When you add a secondary language, you add additional language objects
for the licensed programs that are installed on your system. <p>When you
change the primary language, you replace the existing language objects. Depending
on the procedure that you use, you can also replace program objects. </p>
</dd>
</dl>
<p>If a failure occurs during the installation process, <a href="rzahctroubleshoot.htm#rzahctroubleshoot">Troubleshooting software installation problems</a> contains
information that can help you determine the problem and the necessary recovery
steps.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahcswconcepts1.htm" title="You and IBM together manage the use, documentation, and transfer of i5/OS licensed programs.">Concepts for software installation</a></div>
</div>
</div>
</body>
</html>