72 lines
4.3 KiB
HTML
72 lines
4.3 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="Edit time presentation" />
|
||
|
|
<meta name="abstract" content="You need to handle the presentation of times on display files and printer files differently, depending on the way they are stored." />
|
||
|
|
<meta name="description" content="You need to handle the presentation of times on display files and printer files differently, depending on the way they are stored." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagscultconvappdesign.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="rbagstimepresentation" />
|
||
|
|
<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>Edit time presentation</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagstimepresentation"><a name="rbagstimepresentation"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Edit time presentation</h1>
|
||
|
|
<div><p>You need to handle the presentation of times on display files and
|
||
|
|
printer files differently, depending on the way they are stored.</p>
|
||
|
|
<ul><li>As a decimal data field <p>Your application program has responsibility
|
||
|
|
for the way the value is entered, stored, and presented. The program must
|
||
|
|
check for the correct format, eliminate the time separators, convert the time
|
||
|
|
to another format when necessary, and edit it on the display file or printer
|
||
|
|
file.</p>
|
||
|
|
<p>The editing can be done by specifying the edit word (EDTWRD) for
|
||
|
|
the field. The TIME keyword is an output-only field. Both the edit word and
|
||
|
|
TIME keyword use the information available at creation time. The time separators
|
||
|
|
are integrated in the device file object.</p>
|
||
|
|
<p>Both ways force you to have
|
||
|
|
different copies of the source and objects for different editing requirements.</p>
|
||
|
|
</li>
|
||
|
|
<li>As an SAA<sup>®</sup> data
|
||
|
|
type TIME (T) field <p>The operating system allows you
|
||
|
|
to specify different time formats and time separators on the database file
|
||
|
|
level. The TIME keywords allow you to specify the format and editing characters
|
||
|
|
for storing time fields. The time type field is shown as a character string
|
||
|
|
that includes the separators.</p>
|
||
|
|
<p>As an SAA data type, you can specify such time
|
||
|
|
fields as normal character fields on the display file or printer file. On
|
||
|
|
an input operation, your program has to check entered values for the correct
|
||
|
|
format and separators and move them over to the database field. On an output
|
||
|
|
operation, you just move the character string from the database file field
|
||
|
|
to the device file field, including the separators. Any format conversion
|
||
|
|
between the input and output format and the format that the database asks
|
||
|
|
for can be done by either of the following two ways:</p>
|
||
|
|
<ul><li>Application program routines</li>
|
||
|
|
<li>Field mapping through logical files that define different time format
|
||
|
|
and separators</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagscultconvappdesign.htm" title="Different countries have different standards that must be taken into account when developing an NLS-enabled application. This culturally sensitive information must be placed outside the program the same way as the textual data is handled.">Cultural-dependent design</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|