Going in infinite loop while using CEEDAYS

sriram1982 · New User Joined: 20 Nov 2009 Posts: 4 Location: India

In one of our programs, we are calling CEEDAYS to get the lilian date. The program is working fine all the Years except 2099. It is taking more than an hour and not resulting anything. A similar issue happening for 2199, but not for 1999.

Can any of you help me in this?

dick scherrer · Posted: Fri Nov 20, 2009 3:16 am

Hello and welcome to the forum,

Please post the working-storage fields and procedural code that is used to call CEEDAYS.

sriram1982 · New User Joined: 20 Nov 2009 Posts: 4 Location: India

This is what we are passing to call the procedure

CALL CEEDAYS USING '06022099' , 'MMDDYYYY' , lildate, fc.

Lildate and fc and are the output parameters.

dick scherrer · Posted: Fri Nov 20, 2009 3:31 am

Hello,

dbzTHEdinosauer · Posted: Fri Nov 20, 2009 3:58 am

I am sure you read the manual about CEEDAYS

did you bother to read about CEESCEN

and obviously you did not bother to read Table 30 in topic APPENDIX1.2 for a list of valid picture character terms that can be specified in input_char_date

it is in the middle of the page. do not stop reading after table 29.

sriram1982 · New User Joined: 20 Nov 2009 Posts: 4 Location: India

i feel there is no errors in passing parameters or the syntax. I am trying to use a very common project which is used by many programs in our company and working fine all other years except for 2099 and 2199. i am just wondering if there is any limitation in using CEEDAYS

Bill O'Boyle · Posted: Fri Nov 20, 2009 7:22 am

Review the links in Dick's posting and you'll immediately find your error.

Out of courtesy to other members as well as building your own knowledge base, please take the time to research questions before posting.

Nine times out of Ten, it's clearly documented.

The date ranges for the LE Callable Date routines are 14 October 1582 through 31 December 9999.

I'm confident your ranges are covered....

Bill

Robert Sample · Posted: Fri Nov 20, 2009 8:43 am

I just ran a program that converted 06222009 and 06222099 using CEEDAYS. Total time used was under a second elapsed. There is probably something about the way you're setting up and passing the data that is causing the loop. Unless you post the exact code and data definitions you are using (please use BBcode), there's not going to be much we can say.

Have you tried ZMZDYYYY for the date format?

sriram1982 · New User Joined: 20 Nov 2009 Posts: 4 Location: India

Thanks for your responses! I will once again check the documentation to find out my error that causing this issue.