70 lines
4.6 KiB
HTML
70 lines
4.6 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: Central server ORDERENT files" />
|
||
|
|
<meta name="abstract" content="At the central site of Philadelphia, the four files shown in the figure are being used by the ORDERENT application program." />
|
||
|
|
<meta name="description" content="At the central site of Philadelphia, the four files shown in the figure are being used by the ORDERENT application program." />
|
||
|
|
<meta name="DC.subject" content="logical file, application program examples, application program, logical file example" />
|
||
|
|
<meta name="keywords" content="logical file, application program examples, application program, logical file example" />
|
||
|
|
<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="rbae5apaex2a" />
|
||
|
|
<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: Central server ORDERENT files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5apaex2a"><a name="rbae5apaex2a"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">DDM example 2: Central server ORDERENT files</h1>
|
||
|
|
<div><p>At the central site of Philadelphia, the four files shown in the
|
||
|
|
figure are being used by the ORDERENT application program.</p>
|
||
|
|
<div class="section"><p> At the central server, the CUSTMAST file is a physical file that
|
||
|
|
is the primary file of customer data for all locations. The CUSTMST2 file
|
||
|
|
is a logical file that is based on the CUSTMAST physical file. Using a logical
|
||
|
|
file at the central server provides at least two advantages:</p>
|
||
|
|
<ul><li>The same program, ORDERENT, can be used <em>without</em> change by the central
|
||
|
|
server and by each of the remote servers.</li>
|
||
|
|
<li>The data can be accessed through a separate file and cannot keep a customer's
|
||
|
|
primary record locked for the duration of the order.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The four files at the central site are used as follows:</p>
|
||
|
|
<ul><li>The CUSTMAST file contains all the data about all its customers. After
|
||
|
|
a customer order is completed, the CUSTMAST file is changed with all the new
|
||
|
|
information provided by that order.</li>
|
||
|
|
<li>The CUSTMST2 file, which is a logical file at the central server, is used
|
||
|
|
at the beginning of a customer order. When an operator enters a customer number,
|
||
|
|
the program reads the customer data from the CUSTMST2 logical file, but the
|
||
|
|
data actually comes from the primary file, CUSTMAST.</li>
|
||
|
|
<li>The INVEN file contains the current quantities of all items available
|
||
|
|
for sale to customers. When the operator enters an item number and quantity
|
||
|
|
ordered, the corresponding primary item in the INVEN file is changed.</li>
|
||
|
|
<li>The DETAIL file is a list of all the individual items ordered; it contains
|
||
|
|
a record for each item and quantity ordered by customers.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="example"> <div class="fignone" id="rbae5apaex2a__rbae5localoe"><a name="rbae5apaex2a__rbae5localoe"><!-- --></a><span class="figcap">Figure 1. Files used by central server ORDERENT
|
||
|
|
program</span><br /><img src="rsll113.gif" alt="The files being used by the ORDERENT application program in this figure are CUSTMAST (physical file), CUSTMST2 (logical file), INVEN, and DETAIL." /><br /></div>
|
||
|
|
</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>
|