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



How does such a supposedly minor issue explode into a big deal?

At issue is the JODATE field in the journal entry formats QJORDJE &
QJORDJE2 (External definitions QADSPJRN & QADSPJR2, respectively.  The
text description for this field is "Date of entry: Job date format".  An
expanded definition in the Backup & Recovery Guide says "Specifies the
system date when the entry was added and is in the format of the job
attribute DATFMT."

Question:  From which job is the DATFMT attribute used?  #1, The job that
performed the transaction that created the journal entry?  Or #2, the job
that the RCVJRNE/RTVJRNE runs from?  I'm guessing #1.  In which case I
can't ever really be sure of the format of the date.  It's true that there
are probably no jobs for which the date format is changed from the
default, but here's where we smack our heads against the "assume" proverb.

So, now I see that the three other journal entry formats replace the two
separate date & time fields with a single timestamp field.  It appears
that I could use *TYPE3, but does anyone know if there is additional
performance overhead for doing so (vs. *TYPE1)?  FWIW, this is a typical
data file with no variable-length fields or null values.

TIA, GA

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.