Date Conversion Problem( Due to ESQL 9.30.UC1 upgrade)
Posted in 2000
Topics: Installation, Setup & Upgrades, Connectivity: ESQL/C, 4GL & Embedded SQL, Platform-Specific Issues, Versions, Editions & End-of-Life
This is a multi-part message in MIME format. ------=_NextPart_000_001F_01BFDAC5.402767C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi I am having problems with a particular ESQL/C Routine and would = appreciate any assistance in this area. We have recently upgrade to Informix Server 7.31.UC4, ESQL 9.30.UC1, IDS = 7.31.UC4 runing on top of Solaris 2.6 and on a SUN-4500 machine. I have found out the the rstrdate() routine converts a string date to = internal format without any errors. However, when I use the rfmtdate() = routine to make sure that I can convert the date from internal format = back to a string, it fails. Note: This is only a problem after the = program have process successfully over 2000 records of a possible 40000. = I am thinking that this problem may not be related to date conversion, = but instead to resources, but I cant prove it. =20 Vic ------=_NextPart_000_001F_01BFDAC5.402767C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hi</FONT></DIV> <DIV><FONT face=3DArial size=3D2> I am having problems = with a=20 particular ESQL/C Routine and would appreciate any assistance in this=20 area.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>We have recently upgrade to Informix = Server=20 7.31.UC4, ESQL 9.30.UC1, IDS 7.31.UC4 runing on top of Solaris 2.6 and = on a=20 SUN-4500 machine.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>I have found out the the = <STRONG>rstrdate()=20 </STRONG>routine converts a string date to internal format without any = errors.=20 However, when I use the <STRONG>rfmtdate() </STRONG>routine to make sure = that I=20 can convert the date from internal format back to a string, it=20 fails. <STRONG>Note</STRONG>: This is only a problem = after the=20 program have process successfully over 2000 records of a possible 40000. = I am=20 thinking that this problem may not be related to date conversion, but = instead to=20 resources, but I cant prove it. </FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>Vic</FONT></DIV></BODY></HTML> ------=_NextPart_000_001F_01BFDAC5.402767C0--
Victor Castillo wrote: > > This is a multi-part message in MIME format. > > ------=_NextPart_000_001F_01BFDAC5.402767C0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Hi > I am having problems with a particular ESQL/C Routine and would = > appreciate any assistance in this area. > > We have recently upgrade to Informix Server 7.31.UC4, ESQL 9.30.UC1, IDS = > 7.31.UC4 runing on top of Solaris 2.6 and on a SUN-4500 machine. > > I have found out the the rstrdate() routine converts a string date to = > internal format without any errors. However, when I use the rfmtdate() = > routine to make sure that I can convert the date from internal format = > back to a string, it fails. Note: This is only a problem after the = > program have process successfully over 2000 records of a possible 40000. = > I am thinking that this problem may not be related to date conversion, = > but instead to resources, but I cant prove it. =20 > > Vic 1. Don't post HTML 2. What is the error from rftmdate()? What does the code look like? What is the return from rstrdate(), both the error indication and the converted date? What is the input string to rstrdate()? What is the setting of DBDATE? And other locale-controlling environment variables set? Basically, at the point when the error occurs, log all the details, and post them along with the fragment of code which handles the trouble. Ideally, you'll create a small self-contained program which doesn't use any database but which does reproduce the error. -- Yours, Jonathan Leffler (Jonathan.Leffler@Informix.com) #include <disclaimer.h> Guardian of DBD::Informix v1.00.PC1 -- http://www.perl.com/CPAN "I don't suffer from insanity; I enjoy every minute of it!"
Related threads
- Conversion to differeent characters sets
- Problem in changing locale via dbexport/dbimport
- RE: openlink error "Unable to load locale categories"