ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaih_5.4.0.1/rzaih3e.htm

103 lines
6.8 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="Package and send objects with Management Central" />
<meta name="abstract" content="A bulk data transfer is the process of sending packages, fixes, PDFs and so on, from a source system to a target system in a single transfer. This topic discusses package definitions, what happens when a package is sent, and how to troubleshoot a failed transfer." />
<meta name="description" content="A bulk data transfer is the process of sending packages, fixes, PDFs and so on, from a source system to a target system in a single transfer. This topic discusses package definitions, what happens when a package is sent, and how to troubleshoot a failed transfer." />
<meta name="DC.Relation" scheme="URI" content="rzaih2.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="rzaih3e" />
<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>Package and send objects with Management Central</title>
</head>
<body id="rzaih3e"><a name="rzaih3e"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Package and send objects with Management Central</h1>
<div><p>A bulk data transfer is the process of sending packages, fixes,
PDFs and so on, from a source system to a target system in a single transfer.
This topic discusses package definitions, what happens when a package is sent,
and how to troubleshoot a failed transfer.</p>
<div class="section"><h4 class="sectiontitle">What you can do with package definitions</h4><p>Sending
files to another system or group of systems is a simple point-and-click operation
in iSeries™ Navigator.
If you expect to send the same files again at a later date, you can create
a <dfn class="term">package definition</dfn>, which can be saved and reused at any time
to send the defined set of files and folders to multiple endpoint systems
or system groups. If you create a snapshot of your files, you can keep more
than one version of copies of the same set of files. Sending a snapshot ensures
that no updates are made to the files during the distribution, so that the
last target system receives the same objects as the first target system.</p>
<p>Another
benefit of using iSeries Navigator
to package and send objects is that you can run a command when the distribution
of the package is complete. This means that you can:</p>
<ul><li>Distribute a batch input stream and run it.</li>
<li>Distribute a set of programs and start your application.</li>
<li>Distribute a set of data files and run a program that acts on that data.</li>
</ul>
<p>You can specify whether to include subfolders in the package. You
can also specify whether to keep or replace any file that already exists on
the target system. You can start the send task immediately or click <span class="uicontrol">Schedule</span> to
specify when you want the task to start.</p>
<p>You can select and send files
and folders without creating a package definition. However, a package definition
allows you to group together a set of i5/OS™ objects or integrated file system
files. The package definition also allows you to view this same group of files
as a logical set, or as a physical set, by taking a snapshot of the files
to preserve them for later distribution.</p>
<p>For more information about these
and other Management Central tasks and topics, refer to the detailed task
help that is available from the iSeries Navigator window. Click <span class="uicontrol">Help</span> from
the menu bar and select <span class="menucascade"><span class="uicontrol">iSeries Navigator overview</span> &gt; <span class="uicontrol">Management Central</span></span>.</p>
</div>
<div class="section"><h4 class="sectiontitle">Troubleshooting a failed transfer</h4><div class="p"><ul><li>Look at the task's job log and try to determine a cause. From the Task
Status window, right-click the failed endpoint and click <span class="uicontrol">Task Output</span>.<p>Sending
packages uses the Save/Restore function. When a save or restore operation
issues an error or warning message, the Management Central package send function
marks the status as failed. This does not necessarily mean that the entire
process failed. You need to check the job log and determine the cause of the
failure. It is possible that there is a message that indicates that the restore
function worked with limitation and thus generated a warning.</p>
</li>
<li>Make sure that the target system can connect back to the source system. <p>On
the endpoint system ping itself by the long name. If this is successful, then
on the source system, ping the endpoint system using its long name. </p>
<p>To
complete a successful transfer, the target system must connect back to the
source system. The IP address that is used on the target system is determined
by the lookup frequency on the target system. If the lookup frequency is Never
then the IP address that is used is the one that is provided by the central
system for the source system. </p>
<p>It might be that target system cannot
connect to the source system via this IP address, but can connect by using
a different IP address, one that is defined in its host table. If the lookup
frequency on the target is set to Always then it will use DNS, the host table,
or both to determine the IP address of the source system and it will not use
the IP address that is provided by the central system.</p>
</li>
</ul>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaih2.htm" title="After Management Central has been set up, you can use it to streamline your server administration tasks.">Work with Management Central</a></div>
</div>
</div>
</body>
</html>