by Allan Hertling SSG Group
R&D
FORTRAN 77/iX |
 |
Please make the following corrections to the FORTRAN
77/iX Reference Manual.
This manual incorrectly states that a four-digit calendar
year may be computed by adding 1900 to the YEAR parameter resulting
from a IDATE subroutine call. As
the year parameter is always in the range of 0 to 99, that calculation
will not be correct after 1999.
The last sentence describing the four-digit calculation under
the IDATE Subroutine discussion
on page B-21 should be deleted.
Business BASIC |
|
Please make the following corrections to the Business
BASIC Reference Manual.
The TIME function documentation on page 18-8 should be changed
as follows:
Under Parameters, num_expr, Three or greater:
change
"Current year" to "Years since 1900".
Under Examples, add an example of getting the current year:
160 Year2 = TIME (3) MOD 100 ! Get the current year of the century
170 Year4 = TIME (3) + 1900 ! Get the current 4-digit year |
Business BASIC/iX |
|
Please make the following corrections to the Business
BASIC/iX Reference Manual (Part # 32715-90001).
The TIME function documentation on page 5-98 should be changed
as follows:
Under Parameters, num_expr, Three or greater:
change
"Current year" to "Years since 1900".
Under Examples, lines 140 and 150:
change "the
current year" to "years since 1900".
Add an example to get the current year:
160 Year2 = TIME(3) MOD 100 ! Get the current year of the century
170 Year4 = TIME(3) + 1900 ! Get the current 4-digit year |
BASIC |
|
Please make the following corrections to the BASIC
INTERPRETER Reference Manual.
The TIM function documentation on page E-3 should be changed
as follows:
For x >= 3, change "current year (0-99)"
to "years since 1900".
Add an example of getting the current year:
150 REM -- Get the current year of the century
160 Y2 = TIM(3) MOD 100
170 REM -- Get 4-digit year
180 Y4 = TIM(3) + 1900 |
RPG/iX |
|
Please make the following changes to the RPG/iX
Reference Manual.
The following changes to the RPG/iX Reference Manual
describe the new functionality:
In the Header Specifications chapter, make the following changes
to UDATE Source (Column 17):
Add *DATE and *YEAR to the list of
predefined fields whose initial value is set by the RPGUDATE
file.
Change the second paragraph under F (Date Record)
to:
You can enter the date (in the date record) in a flexible
manner. The first number begins the date (the number does not have
to start in column 1). Enter the date as six or eight consecutive
digits (mmddyy or mmddyyyy) or in three sets of digits (mm, dd,
and yy or yyyy). Enter the month (mm),the day (dd), and then the
year (yy or yyyy).
Add the following:
If the RPGUDATE file contains
a 2-digit year, *DATE and *YEAR will contain a 4-digit year based
on a date window of 1940-2039. Thus, a yy of 39 will be taken as
2039, while a yy of 40 will be taken as 1940.
Add the following examples using 4-digit years:
04101988
FORMAT OF DATE IS MMDDYYYY = 04101988
4/10/1988
MONTH IS 4; DAY IS 10; YEAR IS 1988 |
Remove the invalid date example for 4/10/1988.
In the Output Specifications chapter, make the following changes
to Field Description Fields (Columns 32-70):
Add *DATE
and *YEAR to the section on UDATE, UDAY, UMONTH, UYEAR:
Table 9-9 DATE Field
Descriptions
| Field Name | Contents | UneditedExample | Edited Example | Description |
|---|
| *DATE | Current date with 4-digit year | 10111988 | 10/11/1988 | October 11, 1988 (Domestic Format) |
| | | 11101988 | 11/10/1988 | October 11, 1998 (United Kingdom Format) |
| | | 11101988 | 11.10.1988 | October 11, 1988 (European Format) |
| *YEAR | Current 4-digit year | 1988 | 19/88 | 1988 |
|
| |
|
 | NOTE: At the point that editing is done, there is no way for
RPG to tell that the original field was a 4-digit year and not a
truncated date. Therefore, the edited output for *YEAR
will be of the form nn/nn, as described in the documentation for
Edit Code (column 38). |
|
| |
|
In the Output Specifications chapter, make the following changes
to Edit Code (Column 38):
In the Description for the Y edit
code field, change the maximum field length to 8, and add the specification
for field lengths 7 and 8:
Slash marks can be used with fields having three to eight
digits as follows:
Table 9-10 Edit Code
Fields
| Field length | Edited output |
|---|
| 7 | nn/nn/nnn |
| 8 | nn/nn/nnnn |
