Re: Performance and timestamp fileds

[Marco Facchinetti <facchinetti@xxxxxxxxx>]

message 1 is: CPI432C
   METAILED/FTTES01L 17, METAILED/FTTES04L 11,
METAILED/FTTES06L 11,  METAILED/FTTES05L  0,
METAILED/FTTES03L 17, METAILED/FTTES02L 17.   

FTTES05L key is DATADOC and DOCID.

message 2 is:  CPI4328 
Selected FTTES05L with error code 1 (Record selection)

message 3 is:  CPI432F
Sugges to to build a logical with key fields: RECSTATE,
DATEDOC, MODIFIED.
--- Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
> Marco
> 
> CHGQRYA QRYTIMLMT(0) & STRDBG
> 
> Then run the statement - when the message comes up, take
> 'C' to cancel, 
> then check your joblog for what the SQL Optimizer
> recommends for indexes. 
> Then ENDDBG and CHGQRYA QRYTIMLMT(*NOMAX) (or whatever
> was the original 
> setting). Let us know what you see, including reasons for
> rejecting indexes.
> 
> HTH
> 
> Vern
> 
> At 08:23 AM 5/15/2003 -0700, you wrote:
> >I'm at V5R2:
> >
> >Executing a runqry with rcdslt(*yes) on a file with:
> >
> >RECSTATE       1A
> >.....
> >DATEDOC         L
> >.....
> >MODIFIED        Z
> >
> >if the record select is:
> >
> >     RECSTATE  EQ  ' '
> >AND MODIFIED  GE  '2003-05-09-00.00.00.000000'
> >
> >it takes few seconds, if
> >
> >     RECSTATE  EQ  ' '
> >AND DATADOC   LT  '31/13/02'
> >AND MODIFIED  GE  '2003-05-09-00.00.00.000000'
> >
> >it takes 7 minutes.
> >
> >All the logical files exclude RECSTATE *NE ' '.
> >There is a logical with the key on DATADOC.
> >Other logicals don't use DATADOC.
> >
> >Any idea?
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com