59 lines
3.9 KiB
HTML
59 lines
3.9 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="DDM example 2: Remote server ORDERENT files" />
|
||
|
|
<meta name="abstract" content="The ORDERENT program remains the same at all locations, but the CUSTMST2 file is now a copy of the central server's customer primary file CUSTMAST." />
|
||
|
|
<meta name="description" content="The ORDERENT program remains the same at all locations, but the CUSTMST2 file is now a copy of the central server's customer primary file CUSTMAST." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5apaex2.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="rbae5apaex2c" />
|
||
|
|
<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>DDM example 2: Remote server ORDERENT files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5apaex2c"><a name="rbae5apaex2c"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">DDM example 2: Remote server ORDERENT files</h1>
|
||
|
|
<div><p>The ORDERENT program remains the same at all locations, but the
|
||
|
|
CUSTMST2 file is now a <em>copy</em> of the central server's customer primary
|
||
|
|
file CUSTMAST.</p>
|
||
|
|
<div class="section"><p>By using CUSTMST2 whenever possible for data that does not change
|
||
|
|
often, the amount of communications time needed to process each order entry
|
||
|
|
request can be minimized. The remote ORDERENT program reads the
|
||
|
|
local CUSTMST2 file at the beginning of each order, and then, using DDM, updates
|
||
|
|
the CUSTMAST file on the central server only when an order has been completed.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The other two files, INVEN and DETAIL, have the same functions
|
||
|
|
on each remote server as on the central server.</p>
|
||
|
|
</div>
|
||
|
|
<div class="example"> <div class="fignone" id="rbae5apaex2c__rmtoe"><a name="rbae5apaex2c__rmtoe"><!-- --></a><span class="figcap">Figure 1. Files used by remote ORDERENT programs</span><br /><img src="rsll117.gif" alt="The files used by the ORDERENT programs are CUSTMAST, CUSTMST2, INVEN, and DETAIL." /><br /></div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The CUSTMAST file is changed by all locations and contains the
|
||
|
|
most current information for each customer (for constantly changing data such
|
||
|
|
as the customer's account balance). The CUSTMST2 file, which is used for reading
|
||
|
|
data that changes only occasionally (such as name and address), should be
|
||
|
|
changed periodically (once a week, for example), by recopying the CUSTMAST
|
||
|
|
file into it. Task 2 of this example explains one way to do this.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5apaex2.htm" title="This second example shows how multiple locations in a customer's business can process the same order entry application using DDM.">DDM example 2: ORDERENT application</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|