All currently supported StarQuest products, when used in accordance with associated documentation, are capable of correctly processing, providing and/or receiving all date data, if all products used with StarQuest products properly exchange accurate date data.
StarSQL
StarQuest Software, Inc. certifies that version 2.61 and above of the StarSQL suite of products, including StarSQL Enterprise Edition, StarSQL Pro and all related ancillary software, including StarScribe, StarAdmin and StarTour will successfully process dates falling on or after January 1, 2000. These products use four digit date fields where dates are used internally. StarSQL does not perform "windowing," where two digit date fields assume certain date ranges crossing the year 2000 boundary.
There are no components of the StarSQL suite that could be affected by year 2000 leap year problems. The product has been successfully tested across a wide range of dates, including February 29, 2000. Please note that while the StarSQL suite of products have been tested on client and host systems with date ranges modified to simulate a variety of year 2000 situations, StarQuest does not certify the year 2000 compliance of third party client or host based software components used with the StarSQL product suite.
Please note that while the StarSQL suite of products have been tested on client and host systems with date ranges modified to simulate a variety of year 2000 situations, StarQuest does not certify the year 2000 compliance of third party client or host based software components used with the StarSQL v2.61 product suite. StarSQL Pro Server v2.61 makes use of the Flex/LM license management product from Globetrotter software. Please see the Globetrotter web page http://www.globetrotter.com/y2000.htm.
for Globetrotter's Year 2000 compliance information.
StarPipes
StarQuest Software, Inc. certifies that version 2.11 of StarPipes for Windows NT 4.0, version 2.0 of StarPipes for AS/400, and version 1.95 of StarPipes on UNIX OS will successfully process dates falling on or after January 1, 2000. These products use four digit date fields where dates are used internally. StarPipes does not perform "windowing", where two digit date fields assume certain date ranges crossing the year 2000 boundary.
There are no components of StarPipes that could be affected by year 2000 leap year problems. The product has been successfully tested across a wide range of dates, including February 29, 2000. Please note that while the StarPipes product has been tested on client and host systems with date ranges modified to simulate a variety of year 2000 situations, StarQuest does not certify the year 2000 compliance of third party clients or AS/400 host based software components used with the StarPipes product. StarPipes on UNIX OS makes use of the Flex/LM license management product from Globetrotter software. Please see the Globetrotter web page http://www.globetrotter.com/y2000.htm for Globetrotter’s Year 2000 compliance information.
StarQuest Data Replicator
StarQuest Software, Inc. certifies that StarQuest Data Replicator (SQDR), version 1.5, will not be adversely affected by dates falling on or after January 1, 2000. SQDR uses four digit date fields where dates are used internally.
Although there are no components of SQDR that could be affected by year 2000 leap year problems the product has been successfully tested across a wide range of dates, including February 29th, 2000. Please note that while SQDR has been rigorously tested on client and host systems with date ranges modified to simulate a variety of year 2000 situations, StarQuest can not certify the year 2000 compliance of third party client or host based software components used with the SQDR product.
Client Access for UNIX OS
StarQuest Software, Inc. certifies that version 1.04 (Service Pack 1.0) of Client Access for UNIX OS will successfully process dates falling on or after January 1, 2000. This product uses four digit date fields where dates are used internally. Client Access for UNIX OS does not perform "windowing", where two digit date fields assume certain date ranges crossing the year 2000 boundary.
There are no components of Client Access for UNIX OS that could be affected by year 2000 leap year problems. The product has been successfully tested across a wide range of dates, including February 29, 2000. Please note that while the Client Access for UNIX OS product has been tested on client and host systems with date ranges modified to simulate a variety of year 2000 situations, StarQuest does not certify the year 2000 compliance of third party clients or AS/400 host based software components used with the Client Access for UNIX OS product.
There is a known limitation that dates and timestamps in the transferred files outside the range 1939 < x < 2040 will not be transferred by cash or caftp. To resolve the problem, you must apply a patch. This patch is available at ../Supportdocs/techdocs/cash_datefix.html. This fix has been rolled into version 1.0.4.1 eliminating the need for the patch.
StarTools
StarQuest discontinued support of its StarTools product in 1998 and has no plans to test it for Y2K compliance. If your organization is still using StarTools, StarQuest recommends that you upgrade to Client Access for UNIX OS (CA-UNIX) and retest your applications as part of your Y2K preparations.
CA-UNIX is fully Y2K compliant. Jointly developed by IBM and StarQuest Software, CA-UNIX is built on the same technology base as many of other IBM Client Access products--a member of the IBM Client Access Extended Family. This ensures optimum compatibility and performance with your AS/400 systems. CA-UNIX takes full advantage of IBM's Client Access API libraries to enable delivery of a feature-rich UNIX-to-AS/400 connectivity solution with unsurpassed high-performance.
Site Search | Products | Contact Sales | Home