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



Hmmm ... this compiles OK for me at V7.4.

**FREE
DCL-DS JOBSCHEDDS_t EXTNAME('SCHED_JOB') ALIAS QUALIFIED TEMPLATE;
END-DS;
*InLR = *On;

The RPG IV Reference states:

"The default size of a timestamp is 26, with 6 fractional seconds. For a free-form timestamp definition, you
use the parameter of the TIMESTAMP keyword to control the number of fractional seconds. For a
fixed-form timestamp definition, you can either specify the length of the timestamp item as 19, or a value
between 21 and 32, or you can specify the number of fractional seconds in the Decimal Positions entry."

Which seems to concur with the generated D-specs in the compiler listing:

    40=D LAST_SUCCESSFUL_SUBMISSION_TIMESTAMP... 1000036
    41=D                               19Z

PTF needed maybe?

Brian.

On 12/03/2021 20:14, Brian Garland via RPG400-L wrote:
I'm trying to use one of the system views as the EXTNAME of a
data-structure but it has a TIMESTAMP(0) field and the RPGLE compiler
complains that it has a length of 19 when it should be 26.

Is there anything I can do in RPGLE to use this view as a data-structure?

My code:
DCL-DS JOBSCHEDDS_t EXTNAME('SCHED_JOB') ALIAS QUALIFIED TEMPLATE;
END-DS;

>From the compile listing:
LAST_SUCCESSFUL_SUBMISSION_TIMESTAMP 19Z
20 70000037 The length of a timestamp item must be exactly 26.




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.