Re: Object Last Use Date MDY compare issue -- MIDRANGE-L

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

To add an RTFM to this good reply -

Paul, et al., you can find out what the formats are in the help text for things like DSPOBJD - if there is an *OUTFILE option for the OUTPUT parameter, look at the help for that parameter. It is in there, in the discussion about the *OUTFILE setting.

Regards
Vern

On 2/11/2015 1:16 PM, rob@xxxxxxxxx wrote:

>From the help for dSPobjd:
The database format (QLIDOBJD) of the output file is the same as that used
in the IBM-supplied database file QADSPOBJ.

DSPFFD FILE(QADSPOBJ)

ODUCEN CHAR 1 1 434 Both Last Used
Century
Field text . . . . . . . . . . . . . . . : Last used century: 0=19xx,
1=20xx
Coded Character Set Identifier . . . . . : 37
ODUDAT CHAR 6 6 435 Both Last Used
Date
Field text . . . . . . . . . . . . . . . : Last used date (MMDDYY)
Coded Character Set Identifier . . . . . : 37

Any idiot can work around these by parsing, concatenation, sql date
routines, etc. The problem when you store it in such a cluster flop is
that you cannot build an efficient index.

Rob Berendt

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.