ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaik_5.4.0.1/rzaikoptionalduentries.htm

95 lines
6.2 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="Options for Directory Update entries" />
<meta name="abstract" content="The following are optional for Directory Update entries:" />
<meta name="description" content="The following are optional for Directory Update entries:" />
<meta name="DC.Relation" scheme="URI" content="rzaikupdatex.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="optionalduentries" />
<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>Options for Directory Update entries</title>
</head>
<body id="optionalduentries"><a name="optionalduentries"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Options for Directory Update entries</h1>
<div><p>The following are optional for Directory Update entries: </p>
<div class="section"><dl><dt class="dlterm">Package files:</dt>
<dd>PC files that contain information on other files to be updated. See <a href="rzaikdupkgfilelayout.htm#dupkgfilelayout">Directory Update package files syntax and format</a> for more information.
Package files are added to update entries by using the <a href="rzaikcwbupaddpackagefile.htm#cwbup_addpackagefile">cwbUP_AddPackageFile</a> API.</dd>
<dt class="dlterm">Callback DLL:</dt>
<dd>A DLL provided by the application programmer that Directory Update will
call into during different stages of the update process. This allows programmers
to perform application unique processing during the different stages of an
update. A callback DLL is added to an update entry using the <a href="rzaikcwbupsetcallbackdll.htm#cwbup_setcallbackdll">cwbUP_SetCallbackDLL</a> API. <div class="p">The
different stages of update when Directory Update may call into the callback
DLL are: <dl><dt class="dlterm">Pre-update:</dt>
<dd>This is when Directory Update is about to begin its processing of an update
entry. The following entry point prototype must be in the callback DLL: <strong>unsigned
long _declspec(dllexport) cwbUP_PreUpdateCallback();</strong></dd>
<dt class="dlterm">Post-update:</dt>
<dd>This is when Directory Update has completed moving the files. The following
entry point prototype must be in the callback DLL: <strong>unsigned long _declspec(dllexport)
cwbUP_PostUpdateCallback();</strong></dd>
<dt class="dlterm">Pre-migration:</dt>
<dd>This is when Directory Update is about to begin version-to-version migration
of an update entry. Version-to-version migrations are triggered by QPTFIDX
files. The following entry point prototype must be in the callback DLL: <strong>unsigned
long _declspec(dllexport) cwbUP_PreMigrationCallback();</strong></dd>
<dt class="dlterm">Post-migration:</dt>
<dd>This is when Directory Update has completed processing of a version-to-version
migration of an update entry. The following entry point prototype must be
in the callback DLL: <strong>unsigned long _declspec(dllexport) cwbUP_PostMigrationCallback();</strong></dd>
</dl>
</div>
</dd>
<dt class="dlterm">Attributes:</dt>
<dd>Set the type or mode of the update to be performed. Combinations of the
attributes are allowed. Attributes are: <dl><dt class="dlterm">File-driven update:</dt>
<dd>The files in the target directory are compared to the files in the source
directory. Target files with dates older than the source files are updated.
No new files will be created in the target.</dd>
<dt class="dlterm">Package-driven update:</dt>
<dd>The package files listed in the update entry are scanned for files to
be updated. The dates of the files that are listed in the package file are
compared between the source and the target directories. The source files with
newer dates are updated or moved into the target directory. If a file that
is listed in the package file does not exist in the target, but exists in
the source, the file is created in the target directory.</dd>
<dt class="dlterm">Subdirectory update:</dt>
<dd>Subdirectories under the target directory are included in the update.</dd>
<dt class="dlterm">Onepass update:</dt>
<dd>Updates occur directly from source to target. If this is not specified,
updates occur in two passes. The first pass of the update will copy the files
to be updated into a temporary directory. Then the PC is restarted. On restart,
the files are copied to the target directory. This is useful for locked files.</dd>
<dt class="dlterm">Backlevel update:</dt>
<dd>This controls if updates will occur if the source files are older than
the target files.</dd>
</dl>
</dd>
</dl>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikupdatex.htm" title="The iSeries Access for Windows Directory Update function allows users to specify PC directories for updating from a configured network server or from multiple networked servers. This permits users to load non-iSeries Access for Windows software products on a server in the network, and to keep those files updated on PCs. Directory Update is an optionally installable iSeries Access for Windows component.">iSeries Access for Windows Directory Update APIs</a></div>
</div>
</div>
</body>
</html>