Chapter 129 VIEWPT (ViewPoint) Messages

Cause  The ViewPoint data file filename was removed, damaged, or made inaccessible.

Effect  If this is a message-collection error, collection stops. Depending on the error, the system might try to restart message collection.

If this error is a garbage-collect error, the cleanup operation stops. The ViewPoint database is not cleaned up.

Recovery  You can reestablish the data files by using the FUPCMDS file in the ViewPoint installation subvolume. For information about error file-error, see Appendix B.

	CAUTION: Recreating files destroys the current contents of the files.

Cause  The ViewPoint data file filename was removed, damaged, or made inaccessible.

Effect  If this is an error-collection error, collection stops. Depending on the error, the system might try to restart error collection.

If this error is a garbage-collect error, the cleanup operation stops. The ViewPoint database is not cleaned up.

Recovery  If the file is missing (error 11), the PATHMON configuration ASSIGNs for the server may be directing the server to the wrong file. Use the PATHCOM INFO command to check the configuration.

You can reestablish the data files by using FUP commands in the FUPCMDS file on the ViewPoint installation subvolume. For information about error file-error, see Appendix B.

Cause  The Garbage Collection server or Event Collection server generates this event when it encounters a SQL Internal Error during shutdown of a ViewPoint terminal.

Effect  None.

Recovery  Informational message only; no corrective action is necessary.

Cause  The ViewPoint server received an error in an message-cache data file. This internal error indicates improperly formatted messages. This error might result when incompatible versions of software are installed on the same system.

Effect  If this is a message-collection error, collection stops. Depending on the error, the system might try to restart message collection.

If this error is a garbage-collect error, the cleanup operation stops. The ViewPoint database is not cleaned up.

Recovery  Contact your HP support representative and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The ViewPoint server received an operator message that is too large (greater than 3900 bytes) to record in the message cache.

Effect  This message replaces the large message in ViewPoint’s message cache and appears in ViewPoint’s message displays. This message is not sent to the EMS collector and does not appear in the message log. The original (large) message appears in the message log.

Recovery  A very large error message could indicate erroneous error creation in the subsystem or application that generates the message. If so, correct this error so ViewPoint can correctly record the message.

If subsystem-id identifies an application program, contact the application programmer. The programmer should correct the program that issued the message if it is necessary. Otherwise, no corrective action is needed.

If subsystem-id identifies a Compaq system component, contact your HP representative and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The message collection server generates this error when it receives an error while reading edit files that supply collector configuration information.

The message collection server received an Editread or format error when reading a configuration edit file. Error numbers are:

Effect  The message collection server abends after generating this error. The server is restarted up to five times in the default configuration. If the error persists, you cannot enter ViewPoint or use the message screens.

Recovery  Correct the problem indicated by the error number. For syntax errors, see the rules specified in the ViewPoint Manual. You can then restart the server using the PATHCOM START SERVER command.

Cause  The message-collector server encountered a memory allocation error in managing the message display.

Effect  If the procedure specified in proc-name is not ALLOCATESEGMENT, the message-collection server terminates abnormally. The server automatically restarts up to five times in the default configuration. If the error persists, you cannot enter ViewPoint or use the message screens.

Recovery  For ALLOCATESEGMENT or RESIZESEGMENT errors, which indicate the inability to allocate segment space, either configure a smaller cache size for the message display or correct the specified file-system error. For information on the specified errors, see Appendix B, or to Appendix E. For any other error, contact your HP representative and provide all relevant information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.