134 lines
8.6 KiB
HTML
134 lines
8.6 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="task" />
|
||
|
|
<meta name="DC.Title" content="Scenario: Preparing to upgrade or replace software using an image catalog" />
|
||
|
|
<meta name="abstract" content="The following is a scenario of how you create an image catalog and an image catalog entry, add an image catalog entry, and load the image catalog in preparation of performing a software upgrade." />
|
||
|
|
<meta name="description" content="The following is a scenario of how you create an image catalog and an image catalog entry, add an image catalog entry, and load the image catalog in preparation of performing a software upgrade." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="prepareimagecatalog.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="scenarioprepareimagecatalog" />
|
||
|
|
<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: Preparing to upgrade or replace software using an image catalog</title>
|
||
|
|
</head>
|
||
|
|
<body id="scenarioprepareimagecatalog"><a name="scenarioprepareimagecatalog"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario: Preparing to upgrade or replace software using an image catalog</h1>
|
||
|
|
<div><p>The following is a scenario of how you create an image catalog
|
||
|
|
and an image catalog entry, add an image catalog entry, and load the image
|
||
|
|
catalog in preparation of performing a software upgrade. </p>
|
||
|
|
<div class="p"><div class="p"><em>To perform a V5R2-to-V5R4 software upgrade</em> from
|
||
|
|
an image catalog, load and apply V5R2 PTF SI19886. <em>To perform a V5R3-to-V5R4
|
||
|
|
software upgrade</em> from an image catalog, load and apply V5R3 PTF SI19888.
|
||
|
|
After either of these PTFs have been applied, follow these steps. <div class="note"><span class="notetitle">Note:</span> For
|
||
|
|
a V5R4 replacement, ensure that the IBM-supplied media B29xx_01 and B29xx_02
|
||
|
|
have matching identifiers. The identifier on the CD-ROM label begins with
|
||
|
|
the letters <em>RS</em> and is followed by a series of numbers.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand" id="scenarioprepareimagecatalog__createvirtualoptical"><a name="scenarioprepareimagecatalog__createvirtualoptical"><!-- --></a><span><strong>Create a virtual optical device.</strong> </span> <p>To create a device description, enter the following: </p>
|
||
|
|
<pre>CRTDEVOPT DEVD(<em>virtual-device-name</em>) RSRCNAME(*VRT)+
|
||
|
|
ONLINE(*YES) TEXT(<em>text-description</em>)</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span><strong>Vary on the virtual optical device</strong></span> <div class="p">Enter the
|
||
|
|
following: <pre>VRYCFG CFGOBJ(<em>virtual-device-name</em>) CFGTYPE(*DEV) STATUS(*ON)</pre>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span><strong>Create an image catalog</strong></span> <p>Create an image catalog
|
||
|
|
for the licensed programs that you want to install. The Create Image Catalog
|
||
|
|
(CRTIMGCLG) command associates an image catalog with a target directory where
|
||
|
|
the optical image files are loaded. </p>
|
||
|
|
<pre>CRTIMGCLG IMGCLG(<em>catalog-name</em>) DIR(<em>catalog-path</em>)
|
||
|
|
CRTDIR(*YES) TEXT(<em>text-description</em>)</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span><strong>Add an image catalog entry</strong></span> <p>Add an image catalog
|
||
|
|
entry for each physical media or optical image file that you have. You need
|
||
|
|
to repeat this step for each volume of media. You should add the physical
|
||
|
|
media or optical image files in the same order as if you were going to install
|
||
|
|
from them. Start with the first media in the list and continue until all the
|
||
|
|
media are loaded. </p>
|
||
|
|
<p>You can add the entries from either an optical device
|
||
|
|
or from an existing optical image file. Select one of the following ways:</p>
|
||
|
|
<p>From
|
||
|
|
an image file:</p>
|
||
|
|
<ul><li>(This is the fastest way.) To add an image entry to an image catalog from
|
||
|
|
an integrated-file-system file that is already in the image catalog directory,
|
||
|
|
enter the following: <pre>ADDIMGCLGE IMGCLG(<em>catalog-name</em>) FROMFILE(<em>file-name</em>)
|
||
|
|
TOFILE(<em>*fromfile</em>) TEXT(<em>text-description</em>)</pre>
|
||
|
|
</li>
|
||
|
|
<li>To add an image catalog entry to an image catalog from an existing integrated-file-system
|
||
|
|
optical image file from a directory other than the image catalog directory,
|
||
|
|
enter the following: <pre>ADDIMGCLGE IMGCLG(<em>catalog-name</em>)
|
||
|
|
FROMFILE(<em>/directory-name/directory-name/file-name</em>)
|
||
|
|
TOFILE(<em>file-name</em> or *FROMFILE) TEXT(<em>text-description</em>)</pre>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>From a physical device:</p>
|
||
|
|
<ul><li>To add an image catalog entry to an image catalog from a physical optical
|
||
|
|
media using optical device named OPT01, enter the following: <pre>ADDIMGCLGE IMGCLG(<em>catalog-name</em>) FROMDEV(OPT01)
|
||
|
|
TOFILE(<em>file-name</em> or *GEN) TEXT(<em>text-description</em>)</pre>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> To generate a name for the TOFILE parameter, specify <tt>*GEN</tt>.
|
||
|
|
To generate a text description from the media, specify <tt>*GEN</tt>.</div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand" id="scenarioprepareimagecatalog__loadimagecatalog"><a name="scenarioprepareimagecatalog__loadimagecatalog"><!-- --></a><span><strong>Load the image catalog</strong></span> <p>This
|
||
|
|
step associates the virtual optical device to the image catalog. Only one
|
||
|
|
image catalog at a time can be associated with a specific virtual optical
|
||
|
|
device. To load the image catalog, type the following command: </p>
|
||
|
|
<div class="p"> <pre>LODIMGCLG IMGCLG(<em>catalog-name</em>)
|
||
|
|
DEV(<em>virtual-device-name</em>) OPTION(*LOAD)</pre>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand" id="scenarioprepareimagecatalog__verifyimagescorrect"><a name="scenarioprepareimagecatalog__verifyimagescorrect"><!-- --></a><span><strong>Verify that the images are in the correct
|
||
|
|
order</strong> </span> <div class="attention"><span class="attentiontitle">Attention:</span> If you are here because you
|
||
|
|
are performing the steps in <a href="rzahcpreselect.htm#rzahcpreselect">Preselecting the licensed programs to install</a>,
|
||
|
|
do not perform this step at this time. You are directed to perform this step
|
||
|
|
later.</div>
|
||
|
|
<p>If you are preparing for an upgrade, you need to verify that
|
||
|
|
the required media for an upgrade exist and are sorted in the correct sequence.
|
||
|
|
You also need to verify that your software agreements have been accepted,
|
||
|
|
that you have enough storage on the load source, and that you have enough
|
||
|
|
reserved storage for the Licensed Internal Code.</p>
|
||
|
|
<p>Enter the following
|
||
|
|
command:</p>
|
||
|
|
<pre>VFYIMGCLG IMGCLG(<em>catalog-name</em>) TYPE(*UPGRADE) SORT(*YES)</pre>
|
||
|
|
<p>To
|
||
|
|
verify that images are added, an additional method would be to enter the following:</p>
|
||
|
|
<pre>WRKIMGCLGE IMGCLG(<em>catalog-name</em>)</pre>
|
||
|
|
<p>Then press PF7 to prompt for the VFYIMGCLG command. Enter <tt>*UPGRADE</tt> for
|
||
|
|
the type and <tt>*YES</tt> for the sort field.</p>
|
||
|
|
<p>The server puts the images
|
||
|
|
in the correct order. <span>(If you are not successful, </span>refer
|
||
|
|
to <a href="imagecatalogrecovery.htm#imagecatalogrecovery">Image catalog recovery</a>.) By
|
||
|
|
default, the volume with the lowest index is mounted. Then all the other volumes
|
||
|
|
are loaded. To see the order of the images, use the Work with Image Catalog
|
||
|
|
Entries (WRKIMGCLGE) command: </p>
|
||
|
|
<pre>WRKIMGCLGE IMGCLG(<em>catalog-name</em>)</pre>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"> <p>After completing these steps, your image catalog is ready for
|
||
|
|
use.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="prepareimagecatalog.htm" title="You can use an image catalog to perform a software upgrade, to install PTFs (fixes), or to install single licensed programs that you receive on media.">Preparing to upgrade or replace software using an image catalog</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|