Re: Different date format when setting Date/Time field into a Character Field when moving from Solaris to Linux
Hi, You need to make sure both Solaris 9 and RHEL 6 recognize the common date format. You can achieve this by setting the ARDATE environment variable. HTH -- Regards, Amol Vyom Labs Pvt. Ltd. BSM Solutions & Services || ITIL Consulting & Training Email: [hidden email] <http://ars-action-request-system.1093659.n2.nabble.com/user/SendEmail.jtp?t ype=node&node=7583733&i=0> || Web Site: www.vyomlabs.com Follow Vyom Labs http://twitter.com/#!/vyomlabs <http://twitter.com/#%21/vyomlabs> || http://www.linkedin.com/company/vyom-labs From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Campbell, Paul (Paul) Sent: Tuesday, January 15, 2013 9:58 PM To: arslist@ARSLIST.ORG Subject: Different date format when setting Date/Time field into a Character Field when moving from Solaris to Linux ** We are moving our 7.6.04 servers from Solaris 9 to RHEL 6 and we have noticed that when you do a filter set fields and set the value of a Date/Time field into a character field, I get a differently formatted time value on our Solaris server as opposed to our new Linux servers, this is causing an external Web Service call to fail. The Solaris server sets the value as 01/14/13 22:00:00 The RHEL server sets the value as 01/14/2013 09:17:19 AM Both servers have LANG= en_US.UTF-8 time zone of GMT LC_ALL=en_US.UTF-8 NLS_LANG=american_america.AL32UTF8 Both servers are 7.6.04 SP4 and using ORACLE 10G database and the database time zones are the same and the 2 database instances are on the same physical server I have no clue what is causing this difference in the way the server is formatting the value, I suspect is a difference in the locale setting between Solaris and RHEL6, but I have no clue where to look, Ideas? Paul Campbell | Development Team Lead | TS&D SSBL, A2R WFE, and ESP Remedy Team | Avaya Client Services | | 1145 Sanctuary Parkway Lake View II Suite 110 Alpharetta, GA 30009 | 678-421-5342 Everyone needs deadlines. Even the beavers. They loaf around all summer, but when they are faced with the winter deadline, they work like fury. If we didn't have deadlines, we'd stagnate. Walt Disney _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Different date format when setting Date/Time field into a Character Field when moving from Solaris to Linux
Many thanks Fred, that was it. I probably would have never found that myself. Paul Campbell | Development Team Lead | TS&D SSBL, A2R WFE, and ESP Remedy Team | Avaya Client Services | | 1145 Sanctuary Parkway Lake View II Suite 110 Alpharetta, GA 30009 | 678-421-5342 Everyone needs deadlines. Even the beavers. They loaf around all summer, but when they are faced with the winter deadline, they work like fury. If we didn't have deadlines, we'd stagnate. Walt Disney -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Tuesday, January 15, 2013 11:38 AM To: arslist@ARSLIST.ORG Subject: Re: Different date format when setting Date/Time field into a Character Field when moving from Solaris to Linux Try setting the ARDATE environment variable See the FormAppObj manual page 596 Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Campbell, Paul (Paul) Sent: Tuesday, January 15, 2013 10:28 AM To: arslist@ARSLIST.ORG Subject: Different date format when setting Date/Time field into a Character Field when moving from Solaris to Linux ** We are moving our 7.6.04 servers from Solaris 9 to RHEL 6 and we have noticed that when you do a filter set fields and set the value of a Date/Time field into a character field, I get a differently formatted time value on our Solaris server as opposed to our new Linux servers, this is causing an external Web Service call to fail. The Solaris server sets the value as 01/14/13 22:00:00 The RHEL server sets the value as 01/14/2013 09:17:19 AM Both servers have LANG= en_US.UTF-8 time zone of GMT LC_ALL=en_US.UTF-8 NLS_LANG=american_america.AL32UTF8 Both servers are 7.6.04 SP4 and using ORACLE 10G database and the database time zones are the same and the 2 database instances are on the same physical server I have no clue what is causing this difference in the way the server is formatting the value, I suspect is a difference in the locale setting between Solaris and RHEL6, but I have no clue where to look, Ideas? Paul Campbell | Development Team Lead | TS&D SSBL, A2R WFE, and ESP Remedy Team | Avaya Client Services | | 1145 Sanctuary Parkway Lake View II Suite 110 Alpharetta, GA 30009 | 678-421-5342 Everyone needs deadlines. Even the beavers. They loaf around all summer, but when they are faced with the winter deadline, they work like fury. If we didn't have deadlines, we'd stagnate. Walt Disney ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Different date format when setting Date/Time field into a Character Field when moving from Solaris to Linux
Try setting the ARDATE environment variable See the FormAppObj manual page 596 Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Campbell, Paul (Paul) Sent: Tuesday, January 15, 2013 10:28 AM To: arslist@ARSLIST.ORG Subject: Different date format when setting Date/Time field into a Character Field when moving from Solaris to Linux ** We are moving our 7.6.04 servers from Solaris 9 to RHEL 6 and we have noticed that when you do a filter set fields and set the value of a Date/Time field into a character field, I get a differently formatted time value on our Solaris server as opposed to our new Linux servers, this is causing an external Web Service call to fail. The Solaris server sets the value as 01/14/13 22:00:00 The RHEL server sets the value as 01/14/2013 09:17:19 AM Both servers have LANG= en_US.UTF-8 time zone of GMT LC_ALL=en_US.UTF-8 NLS_LANG=american_america.AL32UTF8 Both servers are 7.6.04 SP4 and using ORACLE 10G database and the database time zones are the same and the 2 database instances are on the same physical server I have no clue what is causing this difference in the way the server is formatting the value, I suspect is a difference in the locale setting between Solaris and RHEL6, but I have no clue where to look, Ideas? Paul Campbell | Development Team Lead | TS&D SSBL, A2R WFE, and ESP Remedy Team | Avaya Client Services | | 1145 Sanctuary Parkway Lake View II Suite 110 Alpharetta, GA 30009 | 678-421-5342 Everyone needs deadlines. Even the beavers. They loaf around all summer, but when they are faced with the winter deadline, they work like fury. If we didn't have deadlines, we'd stagnate. Walt Disney ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Different date format when setting Date/Time field into a Character Field when moving from Solaris to Linux
We are moving our 7.6.04 servers from Solaris 9 to RHEL 6 and we have noticed that when you do a filter set fields and set the value of a Date/Time field into a character field, I get a differently formatted time value on our Solaris server as opposed to our new Linux servers, this is causing an external Web Service call to fail. The Solaris server sets the value as 01/14/13 22:00:00 The RHEL server sets the value as 01/14/2013 09:17:19 AM Both servers have LANG= en_US.UTF-8 time zone of GMT LC_ALL=en_US.UTF-8 NLS_LANG=american_america.AL32UTF8 Both servers are 7.6.04 SP4 and using ORACLE 10G database and the database time zones are the same and the 2 database instances are on the same physical server I have no clue what is causing this difference in the way the server is formatting the value, I suspect is a difference in the locale setting between Solaris and RHEL6, but I have no clue where to look, Ideas? Paul Campbell | Development Team Lead | TS&D SSBL, A2R WFE, and ESP Remedy Team | Avaya Client Services | | 1145 Sanctuary Parkway Lake View II Suite 110 Alpharetta, GA 30009 | 678-421-5342 Everyone needs deadlines. Even the beavers. They loaf around all summer, but when they are faced with the winter deadline, they work like fury. If we didn't have deadlines, we'd stagnate. Walt Disney ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
