Re: Transaction date format in journal entry

A quick test using RTVJRNE and DSPJRN to an outfile shows that #2 (the
DATFMT of the requesting job) is the one in both cases.  And please note
that *type5 is where the most information is available (though you perhaps
don't need that additional information at this time).



                                                                                
                                                      
                      G Armour                                                  
                                                      
                      <garmour400m@xxxxxxx        To:       
midrange-l@xxxxxxxxxxxx                                                   
                      om>                         cc:                           
                                                      
                      Sent by:                    Subject:  Transaction date 
format in journal entry                                  
                      midrange-l-bounces@m                                      
                                                      
                      idrange.com                                               
                                                      
                                                                                
                                                      
                                                                                
                                                      
                      10/02/2003 12:58 PM                                       
                                                      
                      Please respond to                                         
                                                      
                      Midrange Systems                                          
                                                      
                      Technical Discussion                                      
                                                      
                                                                                
                                                      
                                                                                
                                                      




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
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.