145 lines
10 KiB
HTML
145 lines
10 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="Move data from another IBM server" />
|
||
|
|
<meta name="abstract" content="There are a number of methods you can use to move data from another IBM server to an iSeries server." />
|
||
|
|
<meta name="description" content="There are a number of methods you can use to move data from another IBM server to an iSeries server." />
|
||
|
|
<meta name="DC.subject" content="moving data, between unlike servers, using SQL functions, using tape, using communications, migration of data from mainframes" />
|
||
|
|
<meta name="keywords" content="moving data, between unlike servers, using SQL functions, using tape, using communications, migration of data from mainframes" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1movedata.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/cpyfrmtap.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/cpyf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../ddm/rbae5kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/ovrdbf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/rcvnetf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzam4/rzam4overview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1appcons.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/wrknetf.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="rbal1moveibm" />
|
||
|
|
<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>Move data from another IBM server</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1moveibm"><a name="rbal1moveibm"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Move data from another IBM server</h1>
|
||
|
|
<div><p>There are a number of methods you can use to move data from another IBM<sup>®</sup> server
|
||
|
|
to an <span class="keyword">iSeries™ server</span>. </p>
|
||
|
|
<div class="section"> <p>You can use the methods listed here to move data:</p>
|
||
|
|
<ul><li>A high-level language program can be written to extract data from another
|
||
|
|
server. A corresponding program for the server can be used to load data to
|
||
|
|
the server.</li>
|
||
|
|
<li>For servers supporting other Distributed
|
||
|
|
Relational Database Architecture™ (DRDA<sup>®</sup>) implementations, you can use SQL
|
||
|
|
functions to move data. For example, with distributed unit of work, you can
|
||
|
|
open a query against the source of the data and, in the same unit of work,
|
||
|
|
insert the data into a table on the server. For best performance, blocking
|
||
|
|
should be used in the query and a multirow insert should be done at the server.</li>
|
||
|
|
<li>Data can be extracted from tables and files on the other server and sent
|
||
|
|
to the <span class="keyword">iSeries server</span> on tape or
|
||
|
|
over communications lines. <ul><li>From a DB2
|
||
|
|
Universal Database™ for z/OS<sup>®</sup> database, a sample program called DSNTIAUL, supplied
|
||
|
|
with the database manager, can be used to extract data from file or tables.</li>
|
||
|
|
<li>From a DB2
|
||
|
|
Universal Database Server for VM (SQL/DS™) database, the Database Services
|
||
|
|
Utility portion of the database manager can be used to extract data.</li>
|
||
|
|
<li>From both DB2
|
||
|
|
Universal Database for z/OS and DB2 Universal Database™ Server
|
||
|
|
for VM databases, Data Extract (DXT™) can be used to extract data. However, DXT handling
|
||
|
|
of null data is not compatible with the Copy File handling of null data described
|
||
|
|
below. Therefore, DXT is not recommended for use in unloading relational
|
||
|
|
data for migration to an <span class="keyword">iSeries server</span>.</li>
|
||
|
|
<li>From IMS/DB hierarchical databases, DXT can be used to extract data.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>You can use standard tape management techniques to copy data to tape from DB2
|
||
|
|
Universal Database for z/OS or DB2 Universal Database Server
|
||
|
|
for VM databases. The <span class="keyword">iSeries server</span> uses
|
||
|
|
the <span class="cmdname">Copy from Tape (CPYFRMTAP)</span> command to load data from
|
||
|
|
tape. The <span class="cmdname">Copy File (CPYF)</span> command, however, provides special
|
||
|
|
support for migrating data from IBM mainframe computers. <span class="cmdname">CPYF</span> can
|
||
|
|
be used with tape data by the use of the <span class="cmdname">Override with Tape File
|
||
|
|
(OVRTAPF)</span> command. The <span class="cmdname">OVRTAPF</span> command lets you
|
||
|
|
specify special tape-specific parameters which might be necessary when you
|
||
|
|
import data from a server other than the <span class="keyword">iSeries server</span>. <p>The
|
||
|
|
special <span class="cmdname">CPYF</span> support lets you import nullable data and
|
||
|
|
floating point data. Nullable data can be unloaded from mainframes in such
|
||
|
|
a way that a single-byte flag can be associated with each nullable field.
|
||
|
|
With the *NULLFLAGS option specified for the FMTOPT parameter, the <span class="cmdname">Copy
|
||
|
|
File (CPYF)</span> command can recognize the null flags and ignore the
|
||
|
|
data in the adjacent field on the tape and make the field null in DB2
|
||
|
|
Universal Database for iSeries. The other useful FMTOPT parameter value
|
||
|
|
for importing data from IBM mainframes is the *CVTFLOAT value. It allows floating
|
||
|
|
point data stored on tape in S/390<sup>®</sup> format to be converted to the IEEE format used
|
||
|
|
by <span class="keyword">DB2<sup>®</sup> UDB for iSeries</span>.</p>
|
||
|
|
<p>For more
|
||
|
|
information on using tape devices with the <span class="keyword">iSeries server</span>,
|
||
|
|
see the Storage solutions topic. </p>
|
||
|
|
</li>
|
||
|
|
<li>Data sent over communications lines can be handled through SNADS support
|
||
|
|
on the <span class="keyword">iSeries server</span>. SNADS support
|
||
|
|
transfers network files for BSCEL and SNUF protocols in addition to the Advanced
|
||
|
|
Program-to-Program Communication (APPC) or Advanced Peer-to-Peer
|
||
|
|
Networking<sup>®</sup> (APPN) protocols used for distributed relational database
|
||
|
|
processing. <ul><li>From an MVS™ system,
|
||
|
|
data can be sent to the <span class="keyword">iSeries server</span> using
|
||
|
|
TSO XMIT functions. The server uses the <span class="cmdname">Work with Network Files (WRKNETF)</span> or <span class="cmdname">Receive
|
||
|
|
Network File (RCVNETF)</span> command to receive a network file.</li>
|
||
|
|
<li>From a VM system, data can be sent to the server using SENDFILE functions.
|
||
|
|
The server uses the <span class="cmdname">Work with Network Files (WRKNETF)</span> or <span class="cmdname">Receive
|
||
|
|
Network File (RCVNETF)</span> command to receive a network file.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>From Microsoft<sup>®</sup> Windows<sup>®</sup>, client data can be sent to
|
||
|
|
the iSeries server
|
||
|
|
using iSeries Access,
|
||
|
|
a separately ordered IBM product. </li>
|
||
|
|
<li id="rbal1moveibm__import"><a name="rbal1moveibm__import"><!-- --></a>From a variety of workstation clients, you can use the DB2
|
||
|
|
Universal Database for Linux<sup>®</sup>, UNIX<sup>®</sup> and Windows IMPORT and EXPORT utilities
|
||
|
|
to copy data to and from an <span class="keyword">iSeries server</span>.
|
||
|
|
The IMPORT can import data only into existing tables. See the <a href="http://publib-b.boulder.ibm.com/Redbooks.nsf/9445fa5b416f6e32852569ae006bb65f/189e93edc38f03b7852569d2005a959a?OpenDocument" target="_blank">Advanced Functions and Administration on DB2
|
||
|
|
Universal Database for iSeries, SG24-4249-03</a><img src="rbpdf.gif" alt="Link to PDF" /> redbook for examples of the IMPORT and EXPORT utilities.
|
||
|
|
This redbook also provides information about what file types and data formats
|
||
|
|
can be used with the IMPORT and EXPORT utilities.</li>
|
||
|
|
<li>Data can also be sent over communications lines that do not support SNADS,
|
||
|
|
such as asynchronous communications. File transfer support (FTS), a utility
|
||
|
|
that is part of the <span class="keyword">i5/OS™</span> licensed
|
||
|
|
program, can be used to send and receive data. For more information about
|
||
|
|
working with communications and communications files, see <a href="../books/sc415442.pdf " target="_blank">ICF Programming</a><img src="wbpdf.gif" alt="Link to PDF" />.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1movedata.htm" title="You might need to move a file from another IBM server to an iSeries server or from a non-IBM server to the iSeries server. This topic collection lists alternatives for moving data to an iSeries server from a non-iSeries server. However, you must refer to manuals supplied with the other server or identified for the application for specific instructions on its use.">Move a database to an iSeries server from a non-iSeries server</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../ddm/rbae5kickoff.htm">Distributed data management</a></div>
|
||
|
|
<div><a href="../rzam4/rzam4overview.htm">Storage solutions</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/cpyfrmtap.htm">Copy From Tape (CPYFRMTAP) command</a></div>
|
||
|
|
<div><a href="../cl/cpyf.htm">Copy File (CPYF) command</a></div>
|
||
|
|
<div><a href="../cl/ovrdbf.htm">Override with Database File (OVRDBF) command</a></div>
|
||
|
|
<div><a href="../cl/rcvnetf.htm">Receive Network File (RCVNETF) command</a></div>
|
||
|
|
<div><a href="rbal1appcons.htm" title="Distributed relational database applications have different requirements from applications developed solely for use on a local database.">Tips: Design distributed relational database applications</a></div>
|
||
|
|
<div><a href="../cl/wrknetf.htm">Work with Network File (WRKNETF) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|