This post refers to entries in the SystemOut.log /

In a previous article I explained the impact of repeated entries. This article gives another couple of examples and why you need to understand what is normal in your logs.

The importance of understanding what is normal

Unfortunately minor pain is a normal part of life and we have to live with it.

During your everyday life you will probably recognise pain that is normal and learn to discount it. When you feel a new pain then you know that you need to take action/investigate it.

If you are a system administrator then do you know what “normal” is in your logs?

Do you now what the standard irritations are that appear in the logs?

Periodically I meet system administrators who don’t know what normal is.

This can delay investigations because the “normal” problems need to be discounted. Spend a little time understanding what normal is because it could dramatically speed up fault investigations when you hit a serious problem.

If you can make the time then resolve as many of the normal problems as possible as this will reduce your workload in the longer term.

Missing system property Mxe.int.bidi.os log entry

If this integration system property is not set then administrators can see warnings when the Maximo integration code handles messages.

BMXAA7785W - The property mxe.int.bidi.os does not exist in the MAXPROP or MAXPROPVALUE tables

This technote explains the cause and how adding a system property with no value will prevent this error.

Missing system properties (mxe.int.ignoreerrorfile or mxe.oslc.enableprovider) log entries

These errors can also be seen at times when Maximo’s integration code runs.

This technote explains how setting the default to 0 for both properties will prevent these errors.

Other properties

There are other properties and later posts will discuss them.