86 lines
6.1 KiB
HTML
86 lines
6.1 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="Date, time, and timestamp fields used by record keys (FROMKEY and TOKEY)" />
|
||
|
|
<meta name="abstract" content="When the number of key fields and a value are used to specify the FROMKEY or TOKEY parameter, no conversion of data occurs if the corresponding key field in the from-file is a date, time, or timestamp field." />
|
||
|
|
<meta name="description" content="When the number of key fields and a value are used to specify the FROMKEY or TOKEY parameter, no conversion of data occurs if the corresponding key field in the from-file is a date, time, or timestamp field." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3copyrrk.htm" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbal3copydtt" />
|
||
|
|
<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>Date, time, and timestamp fields used by record keys (FROMKEY and TOKEY)</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal3copydtt"><a name="rbal3copydtt"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Date, time, and timestamp fields used by record keys (FROMKEY and TOKEY)</h1>
|
||
|
|
<div><p>When the number of key fields and a value are used to specify the
|
||
|
|
FROMKEY or TOKEY parameter, no conversion of data occurs if the corresponding
|
||
|
|
key field in the from-file is a date, time, or timestamp field.</p>
|
||
|
|
<p> The user input string that you specify (including the separators) must
|
||
|
|
be in the same format as the date, time, or timestamp field. If it is not,
|
||
|
|
a file open error might occur, or the records copied might not be the result
|
||
|
|
that you want.</p>
|
||
|
|
<div class="p">If *BLDKEY is specified for the FROMKEY or TOKEY parameter and the corresponding
|
||
|
|
key field in the from-file is a date, time, or timestamp field, the system
|
||
|
|
attempts to convert the user-input key field value to the format (and separators)
|
||
|
|
of the from-file field. The following rules apply to the conversion: <ul><li><span class="uicontrol">If the from-field is a date key field,</span> the system
|
||
|
|
first determines if the user-input key value is in the same format and has
|
||
|
|
the same separator as specified in the current job under which the copy command
|
||
|
|
is running. This can be *MDY, *DMY, *YMD, or *JUL for the format and slash
|
||
|
|
(/), hyphen (-), period (.), comma (,), or blank ( ) for the separator. If
|
||
|
|
the user-input key value is not in the current job specified format and separator
|
||
|
|
form, it determines if it is in one of the Systems Application
|
||
|
|
Architecture<sup>®</sup> (SAA<sup>®</sup>) formats (*ISO, *USA, *EUR, or *JIS). It also determines
|
||
|
|
if it is in a YYYYDDD form (no separator). If the system can determine the
|
||
|
|
user-input key value is in one of these forms, the input string is converted
|
||
|
|
to the actual format (and separator) of the from-file date field, which is
|
||
|
|
used for the key comparison. If the user-input string format cannot be determined
|
||
|
|
or the length or data value is not valid, the system issues a diagnostic message.
|
||
|
|
You must left-justify the date portion of the user-input key value; it can
|
||
|
|
contain trailing blanks.</li>
|
||
|
|
<li><span class="uicontrol">If the from-field is a time key field,</span> the system
|
||
|
|
first determines if the user-input key value is in the same format and has
|
||
|
|
the same separator as specified in the current job under which the copy command
|
||
|
|
is running. This might be HHMMSS for the format and colon (:), comma (,),
|
||
|
|
period (.), or blank ( ) for the separator. If the user-input key value is
|
||
|
|
not in the current job specified format and separator form, the system determines
|
||
|
|
if it is in one of the SAA formats (*ISO, *USA, *EUR, or *JIS). If the system
|
||
|
|
can determine the user-input key value is in one of these forms, the input
|
||
|
|
string is converted to the actual format (and separator) of the from-file
|
||
|
|
time field, which is used for the key comparison. If the user-input string
|
||
|
|
format cannot be determined, or the length or data value is not valid, the
|
||
|
|
system issues a diagnostic message. You must left-justify the time portion
|
||
|
|
of the user-input key value; it can contain trailing blanks.</li>
|
||
|
|
<li><span class="uicontrol">If the from-field is a timestamp key field,</span> the
|
||
|
|
system first determines if the user-input key value is in the SAA format or
|
||
|
|
YYYYMMDDHHMMSS form. If the system determines the user-input key value is
|
||
|
|
in one of these forms, the input string is converted to the actual SAA timestamp
|
||
|
|
format, which is used for the key comparison. If the user-input string format
|
||
|
|
cannot be determined, or the length or data value is not valid, the system
|
||
|
|
issues a diagnostic message. You must left-justify the timestamp portion of
|
||
|
|
the user-input key value; it can contain trailing blanks.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal3copyrrk.htm" title="You can specify record keys to copy only from a keyed database file. Note that you can use this parameter on the CPYF command only.">Select records by record keys (FROMKEY and TOKEY Parameters)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|