That doesn't answer the question about whether the key contained any mark
characters.
What was the value returned by STATUS() when the WRITE failed?
Does the file have any SQL privileges or triggers associated with it?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe
What was the value of ID (include any non-printing characters)?
That was my first thought. In the else clause, we wrote the key and
record using an OPENSEQ/WRITEBLK combination and verified the resulting
unix file using the od -cx command in Unix. Everything was exactly as
expected.
---
STATUS()=137 I'm not sure about. It's not in SYS.MESSAGES. Or ERRMSG,
for that matter. It's always 137?
The 20 minute wait makes me think it is a lock problem.
How about this:
- You are attempting top write without first EXPLICITLY locking the
record.
- Another user is holding a lock on that
STATUS()=137 I'm not sure about. It's not in SYS.MESSAGES.
Error numbers 0- are operating system errors.
1+ are found in SYS.MESSAGES.
So have to find out 137 from :
Unix SunOS 5.8
cds
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit
What was the value of ID (include any non-printing characters)?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
