|
Larry, In a message dated 98-05-18 15:31:35 EDT, you write: > Actually I have had problems with date specific program as well during > conversions, but this is really not a CISC-RISC issue as much as a Y2K > conversion issue. The problem crops up because two things are being > changed at once. (CISC-RISC and issues related to Y2K) In our case, it _was_ a CISC-RISC issue. The programs tested out fine on our development 320 (mit 4 processors) CISC box. They only failed after being promoted to the production 530 "stress test" environment, and restored on the 50S we use for Y2K testing. A quick re-compile with the proper field reference (they were mistakenly pointed at the "length" field for a QCMDEXC call instead of the file date) and the programs worked like champs on RISC! Regards, Dean Asmussen Enterprise Systems Consulting, Inc. Fuquay-Varina, NC USA E-Mail: DAsmussen@aol.com "PC Haiku" Windows NT crashed. I am the Blue Screen of Death No one hears your screams. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.