I'm rather hoping someone can tell me what messages such as:

"ARWARN [8911] Message not in catalog -- message number = xxxx"

mean.

I don't think I have a list of error mesages for ARS 4.0.2 anywhere.

I get them when starting my arserverd as well as when submitting new tickets
sometimes.

Many thanks in advance,

Matt

To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist

This error means that the form that is being queried has a defined
results list (query list) that contains more than 128 bytes.

If you go to the Admin Tool, open the form in question, go to the
Form Properties, you will find a tab to define the Results List (Query
List). The total of the widths and separators specified cannot be more
than 128 bytes.

Now, pre 4.0, this definition and the lengths specified is the data you
will get back in the query list of the User Tool. Data will be truncated to
the length specified and you will get back a maximum of 128 bytes.
This is all tied to the definition of the API call ARGetListEntry.

In 4.0 and later, an additional API call was added
ARGetListEntryWithFields. This call uses the same definition of what
fields to retrieve. HOWEVER, it ignores the width and separator
information. So, regardless of how many fields you specify or what
width you specify, you will get full contents of each field on the result
list.

Now, the width and separator information is still important for 4.0 as
the ARGetListEntry call is still fully supported and is used in many
locations (it is a bit more efficient internally in some cases).

What it looks like has happened is that you are using 4.0 and have
defined the Result list with the total of width and separators over
128 bytes. If you go and adjust the widths of some of the fields so that
the total is less than 128 bytes, you should find that you get the same
result data in the result list and the warning goes away.

Now, there is a second option. This is not a documented option
(well, the setting is present in the man page description but...) and it
only covers the server, but it is a possibility if you want to use it.

There is a setting that can be made to the ar.conf/ar.cfg file that can
be used to suppress warnings that come from the server. NOTE: This
can only be used for warnings from the server. You cannot use this
setting to suppress warnings from any client at this time as the
clients do not know about this setting.

If you add the following to your ar.conf file:

Suppress-warnings: 8911

This should cause the server to suppress any occurrance of the
warning 8911.

Remember:
- You can suppress only notes and warnings, you cannot suppress
errors
- You can suppress only messages that are generated by the server,
you cannot suppress messages from the client
- The setting will not take affect until the next time you restart your
server since this setting will likely not be read until the config
file is loaded at startup the next time (a change of the file
directly is not picked up by the system until restart)

Hopefully, this provides a couple of ideas for how to address the
extra message.

Doug Mueller

To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist

Thanks again,

Matt

> -----Original Message-----
> From: Simon Fan [SMTP:sifan@UU.NET]
> Sent: Thursday, October 28, 1999 4:49 PM
> To: ARSLIST@LISTSERV.VISTAIT.COM
> Subject: Re: "Message not in catalog" errors
>
> This warning has been explained by Doug Mueller clearly:
>
> This error means that the form that is being queried has a defined
> results list (query list) that contains more than 128 bytes.
>
> If you go to the Admin Tool, open the form in question, go to the
> Form Properties, you will find a tab to define the Results List (Query
> List). The total of the widths and separators specified cannot be more
> than 128 bytes.
>
> Now, pre 4.0, this definition and the lengths specified is the data you
> will get back in the query list of the User Tool. Data will be truncated
> to
> the length specified and you will get back a maximum of 128 bytes.
> This is all tied to the definition of the API call ARGetListEntry.
>
> In 4.0 and later, an additional API call was added
> ARGetListEntryWithFields. This call uses the same definition of what
> fields to retrieve. HOWEVER, it ignores the width and separator
> information. So, regardless of how many fields you specify or what
> width you specify, you will get full contents of each field on the result
> list.
>
> Now, the width and separator information is still important for 4.0 as
> the ARGetListEntry call is still fully supported and is used in many
> locations (it is a bit more efficient internally in some cases).
>
> What it looks like has happened is that you are using 4.0 and have
> defined the Result list with the total of width and separators over
> 128 bytes. If you go and adjust the widths of some of the fields so that
> the total is less than 128 bytes, you should find that you get the same
> result data in the result list and the warning goes away.
>
> Now, there is a second option. This is not a documented option
> (well, the setting is present in the man page description but...) and it
> only covers the server, but it is a possibility if you want to use it.
>
> There is a setting that can be made to the ar.conf/ar.cfg file that can
> be used to suppress warnings that come from the server. NOTE: This
> can only be used for warnings from the server. You cannot use this
> setting to suppress warnings from any client at this time as the
> clients do not know about this setting.
>
> If you add the following to your ar.conf file:
>
> Suppress-warnings: 8911
>
> This should cause the server to suppress any occurrance of the
> warning 8911.
>
> Remember:
> - You can suppress only notes and warnings, you cannot suppress
> errors
> - You can suppress only messages that are generated by the server,
> you cannot suppress messages from the client
> - The setting will not take affect until the next time you restart your
> server since this setting will likely not be read until the
> config
> file is loaded at startup the next time (a change of the file
> directly is not picked up by the system until restart)
>
> Hopefully, this provides a couple of ideas for how to address the
> extra message.
>
> Doug Mueller
>
> To Unsubscribe send e-mail to:
> body of text is: unsubscribe arslist

To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist