Hi, apparently it's not you who locks the records? So you're reading records while somebody else is writing?
Files that you're reading usually don't have NULL IDs in them. I saw an issue in this group when somebody referred to "group locks" seeing similar SHOW-ITEM-LOCKS output. BTW, what's the idea of reading the whole STMT.ENTRY and CATEG.ENTRY during the work day? Or you have NON-stop? I believe that's an overkill; "accounting hook" or a trigger would do much better... Also you have CONCATs for both these files to process appropriate portions every day (since these records never change after they were created). VK On Mar 10, 6:52 pm, Austin Aghedo <[email protected]> wrote: > Hi, > > We are trying to read a high volume of records (more than 10M) to write to > a flat file. When the RECORDKEY is null, the process is taking a > significantly longer time to read and process the records. When there is > not blank key, the processing is pretty fast. The file type is “JR” on an > AIX 6.1 environment. This happens with several other files as well. > > Any idea as to how this can be resolved. > > SHOW-ITEM-LOCKS > PORT PID > FILENAME > RECORDKEY > LOCK# PORT/-PID 58 323678 > ../bnk.data/ac/FBNK.CATE002 > 0x11a40000,W --- 219 323678 > ../bnk.data/ac/FBNK.CATE002 > 0x79201600,R --- 227 255908 > ../bnk.data/ic/FBNK.STMT009 > 0xc2000000,W --- 227 255908 > ../bnk.data/ic/FBNK.STMT009 > 0xc2001800,R --- 241 > > Regards, -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
