Fast/Unload datetime processing considerations - Revision history

JAL: link repair

2018-02-08T22:48:52Z

link repair

← Older revision		Revision as of 22:48, 8 February 2018
Line 116:		Line 116:
	<li><var class="product">[[Media:SirfieldNew.pdf\|Sir2000 Field Migration Facility]]</var>		<li><var class="product">[[Media:SirfieldNew.pdf\|Sir2000 Field Migration Facility]]</var>

	<li><var class="product">[[~~Media:Ul2krNew.pdf\|~~Sir2000 User Language Tools]]</var> </li>		<li><var class="product">[[Sir2000 User Language Tools]]</var> </li>
	</ul>		</ul>
	<!-- Note: all the above products imbed the SCRIPT file COMDATE except Janus Web -->		<!-- Note: all the above products imbed the SCRIPT file COMDATE except Janus Web -->

JAL: /* Strict and non-strict format matching */ replace table with template

2018-02-02T20:12:19Z

Strict and non-strict format matching: replace table with template

← Older revision		Revision as of 20:12, 2 February 2018
Line 467:		Line 467:
	However, non-strict #functions sometimes allow a string		However, non-strict #functions sometimes allow a string
	to match a token on input that would not be produced by that token on output.		to match a token on input that would not be produced by that token on output.
			<p>
	The types of strict matching are as follows:		The types of strict matching are as follows:
	~~<table class="thJustBold">~~		</p>
	~~<tr><th nowrap>Alpha tokens</th>~~		{{Template:Datetime format matching}}
	<td>For alphabetic tokens (for example, <var>Month</var>), a strict match requires the input value to be the correct case. For example, the <var>MON</var> token is strictly matched by <code>JAN</code> but not by <code>Jan</code>, and the reverse is true for the <var>Mon</var> token. For non-strict matching, the alphabetic tokens are matched by any combination of uppercase and lowercase input.</td></tr>

	~~<tr><th>HH, MM, DD~~</th>
	~~<td>For these tokens, a strict match requires a leading zero for values less than 10. For non-strict~~ matching~~, a value less than 10 can also be represented by a leading blank followed by a single numeric digit.</td></tr>~~

	~~<tr><th>BH, BM, BD</th>~~
	<td>For these tokens, a strict match requires a leading blank for values less than 10. For non-strict matching, a value less than 10 can also be represented by a leading zero followed by a numeric digit.</td></tr>

	~~<tr><th>DAY</th>~~
	<td>For this token, a strict match requires a single digit for values less than 10. For non-strict matching, a value less than 10 can also be represented by a leading zero followed by a numeric digit.</td></tr>

	~~<tr><th>ZYY</th>~~
	<td>For this token, a strict match requires two digits for values less than 100. For non-strict matching, a value less than 100 can also be represented by a leading zero followed by a two numeric digits.</td></tr>
	~~</table>~~

	If you want to check a datetime string using strict rules, you can use the following technique with the non-strict date #functions:		If you want to check a datetime string using strict rules, you can use the following technique with the non-strict date #functions:
