All,
Please trim your quotes! The excessively long e-mails which result
from quoting the entire digest or by quoting all the previous e-mails,
cuases problems for several member's mail filters.
Be kind and trim.
- Charles Barouch, Moderator
U2-Users
I'm not getting the D Option when entering a control-break while
running basic programs.
Just guessing, but does the program have to be compiled with -D or -Z
option?
-Kevin
[EMAIL PROTECTED]
http://www.PrecisOnline.com
** Check out scheduled Connect! training courses at
I'm not getting the D Option when entering a control-break while
running basic programs.
I checked VOC INTR.KEY and it looks okay - what else controls the D
option?
RUN OE.BP X TRAP
ENTER [RETURN] ?
Break: Option (A,C,L,Q,?) =
.L INTR.KEY
INTR.KEY
001 X
002 ACLQD
Thanks,
Mark
I have noticed that if you happen to be EXECUTEing a TCL command when you
depress the break key it will not give you the D option because you can not
debug a non-basic process.
Tom Dodds
[EMAIL PROTECTED]
513-563-2800 Cincinnati Office
708-234-9608 Chicago Office
630-235-2975 Anywhere Cell
Mark
Try checking your PTERM settings to make sure your break key isn't assigned
to the susp or quit actions instead. Also, did you log directly into that
account, or did you LOGTO from somewhere else? AFAIR the settings are read
when you first log into UniVerse and remain in force for your
Just tried both, but still not luck.
Forgot to mention; this is Pick Flavor account.
Thanks,
Mark
I'm not getting the D Option when entering a control-break while
running basic programs.
Just guessing, but does the program have to be compiled with -D or -Z
option?
---
u2-users
I will be out of the office starting 09/06/2006 and will not return until
09/11/2006.
For pricing information, contact Louia Purinton at 913-795-2769 or
[EMAIL PROTECTED]
For technical product questions, contact Louis Tur at 813-356-3615 or
[EMAIL PROTECTED]
---
u2-users mailing list
It seems like this has always happened when the process was waiting on a record
lock. In other words, the process you're interrupting is trying to do a READU
without a LOCKED clause, but the record it's trying to READU is locked by
another process.
I think I've also run into this when the
