72 lines
5.0 KiB
HTML
72 lines
5.0 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="Considerations for creating a file and using the FORMAT parameter" />
|
||
|
|
<meta name="abstract" content="This topic discusses the considerations for creating a file and using the FORMAT parameter." />
|
||
|
|
<meta name="description" content="This topic discusses the considerations for creating a file and using the FORMAT parameter." />
|
||
|
|
<meta name="DC.subject" content="database file, creating, using FORMAT parameter, FORMAT parameter, creating a file, considerations" />
|
||
|
|
<meta name="keywords" content="database file, creating, using FORMAT parameter, FORMAT parameter, creating a file, considerations" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoopnqf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafodynjfex1.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="rbafoccfufmt" />
|
||
|
|
<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>Considerations for creating a file and using the FORMAT parameter</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbafoccfufmt"><a name="rbafoccfufmt"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Considerations for creating a file and using the FORMAT parameter</h1>
|
||
|
|
<div><p>This topic discusses the considerations for creating a file and
|
||
|
|
using the FORMAT parameter.</p>
|
||
|
|
<div class="p">You must specify a record format name on the FORMAT parameter when you
|
||
|
|
request join processing by specifying multiple entries on the FILE parameter
|
||
|
|
(that is, you cannot specify FORMAT(*FILE)). Also, a record format name is
|
||
|
|
normally specified with the grouping function or when you specify a complex
|
||
|
|
expression on the MAPFLD parameter to define a derived field. Consider the
|
||
|
|
following guidelines and rules:<ul><li>The record format name is any name you select. It can differ from the
|
||
|
|
format name in the database file you want to query.</li>
|
||
|
|
<li>The field names are any names you select. If the field names are unique
|
||
|
|
in the database files you are querying, the system implicitly maps the values
|
||
|
|
for any fields with the same name in a queried file record format (FILE parameter)
|
||
|
|
and in the query result format (FORMAT parameter). </li>
|
||
|
|
<li>If the field names are unique, but the attributes differ between the file
|
||
|
|
specified on the FILE parameter and the file specified on the FORMAT parameter,
|
||
|
|
the data is implicitly mapped.</li>
|
||
|
|
<li>The correct field attributes must be used when using the MAPFLD parameter
|
||
|
|
to define derived fields. For example, if you are using the grouping %SUM
|
||
|
|
function, you must define a field that is large enough to contain the total.
|
||
|
|
If not, an arithmetic overflow occurs and an exception is sent to the program.</li>
|
||
|
|
<li>Decimal alignment occurs for all field values mapped to the record format
|
||
|
|
identified on the FORMAT parameter. Assume that you have a field in the query
|
||
|
|
result record format with 5 digits with 0 decimals, and the value that was
|
||
|
|
calculated or must be mapped to that field is 0.12345. You will receive a
|
||
|
|
result of 0 in your field because digits to the right of the decimal point
|
||
|
|
are truncated.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafoopnqf.htm" title="The Open Query File (OPNQRYF) command is a control language (CL) command that allows you to perform many data processing functions on database files. These topics discuss how to create a query using the OPNQRYF command, how to specify parameters for its major functions, and how to use it with your high-level language program.">Use Open Query File (OPNQRYF) command</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbafodynjfex1.htm" title="This example shows how to dynamically join database files without DDS.">Example 1: Dynamically join database files without DDS</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|