Line 490:		Line 477:
	END IF		END IF
	</p>		</p>

	==<b id="fmtex"></b>Datetime and format examples==		==<b id="fmtex"></b>Datetime and format examples==
	There is an extensive set of format tokens, as shown in [[#dtfmt\|Datetime formats]].		There is an extensive set of format tokens, as shown in [[#dtfmt\|Datetime formats]].

JAL: misc cleanup

2018-01-25T19:00:48Z

misc cleanup

← Older revision		Revision as of 19:00, 25 January 2018
Line 683:		Line 683:
	being executed. In this case, the argument values are dumped as well.</p>		being executed. In this case, the argument values are dumped as well.</p>

	==#DATExxx functions ~~CENTSPAN argument~~==		==CENTSPAN argument of #DATExxx functions==
	<p>		<p>
	Many of the #DATExxx functions accept an optional argument		Many of the #DATExxx functions accept an optional argument
Line 690:		Line 690:
	You can customize the default value of <var>CENTSPAN</var>		You can customize the default value of <var>CENTSPAN</var>
	in your load module (see [[Fast/Unload customization of defaults#dfcs\|CENTSPAN and SPANSIZE]]).</p>		in your load module (see [[Fast/Unload customization of defaults#dfcs\|CENTSPAN and SPANSIZE]]).</p>
	~~<p class="note">~~
	~~<b>Note:</b> In version 3.0 of <var class="product">Fast/Unload</var>, the default <var>CENTSPAN</var> argument cannot be customized.</p>~~
	<p>		<p>
	The default value should be adequate in most cases. If you have		The default value should be adequate in most cases. If you have
Line 697:		Line 695:
	code the value on the relevant #function invocations.</p>		code the value on the relevant #function invocations.</p>
	<p>		<p>
	For a different approach, see the description of the <var>[[CENTSPLT parameter\|CENTSPLT]]</var> and <var>DEFCENT</var> parameters and $function arguments.</p>		For a different approach, see the description of the <var>[[CENTSPLT parameter\|CENTSPLT]]</var> and <var>[[DEFCENT parameter\|DEFCENT]]</var> parameters and $function arguments.</p>
	<p class="note"><b>Note:</b>		<p class="note"><b>Note:</b>
	The <var>CENTSPAN</var> argument may not be specified as		The <var>CENTSPAN</var> argument may not be specified as
	an entity whose value is <var>MISSING</var>.		an entity whose value is <var>MISSING</var>.
	For most #function numeric arguments, the <var>MISSING</var> value is allowed		For most #function numeric arguments, the <var>MISSING</var> value is allowed if a value of zero for the argument is allowed.
	if a value of zero for the argument is allowed.
	Zero is allowed for <var>CENTSPAN</var>, but since it is an unusual		Zero is allowed for <var>CENTSPAN</var>, but since it is an unusual
	<var>CENTSPAN</var> value, the <var>MISSING</var> value may <i>not</i> be supplied. </p>		<var>CENTSPAN</var> value, the <var>MISSING</var> value may <i>not</i> be supplied. </p>

	==Benefits of ~~<var class="product">~~Fast/Unload~~</var>~~ datetime processing==		==Benefits of Fast/Unload datetime processing==
	<p>		<p>
	Following is a list of benefits offered by <var class="product">Fast/Unload</var>		Following is a list of benefits offered by <var class="product">Fast/Unload</var> datetime processing.
	datetime processing.		To provide concrete comparisons, there are some references to some <var class="product">[[SOUL]]</var> date $functions.</p>
	To provide concrete comparisons, there
	are some references to some <var class="product">[[SOUL]]</var> date $functions.</p>
	<table class="thJustBold">		<table class="thJustBold">
	<tr><th>SPANSIZE</th>		<tr><th>SPANSIZE</th>

JAL: typos

2018-01-24T20:46:26Z

typos

← Older revision		Revision as of 20:46, 24 January 2018
Line 213:		Line 213:
	All of the tokens that match alphabetic strings (for example, <var>MON</var>) match any case for non-strict matching.		All of the tokens that match alphabetic strings (for example, <var>MON</var>) match any case for non-strict matching.
	All other tokens that have differing strict and non-strict matching		All other tokens that have differing strict and non-strict matching
	rules ~~are listed under "Special date format rules" in~~		rules have usage notes in [[#fmtex\|Datetime and format examples]].
	~~the index at the back of the manual, and~~ usage notes ~~for them are~~
	~~contained~~ in [[#fmtex\|Datetime and format examples]].
	Each input datetime format argument in the description of a #function		Each input datetime format argument in the description of a #function
	~~specificies~~ whether the use of the format observes strict or non-strict format matching.		specifies whether the use of the format observes strict or non-strict format matching. See [[#strict\|Strict and non-strict format matching]].
	See [[#strict\|Strict and non-strict format matching]].

	<table class="thJustBold">		<table class="thJustBold">

JAL: /* Datetime formats */ typo

2018-01-24T20:19:45Z

Datetime formats: typo

← Older revision		Revision as of 20:19, 24 January 2018
Line 101:		Line 101:
	The additional products using datetime format strings are:		The additional products using datetime format strings are:
	<ul>		<ul>
	<li><var class="product">[[Media:~~JocliNew~~.pdf\|Janus Open Client]]</var> </li>		<li><var class="product">[[Media:JoclrNew.pdf\|Janus Open Client]]</var> </li>

	<li><var class="product">[[Media:JosrvrNew.pdf\|Janus Open Server]]</var>		<li><var class="product">[[Media:JosrvrNew.pdf\|Janus Open Server]]</var>
Line 110:		Line 110:
	<li><var class="product">[[Janus Web Server]]</var> </li>		<li><var class="product">[[Janus Web Server]]</var> </li>

	<li><var class="product">[[~~Media:DbarNew.pdf\|~~SirDBA]]</var> </li>		<li><var class="product">[[SirDBA]]</var> </li>

	<li><var class="product">[[Release notes for Model 204 version 7.5#Former Sirius $functions\|Sirius Functions]]</var> </li>		<li><var class="product">[[Release notes for Model 204 version 7.5#Former Sirius $functions\|Sirius Functions]]</var> </li>

JAL: minor formatting

2018-01-24T19:59:28Z

minor formatting

← Older revision		Revision as of 19:59, 24 January 2018
Line 386:		Line 386:
	of dates does not exceed 100 years.		of dates does not exceed 100 years.

	<~~div~~ id="cspan"></~~div~~>		===<b id="cspan"></b>CENTSPAN===
	~~===~~CENTSPAN===
	~~<!--Caution: <div> above-->~~

	<var>CENTSPAN</var> provides a mechanism for unambiguously converting dates with		<var>CENTSPAN</var> provides a mechanism for unambiguously converting dates with
	two-digit year values into dates with four-digit year values.		two-digit year values into dates with four-digit year values.
Line 433:		Line 430:
	more than one hundred years of values with a two-digit year.		more than one hundred years of values with a two-digit year.

	<~~div~~ id="ssize"></~~div~~>		===<b id="ssize"></b>SPANSIZE===
	~~===~~SPANSIZE===
	~~<!--Caution: <div> above-->~~

	There is a method to protect from the ambiguities that		There is a method to protect from the ambiguities that
	can occur at each end of the 100-year window defined by <var>CENTSPAN</var>.		can occur at each end of the 100-year window defined by <var>CENTSPAN</var>.
Line 470:		Line 464:
	case where a range greater than one hundred years is being used.		case where a range greater than one hundred years is being used.

	<~~div~~ id="strict"></~~div~~>		==<b id="strict"></b>Strict and non-strict format matching==
	==Strict and non-strict format matching==
	~~<!--Caution: <div> above-->~~

	As mentioned in [[#dtfmt\|Datetime formats]], for some of the #functions,		As mentioned in [[#dtfmt\|Datetime formats]], for some of the #functions,
	the input format rule for a token is the same as the output format rule.		the input format rule for a token is the same as the output format rule.
Line 503:		Line 494:
	</p>		</p>

	<~~div~~ id="fmtex"></~~div~~>		==<b id="fmtex"></b>Datetime and format examples==
	==Datetime and format examples==
	~~<!--Caution: <div> above-->~~

	There is an extensive set of format tokens, as shown in [[#dtfmt\|Datetime formats]].		There is an extensive set of format tokens, as shown in [[#dtfmt\|Datetime formats]].
	These tokens and the various separator characters		These tokens and the various separator characters
Line 552:		Line 540:
	<li>With non-strict format matching, such as with <var>#DATE2ND</var>, the leading zero corresponding to an <var>MM</var> token may be given as a blank, thus allowing <code>' 7/15/98'</code>.		<li>With non-strict format matching, such as with <var>#DATE2ND</var>, the leading zero corresponding to an <var>MM</var> token may be given as a blank, thus allowing <code>' 7/15/98'</code>.
	<p>		<p>
	With strict matching, however, such a leading blank is not allowed for <var>MM</var>. A leading blank month value with a strict #function requires the <var>BM</var> token. If the data contains leading zeroes in some month instances and leading blanks in others, you must use a non-strict #function~~. The <var>BM</var> token is available starting with version 3.2 of <var class="product">Fast/Unload</var>~~. </p></li>		With strict matching, however, such a leading blank is not allowed for <var>MM</var>. A leading blank month value with a strict #function requires the <var>BM</var> token. If the data contains leading zeroes in some month instances and leading blanks in others, you must use a non-strict #function. </p></li>
	</ul></td></tr>		</ul></td></tr>

Line 563:		Line 551:
	</nowiki></p>		</nowiki></p>
	<p>		<p>
	Notes:		Notes: </p>
	<ul>		<ul>
	<li>With non-strict format matching, such as with <var>#DATE2ND</var>, the leading zero corresponding to a <var>DD</var> token may be given as a blank, thus allowing <code>' 1.01.00'</code>.		<li>With non-strict format matching, such as with <var>#DATE2ND</var>, the leading zero corresponding to a <var>DD</var> token may be given as a blank, thus allowing <code>' 1.01.00'</code>.
	<p>		<p>
	With strict matching, however, such a leading blank is not allowed for <var>DD</var>. A leading blank day value with a strict #function requires the <var>BD</var> token. If the data contains leading zero days in some instances and leading blanks in others, you must use a non-strict #function. ~~The <var>BD</var> token is available starting with version 3.2 of <var class="product">Fast/Unload</var>.~~ </p></li></ul></td></tr>		With strict matching, however, such a leading blank is not allowed for <var>DD</var>. A leading blank day value with a strict #function requires the <var>BD</var> token. If the data contains leading zero days in some instances and leading blanks in others, you must use a non-strict #function. </p></li>
			</ul></td></tr>

	<tr><th nowrap>Wkday, DAY Month YYYY "A"T HH:MI</th>		<tr><th nowrap>Wkday, DAY Month YYYY "A"T HH:MI</th>
Line 582:		Line 571:
	<li>If an input format contains <var>DAY</var> (for example, <var>DAY MON YY</var>) with non-strict format matching, such as with <var>#DATE2ND</var>, a matching string may have a leading zero, thus allowing <code>06 MAY 98</code>. With strict matching #functions however, such a leading zero is not allowed for <var>DAY</var>, and a single digit must be supplied for days 1 through 9. </li>		<li>If an input format contains <var>DAY</var> (for example, <var>DAY MON YY</var>) with non-strict format matching, such as with <var>#DATE2ND</var>, a matching string may have a leading zero, thus allowing <code>06 MAY 98</code>. With strict matching #functions however, such a leading zero is not allowed for <var>DAY</var>, and a single digit must be supplied for days 1 through 9. </li>

	<li>If an input format contains <var>HH</var> with non-strict format matching, such as with <var>#DATE2ND</var>, a matching string may have a leading blank, thus allowing <code>' 8:30'</code>. With strict matching, however, such a leading blank is not allowed for <var>HH</var>. A leading blank hour value with a strict #function requires the <var>BH</var> token. If the data contains leading zero hours in some instances and leading blanks in others, you must use a non-strict ~~<nowiki>~~#function~~</nowiki>. The BH token is available starting with version 3.2 of <var class="product">Fast/Unload</var>~~. </li> </ul></td></tr>		<li>If an input format contains <var>HH</var> with non-strict format matching, such as with <var>#DATE2ND</var>, a matching string may have a leading blank, thus allowing <code>' 8:30'</code>. With strict matching, however, such a leading blank is not allowed for <var>HH</var>. A leading blank hour value with a strict #function requires the <var>BH</var> token. If the data contains leading zero hours in some instances and leading blanks in others, you must use a non-strict #function. </li>
			</ul></td></tr>

	<tr><th>YYIIII</th>		<tr><th>YYIIII</th>
Line 659:		Line 649:
	<ul>		<ul>
	<li>Numeric separators, unlike alphabetic separators, do not need to be preceeded by a quotation mark character (<tt>"</tt>). </li>		<li>Numeric separators, unlike alphabetic separators, do not need to be preceeded by a quotation mark character (<tt>"</tt>). </li>

	~~<li>Numeric separators are available starting with version 3.2 of <var class="product">Fast/Unload</var>. </li>~~
	</ul></td></tr>		</ul></td></tr>
	</table>		</table>

	<~~div~~ id="dterr"></~~div~~>		==<b id="dterr"></b>Datetime error handling==
	==Datetime error handling==
	~~<!--Caution: <div> above-->~~

	Due to an invalid argument value to a datetime #function,		Due to an invalid argument value to a datetime #function,
	any of the following errors can occur:		any of the following errors can occur:

JAL: /* Datetime formats */ add link to Sirius Functions

2018-01-24T18:24:56Z

Datetime formats: add link to Sirius Functions

← Older revision		Revision as of 18:24, 24 January 2018
Line 112:		Line 112:
	<li><var class="product">[[Media:DbarNew.pdf\|SirDBA]]</var> </li>		<li><var class="product">[[Media:DbarNew.pdf\|SirDBA]]</var> </li>

	<li><var class="product">Sirius Functions</var> </li>		<li><var class="product">[[Release notes for Model 204 version 7.5#Former Sirius $functions\|Sirius Functions]]</var> </li>

	<li><var class="product">[[Media:SirfieldNew.pdf\|Sir2000 Field Migration Facility]]</var>		<li><var class="product">[[Media:SirfieldNew.pdf\|Sir2000 Field Migration Facility]]</var>

JAL: /* Valid separators */ typo

2018-01-18T23:19:43Z

Valid separators: typo

← Older revision		Revision as of 23:19, 18 January 2018
Line 342:		Line 342:
	<li>at sign (<tt>@</tt>)		<li>at sign (<tt>@</tt>)
	<li>sharp (<tt>#</tt>)		<li>sharp (<tt>#</tt>)
	<li>the decimal digits (0 - 9).		<li>the decimal digits (0 - 9)
	</ul>		</ul>
	In addition, any character may be a separator character if preceeded by		In addition, any character may be a separator character if preceeded by

JAL: misc formatting

2018-01-18T19:51:55Z

misc formatting

← Older revision		Revision as of 19:51, 18 January 2018
Line 83:		Line 83:
	Finally, there is a list of benefits of <var class="product">Fast/Unload</var> datetime processing.		Finally, there is a list of benefits of <var class="product">Fast/Unload</var> datetime processing.

	<~~div~~ id="dtfmt"></~~div~~>		==<b id="dtfmt"></b>Datetime formats==
	==Datetime formats==		The representation of a date is determined by a <b>datetime format</b>.
	~~<!--Caution: <div> above-->~~

	The representation of a date is determined by a <i>datetime format</i>.
	This value is a character string, composed of the concatenation of these:		This value is a character string, composed of the concatenation of these:
	<ul>		<ul>
Line 130:		Line 127:
	<nowiki>#functions</nowiki>.		<nowiki>#functions</nowiki>.

			===Basic rules===
	There are certain rules applied to determine if a format is valid.		There are certain rules applied to determine if a format is valid.
	The basic rules are:		The basic rules are:
Line 166:		Line 164:
	length values, then an <var>*</var> token may only appear as the last character of the format string. </li>		length values, then an <var>*</var> token may only appear as the last character of the format string. </li>

	<li>The <var>DAY</var> token may not be immediately followed by another token		<li>The <var>DAY</var> token may not be immediately followed by another token whose value may be numeric, regardless of whether the following
	whose value may be numeric, regardless of whether the following
	token represents a variable length value.		token represents a variable length value.
	Thus, <var>DAY</var> may not be followed by <var>*</var>, <var>I</var>, <var>YY</var>, <var>YYYY</var>, <var>CYY</var>, <var>MM</var>, <var>HH</var>, <var>MI</var>, <var>SS</var>,		Thus, <var>DAY</var> may not be followed by <var>*</var>, <var>I</var>, <var>YY</var>, <var>YYYY</var>, <var>CYY</var>, <var>MM</var>, <var>HH</var>, <var>MI</var>, <var>SS</var>,
	<var>X</var>, <var>XX</var>, or <var>XXX</var>; <var>DAY</var> may not be followed by a decimal digit separator,		<var>X</var>, <var>XX</var>, or <var>XXX</var>; <var>DAY</var> may not be followed by a decimal digit separator,
	and <var>DAY</var> may not be followed by a quote followed by a decimal digit. </li>		and <var>DAY</var> may not be followed by a quote followed by a decimal digit.
			<p class="note"><b>Note:</b>
			A common mistake is to use <var>MM</var> for minutes; it should be
			<var>MI</var>.</p></li>

	<li>When a pair of format strings are used for transforming date values,		<li>When a pair of format strings are used for transforming date values,
Line 200:		Line 200:
	</ol>		</ol>

	~~<p class~~=~~"note"><b>Note:</b>~~		===Valid tokens===
	~~A common mistake is to use <var>MM</var> for minutes; it should be~~
	~~<var>MI</var>.</p>~~

	The valid tokens in a date format are shown in the following list.		The valid tokens in a date format are shown in the following list.
	In general, the output format rule for a token is shown.		In general, the output format rule for a token is shown.
Line 324:		Line 321:
	</table>		</table>

			===Valid separators===
	The valid separators in a date format are:		The valid separators in a date format are:

JAL: misc cleanup

2015-09-22T18:37:40Z

misc cleanup

Show changes