[SUGBU-L] Gov: Malacanang alerts computer users programmers
Sugbu-L
Newsgroup: alt.language.cebuano
--------------------------------------------------------
Malacanang alerts computer users programmers on Y2K problem dates'
MANILA, Feb. 13 (PNA) - -There are at least 37 dates before and
after Jan. 1, 2000 that computer users and programmers have to watch out
for, according to the Presidential Commission on Year 2000 Compliance.
In a message posted on its Internet site, the Y2K Commission
pointed out that these dates would have different effects on different
computer systems and chips.
Because of this, the Commission said, "testing should include a
number of critical dates to ensure compliance, so that no problems occur
prior to, on, or after January 1, 2000."
"The algorithms of systems and chips need to be tested for forward
and backward processing (although) not all systems need to test for all
dates listed," it added.
According to the Y2K Commission, the 37 dates range from April 9
this year to as far as Feb. 28 in the year 2100.
"Different application domains may have specially significant dates
like the fiscal year for business systems. It is up to the program
managers to determine which are most likely to impact their systems," it
said.
The most critical dates that should be considered for testing at
this phase, according to the Y2K commission, include:
* April 9, 1999, where a system looking for Short Julian days might
stop since this is day 99 of year 99 (9999).
* Aug. 21, 1999, which may affect Global Positioning System (GSP)
equipment. GSP receives use a 10-bit field for weeks since January 5,
1980. To get the current date, they compute the days from the base and
divide successively to get the increments for year, month, and day.
Given the limit of 1024 weeks, input values at receives using the 1980
base date will roll over at midnight on August 21, 1999.
* Aug. 22, 1999: Overflow of week counter for equipment such as GSP
receives. Unadjusted GPS would assume the date as Jan. 5, 1980.
* Sept. 9, 1999 (9/9/99 or Possibly 9999), which may trigger a red
flag, resulting in erroneous branching or otherwise cause a processing
error.
* Sept. 23, 1999, which marks 99 days to Year 2000.
* Dec. 1, 1999, the first monthly plan to look ahead past rollover
date.
* Dec. 31, 1999, the last day before two-digit year equals 00. Many
systems will not operate correctly as they transition to the next
day,Also, sometimes used as "Never Expires" date.
* Jan. 0, 2000, which may appear in some spreadsheets and database
applications.
* Jan. 1, 2000, a key date in any compliance testing. The first
possible weekend day may be mistaken for a weekday.
* Jan 3, 2000, the first full business day in the year 2000 - and
the possible payday after rollover.
* Jan. 6, 2000, the first possible weekday mistaken for weekend
day.
* Jan 7, 2000, the first weekly payday.
* Jan 10, 2000, where some computers may register the first seven
character date in M/DD/YYYY or format (1/10/2000).
* Jan. 14, 2000, the first semi-monthly payday.
* Jan. 31, 2000, the first monthly close and first monthly payday.
* Feb. 28, 2000- Many programmers have incorrectly been taught that
the year 2000 is not a leap year so systems should be tested to ensure
correct handling of the transition to the 29th day of February 2000.
* Feb. 29, 2000 - Some systems may transition to the 29th of
February 2000 correctly, but may not allow the date to be set to the
29th.This would happen if a system was reinitialized after the
transition and should be explicitly tested for.
* Feb. 30 and 31, 2000 - may appear in some PC applications.
* March 1, 2000 - to ensure date calculations have taken leap year
into account.
* March 31, 2000 - first quarterly close.
* April 3, 2000 - first business day after quarter ends Friday,
March 31, 2000.
* Oct. 10, 2000 - first eight-character date using a two-digit
month (10/10/2000).
* Oct. 28, 2000 - Possible false change back to Standard Time
(October 28 was last Sunday in October 1900).
* Dec. 29, 2000 - first yearly close.
* Dec. 31, 2000 - 366th day of the year 2000, which could be a
problem for systems that use Short Julian days.
* Jan. 1, 2001 - First day in he 21st century and the last leap
year-related date, requiring testing of the first day of January 2001 to
ensure it can be set.
* Feb. 29, 2001 - some computers may process this date as a leap
year.
* Sept. 9, 2001 - A UNIX date when the "time -T"value goes from 9
to 10 digits. Suspects are time stamps stored in fixed-column tables
and internal variables.
* June 30, 2002 -last day European national currencies are
acceptable.
* July 1, 2002 - First day Euro-only transactions in the Economic
and Monetary Union (EMU).
* Feb. 29, 2004 - To ensure that this date is processed as a leap
year.
* Jan. 1, 2037 - Rollover date for NTP systems.
* Jan. 19, 2038 - Overflow of UNIX systems.
* Sept. 18, 2042 - Overflow of IBM system/360/
* Sometime in 2072 - overflow of Milstar Operating System.
* Feb. 28, 2100-Last Day of February and not a leap year.
(PNA) rgc/OPS/ aav
PNA 02131609
Todays SUGBU-L is sponsored by: The Ancestor's Pension House
Cebu's Finest (http://www.angelfire.com/biz/cebu/index.html)
-------------------------------------------------------------------
This is the SUGBU-L list operated by Bayanihan
-------------------------------------------------------------------
To unsubscribe, send a message without the quotes to:
"SIGNOFF SUGBU-L" to LIST...@HOME.EASE.LSOFT.COM (not to the list)
Any problems contact: sup...@lists.brifil.org.uk