Re: whats the difference on this update.

[Scott Mildenberger <scottmildenberger@xxxxxxxxx>]

Is the key on the logical such that there are records with the
same key?  I assume the logical on the test file was the only
logical existing.  The logical on the production file is
probably sharing another access path that forces the order of
the records to use more fields than the key on the logical being
used.  The field you are changing is probably one of these
additional ordering fields caused by the access path sharing so
it is acting like you are actually changing the key fields.

I'm not sure that is a clear description above :) but it is
saying that the production file is sharing a different access
path than the test file which is causing the problem (my guess
anyway).

Scott Mildenberger

--- "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx> wrote:
> A coworker has come to me on this and I don't have the answer.
>  Here is
> the situation
>  
> a copy of a production physical was created in test library
> via CPYF.
> Logical was built over the copied file. 
> Program does a read loop on the file updating records in the
> test
> library.  The program updates as desired. 
>  
> Same program over the production file when it updates a
> record, proceeds
> to read the same record again.  
> The field that is being updated is not  one of the key fields.
> 
>  
> I have verified the logical in test and the logical in
> production are
> the same.  
>  
> The only real difference i can find in the physical file is
> that the
> production file is journaled. Could this be the cause?
> There is only 1 copy of the program.  
>  



__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you?re looking for faster
http://search.yahoo.com