I guess the term abnormal comes from the old days in mainframes where you got an "ABEND" (abnormal ending) error. In this case, it would be any termination of the loop other that the intended termination, most of the time it would be crash, GOTO out of the loop, power brownout, bad NIC, etc., in other word it terminates in way that it does not drop the cursor. Of course DISC and CONN would drop the cursor, but you would have to do it from the station where the Cursor originated. Javier,
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all system and destroy all copies. ====================================================== -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Lawrence Lustig Sent: Thursday, June 23, 2005 11:27 AM To: RBG7-L Mailing List Subject: [RBG7-L] - RE: Stuck cursor lock. > I have found that many times when you exit a cursor abnormally, it leaves a > lock. Do LIST CURSORS and if there is one, then DROP CURSOR > your_cursor_name. I tried that -- anyway, it was a fresh connection. But is it possible for a different session (on another machine) to leave that lock around? If so, that's probably what happened. Do you know what constitutes an "abnormal" exit from a cursor? I always DROP my cursors, but this table is under development and something may have happened. -- Larry
