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



Hi, James:

Just issue:
CHGJOB JOB(*) DATFMT(*YMD)

Then run your DSPOBJD command.

Then change your job back to the previous date format, if needed.

You will find that all the date fields in the *OUTFILE are formatted according to your current job's date format. :-)

All the best,

Mark S. Waterbury

> On 6/23/2010 7:41 PM, James H. H. Lampert wrote:
Dennis Lovelady wrote:
I believe you will find that they are CMMDDYY fields.
I wish.

From the file's field text itself

Creation:
ODCCEN - Creation century
ODCDAT - Creation date: format- mmddyy
ODCTIM - Creation time

Last Changed:
ODLCEN - Change century
ODLDAT - Change date: format- mmddyy
ODLTIM - Change time

Source Changed (rather perversely):
ODSRCC - Source change century
ODSRCD - Source change date: format- yymmdd
ODSRCT - Source change time

And they're all simple alphanumeric character fields, not L-date,
T-time, or Z-timestamp.

Wrote a little RPG Cycle program to reformat the dates into a second
file, then a CL to do the DSPOBJD, reformat it with the RPG program, and
open it in QuestView (using a VIEW program I'd created, which
encapsulated an OPNQRYF call, as well as suppressing irrelevant fields
from the screen).

A bit Rube Goldberg, but it works.

As to the outfile format for DSPOBJD, I can only say (quoting David
Gerrold):

IBM
UBM
We all BM
for IBM.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.