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


  1.  Home
  2. RPG400-L
  3. August 2022

Special Register CURRENT TEMPORAL SYSTEM_TIME

Hi,

has anyone an explanation for me, why

set current temporal system_time = timestamp('2022-……‘);
values (current temporal system_time);

in iACS and STRSQL gives me a correct timestamp (or null), whereas

exec sql set current temporal system_time = :XXX;
exec sql values(current temporal system_time) into :XXX;

gives me glibber and if I use a timestamp(12) field as the receiver, and also emits a RNX0112 message?

And I also always receive the wrong value using this statement:

exec sql values case when current temporal system_time is null then '*CURRENT‘ else '*PAST‘ end into :YYY;

It always ends with "*PAST“ returned, even if my program executes a set current temporal system_time = :XXX before the values statement.

I’m kind of puzzled, because everything seems to work fine in iACS - but it doesn’t in SQLRPGLE.

Any help is greatly appreciated - so thanks in advance.

Kind regards,
Daniel

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.