Program Name | Vendor | URL |
Compliant?
|
Contact Person |
Complete? |
---|---|---|---|---|---|
MATH/ ENGINEERING/ SCIENCES |
|||||
ESSL, Ver 2.2 (m) |
IBM | IBM's Readiness Report for ESSL | Version 2.2.2 yes | e-mail to IBM | Yes |
Fidap (m, g, j) |
Fluent Inc. | www.fluent.com /software/FIDAP.htm (Home Page) |
In process | No | |
Gaussian 94 (m) |
Gaussian Inc. | y2k.policyworks.gov/... | Yes | . | Yes |
IMSL (s, m, g) |
Visual Numerics | www.vni.com/books/ newdir/nextm.html |
Yes, but see Contact Person |
e-mail to IMSL |
Yes |
LibSci (j) |
Cray Research | www.cray.com/products/year2000 (Year 2000 Web page only) |
Yes | Yes | |
Lindo (s) |
Lindo Systems Inc. | www.lindo.com/twoth.html (Year 2000 Web page) |
Yes | Mark Wiley | Yes |
Macsyma (s) |
Macsyma Inc. | www.macsyma.com (No 2000 info here yet) |
Yes | Sharon Cassavant | Yes |
Maple 5 (s) |
Waterloo Maple, Inc. | www.maplesoft.com/faq1.html#q29 |
Yes | . | Yes |
Mathematica (s) |
Wolfram | www.wolfram.com/support /Systems/All/Year2000.html |
Yes | Tech Support | Yes |
Matlab (s) |
MathWorks | www.mathworks.com/support/ solutions/v4/7405.html |
Yes | . | Yes |
NAG (s) |
NAG | extweb.nag.co.uk/other/ Year2000.html |
In process. At the latest the next release will be y2000 compliant |
. | No |
Nastran (s) |
MacNeal Schwendler Corp. | www.macsch.com/msc/ press_releases/jun0397a.html |
Yes | . | Yes |
SgiMath (g) |
Silicon Graphics | www.sgi.com/ Technology/year2000/ (Year 2000 Web Page Only) |
No | ||
STATISTICS | |||||
BMDP (s) |
SPSS | www.spss.com/cool/papers/ sci2000.htm (see "Conclusion") |
No | . | Yes |
ITEMAL (s) |
U of D | Yes | . | Yes | |
LIMDEP (s) |
Economic Software Inc | y2k.policyworks.gov/.... | Yes | . | Yes |
LISREL (s) |
SSI | www.ssicentral.com/home.htm (SSI Home Page) |
Yes, but see e-mail response. |
No | |
Minitab (s) |
Minitab, Inc. | www.minitab.com/tech/mt48.htm | Yes (see Web page and contact) |
Tel. inquiry |
Yes |
PRELIS (s) |
SSI | www.ssicentral.com/home.htm (SSI Home Page) |
Yes, but see e-mail response. |
No | |
SAS (s) |
SAS | www.sas.com www.sas.com/software/year2000 |
Yes | . | Yes |
S-Plus Version 3.3 (s) |
MathSoft | www.mathsoft.com/press/ y2k/splus.html |
Yes for the internal computations but no for the print methods (See the Web page for details) |
. | Yes |
SPSS (s) |
SPSS | y2k.policyworks.gov/... |
Yes | . | Yes |
GEOGRAPHIC INFO SYSTEMS | |||||
Arc/Info 7.1.1 (s) |
ESRI | y2k.policyworks.gov/srch.... | Yes for for Ver. 7.1 |
. | Yes |
ArcView 3.0 A (s) |
ESRI | y2k.po licyworks.gov/srch.... | Yes for Ver. 3.0 |
. | Yes |
Grass (s) |
www.cecer.army.mil/grass/ faqtxt1.html#mm |
Yes | Yes | ||
GRAPHICS | |||||
DI3000 (s) |
VNI | Yes, but see e-mail | Yes | ||
graphPHIGS (s) |
Sun Microsystems | www.sun.com/y2000/cpl.html | Yes | . | Yes |
Meta File System (s) |
. | No | |||
NCAR (s) |
NCAR/SCD | ngwww.ucar.edu www.sc.ucar.edu/ngg/ 2 Home Pages? |
Yes | Yes | |
PV-Wave Advantage (s) |
Visual Numerics | WWW.VNI.COM/produc
ts/ millennium_not.html |
Yes | Yes | |
Xfig (s) |
SGI (freeware) | www.sgi.com/TasteOfDT/ public/freeware1.0/fw_xfig.xfig.html (Release Notes) |
Yes | Yes | |
xv (s) |
John Bradley | www.chest.ac.uk/software/ xv/overview.html#TofC10 |
Yes | . | Yes |
COMPILERS | |||||
AcuCobol | AcuCobol | www.acucobol.com/Services /year2000.html | Yes for ver. 2.3 We have ver. 2.1.1 |
e-mail sent |
No |
Cray C | Cray Research | www.cray.com/produc
ts/software/year2000 (Year 2000 Web page) |
A qualified "Yes" (see comments). | Cray states no major Year 2000 bugs found. Compiler will be retired prior to year 2000. See URL for details. | Yes |
Cray C++ | Cray Research | www.cray.com/produc
ts/software/year2000 (Year 2000 Web page) |
A qualified "Yes" (see comments). | Targeted release date for Year 2000 compliant product is April 1998 | No |
Cray Fortran 77 | Cray Research | www.cray.com/produc
ts/software/year2000 (Year 2000 Web page) |
A qualified "Yes" (see comments). | Cray states no major Year 2000 bugs found. Compiler will be retired prior to year 2000. See URL for details. | Yes |
Cray Fortran 90 | Cray Research | www.cray.com/produc
ts/software/year2000 (Year 2000 Web page) |
A qualified "Yes" (see comments). | Targeted release date for Year 2000 compliant product is April 1998 | No |
Sun Workshop for Ada | Sun | www.sun.com/Y2000/cpl.html | Unknown | No | |
Sun Workshop Compilers C | Sun | www.sun.com/Y2000/cpl.html td> | Yes | . | Yes |
Sun Workshop Compilers C++ | Sun | www.sun.com/Y2000/cpl.html | Yes | . | Yes |
Sun Workshop Compilers Fortran | Sun | www.sun.com/Y2000/cpl.html | No (See Note) |
Note | No |
Sun Workshop Compilers Pascal |
Sun | www.sun.com/Y2000/cpl.html (No entry..see e-mail) |
In process | No | |
Scheme - scm (s) |
MIT | See e-mail | No |
Tech Support says the program is year 2000 compliant. This info is also on their web page.
February 1, 1998: Talked to Mark Wiley, Tech support, 312-998-9421. Year 2000 compliance for Lindo is not really a relevant problem because there are no commands that process date info in the program. So, by default it is year 2000 compliant.
Feb 1, 1998: Talked to Sharon Cassavant, Adm. Supervisor, who said that Macsyma is year 2000 compliant. This info will be posted on their web page within the next thirty days.
Contact unnecessary (see URL)
Feb 3, 1998: E-mail response: January 30, 1998 To Whom It May Concern: We are currently reviewing all our products for Year 2000 compliance. The impact of Year 2000 issues on our products is minimal and it is our plan that the next release of our products will be certified to be Year 2000 compliant. We anticipate that new releases of all of our products will be available by the end of 1998. Please do not hesitate to contact us if you need any further information. Sincerely, Michael S. Engelman Corporate Vice President ----- Jan 29, 1998: E-mail sent asking which versions of Fidap are Year 2000 compliant and what is the definition of compliance they are going by.
----- Date: Wed, 23 Dec 1998 13:01:12 -0600 From: Trudi SchweizerTo: "'jack@udel.edu'" Subject: FW: Y2k Info at http://www.vni.com/products/y2k. Here are answers to your year 2000 questions, forwarded to me from Nancy Meneely: 1. According to the Web page at the addressing the subject, IMSL Fortran Numerical Libraries, version 3.0, 3.01 and IMSL Fortran 90 MP Library, Version 3.0, 3.01 have been tested for Year 2000 compliance. Does this implicitly mean that they also passed the test (with the exception of the required patch for TDATE)? yes 2. We are running IMSL version 3.0. Therefore, once the TDATE patch is installed, this product will be y2k compliant. Is this correct? yes 3. We are running IMSL version 1.0 of the Fortran 90 MP Library. Your Web info specifies versions 3.0,3.01. What about version 1.0? We have not tested any versions of the Fortran 90 MP library prior to 3.0 for year 2000 compliance. Trudi Schweizer Visual Numerics, Inc. - Technical Support tschweizer@houston.vni.com VNI Technical Support email: support@houston.vni.com VNI Web site: www.vni.com ----------------- Date: Mon, 16 Mar 1998 13:36:07 -0600 From: Trudi Schweizer To: "'jack@udel.edu'" Subject: FW: Y2K We have no record of a previous request for this information so apparently we did not receive your first email. Version 3.0 of our Fortran Numerical Libraries are year 2000 compliant. Trudi Schweizer Visual Numerics, Inc. - Technical Support tschweizer@houston.vni.com VNI Technical Support email: support@houston.vni.com VNI Web site: www.vni.com -------------- E-Mail sent to IMSL (didn't respond to letter below) - 03/16/1998 Date: Mon, 16 Mar 1998 14:22:29 -0500 (EST) From: Jack Seltzer To: support@boulder.vni.com Cc: Jack Seltzer To Whom It May Concern, Below is a copy of mail I sent over a month ago but have not received a reply. Jack Seltzer >Date: Mon, 12 Jan 1998 15:12:27 -0500M >From: Jack Seltzer
>To: support@boulder.vni.com, jack@udel.edu >Subject: Year 2000 Compliance for IMSL > >According to the information on year 2000 compliance presented >at > > http://WWW.VNI.COM/products/millennium_not.html > >the IMSL librares are year 2000 compliant as long as the user >uses 4 digit dates in his calling programs. I looked at some >of the date programs in the MATH library and I found that the >user is pretty much constrained to user 4 digit dates, which >is fine, of course (at least for the routines I looked at: >ndays,idywk).> >Am I correct then in assuming that there are no calls in any of >the routines to any system routines which call date routines (e.g., >getdate) which could lead to problems? > >This being the case, the MATH and STAT libraries are 100% year 2000 >compliant. Correct? > > Thanks in advance, > > Jack Seltzer ----- --------- E-mail sent to IMSL for cohfirmation: Date: Mon, 12 Jan 1998 15:12:27 -0500M From: Jack Seltzer
To: support@boulder.vni.com, jack@udel.edu Subject: Year 2000 Compliance for IMSL According to the information on year 2000 compliance presented at http://WWW.VNI.COM/products/millennium_not.html the IMSL librares are year 2000 compliant as long as the user uses 4 digit dates in his calling programs. I looked at some of the date programs in the MATH library and I found that the user is pretty much constrained to user 4 digit dates, which is fine, of course (at least for the routines I looked at: ndays,idywk).Am I correct then in assuming that there are no calls in any of the routines to any system routines which call date routines (e.g., getdate) which could lead to problems? This being the case, the MATH and STAT libraries are 100% year 2000 compliant. Correct? Thanks in advance, Jack Seltzer User Services University of Delaware
NAG Contact
ESSL Contact
Feb 4 Our Version on Mozart is Version 2.2 (greback) Date: Wed, 4 Feb 1998 14:36:36 -0500 (EST) From: Dave GrebackTo: Jack Seltzer Cc: Requests , Jack Seltzer , Dick Sacher Subject: Re: Version of ESSL on Mozart We are running Version 2.2 of ESSL (rest of mail deleted - cc of my mail to Dave) David J. Greback vette@udel.edu University of Delaware (302)831-1129 Systems Programmer II IT/Network and Systems Services Feb 3, 1998: Mail via report request at wwwyr2k.raleigh.ibm.com. (click on "Generate a Software Report, select "Create a new session" and select the start button. Next select "risc" and "aix", type in "essl" and select the "perform search" button. From yr2krept@wwwyr2k.raleigh.ibm.com Tue Feb 3 16:29 EST 1998 Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by zebra.us.udel.edu (8.8.7/8.8.7) with ESMTP id QAA10633 for ; Tue, 3 Feb 1998 16:29:10 -0500 (EST) Received: from wwwyr2k.raleigh.ibm.com (wwwyr2k.raleigh.ibm.com [204.146.167.68]) by copland.udel.edu (8.8.8/8.8.8) with ESMTP id QAA28205 for ; Tue, 3 Feb 1998 16:28:33 -0500 (EST) Received: (from yr2krept@localhost) by wwwyr2k.raleigh.ibm.com (AIX4.2/UCB 8.7/8.7) id QAA44826 for jack@udel.edu; Tue, 3 Feb 1998 16:25:55 -0500 (EST) From: yr2krept@wwwyr2k.raleigh.ibm.com Date: Tue, 3 Feb 1998 16:25:55 -0500 (EST) Message-Id: <199802032125.QAA44826@wwwyr2k.raleigh.ibm.com> Content-Type: text Content-Length: 9521 Status: RO X-Status: February 3, 1998 SESSION NAME: ESSL0002 ESSL Status PRODUCT READINESS REPORT IBM is pleased to provide you with the following Year 2000 product readiness report. We believe the report will be helpful in guiding your efforts to become Year 2000 ready. IBM has taken reasonable measures to provide accurate information regarding the readiness of our products. However, you should be aware that information regarding Year 2000 can change rapidly. IBM cannot guarantee that the information contained in this report is complete, current or applies in every situation. For questions about information contained in this report or other products not listed in it, please contact your IBM representative or the Year 2000 Technical Support Center at www.software.ibm.com/year2000 (click on the "feedback" icon). PRODUCT: 5621060 AIX ESSL/6000 V1 RISC AIX LATEST REL: 1 READINESS: not ready DATE: N/A REPLACEMENT PRODUCT: 5765042 PRODUCT: 5668863 ESSL SCALAR/370 VECTOR RISC MULTI/S LATEST REL: 1.4 READINESS: Year 2000 Ready DATE: REPLACEMENT PRODUCT: 5688226 PRODUCT: 5688226 ESSL/370 VECTOR MULTI XPLAT LATEST REL: 2.2 READINESS: Year 2000 Ready DATE: =<1996 PRODUCT: 5765042 ESSL/6000 V2 RISC AIX LATEST REL: 2.2.2 READINESS: Year 2000 Ready DATE: =<1996 PRODUCT: 5765422 PARALLEL ESSL V1 FOR AIX V4 RISC AIX LATEST REL: 1.2.0 READINESS: Year 2000 Ready DATE: =<1996 PRODUCT: 5765645 ESSL PARALLEL V1 RISC AIX LATEST REL: 1.1.0 READINESS: Year 2000 Ready DATE: =<1996 REPLACEMENT PRODUCT: 5765422 PRODUCT: 5799FLJ ESSL/6000 V2.2 RISC AIX LATEST REL: N/A READINESS: Year 2000 Ready DATE: N/A To help you understand the terms used in this report, please review the "report definition" document which can be found in the product readiness web pages (link from www.ibm.com/ibm/year2000). For additional assistance please contact your IBM representative or the Year 2000 Technical Support Center at www.software.ibm.com/year2000. Year 2000 Ready Definition : IBM uses the term "Year 2000 ready" to refer to products that will function correctly into the 21st century. Specifically, "Year 2000 ready" means that "a product, when used in accordance with its associated documentation, is capable of correctly processing, providing and/or receiving date data within and between the 20th and 21st centuries, provided that all products (for example, hardware, software and firmware) used with the product properly exchange accurate date data with it." IBM considers products not ready for Year 2000 if they don't meet the definition set out above, or if they have not been tested. Products not affected by the Year 2000, such as hardware frames, keyboards, power supplies, and hardware or software product publications are considered ready. IBM Position on the Readiness of its Products: For general overview of the ready status of IBM products, please visit the IBM Year 2000 web site at www.ibm.com/year2000. Software Provided with IBM Products: Information referring to the Year 2000 ready status of IBM hardware products refers to hardware only and not to software that may be pre-installed or otherwise provided by IBM with the purchase of IBM hardware. Information on the Year 2000 ready status of IBM software applies to IBM products only. It does not apply to any "as is" or non-IBM software that may be provided along with IBM software products. For non-IBM products, whether or not obtained from IBM, please consult directly with the third party product developer for information about whether the products are Year 2000 ready. In some cases IBM may pass along information that third parties have provided us about the status of their products. However, IBM is not in a position to independently verify, or accept any responsibility for, the accuracy or completeness of such information. Other Important Information: IBM is providing this information to assist you in understanding and addressing your Year 2000 challenge. By providing this data, IBM is not performing a Year 2000 assessment or conversion. You are solely responsible for the implementation of your Year 2000 project and IBM does not guarantee your results. IBM may not offer the products, services and/or features discussed in this document in all countries. Consult with your IBM representative for information on the products available in your area. Any reference to an IBM product is not intended to imply that only that IBM product may be used. The information in this report could contain technical inaccuracies or typographical errors, and is subject to change without notice. You are solely responsible for the installation and implementation of any Product Temporary Fix, Customer Service Diskette(s) or other related Year 2000 modification required for an IBM product to be considered Year 2000 Ready. IBM shall not in any way be responsible for your failure to apply such correction. THE DATA IN THIS REPORT OR RELATED COMMUNICATIONS IS PROVIDED ON AN "AS IS" BASIS FOR INFORMATION PURPOSES ONLY. IN ADDITION, ALL WARRANTIES ARE HEREBY EXPRESSLY DISCLAIMED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IBM's obligations and responsibilities regarding IBM products are governed solely by the agreements under which they are sold or licensed. Always check your software license agreements to make sure that you do not infringe the intellectual property rights of others. You must have the consent of the licensor or owner of the software before accessing or modifying it. End of Report ------ E-mail sent to IBM to verify that Version 2.2 of ESSL is compliant as reported on the y2k.policyworks.gov web page. Mail asked:
According to an entry in the Year 2000 COTS Product Database (http://y2k.policyworks.gov/srch/y2kretr2.cfm?product=1118),Version 2.2 of ESSL is Year 2000compliant. I have not been able to verify this through your web site.Questions:
. Is IBM's ESSL Version 2.2 Year 2000 compliant?
. Where can I find this confirmation in your web pages?
. What is the definition of compliant that IBM is using and specifically, what does this mean in terms of the range of years? (e.g., Sun defines compliant to include that computations are valid over the range 1970 to 2038.IBM's E-mail Response:
From d03nm024@us.ibm.com Tue Jan 13 17:49 EST 1998 Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by zebra.us.udel.edu (8.8.7/8.8.7) with ESMTP id RAA13459 for; Tue, 13 Jan 1998 17:49:50 -0500 (EST) Received: from smtp4.ny.us.ibm.COM (smtp4.ny.us.ibm.com [198.133.22.43]) by copland.udel.edu (8.8.8/8.8.8) with ESMTP id RAA05391 for ; Tue, 13 Jan 1998 17:49:47 -0500 (EST) Received: from relay2.server.ibm.com (relay2.server.ibm.com [9.14.2.99]) by smtp4.ny.us.ibm.COM (8.8.7/8.8.7) with ESMTP id RAA15782 for ; Tue, 13 Jan 1998 17:50:04 -0500 Received: from US.IBM.COM (d03lms01.boulder.ibm.com [9.99.80.11]) by relay2.server.ibm.com (8.8.7/8.7) with SMTP id RAA38728 for ; Tue, 13 Jan 1998 17:47:15 -0500 Received: by US.IBM.COM (Soft-Switch LMS 2.0) with snapi via D03AU005 id 5030100016118872; Tue, 13 Jan 1998 17:49:18 -0500 From: D03NM024/03/M/IBM To: Subject: IBM Year 2000 Technical Support Center - North America Message-ID: <5030100016118872000002L022*@MHS> Date: Tue, 13 Jan 1998 17:49:18 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by zebra.us.udel.edu id RAA13459 Content-Type: text/plain; charset=iso-8859-1 Content-Length: 5238 Status: RO X-Status: Below is the response to the question that you sent to the Year 2000 Technical Support Center. In response to your E-mail, we at the IBM Technical Support Center would like to know how we're doing. Please help us to serve you better by letting us know and send your response back to y2ktsc@us.ibm.com. Thank you ____1 Excellent ____2. Very Good ____3. Good ____4. Poor ____5. Very Poor Comments: ================================================================================ ******************************************************************************** REPLY : Jack. ESSL V2.2, 5799FLJ, is year 2000 ready. The product is in our readiness database at URL: http://wwwyr2k.raleigh.ibm.com Some information is missing in the record for this product and we cannot send you a readiness report right now. As soon as all the necessary information becomes available, we will send you a report for this product. We are putting your record on HOLD status until the product record is updated. Following is IBM's definition of year 2000 ready. This definition is contained within reports generated from the Product Readiness Database. "Year 2000 Ready Definition : IBM uses the term "Year 2000 ready" to refer to products that will function correctly into the 21st century. Specifically, "Year 2000 ready" means that "a product, when used in accordance with its associated documentation, is capable of correctly processing, providing and/or receiving date data within and between the 20th and 21st centuries, provided that all products (for example, hardware, software and firmware) used with the product properly exchange accurate date data with it." IBM considers products not ready for Year 2000 if they don't meet the definition set out above, or if they have not been tested. Products not affected by the Year 2000, such as hardware frames, keyboards, power supplies, and hardware or software product publications are considered ready." IBMs preferred method of implementing changes for year 2000 is field expansion, i.e., 2 digit year to 4 digit year. Some products, however, may have used a fixed or sliding window to achieve year 2000 readiness. Our readiness reports may include this information. Also, you may contact IBM service and support (1-800-237-5511) and speak to the individual product areas for that information. ******************************************************************************** Y2K QUESTION: Please respond to nobody@col-sp7.www.ibm.com @ internet To: Project Y2KTSC/Santa Teresa/IBM@IBMUS cc: Subject: Via WWW-Mail gateway at Remote host: [128.175.8.38] Mailed to: y2ktsc@us.ibm.com Full name: Jack Seltzer Really from: jack@udel.edu Comments: Phone Number: 302-831-1986 Company or Organization:User Services/University of Delaware Question or Comment:According to an entry in the Year 2000 COTS Product Datavbase (http://y2k.policyworks.gov/srch/y2kretr2.cfm?product 1118), Version 2.2 of ESSL is Year 2000 compliant. I have not been able to verify this through your web site. Questions: . Is IBM's ESSL, v2.2 for the RS/6000 year 2000 compliant? . Where can I find this confirmation in your web pages? . What is the definition of compliant that IBM is using and, specifically, . what does this mean in terms of the range of years? (e.g., Sun defines compliant to include that computations are valid over the (approx) span 1970 to 2038) Jack Seltzer User Services University of Delaware : HTTP-Referer: http://www.software.ibm.com/year2000/sendgtsc.html Browser: Mozilla/4.03 [en] (Win95; I) -- This mail delivered courtesy of webmaster@www.ibm.com ******************************************************************************** Year 2000 Ready A product is Year 2000 ready if the product, when used in accordance with its associated documentation, is capable of correctly processing, providing and/or receiving date data within and between the 20th and 21st centuries, provided all other products (e.g. software, hardware and firmware) used with the product properly exchange date data with it IBM is providing information in this document to assist you in understanding and addressing your Year2000 challenge. IBM does not guarantee your results. You are solely responsible for implementation of your Year2000 project. With respect to software distributed with IBM PCs, it is the responsibility of the software manufacturer or developer to address their specific implementation of the Year 2000 transition. IBM makes no representation or warranty regarding software provided with IBM PCs, including whether or how it might implement the year 2000 transition. You may contact the IBM Year 2000 Technical Support Centers as follows: NORTH AMERICA Y2KTSC@VNET.IBM.COM AS/400 Y2KTSC4@VNET.IBM.COM ASIA and PACIFIC Y2KTSCAP@VNET.IBM.COM LATIN AMERICA Y2KTSCLA@VNET.IBM.COM EUROPE, MIDDLE EAST, AFRICA Y2KTSCE@IE.IBM.COM For more information on Visual Age 2000 product solution offering, go to the following web site: www.software.ibm.com/ad/va2000
SgiMath Contact
Date: Mon, 16 Mar 1998 15:42:05 -0500 From: Jack SeltzerTo: asnell@engr.sgi.com, jack@udel.edu Subject: Library "sgimath" - Year 2000 Compliant? Dear Addison, Is the library, sgimath, available on our Power Challenge at the University of Delaware, y2k compliant? I've looked at the SGI Web pages, but there is no information on this product. Jack Seltzer University of Delaware User Services 302-831-1986
LibSci Contact
(following was faxed to Lindy Brown at SGI on january 12. It included a copy of the mail received from Bruce Schneider that follows). Dear Lindy, In March, 1988 Bruce Schneider (then, Product Marketing Mangager, Operating Systems with Cray) told me that the libsci library (which we have installed on our J90) was year 2000 compliant (see his note below) and that this info would be added to the (then) Cray Year 2000 Web pages. I have searched the SGI/Cray web pages recently and didn't find any such info. This is a request to add this information. We need this information for our y2k web page dealing with vendors of application software that the university uses (http://www. udel.edu/topics/software/general/y2k/vendorspublic.html) Thanks, Jack Seltzer User Services ----------------- Date: Mon, 2 Mar 1998 15:54:27 -0600 From: Bruce SchneiderTo: jack@udel.edu Subject: Cray Year 2000 compliance Mr. Seltzer, The libsci library is year 2000 compliant. We will be updating our Web site to list specific products, including libsci, over the next month as we gather this information. Your request, along with others have indicated the need for more specific information than what is currently available on the Web page. We plan on providing this additional level of detail. Thank you for your inquiry. Please periodically check out the Cray Web page at http://www.cray.com/products/software/year2000 for additional detailed information. Best Regards, Bruce Schneider Product Marketing Manager, Operating Systems 612-683-5365 >What is the status of the libsci library, the collection of scientific >library routines >available on our Cray J90 (serial number 9108) with >respect to Year 2000 >compliance? > >Are there web pages that have this information? What are the latest Cray >web pages with general Year 2000 information on the Cray J90 systems >software as well as libraries like libsci. Date: Thu, 12 Feb 1998 18:29:36 -0500 (EST) From: Jack P Seltzer Reply-To: Research Comp To: cri_support_us@atlanta.cray.com Cc: Research Comp , jack@udel.edu Subject: Year 2000 Compliance for the libsci Libary What is the status of the libsci library, the collection of scientific library routines available on our Cray J90 (serial number 9108) with respect to Year 2000 compliance? Are there web pages that have this information? What are the latest Cray web pages with general Year 2000 information on the Cray J90 systems software as well as libraries like libsci. Jack Seltzer User Services University of Delaware 302-831-1986 ---- Date: Thu, 12 Feb 1998 18:55:17 -0600 From: cri_support_us@cray.com To: jack@udel.edu Subject: Ticket 141513: Year 2000 Compliance for the libsci Libary Jack, Check out http://www.sgi.com/Technology/year2000/ That is SGI/Cray's public year 2000 web page, and should answer a lot of your questions. If something is still unclear let me know and I will see what I can find out for you. Thanks Kevin Kramer kak1@ironwood.cray.com ----- Date: Fri, 13 Feb 1998 18:34:21 -0500 (EST) From: Jack Seltzer To: cri_support_us@cray.com Cc: jack@udel.edu Subject: Re: Ticket 141513: Year 2000 Compliance for the libsci Libary kevin, Thanks for your reply. The web pages you mentioned do not have any information relating to the libsci library, the collection of scientific library routines available on the Cray J90. Your help in this matter will be greatly appreciated. Jack Seltzer User Services University of Delaware Tel. 302-831-1986 On Thu, 12 Feb 1998 cri_support_us@cray.com wrote: > Jack, > > Check out http://www.sgi.com/Technology/year2000/ > > That is SGI/Cray's public year 2000 web page, and should > answer a lot of your questions. If something is still > unclear let me know and I will see what I can find out > for you. > > Thanks > Kevin Kramer > > kak1@ironwood.cray.com >
BMDP Contact
Itemal Contact
Limdep Contact
Lisrel Contact
On Thu, 19 Mar 1998, Mdutoit wrote: > In a message dated 98-03-16 17:25:38 EST, you write: > > << jack@UDel.Edu >> > Dear Jack: > > As far as what we can establish none of our LISREL version should cause > 2000 year problems. > We will update our website to reflect this info > Regards, > Stephen du Toit > -------- Response: Date: Thu, 19 Mar 1998 21:08:04 EST From: MdutoitTo: jack@udel.edu Subject: Re: Year 2000 Compliance for Lisrel and Prelis In a message dated 98-03-16 17:25:38 EST, you write: << jack@UDel.Edu >> Dear Jack: As far as what we can establish none of our LISREL version should cause 2000 year problems. We will update our website to reflect this info Regards, Stephen du Toit ------------ Date: Mon, 16 Mar 1998 17:12:07 -0500 From: Jack Seltzer To: techsupport@ssicentral.com, jack@udel.edu Subject: Year 2000 Compliance for Lisrel and Prelis What versions of lisrel and prelis are year 2000 compliant? Is there a web page for this info? I found the SSI homepage, but did not find any info on y2k compliance. Thanks in advance, Jack Seltzer University of Delaware User Services 302-831-1986
Prelis Contact
Response to question if response included prelis... Date: Fri, 20 Mar 1998 17:20:27 EST From: MdutoitTo: jack@zebra.us.udel.edu Subject: Re: Year 2000 Compliance for Lisrel and Prelis Hi Jack: Yes it includes the PRELIS program Best Regards, Stephen (didn't mention prelis in response)..... Date: Fri, 20 Mar 1998 16:00:52 -0500 (EST) From: Jack Seltzer To: Mdutoit Cc: jack@udel.edu Subject: Re: Year 2000 Compliance for Lisrel and Prelis Stephen, Thanks for responding. I assume that your statement applies to Prelis also? You only mentioned Lisrel in your response. Jack Seltzer User Services University of Delaware Tel. 302-831-1986 ----- On Thu, 19 Mar 1998, Mdutoit wrote: > In a message dated 98-03-16 17:25:38 EST, you write: > > << jack@UDel.Edu >> > Dear Jack: > > As far as what we can establish none of our LISREL version should cause > 2000 year problems. > We will update our website to reflect this info > Regards, > Stephen du Toit > Date: Thu, 19 Mar 1998 21:08:04 EST From: Mdutoit To: jack@udel.edu Subject: Re: Year 2000 Compliance for Lisrel and Prelis In a message dated 98-03-16 17:25:38 EST, you write: << jack@UDel.Edu >> Dear Jack: As far as what we can establish none of our LISREL version should cause 2000 year problems. We will update our website to reflect this info Regards, Stephen du Toit ------------ Date: Mon, 16 Mar 1998 17:12:07 -0500 From: Jack Seltzer To: techsupport@ssicentral.com, jack@udel.edu Subject: Year 2000 Compliance for Lisrel and Prelis What versions of lisrel and prelis are year 2000 compliant? Is there a web page for this info? I found the SSI homepage, but did not find any info on y2k compliance. Thanks in advance, Jack Seltzer University of Delaware User Services 302-831-1986
Minitab Contact
2/3/1998: Minitab Version 9, the current version on UNIX, is year 2000 compliant by default. That is, the program does not process any time/date information. Version 11 and 12, which includes the data type date/time processes this data in year 2000 compliant mode. Ref: Glenda Bartley. 2/2/1998: Left vm message at Minitab. Asking for details of the new data tuype date/time and an example of failure in current version.
S-Plus Contact
Arc/Info Contact
ArcView Contact
Grass Contact
Mail to Baylor: (fill in later when access to mail on zebra)
DI-3000 Contact
Response: Date: Thu, 19 Mar 1998 13:11:02 -0600 From: Merv PateTo: "'jack@udel.edu'" Subject: RE: Jack, <<<< . Is the di3000 library owned by vni and does exponent graphics replace di3000? >>>> More or less. Basically they do the same thing, both are Fortran callable libraries, but Exponent Graphics is more extensive. <<<< If di3000 is still supported, is it year 2000 compliant? >>>> According to our Boulder support staff, you can still purchase support for the di3000 but no further development work is being done on it. They also stated that it was year 2000 compliant as long as the user expressly uses 4-digit dates. Merv Pate, VNI Technical Support ------ Email sent to vni contained: Questions: . Is the di3000 library owned by vni and does exponent graphics replace di3000? . If di3000 is still supported, is it year 2000 compliant? . The statement on web page at http://www.vni.com. products/millennium_not.html says that all vni products are year 2000 compliant. Therefore, exponent graphics as well as the imsl libraries are year 2000 compliant, correct? We need a definitive statement for our records. Jack Seltzer University of Delaware User Services 302-831-1986
Meta File SystemContact
NCAR Contact
Response; Date: Fri, 20 Mar 1998 14:04:26 -0700 (MST) From: NCAR Graphics Info/marybTo: Jack Seltzer Cc: NCAR Graphics Info/maryb Subject: Re: NCAR Graphics Year 2000 Compliant? Dear Mr. Seltzer, The NCAR Graphics software does not use the system date for any calculations, and therefore, is year 2000 compliant. Sincerely, Mary Buck, NCAR Graphics Information > > Can you tell me or direct me to someone who can > tell me whether NCAR Graphics is Year 2000 compliant? > > Thanks in advance, > > Jack Seltzer > University of Delaware > User Services > > P.S. What I really need is some authoritative statement. If > there is a web page with this info, that will be fine. > -- ============================================================================ NCAR Graphics Information Scientific Computing Division National Center for Atmospheric Research Phone: (303) 497-1201 P.O. Box 3000 FAX: (303) 497-1814 Boulder, CO 80307-3000 e-mail: ncarginf@ncar.ucar.edu ============================================================================ Date: Wed, 18 Mar 1998 18:16:03 -0500 From: Jack Seltzer To: ncarginf@ucar.edu, jack@udel.edu Subject: NCAR Graphics Year 2000 Compliant? Can you tell me or direct me to someone who can tell me whether NCAR Graphics is Year 2000 compliant? Thanks in advance, Jack Seltzer University of Delaware User Services P.S. What I really need is some authoritative statement. If there is a web page with this info, that will be fine.
Xfig Contact
Response: Date: Thu, 19 Mar 98 09:14:00 PST From: "Brian V. Smith"To: jack@udel.edu Subject: Re: Xfig - Year 2000 Compliance > Dear Brian, > > Is Xfig year 2000 compliant? > > Who is responsible for verifying Xfig's year 2000 compliance? Is this a serious question? xfig doesn't use any dates or times except those provided by the underlying operating system. > And, finally, what is SGI's role with respect to Xfig and > year 2000 compliance, if any? SGI has nothing to do with xfig. They choose to provide it to their users but that is their only role. You will find xfig on many different venders' systems. Regards, Brian Smith ------ Date: Thu, 19 Mar 1998 12:00:37 -0500 From: Jack Seltzer To: bvsmith@lbl.gov, jack@udel.edu Subject: Xfig - Year 2000 Compliance Dear Brian, Is Xfig year 2000 compliant? Who is responsible for verifying Xfig's year 2000 compliance? And, finally, what is SGI's role with respect to Xfig and year 2000 compliance, if any? Thanks in advance, Jack Seltzer University of Delaware User Services
xv Contact
grapPHIGS Contact
PV-Wave Advantage Contact
Although the following is part of a response to questions w.r.t. IMSL libs, the answer is geeral. I.e., that thetesting implicitly implies that the product is y2k compliant. te: Wed, 23 Dec 1998 13:01:12 -0600 From: Trudi SchweizerTo: "'jack@udel.edu'" Subject: FW: Y2k Info at http://www.vni.com/products/y2k. Here are answers to your year 2000 questions, forwarded to me from Nancy Meneely: 1. According to the Web page at the addressing the subject, IMSL Fortran Numerical Libraries, version 3.0, 3.01 and IMSL Fortran 90 MP Library, Version 3.0, 3.01 have been tested for Year 2000 compliance. Does this implicitly mean that they also passed the test (with the exception of the required patch for TDATE)? yes
Fortran Contact
Asked Dan if the patches he mentioned below bring fortran up to y2k compliance: Date: Tue, 31 Mar 1998 12:01:20 -0500 (EST) From: Jack SeltzerTo: Dan Grim Cc: Jack Seltzer , Dick Sacher Subject: Re: SunSolve Online (fwd) Dan, Are the patches you mentioned below those that bring Fortran up to y2k compliance? From SunSolve, I found that the patch you mentioned (104529 "jumbo" patch) includes patch 4039702 which corrects a problem with routine "idate" (retrurns incorrect year for 2001), but I don't know if that's the only y2k non-compliance. I doubt it because Sun says the patches bring the fortran workshop including f77, f90 and their performance program up to compliance, but I don't know. Sun's mail on the subject is below. Jack Date: Wed, 25 Mar 1998 10:00:44 -0800 (PST) From: Elan Finch To: jack@udel.edu Cc: elan.finch@Eng.Sun.COM Subject: Re: y2000 Customer Response Questionnaire Hello - Sun WorkShop Fortran Compiler in version 4.2 is Year 2000 compliant with patch applied. The "Sun WorkShop Fortran Compiler 4.2" product consists of Fortran 77 in version 4.2, Fortran 90 in version 1.2, and Performance Library in 1.2. The patch necessary for WorkShop Fortran Compiler 4.2 can be found if you have access to, the SunSolve Online Patch Database. If you do not have access to SunSolve, or do not have a support contract with Sun, please contact SunService at 1-800-USA-4-SUN for assistance in how to obtain patches. Regards, The Sun Microsystems Year 2000 Program Team ------------ Dan's reponsed to mail about patches for fortran: On Wed, 25 Mar 1998, Dan Grim wrote: > Jack, > > The only patch available for Fortran 77 is 104529. We have > already installed revision -03 but the latest revision is -08. We > should have -08 installed today or tomorrow at the latest. > > Dan ------ Sun's Compliant Product List shows that there are patches to make this version of Fortran y2000 compliant. Sent e-mail to Dan asking if these patches have been applied or, if not, do we have a target date. ------ Date: Wed, 25 Mar 1998 10:00:44 -0800 (PST) From: Elan Finch To: jack@udel.edu Cc: elan.finch@Eng.Sun.COM Subject: Re: y2000 Customer Response Questionnaire Hello - Sun WorkShop Fortran Compiler in version 4.2 is Year 2000 compliant with patch applied. The "Sun WorkShop Fortran Compiler 4.2" product consists of Fortran 77 in version 4.2, Fortran 90 in version 1.2, and Performance Library in 1.2. The patch necessary for WorkShop Fortran Compiler 4.2 can be found if you have access to, the SunSolve Online Patch Database. If you do not have access to SunSolve, or do not have a support contract with Sun, please contact SunService at 1-800-USA-4-SUN for assistance in how to obtain patches. Regards, The Sun Microsystems Year 2000 Program Team ===================================================================== Please note that the information being provided does not constitute a warranty or a modification of any agreement you may have with Sun Microsystems, Inc., its subsidiaries, or its customers. ===================================================================== > [Email]: jack@udel.edu > [Company]: University of Delaware, User Services > [Versions of Solaris running]: 2.5 > [Other Sun sw running]: fortan 77, pascal, C, C++ > [Sun products concerned about]: Fortran 90 > [Other Comments]: (below) > You do not list Sun Workshop Compilers Fortran 90. We have version 4.2. > Is this y2k compliant? If not, are there patches to bring it up to > compliance? <1- p -> Return to chart /a ->
AcuCobol Contact
On 2/16/1998 talked to AcuCobol people including a technician. They said that version 2.1 is y2k compliant in the sense that it will function after 2000. However, it does not have the ability to get 4-digit years from the OS, which version 4.1does. In 2.1 asking for a year will give you a 2-digit year. They recommended replacement with version 4.1. ------ E-mail sent to info@acucobol.com on 1/28/1998 asking if version 2.1.1 which we have is year 2000 compliant. Their version 2.3 is compliant according to the info on their web pages.
Ada Contact
Date: Tue, 31 Mar 1998 19:26:12 -0500 (EST) From: Jack SeltzerTo: Elan Finch Cc: Jack Seltzer Subject: Re: y2000 Customer Response Questionnaire Elan, Thank you for your recent response to my question about the Fortran compiler and y2k compliance. Can you help with the following. According to Sun's web page on y2k product compliance, the Sun Workshop for Ada at version 1.1.1 and later is y2k compliant. However this does not tell me specifically about the version of ada we have on our system which is version 3.0 of ada. Is Version 3.0 of ada y2k compliant? And, if not, what versions of ada are? Thanks, Jack Seltzer User Services University of Delaware Tel. 302-831-1986
C Contact
C++ Contact
Pascal Contact
Response to e-mail below; Date: Tue, 24 Mar 1998 11:24:57 -0800 (PST) From: Elan FinchTo: jack@udel.edu Cc: elan.finch@Eng.Sun.COM Subject: Re: y2000 Customer Response Questionnaire Hello - Sun WorkShop Compiler Pascal in version 4.2 is currently under evaluation. Please keep checking back to our Compliant Product Listing for status as it becomes available. Regards, The Sun Microsystems Year 2000 Program Team ===================================================================== Please note that the information being provided does not constitute a warranty or a modification of any agreement you may have with Sun Microsystems, Inc., its subsidiaries, or its customers. ===================================================================== > [Email]: jack@udel.edu > [Company]: University of Delaware, User Services > [Versions of Solaris running]: Solaris 2.5 > [Other Sun sw running]: fortan, c, c++, pascal > [Sun products concerned about]: Sun Workshop Compilers Pascal > [Other Comments]: (below) > You do not list Sun Workshop Compilers Pascal. We have version 4.2. Is this > y2k compliant? If not, are there patches to bring it up to compliance? ---- Sent mail to Sun via their Customer Response Questionnaire (a form off of their y2k page) asking for info on the compliance of pascal. Here is the note: You do not list Sun Workshop Compilers Pascal. We have verion 4.2. Is this y2k compliant? If not, are there patches to bring it up to compliance?
Scheme Contact
Second letter below suggested sending mail to author of scm, Aubrey Jaffer, which follows: Date: Tue, 31 Mar 1998 15:16:35 -0500 (EST) From: Jack SeltzerTo: Aubrey jaffer Cc: Jack Seltzer Subject: scm Aubrey, We are using scm, versin 4c3. Is this version year 2000 compliant? if not, is there a version that is year 2000 compliant? Is such information available on the web? Thanks in advance, Jack Seltzer User Services University of Delaware Tel. 302-831-1986 ------ Date: Wed, 25 Mar 1998 12:10:16 +0900 From: Jong-won Choi To: Jack Seltzer Subject: Re: Scheme Year 2000 Compliance [The following text is in the "euc-kr" character set] [Your display is set for the "US-ASCII" character set] [Some characters may be displayed incorrectly] Hello Jack, I'm not sure implementation detailed things but generally Scheme is not related with such a problem - e.g. in standard Scheme spec, there is not date related operations. Of course, scm has - if my memory serves me - date related operations. Maybe the original writer of Scm is clever enough to avoid Y2000 problem. Also there is universal time package in Slib, using this you get a fair of semi standard date operation. I think the Y2000 problem is almost for Cobol. When you use high level enough programming lanugages, you never concern about such a stupid problem. Happy Lisping, - jwc >We are using scm, version 4c3. Is this version year 2000 >compliant? If not, is there a version that is year 2000 >compliant? Is such information available on the web? > > Thanks in advance, > > > Jack Seltzer > User Services > University of Delaware > Tel. 302-831-1986 > -------- To : scheme@ai.mit.edu Cc : Jack Seltzer Attchmnt: Subject : Scheme Year 2000 Compliance ----- Message Text ----- We are using scm, version 4c3. Is this version year 2000 compliant? If not, is there a version that is year 2000 compliant? Is such information available on the web? Thanks in advance, Jack Seltzer User Services University of Delaware Tel. 302-831-1986