|
Thank You! That was exactly what I was looking for! Once again, this amazing list pays for itself !!! Actually the code I needed was OPTIONS 2:/.HMSISON11 I needed to default to ISO date format, but you had the right idea. I created a tto file with the desired options and compared it to the default transfer file. One copy, one paste and I was done. Thanks again. -----Original Message----- From: Eric Sundell PMI [mailto:esundell@pmi.delta.org] Sent: Tuesday, April 20, 1999 12:31 PM To: "Guzak; Michael" ; "Midrange List (E-mail)" ; MIDRANGE-L@midrange.com Subject: Re:Client Access Data Transfer Options Change it in the default transfer PC5250$A.TTO, here's the code for YMD if you want to edit the file in notepad: OPTIONS 2:/.HMSYMDN11 ____________________Reply Separator____________________ Subject: Client Access Data Transfer Options Author: "Guzak; Michael" [SMTP:Michael_guzak@goval.com] Date: 4/20/99 7:20 AM We recently completed an upgrade for Y2K compliance. All of our date fields are now stored in ISO format. When running file transfers, I began getting the message "Error occurred in the OS/400 database server code". I was finally able to initiate file transfers by changing the date format on the data transfer dialog window under the Format Options button. The date format defaults to MDY with a slash separator. Is there a way to globally configure Data Transfer to default to a different date format. Changing the date once and re-saving the file in stored transfers is no big deal, but it's really a pain to have to go in and change the date format in every adhoc file transfer. This should also be transparent for end users that really have no interest in how or why the date format has changed. Suggestions??? +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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 +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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 +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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-2025 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.