Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

Missing error message text. (AREV Specific)

At 06 APR 2011 12:30:47PM Michael Slack wrote:

We're running on AREV3.12. We've checked that the REVERROR.000 file exists and has data.

A user running a large report received 2 error messages. Both had the line at the top of the screen of:

'RTP57' Line 1. B114 Maximum number of variables exceeded.

At this point I'm not worried about that error message but the message box error that was displayed in the middle of the screen.

One was B161 with an ]. The other was W175 with an ]. No other text in the message box, just those codes.

Shouldn't both message boxes have text that went with both of those error codes? I couldn't find either of those error codes listed within the REVERROR.000 table. Where should I find the text for those error messages? How might I make sure that those and any others like them properly display their text within the message box?

Thanks,

Michael Slack


At 06 APR 2011 01:10PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Did you see this?

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft


At 06 APR 2011 04:49PM Michael Slack wrote:

Hello:

Sorry, I'm being extra dense today.  Nothing clicked for me.  As far as I know (since I'm a programmer and don't have access to our live applications) we haven't made any changes to the REVPARAM file.  None of our other user have had this problem.  The user who did have the problem was running a very large report.  Because of the large report, I'm not totally surprised to see the "B114 Maximum number of variables exceeded." message at the top of the screen.  What I'm wondering about is the message box that only displayed the code "B161" or "W175".  Shouldn't there have been more to the message, such as a line or two of text explaining the error code?

If there should have been more text displayed along with the error code of "B161" or "W175", where should have that text come from? What do I need to do to make sure that text shows up the next time either of these codes (or their relatives) are displayed? I want to make sure we get all of the information we can when a error happens. For one thing, it makes my job a bit easier in trying to figure out and hopefully correct the problem.

Thanks,

Michael Slack


At 07 APR 2011 01:28PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Micheal,

Before I start, I just want to say that some of explanatory comments are for other readers, not for you. You've been around for a while, I know you know most of this.

Messages in ARev will come from two places. They'll either be hardcoded direct into the system code or they'll come from SYSMESSAGES. A small caveat that some of the hardcoded ones are jammed into the compiler from SYSTEXT, but it should appear to the causal reader that they're in the object code.

Debugger messages come from REVERROR.000

So, B161 is:

The object code for %2% cannot be

found in the %1% table.

%2% is also not cataloged.

Please enter the name of the table

containing the object code for %2%.

W175 is:

"%1%" cannot be executed.

"%2%" is not available.

One of two things could be happening here.

One is that since you've run out of variables, the system doesn't have the resources to display the rest of the message.

The other is that when calling a message by number (like B161), the system checks MESSAGES, then SYSMESSAGES. You could have these keys in your MESSAGES file with, well, with anything, really, but enough to make it not display a message properly.

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft


At 08 APR 2011 11:43AM Michael Slack wrote:

Thank you for the explanation. Since it rare for me to have to deal with message problems of this sort, I didn't even think about SYSMESSAGES. After checking to make sure both of those messages are listed and have text, that relieves me of the concern that there is something wrong with the message rows themselves.

So I assume your first suggestion is probably the correct one, in that the system didn't have the resources to display the messages. Now that I have an inkling of an idea of what went wrong with the process, I can try to start to track it down and hopefully correct it.

Making progress and learned something today. I'm off to a good start.

Thanks,

Michael Slack


At 08 APR 2011 05:01PM Eric wrote:

Another way of suppressing timed messages is to define the type in SYSMESSAGES as T0.1 (which makes them display in an instant). Blink and you'll miss them.


At 09 APR 2011 05:57AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Or as N meaning don't bother displaying :)

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft


At 09 APR 2011 11:40AM Eric wrote:

I find the N ones hard to read. Then again, I'm an emu…..

View this thread on the forum...