ibm-information-center/dist/eclipse/plugins/i5OS.ic.dm_5.4.0.1/rbal3mapping.htm

59 lines
3.8 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="copyright" content="(C) Copyright IBM Corporation 2005" />
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
<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="Map considerations using Copy" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbal3mapping" />
<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>Map considerations using Copy</title>
</head>
<body id="rbal3mapping"><a name="rbal3mapping"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Map considerations using Copy</h1>
<div><p><strong>When mapping a character field to a date, time, or timestamp field </strong> and
a format form is being used in the character field, leading zeros can be omitted
from month, day, and hour parts. Microseconds can be truncated or omitted
entirely in the character field.</p>
<p><strong>For mapping to time fields,</strong> the seconds part (and corresponding
separator) can be omitted from the character field.</p>
<p>For *USA form values, the AM or PM with a preceding blank is required.
These rules are also true for date, time, or timestamp values that are entered
when using FROMKEY with *BLDKEY, TOKEY with *BLDKEY, or INCREL parameters
on the CPYF command. All other instances of date, time, and timestamp data
require leading zeros when necessary and no truncation.</p>
<p><strong>For both forms of the TOKEY parameter (*BLDKEY or non-*BLDKEY) the from-field
data must be in a particular format for a chronological comparison to be made.</strong> For the date field, you must use the *ISO or *JIS format to make a chronological
comparison. For the time fields, you must use the *HMS, *ISO, *EUR, or *JIS
formats to make the chronological comparison. For any other formats of date
or time fields (for date (*MDY, *DMY, *YMD, *JUL, *EUR, or *USA) or for time
(*USA)), chronological comparisons are not possible because the TOKEY parameter
performs a straight character string comparison. When you cannot make chronological
comparisons, the system sends an informational message, and the copy operation
continues.</p>
<p><strong>When copying data into a file with date, time, or timestamp
fields, and the from-file is a device file or FMTOPT(*NOCHK) or FMTOPT(*CVTSRC)
has been specified,</strong> output mapping errors might occur if the data copied
to a date, time, or timestamp field is not valid data for the to-file field
format and separator attributes. You cannot copy the record if this occurs. If you use the CPYF or CPYFRMQRYF command, you can specify an error level
other than zero (ERRLVL parameter) to bypass the record and continue the copy
operation. When copying into date, time, or timestamp fields in these instances,
it is important that the from-file data is valid for the to-file.</p>
</div>
</body>
</html>