APPDATE command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
 
No edit summary
 
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
The APPDATE command allows you to control the operation of date and time
<p class="note"><b>Note:</b> This is a <var class="product">[[Sirius Mods]]</var>-only command prior to Version 7.5 of <var class="product">[[Model 204]]</var>. This command will perform no useful processing unless a site is authorized for the <var class="product">[[Sir2000 User Language Tools]]</var>. </p>
oriented User Language $functions, in the following two ways:
 
The <var>APPDATE</var> command allows you to control the operation of date and time
oriented <var class="product">User Language</var> [[SOUL_$functions|$functions]], in the following two ways:
<ol>
<ol>
<li>You can specify a system-wide or user-level
<li>You can specify a system-wide or user-level
clock that is used to obtain date and time values for User Language
clock that is used to obtain date and time values for User Language
$functions.
$functions.
For application testing, this is preferred to the [[Model 204]] SYSDATE
For application testing, this is preferred to the Model&nbsp;204 <var>[[SYSDATE parameter|SYSDATE]]</var> parameter, which is much less flexible and which
parameter, which is much less flexible and which
greatly complicates the ability to do things such as share procedure
greatly complicates the ability to do things such as share procedure
files or read-only data files in the testing environment.
files or read-only data files in the testing environment.
<p>
The <var>APPDATE</var> command affects only date and time oriented User Language $functions; it does not affect any other date or time in the <var class="product">Model 204</var> environment. </p></li>


The APPDATE command affects only date and time oriented User Language
<li>You can use the <var>DATE_ERR</var> clause to
$functions; it does not affect any other date or time in the ''Model 204''
set switches that control the default system behavior when errors are
environment.
encountered in date and time oriented <var class="product">User Language</var> $functions.
<li>You can use the DATE_ERR clause to
set switches that control the default system behaviour when errors are
encountered in date and time oriented User Language $functions.
The choices are to produce an error message along with request
The choices are to produce an error message along with request
cancellation, produce a warning message, or silently continue with
cancellation, produce a warning message, or silently continue with
the request.
the request.
This control is available at the system and user level, and can also
<p>
be set for the duration of a User Language request, via the $SIR_DATE_ERR
This control is available at the system and user level, and you can also
function.
set it for the duration of a User Language request by using the <var>$Sir_Date_Err</var> function. At the system and user level, you can also control whether procedure names and line numbers are available for error messages. </p></li>
At the system and user level, you can also control whether procedure
names and line numbers are available for error messages.
</ol>
</ol>


This command will perform no useful processing unless a site is authorized
==See also==
for the [[Sir2000 User Language Tools]].
[[The Sir2000 APPDATE command]] has detailed information about the <var>APPDATE</var> command.
The APPDATE command has an extensive set of parameters and is more
completely documented in the [[Sir2000 User Language Tools Reference Manual]].


[[Category: User commands]]
[[Category: User commands]]
[[Category: Commands]]
[[Category: Commands]]

Latest revision as of 14:21, 6 February 2019

Note: This is a Sirius Mods-only command prior to Version 7.5 of Model 204. This command will perform no useful processing unless a site is authorized for the Sir2000 User Language Tools.

The APPDATE command allows you to control the operation of date and time oriented User Language $functions, in the following two ways:

  1. You can specify a system-wide or user-level clock that is used to obtain date and time values for User Language $functions. For application testing, this is preferred to the Model 204 SYSDATE parameter, which is much less flexible and which greatly complicates the ability to do things such as share procedure files or read-only data files in the testing environment.

    The APPDATE command affects only date and time oriented User Language $functions; it does not affect any other date or time in the Model 204 environment.

  2. You can use the DATE_ERR clause to set switches that control the default system behavior when errors are encountered in date and time oriented User Language $functions. The choices are to produce an error message along with request cancellation, produce a warning message, or silently continue with the request.

    This control is available at the system and user level, and you can also set it for the duration of a User Language request by using the $Sir_Date_Err function. At the system and user level, you can also control whether procedure names and line numbers are available for error messages.

See also

The Sir2000 APPDATE command has detailed information about the APPDATE command.