×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I am using WDSC 7 with SEP to debug. I have a breakpoint on the statement
and follow it down to the bottome where I increase Running_Date. My
monitor show Running_Date being incremented and To_Date is just as it
always is... its a constant parameter that is passed into this procedure.
My field is 8,0 zoned, not packed. I did see that discrepency in your
code Scott. Not that it should matter I suspect.
I'll play with it again in the mornig. Time to call it a day.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
10/01/2009 03:58 PM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
To
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
cc
Subject
Re: %date not evaluating in DOW as "I" would expect
Hi Bryce,
Bryce Martin wrote:
Dow Running_Date < %date(End_Date:*ISO);
Running_Date is a date, and End_Date is a YYYYMMDD 8,0 zoned.
When Running_Date = 2009-10-17 and End_Date = 20091016 it entered the
loop. How is this possible?
In an attempt to reproduce your problem, I wrote the following code.
However, I could not reproduce the problem. It did not enter the loop
for me.
D Running_Date s D
D End_Date s 8p 0
/free
Running_Date = d'2009-10-17';
End_Date = 20091016;
dow Running_Date < %date(End_Date:*ISO);
dsply 'inside loop';
leave;
enddo;
*inlr = *on;
/end-free
Can you tell me how to reproduce the problem? Or, is it possible that
the dates aren't what you think they are? did you actually set a
breakpoint right before the DOW and check the values?
midrange.com
