99 lines
6.3 KiB
HTML
99 lines
6.3 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="Advanced fix installation: Load fixes" />
|
||
|
|
<meta name="abstract" content="Find out how to load one, some, or all of your fixes with the Load Program Temporary Fix (LODPTF) command." />
|
||
|
|
<meta name="description" content="Find out how to load one, some, or all of your fixes with the Load Program Temporary Fix (LODPTF) command." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzam8fixinstalladv1.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzam8fixinstallload" />
|
||
|
|
<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>Advanced fix installation: Load fixes</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzam8fixinstallload"><a name="rzam8fixinstallload"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Advanced fix installation: Load fixes</h1>
|
||
|
|
<div><p>Find out how to load one, some, or all of your fixes with the Load
|
||
|
|
Program Temporary Fix (LODPTF) command.</p>
|
||
|
|
<div class="section"><p>Typically, you should use option 8 from the GO PTF menu to install
|
||
|
|
your fixes. However, you can encounter some situations where you need to perform
|
||
|
|
the separate steps of loading and then applying the fixes.</p>
|
||
|
|
<p>The fix packages
|
||
|
|
on CD-ROM or in a save file can contain many fixes. You can load one, some,
|
||
|
|
or all of them using the Load Program Temporary Fix (LODPTF) command. As fixes
|
||
|
|
are loaded, the system verifies that the release of the product is correct.
|
||
|
|
Fix status is <span class="uicontrol">not</span> applied after the fix has been loaded
|
||
|
|
on the system. Use the Apply Program Temporary Fix (APYPTF) command to apply
|
||
|
|
the fix. For some of the applied fixes, the status is Temporarily applied
|
||
|
|
- ACN. There are also some temporarily applied fixes that show a status of
|
||
|
|
Temporarily applied - PND. For these fixes, you need additional actions to
|
||
|
|
make them active.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam8fixinstalladv1.htm" title="This topic introduces the advanced topics of loading and applying PTFs. You will also learn how to create your own fix package from CD-ROM and how to create a fix package to a virtual image.">Advanced procedures for fix installation</a></div>
|
||
|
|
</div>
|
||
|
|
</div><div class="nested1" xml:lang="en-us" id="cumptfpackage"><a name="cumptfpackage"><!-- --></a><h2 class="topictitle2">Loading individual fixes from a cumulative PTF package</h2>
|
||
|
|
<div><div class="section">To load one fix from a cumulative package, do the following steps:</div>
|
||
|
|
<ol><li><span>Type LODPTF and press F4 (Prompt).</span></li>
|
||
|
|
<li><span>Specify the parameter values according to the fix you are loading.</span></li>
|
||
|
|
<li><span>Specify the fix identifier you want to load in the fix numbers
|
||
|
|
to select (SELECT) parameter and press Enter.</span></li>
|
||
|
|
<li><span>Repeat LODPTF command for each fix you want loaded from the cumulative
|
||
|
|
package.</span></li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><p>For fixes on a CD-ROM, the system will automatically find the fix
|
||
|
|
file in the cumulative package that contains the selected individual fixes
|
||
|
|
when you specify PATHID(*FIRST). All fixes to be loaded must exist in the
|
||
|
|
same path identifier. Otherwise, you need to load the fixes separately.</p>
|
||
|
|
<p>For
|
||
|
|
fixes on an image catalog, only the images that are part of the volume set
|
||
|
|
for the image that is mounted are searched.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="loadgfixesupersedefixes"><a name="loadgfixesupersedefixes"><!-- --></a><h2 class="topictitle2">Loading fixes that supersede other fixes</h2>
|
||
|
|
<div><div class="section"><p>If the fix being loaded replaces (supersedes) existing fixes (identified
|
||
|
|
in the fix cover letter) the following considerations apply:</p>
|
||
|
|
<ul><li>If the fix to be replaced is not applied to the system, the new fix can
|
||
|
|
be loaded successfully. A record is kept indicating that the replaced fix
|
||
|
|
has been superseded.</li>
|
||
|
|
<li>If the fix to be replaced is permanently applied, it is considered to
|
||
|
|
be a part of the operating system or licensed program to which it was applied.
|
||
|
|
The new fix can be loaded successfully.</li>
|
||
|
|
<li>If the fix to be replaced is temporarily applied, the load operation will
|
||
|
|
automatically permanently apply any replaced (superseded) fixes. If you do
|
||
|
|
not want the fix function to permanently apply any replaced (superseded) temporarily
|
||
|
|
applied fixes automatically, specify *NOAPY for the Superseded PTFs (SPRPTF)
|
||
|
|
parameter on the LODPTF command. The fixes to be replaced must either be permanently
|
||
|
|
applied or permanently removed before fixes that are replacing them can be
|
||
|
|
loaded.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> <img src="./delta.gif" alt="Start of change" />When you order a fix, IBM<sup>®</sup> service does not search through the
|
||
|
|
fixes to determine which one is the latest level. For example, if you order
|
||
|
|
a fix that is superseded by another fix, IBM service will send you only the fix that
|
||
|
|
you ordered instead of the superseding fix. You need to use the summary list
|
||
|
|
to identify the fix you need to order. Scan the summary list for fixes that
|
||
|
|
replace the fix in question and then order the fix.<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|