× 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.



> For the RPG side, any program that can be
> called from a server program should not be
> using udate, umonth, uday, uyear, *date, etc.
> I get the system date with the TIME opcode

Exactly right.  The job date stays the same across the midnight boundary for
a very good reason.  In the olden days, we used to use UDATE to print on the
top of reports, like A/R aged trial balance and so on.  We'd do a CHGJOB
DATE(friday) and run it on Saturday evening.  Even if the job ran until
Sunday morning, we were guaranteed Friday's date on all the reports.  I'm
sure this seems quaint today, but it's not possibly for IBM to change the
way UDATE works without breaking backward compatibility.

Use TIME instead of UDATE.
  --buck




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.