DBDATE format issues

We are running on Sun/Solaris 5.8 and IDS 9.40.UC4. We have an environment set up where DBDATE is set to Y4MD-. It has been running for nearly a year with this IDS version and no changes to the environment settings. Some users noticed issues last week while running queries from Server Studio where the date format was seen as invalid. I asked them to set DBDATE to the appropriate value for their connection and try it again. It seemed to work. I never heard any more complaints...until this morning when they were running some SPs and ran into the same problem. I ran the same EXECUTE FUNCTION call with both Y4MD- and Y4MD/ format and saw the same results as they did from both Server Studio and dbaccess. Only the Y4MD/ format ran successfully. I received a 1205 error for the Y4MD- format. 1205: Invalid month in date Error in line 1Near character position 1 I verified DBDATE by using env | grep DBDATE. It is definitely in Y4MD- format. Has anyone ever seen this problem? What's the solution? Thanks, Gary Andrus

Hi Gary. Just my $0.02. How about using GL_DATE ? Regards. -- Tsutomu Ogiwara from Tokyo Japan. >From: "Gary Andrus" <andrusg@aetna.com> >To: informix-list@iiug.org >Subject: DBDATE format issues >Date: 23 Jan 2006 06:48:45 -0800 > >We are running on Sun/Solaris 5.8 and IDS 9.40.UC4. > >We have an environment set up where DBDATE is set to Y4MD-. It has >been running for nearly a year with this IDS version and no changes to >the environment settings. > >Some users noticed issues last week while running queries from Server >Studio where the date format was seen as invalid. I asked them to set >DBDATE to the appropriate value for their connection and try it again. >It seemed to work. I never heard any more complaints...until this >morning when they were running some SPs and ran into the same problem. > >I ran the same EXECUTE FUNCTION call with both Y4MD- and Y4MD/ format >and saw the same results as they did from both Server Studio and >dbaccess. Only the Y4MD/ format ran successfully. I received a 1205 >error for the Y4MD- format. > > 1205: Invalid month in date >Error in line 1>Near character position 1 > >I verified DBDATE by using env | grep DBDATE. It is definitely in >Y4MD- format. > >Has anyone ever seen this problem? What's the solution? > >Thanks, >Gary Andrus > >_______________________________________________ >Informix-list mailing list >Informix-list@iiug.org >http://www.iiug.org/mailman/listinfo/informix-list

Make sure the session that creates the stored procedure or does update statistics on the stored procedure has the correct DBDATE setting.