This is the Message (imagine it's in a MSG box and all centered) there is NO message number/id on the msg box.

  FS

SI.MFS

PYM.MFS

RTP57

ourtablename

record id

]

The Arev is 3.12 and we are sometimes reading and sometimes writing the record to the 'ourtablename'. We have our mfs named "PYM.MFS" on this table, after the system's SI.MFS.

Our PYM.MFS encrypts one field in the data record, which happens to be a field with a btree index on it (the order of the si.mfs before the pym.mfs therefore is important to keep all of our application code working in unencrypted plain text for our users, especially btree searches).

This table has 7+million records and is HIGHLY active. Only in the last few days have we started getting these messages, and the PYM.MFS was last change Jan 2005.

When we examine the record all is well (data is not corrupted, it encryptes/decrypts fine) and there are no locks reported by the NLM_STATS on this record or the data table or the !table. Of course we are looking 15-60 minutes after the user hits enter and clears the message.

Any thoughts?

It looks like the type of debugging statement a developer might put into a program. Have you checked the code for PYM.MFS for any MSG calls of this nature?

*Well* since I wrote this myself there are none!

that's right there aren't any msg calls in the code.

Not to be annoying… although…

I do remember that an MFS object code must be in the SYSOBJ file. So is it possible that you do not have the most current object code, for the MFS, in the SYSOBJ file?

You're not being annoying. Good call.

SYSOBJ is where our mfs' object code is, AND it matches the object code in the "BP" file where it was last compiled (Jan 2005).

Ctrl-Break during the message, then use R to inspect the return stack or PS to inspect the return stack from the debugger.

View this thread on the forum...