[progress Communities] [progress Openedge Abl] Forum Post: Current-value() Statement And...

  • Thread starter Thread starter George Potemkin
  • Start date Start date
Status
Not open for further replies.
G

George Potemkin

Guest
In Progress V10.2B the CURRENT-VALUE(sequence) statement uses the following latches: SEQ, BHT, LRU and BUF (twice) In V11.6 the same statement additionally uses the TXQ latch (twice). NEXT-VALUE() is not changed between the versions. It uses the latches: MTX, BIB, 2*SEQ, 2*TXQ, BHT, LRU, 2*BUF In other words in both versions it uses the same latches as CURRENT-VALUE() in V11.6 plus (as expected) MTX, BIB, SEQ. Why there is a difference between versions regarding the CURRENT-VALUE() statement? New behavior? Bug in V10.2B? Or in V11.6? Just curios (as usually ;-) George Potemkin

Continue reading...
 
Status
Not open for further replies.
Back
Top