Re: Checking object create dates -- 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.

On 14-Feb-2014 04:14 -0800, rob@xxxxxxxxx wrote:

CRPence on 02/13/2014 05:58 wrote:

Steinmetz, Paul wrote:

<<SNIP>> Problem is that my utility uses dspobjd detail(*full)
output(*outfile), source dates are not in the outfile. If I
change my utility to use detail(*service), I see the source dates
in the outfile. <<SNIP>>

The implication of that claim is in conflict with the documentation
[and actual effect hopefully as experienced by effectively everyone
effectively since forever]. The/source/ related information [fields
ODSRCF, ODSRCL, ODSRCM, ODSRCC, ODSRCD, ODSRCT of the model output
file QADSPOBJ with Record Format QLIDOBJD] should be written to the
output file irrespective of the specified DETAIL():

Then again, source dates from DSPOBJD probably only apply to OPM
programs, not ILE. There are better APIs for that.

While accurate, that would not explain a difference between the effect from DETAIL(*SERVICE) versus DETAIL(*FULL) when each is specified in conjunction with DSPOBJD OUTPUT(*OUTFILE) for the same object(s). A difference, taking that claim at face value, seems can only be explained as a defect.

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.