ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakc_5.4.0.1/rzakcmstdfdatsep.htm

95 lines
5.5 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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="reference" />
<meta name="DC.Title" content="DATSEP (Date Separator) keyword for display files" />
<meta name="abstract" content="Use this field-level keyword to specify the separator character for a date field. This keyword is only valid for date fields (data type L)." />
<meta name="description" content="Use this field-level keyword to specify the separator character for a date field. This keyword is only valid for date fields (data type L)." />
<meta name="DC.subject" content="DATSEP (Date Separator) keyword, Date Separator (DATSEP) keyword" />
<meta name="keywords" content="DATSEP (Date Separator) keyword, Date Separator (DATSEP) keyword" />
<meta name="DC.Relation" scheme="URI" content="rzakcmstkeyent.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2001, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2001, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzakcmstdfdatsep" />
<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>DATSEP (Date Separator) keyword for display files</title>
</head>
<body id="rzakcmstdfdatsep"><a name="rzakcmstdfdatsep"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">DATSEP (Date Separator) keyword for display files</h1>
<div><p>Use this field-level keyword to specify the separator character
for a date field. This keyword is only valid for date fields
(data type L).</p>
<div class="section"><p>The format of the keyword is:</p>
<pre>DATSEP(*JOB | 'date-separator')</pre>
<p>The
date separator parameter specifies the separator character that appears between
the year, month, and day. Valid values are a slash (/), dash (), period (.),
comma (,) or blank ( ). Single quotation marks must enclose the parameter.</p>
<p>If
you specify the *ISO, *USA, *EUR, or *JIS date format value for the DATFMT
keyword, you should not specify the DATSEP keyword. These formats have fixed
date separators.</p>
<p>If you do not specify the DATSEP keyword and the format
that is specified for DATFMT does not have a fixed date separator, DATSEP
is set to *JOB as default.</p>
<p>If you specify *JOB or if DATSEP is set to
*JOB as default, the high-level language and the application will handle the
separator as a slash (/). On output the system will convert the separator
that was specified by the Date Separator Job Definition Attribute. The system
converts the separator to a slash (/) as soon as it receives it, before passing
control to the application.</p>
<p>The separator for DFT, DFTVAL, and MAPVAL
keyword values must match the separator the DATSEP keyword specifies. If the
DATSEP keyword specifies *JOB or the DATSEP keyword is set to *JOB as default,
these values must have a format of a slash (/).</p>
<p>The DATSEP keyword overrides
the job attribute. It does not change the system default.</p>
<p>It is the
responsibility of the high-level language and the application to format the
date field according to the format specified for the DATFMT keyword and use
the separators specified for the DATSEP keyword. The system does format fields
on output. The system validates the date field on input according to the format
that the DATFMT keyword specifies and the separator that the DATSEP keyword
specifies.</p>
<p>Option indicators are not valid for this keyword, although
option indicators can be used to condition the field for which it is specified.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example</h4><p>The following example shows how to specify
the DATSEP keyword.</p>
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
00010A
00020A R RECORD1
00030A DATFLD2 L B 5 2DATFMT(*DMY) DATSEP('-')
00040A DATFLD4 L B 5 22DATFMT(*JUL) DATSEP(' ')
00050A DATFLD6 L B 5 42DATFMT(*JOB) DATSEP(*JOB)
A</pre>
<p>If you want to display the date June 21, 1990, the date
format defined in the Job Definition Attributes is *MDY and the date separator
defined in the Job Definition Attributes is a slash (/), the following values
will be displayed when RECORD1 is written.</p>
<pre>DATFLD2 21-06-90
DATFLD4 90 172
DATFLD6 06/21/90</pre>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakcmstkeyent.htm" title="You type the keyword entries that define display files in positions 45 through 80 (functions).">DDS keyword entries for display files (positions 45 through 80)</a></div>
</div>
</div>
</body>
</html>