73 lines
4.7 KiB
HTML
73 lines
4.7 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Database definitions" />
|
||
|
|
<meta name="abstract" content="You define a file to specify certain facts, and the specifications are then used on database files." />
|
||
|
|
<meta name="description" content="You define a file to specify certain facts, and the specifications are then used on database files." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsarngandarchdsgngd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsapppartnames.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="rbagsdatabasedefs" />
|
||
|
|
<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>Database definitions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagsdatabasedefs"><a name="rbagsdatabasedefs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Database definitions</h1>
|
||
|
|
<div><p>You define a file to specify certain facts, and the specifications
|
||
|
|
are then used on database files.</p>
|
||
|
|
<p>Here are some examples of such specifications:</p>
|
||
|
|
<ul><li>The object description text of the file</li>
|
||
|
|
<li>The explanation text (TEXT keyword) on record formats and field descriptions</li>
|
||
|
|
<li>The column headings (COLHDG keyword) on field descriptions</li>
|
||
|
|
<li>Date and time formats and separators</li>
|
||
|
|
<li>Sort sequence</li>
|
||
|
|
<li>Language identifier</li>
|
||
|
|
</ul>
|
||
|
|
<p>The object description text is shown by all database tools such as DB2
|
||
|
|
Universal Database™ (UDB) for iSeries™ SQL, iSeries Access, and data file utility
|
||
|
|
(DFU) on the file selection display.</p>
|
||
|
|
<p>The column headings are shown by the database tools on the output field
|
||
|
|
definition display. Column headings are also used on screen design aid (SDA)
|
||
|
|
and report layout utility (RLU) as the proposed field-prompting text or heading.</p>
|
||
|
|
<p>Data management handles date- and time-type fields in the format specified
|
||
|
|
at file-creation time, unless your application or database tool does a conversion
|
||
|
|
to present it according to your request or job demand.</p>
|
||
|
|
<p>When you want to present all this information according to the language
|
||
|
|
and culture of the user, you need to provide multiple sets of logical files
|
||
|
|
in separate libraries. Along with the translated text, you can specify different
|
||
|
|
date and time formats or different sort sequence and let data management perform
|
||
|
|
the conversion. A similar technique can also be used for numeric-type date
|
||
|
|
fields (unless they are packed), using the substring (SST) function. The user
|
||
|
|
can access the data only through the designated logical views. When you are
|
||
|
|
defining logical files with different sort sequences, avoid using a unique
|
||
|
|
index with a shared-weight table. Although this is possible, a unique index
|
||
|
|
prevents using keys that differ only in characters with the same weight.</p>
|
||
|
|
<p>The information about Application part names includes a scenario that uses
|
||
|
|
different sets of logical files for different users.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsarngandarchdsgngd.htm" title="When you design an international application, consider the ways that you can organize and structure your application so that it can be used in an international environment.">Application arrangement and architecture</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbagsapppartnames.htm" title="When you want to enable your application for different languages and countries, consider the environments of the target systems in your naming conventions.">Application part names</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|