Chapter 51 MEV (Multi Event Viewer) Messages

The messages in this chapter are sent by the Multi Event Viewer (MEV) subsystem.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

1000

object-name: Process process-name started.

`object-name`	is the name of the object file for the MEV component. The name can be MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.

Cause MEVCOLL or MEVSERV has completed initialization processing and is fully functional.

Effect The specified object-name process started successfully.

Recovery Informational message only; no corrective action is needed.

1005

object-name: Process process-name stopped by monitor request.

`object-name`	is the name of the object file for the MEV component. The name can be MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.

Cause MEVCOLL or MEVSERV has completed shutdown processing.

Effect The monitor stopped the specified object-name process successfully.

Recovery Informational message only; no corrective action is needed.

1010

object-name: Process process-name Initialization error: error.

`object-name`	is the name of the object file for the MEV component. The name can be MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`error`	is the error returned by the INITIALIZER procedure.

Cause MEVCOLL or MEVSERV could not initialize its working environment.

Effect The specified object-name process abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified INITIALIZER error.

1020

object-name: process-name Open $RECEIVE error: error.

`object-name`	is the name of the object file for the MEV component. The name can be MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`error`	is the file-system error returned by the OPEN procedure.

Cause MEVCOLL or MEVSERV could not open $RECEIVE.

Effect The specified object-name process abends.

Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

1050

object-name: process-name Internal error reporting initialization error: api-error, error.

`object-name`	is the name of the object file for the MEV component. The name can be MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`api-error`	is the Event Generation Processing API error.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause MEVCOLL or MEVSERV could not initialize the error-reporting module.

Effect The specified object-name process abends.

Recovery See Table 11-10, “Event Generation Processing API” of the DSM/NOW NT Manual for a definition of the specified API error.

If the error detail is a file-system error, see Appendix B, for a definition of the specified file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

The api-error number.
Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1070

object-name: process-name Open Browsing Distributor filename error: api-error, error.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`filename`	is the process name of the Browsing Distributor.
`api-error`	is the EMS Browsing Distributor API error.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause The MEV Event Collector (MEVCOLL) could not open the EMS Browsing Distributor.

Effect The MEVCOLL process abends.

Recovery See Table 11-11, “EMS Browsing Distributor API” in the DSM/NOW NT Manual for a definition of the API error.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

The api-error number.
Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1080

object-name: process-name ALLOCATESEGMENT filename error: error.

`object-name`	is the name of the object file for the MEV component. The name can be MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the segment file.
`error`	is the error returned by the ALLOCATESEGMENT procedure.

Cause The MEV Event Collector (MEVCOLL) could not allocate the MEV Event Segment or the MEV Event Server (MEVSERV) could not attach to the MEV Event Segment.

Effect The specified object-name process abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified ALLOCATESEGMENT error.

1085

object-name: process-name DEALLOCATESEGMENT filename error: error.

`object-name`	is the name of the object file for the MEV component. The name can be MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the segment file.
`error`	is the error returned by the DEALLOCATESEGMENT procedure.

Cause The MEV Event Collector (MEVCOLL) could not deallocate the MEV Event Segment or the MEV Event Server (MEVSERV) could not detach from the MEV Event Segment.

Effect The specified object-name process abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified DEALLOCATESEGMENT error.

1090

object-name: process-name Unable to USESEGMENT id = segment-id.

`object-name`	is the name of the object file for the MEV component. The name can be MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`segment-id`	is the segment number.

Cause The MEV Event Collector (MEVCOLL) and the MEV Event Server (MEVSERV) could not use a segment number.

Effect The specified object-name process abends.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1095

object-name: process-name MEV Control file (MEVCNTL) error-text error error on filename.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`error-text`	is the action which caused the error. It will contain “open,” “create,” “read,” or “write.”
`error`	is the file-system error.
`filename`	is the name of the MEV control file (MEVCNTL) that had the error.

Cause The MEV Event Collector (MEVCOLL) could not create, open, or access the MEV control file (MEVCNTL).

Effect The MEV Event Collector process stops.

Recovery See Appendix B, for a definition of the specified error. For more detailed information, including recovery actions, see the Guardian Procedure Calls Reference Manual.

1100

object-name: process-name Browsing Distributor configuring error-text filename error: api-error error, error-detail.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`error-text`	describes the operation that failed.
`filename`	is the file name associated with the failed operation.
`api-error`	is the EMS Browsing Distributor API error.
`error`	is a file-system error or the error specified by the EMS Browsing Distributor operation.
`error-detail`	is a file-system error or an EMS Browsing Distributor internal error code.

Cause The MEV Event Collector (MEVCOLL) could not configure the EMS Browsing Distributor.

Effect The MEVCOLL process abends.

Recovery See Table 11-11, “EMS Browsing Distributor API” in the DSM/NOW NT Manual for a definition of the specified API error.

If the error detail is a BDIST error, see the EMS Manual for a definition of the specified error and error detail.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1110

object-name: process-name Get event error: api-error, error.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`api-error`	is the MEV API error.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause The MEV Event Collector (MEVCOLL) could not retrieve events from the EMS Browsing Distributor.

Effect This block of events will be discarded. The number of events discarded is equal to the block-size parameter specified in the MEVCOLL process.

Recovery See Table 11-12, “Miscellaneous MEV Errors” in the DSM/NOW NT Manual for a definition of the specified API error.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1120

object-name: process-name Get event IO error: api-error, error.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`api-error`	is EMS Browsing Distributor API error.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause The MEV Event Collector (MEVCOLL) could not retrieve events from the EMS Browsing Distributor.

Effect The MEVCOLL process abends.

Recovery See Table 11-11, “EMS Browsing Distributor API” in the DSM/NOW NT Manual for a definition of the API error.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

The api-error number.
Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1125

object-name: process-name Browsing distributor configuration reset.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.

Cause The MEV Event Collector (MEVCOLL) reset the EMS Browsing Distributor configuration.

Effect The EMS Browsing Distributor is ready to receive new configuration commands.

Recovery Informational message only; no corrective action is needed.

1140

object-name: process-name Decoding event error: api-error, error.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`api-error`	is the MEV API error.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause The MEV Event Collector (MEVCOLL) could not decode an event.

Effect MEVCOLL discards the bad event buffer.

Recovery See Table 11-12, “Miscellaneous MEV Errors” in the DSM/NOW NT Manual for a definition of the specified API error.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1160

object-name: process-name Collector filename configured.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the configured EMS collector or alternate collector.

Cause The MEV Event Collector (MEVCOLL) configured an EMS collector for the EMS Browsing Distributor.

Effect The specified source collector is configured for the EMS Browsing Distributor.

Recovery Informational message only; no corrective action is needed.

1170

object-name: process-name Filter filename configured.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the filter file that was configured.

Cause The MEV Event Collector (MEVCOLL) configured a filter for the EMS Browsing Distributor.

Effect The specified filter is configured for the EMS Browsing Distributor.

Recovery Informational message only; no corrective action is needed.

1180

object-name: process-name Starttime starttime configured. Positioning mode: param value

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`starttime`	is the start time used to position the EMS Browsing Distributor.
`param-value`	is the value of the invalid parameter.

Cause The MEV event Collector (MEVCOLL) configured the starttime parameter for the EMS Browsing Distributor to read EMS events.

Effect The EMS Browsing Distributor is positioned according to this start time.

Recovery Informational message only; no corrective action is needed.

1185

object-name: process-name Open Browsing Distributor filename opened.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the EMS Browsing Distributor.

Cause The MEV Event Collector (MEVCOLL) opened the EMS Browsing Distributor.

Effect The specified EMS Browsing Distributor is open and ready to be configured.

Recovery Informational message only; no corrective action is needed.

1188

object-name: process-name Saved context position configured.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.

Cause The MEV Event Collector (MEVCOLL) positioned the EMS Browsing Distributor with the last context position saved in the MEV Event Segment.

Effect The EMS Browsing Distributor is positioned to the last processed event information.

Recovery Informational message only; no corrective action is needed.

1190

object-name: process-name Event segment file filename created for segment-size events.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the MEV Event Segment file used by the MEVCOLL process.
`segment-size`	specifies the size, in bytes, requested for the extended segment.

Cause The MEV Event Collector (MEVCOLL) created the MEV Event Segment.

Effect The specified MEV Event Segment is created.

Recovery Informational message only; no corrective action is needed.

1195

object-name: process-name MEV Control file (MEVCNTL) filename opened.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the MEV control file (MEVCNTL) that was opened.

Cause The MEV Event Collector (MEVCOLL) opened the MEV control file (MEVCNTL).

Effect The MEV control file (MEVCNTL) was opened successfully.

Recovery Informational message only; no corrective action is needed.

1196

object-name: process-name MEV Control file (MEVCNTL) filename created.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the MEV control file (MEVCNTL) that was created.

Cause The MEV Event Collector (MEVCOLL) created the MEV control file (MEVCNTL).

Effect The MEV control file (MEVCNTL) was created successfully.

Recovery Informational message only; no corrective action is needed.

1200

object-name: process-name Event segment file filename attached for segment-size events.

`object-name`	is the name of the object file for the MEV component. It contains MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the MEV Event Segment file that was attached.
`segment-size`	is the number of events that can be contained in the MEV Event Segment file.

Cause MEVCOLL or MEVSERV attached the MEV Event Segment.

Effect The specified MEV Event Segment file is attached.

Recovery Informational message only; no corrective action is needed.

1205

object-name: process-name Event segment file filename detached.

`object-name`	is the name of the object file for the MEV component. It contains MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`filename`	is the name of the MEV Event Segment file that was detached.

Cause MEVSERV detached the MEV Event Segment.

Effect The specified MEV Event Segment file is detached.

Recovery Informational message only; no corrective action is needed.

1220

object-name: process-name Acknowledge event request error: api-error, error.

`object-name`	is the name of the object file for the MEV component. It contains MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`api-error`	is the MEV API error returned by the MEV Server (MEVSERV) process.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause The MEV Event Server (MEVSERV) could not process an event acknowledgment request.

Effect This request is discarded.

Recovery See Table 11-12, “Miscellaneous MEV Errors” in the DSM/NOW NT Manual for a definition of the specified API error.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1230

object-name: process-name Broadcast message request error: api-error, error.

`object-name`	contains the name of the MEV Event Server, MEVSERV.
`process-name`	is the process name of the MEV component.
`api-error`	is the MEV API error returned by the MEV Server (MEVSERV) process.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause The MEV Event Server (MEVSERV) could not broadcast an acknowledgment message.

Effect This broadcast request is discarded.

Recovery See Table 11-12, “Miscellaneous MEV Errors” in the DSM/NOW NT Manual for a definition of the specified API error.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1235

object-name: process-name Configuration information request error: api-error, error.

`object-name`	is the name of the object file for the MEV component. It contains MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`api-error`	is the MEV API error returned by the MEV Server (MEVSERV) process.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause The MEV Event Server (MEVSERV) could not process a configuration information request.

Effect This request is discarded.

Recovery See Table 11-12, “Miscellaneous MEV Errors” in the DSM/NOW NT Manual for a definition of the specified API error.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1240

object-name: process-name Invalid server request received.

`object-name`	is the name of the object file for the MEV component. It contains MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.

Cause The MEV Event Server (MEVSERV) received an invalid request.

Effect The request is discarded.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1250

object-name: process-name Get event request error: api-error, error.

`object-name`	is the name of the object file for the MEV component. It contains MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`api-error`	is the MEV API error returned by the MEV Server (MEVSERV) process.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause The MEV Event Server (MEVSERV) encountered an error in processing a get-event request.

Effect This request is discarded.

Recovery See Table 11-12, “Miscellaneous MEV Errors” in the DSM/NOW NT Manual for a definition of the specified API error.

If the error detail is a MEV internal error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1270

object-name: process-name Process starting.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.

Cause The MEV Event Collector (MEVCOLL) and the MEV Event Server (MEVSERV) are starting.

Effect The specified process starts.

Recovery Informational message only; no corrective action is needed.

1280

object-name: process-name Starting Mode = starting-mode.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`starting-mode`	is set to the MEV Event Collector starting mode: COLD or WARM.

Cause The MEV Event Collector (MEVCOLL) is starting in the mode displayed.

Effect The MEVCOLL process starts in the specified mode.

Recovery Informational message only; no corrective action is needed.

1290

object-name: process-name Server server-name opened.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`server-name`	is the process name of the opened MEV Event Server.

Cause The MEV Event Collector (MEVCOLL) opened the MEV Event Server (MEVSERV) process.

Effect The specified MEV Event Server is opened.

Recovery Informational message only; no corrective action is needed.

1295

object-name: process-name Opened server server-name error error.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector.
`process-name`	is the process name of the MEV component.
`server-name`	is the process name of the opened MEV Event Server.
`error`	is a file-system error, or “0” if there is no file-system error.

Cause The MEV Event Collector (MEVCOLL) cannot open the MEV Event Server (MEVSERV) process.

Effect The MEVCOLL process abends after five retries.

Recovery See Appendix B, for a definition of the specified file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

1300

object-name: process-name Value param-value Invalid for param-name. Must be valid-param-value.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`param-value`	is the value of the invalid parameter or ASSIGN.
`param-name`	is the name of the invalid parameter or ASSIGN.
`valid-param-value`	is the valid value or values for this parameter.

Cause The MEV Event Collector (MEVCOLL) or the MEV Event Server (MEVSERV) detected an invalid parameter or ASSIGN passed at the startup.

Effect The specified object-name process stops.

Recovery Specify a valid ASSIGN or PARAM value. See the DSM/NOW NT Manual for more information.

1310

object-name: process-name IO error: error on error-text.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.
`error`	is the file-system error, or “0” if there is no file-system error.
`error-text`	is the name of the I/O.

Cause The specified process received an error on the specified I/O.

Effect The specified object-name process abends.

Recovery See Appendix B, for a definition of the specified file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

1320

object-name: process-name Event segment corrupted. Creating a new Event Segment.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.

Cause The Event Segment file was corrupted.

Effect The specified object-name process abends.

Recovery MEV will try to restart the MEVCOLL and MEVSERV processes. If MEV cannot start correctly, start MEVCOLL with the parameter START-MODE with the value COLD, then start MEVSERV.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

1330

object-name: process-name Deadlock detected on Event segment file.

`object-name`	is the name of the object file for the MEV component. It contains MEVCOLL for the MEV Event Collector or MEVSERV for the MEV Event Server.
`process-name`	is the process name of the MEV component.

Cause The MEV Event Collector (MEVCOLL) or the MEV Event Server (MEVSERV) detected that the MEV Event Segment file has been locked for too long.

Effect The specified object-name process abends.

Recovery Start MEVCOLL with the parameter START-MODE with the value COLD, then start MEVSERV.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25000

MEVMON: mon-process-name, CHECKPOINT failure due to file system error error.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the file-system error returned by the CHECKPOINT procedure.

Cause The MEV monitor process received an I/O error during a checkpoint operation.

Effect The MEVMON backup process is stopped and an attempt is made to create a new backup after a 10-second delay. Resource allocation failures (errors 30 through 37) might indicate that the primary or backup processor is overloaded.

Recovery For errors 30 through 37, free up system resources. For other errors, see the Guardian Procedure Errors and Messages Manual.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25001

MEVMON: mon-process-name, CHECKPOINT illegal parameter error.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the error returned by the CHECKPOINT procedure. It contains the number of the parameter that the error is against.

Cause The MEV monitor (MEVMON) detected an error while invoking the CHECKPOINT procedure.

Effect MEVMON continues processing.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified CHECKPOINT error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25002

MEVMON: mon-process-name, SIGNALTIMEOUT. Unable to allocate TLE or illegal timeout value timeout-value.

`mon-process-name`	is the process name of the MEV monitor.
`timeout-value`	is the timeout value passed to the SIGNALTIMEOUT procedure.

Cause The MEV monitor (MEVMON) detected an error when it invoked the SIGNALTIMOUT procedure.

Effect The MEVMON primary process abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified SIGNALTIMEOUT error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25003

MEVMON: mon-process-name, unable to decompose a process handle due to error error.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the error returned by the PROCESSHANDLE_DECOMPOSE_ procedure.

Cause The MEV monitor (MEVMON) detected an error when it could not decompose a process handle.

Effect MEVMON abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified PROCESSHANDLE_DECOMPOSE_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25004

MEVMON: mon-process-name, unable to obtain a process pair info due to error error.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the error returned by the PROCESS_GETPAIRINFO_ procedure.

Cause The MEV monitor (MEVMON) detected an error when it invoked the PROCESS_GETPAIRINFO_ procedure.

Effect Some information is not available.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified PROCESS_GETPAIRINFO_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25005

MEVMON: mon-process-name, $RECEIVE READ error error.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the file-system error, or “0” if there is no file-system error.

Cause The MEV monitor (MEVMON) detected an error when it read $RECEIVE.

Effect MEVMON abends.

Recovery See Appendix B, for a definition of the specified file-system error. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual.

25006

MEVMON: mon-process-name, CHECKMONITOR error error.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the error returned by the CHECKMONITOR procedure.

Cause The MEV monitor (MEVMON) detected an error when it invoked the CHECKMONITOR procedure.

Effect MEVMON abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified CHECKMONITOR error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25007

MEVMON: mon-process-name, invalid event number event-number.

`mon-process-name`	is the process name of the MEV monitor.
`event-number`	is the event number causing the problem.

Cause The MEV monitor (MEVMON) detected an invalid event message.

Effect The event message is not generated.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25008

MEVMON: mon-process-name, file OPEN checkpoint error error, status error-detail.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the error returned by the FILE_OPEN_CHKPT_ procedure.
`error-detail`	is the file-system error.

Cause The MEV monitor (MEVMON) detected an error when it invoked the FILE_OPEN_CHKPT_ procedure.

Effect The primary process abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified FILE_OPEN_CHKPT_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25011

MEVMON: mon-process-name, WRITE error error on filename.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the file-system error, or “0” if there is no file-system error.
`filename`	is the name of the file that the error is against.

Cause The MEV monitor (MEVMON) detected a file-system error when it invoked the WRITE procedure.

Effect MEVMON cannot send a startup sequence to the specified process. MEVMON tries to recover. If it cannot recover the error, the monitor stops the process.

Recovery See the Guardian Procedure Errors and Messages Manual for a definition of the specified file-system error.

25012

MEVMON: mon-process-name, segment CHECKPOINT error error on filename. Error detail error-detail.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the SEGMENT_ALLOCATE_CHKPT_ procedure error.
`filename`	is the name of the segment file that the error is against.
`error-detail`	is the file-system error.

Cause The MEV monitor (MEVMON) detected an error when it invoked the SEGMENT_ALLOCATE_CHKPT_ procedure.

Effect MEVMON abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified SEGMENT_ALLOCATE_CHKPT_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25013

MEVMON: mon-process-name, segment GETINFO error error.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the error returned by the SEGMENT_GETINFO_ procedure.

Cause The MEV monitor (MEVMON) detected an error when it invoked the SEGMENT_GETINFO_ procedure.

Effect MEVMON abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified SEGMENT_GETINFO_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25014

MEVMON: mon-process-name, ALLOCATE segment error error on filename. Error detail error-detail.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the SEGMENT_ALLOCATE_ procedure error.
`filename`	is the name of the segment file that the error is against.
`error-detail`	is the file-system error.

Cause The MEV monitor (MEVMON) detected an error when it invoked the SEGMENT_ALLOCATE_ procedure.

Effect MEVMON abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified SEGMENT_ALLOCATE_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

25015

MEVMON: mon-process-name, WRITEREAD error error on filename.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the file-system error, or “0” if there is no file-system error.
`filename`	is the name of the file that the error is against.

Cause The MEV monitor (MEVMON) detected an error when it invoked the WRITEREAD procedure.

Effect MEVMON tries to recover.

Recovery See the Guardian Procedure Errors and Messages Manual for a definition of the specified WRITEREAD error.

25016

MEVMON: mon-process-name, internal error error.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the internal error code.

Cause The MEV monitor (MEVMON) detected an internal error.

Effect MEVMON abends.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

26001

MEVMON: mon-process-name, takeover by backup in CPU cpu because primary process stopped.

`mon-process-name`	is the process name of the MEV monitor.
`cpu`	is the processor where the MEVMON primary process is currently executing.

Cause The MEV monitor (MEVMON) primary process was stopped.

Effect The primary process of MEVMON is currently running on another processor.

Recovery If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

26002

MEVMON: mon-process-name, takeover by backup in CPU cpu because primary process abended.

`mon-process-name`	is the process name of the MEV monitor.
`cpu`	is the processor where the MEVMON primary process is currently executing.

Cause The MEV monitor (MEVMON) primary process abended.

Effect The primary process of MEVMON is currently running on another processor.

Recovery If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

26003

MEVMON: mon-process-name, takeover by backup in CPU cpu because primary process was deleted (CPU DOWN).

`mon-process-name`	is the process name of the MEV monitor.
`cpu`	is the processor where the MEVMON primary process is currently executing.

Cause The MEV monitor (MEVMON) primary process stopped because of a processor failure.

Effect The primary process of MEVMON is currently running on another processor.

Recovery Follow the recommended procedure for recovering from a processor failure.

26005

MEVMON: mon-process-name shutdown completed.

mon-process-name

is the process name of the MEV monitor.

Cause The MEV monitor (MEVMON) completed its shutdown.

Effect MEVMON is currently stopped.

Recovery Informational message only; no corrective action is needed.

26006

MEVMON: mon-process-name, backup process deleted. CPU cpu DOWN.

`mon-process-name`	is the process name of the MEV monitor.
`cpu`	is the number of the processor that failed.

Cause The processor in which the backup process was running has failed.

Effect The primary MEVMON process does not attempt to create a backup until it receives the CPU UP system message for its backup processor.

Recovery Follow the recommended procedure for recovering from a processor failure.

26007

MEVMON: mon-process-name backup process stopped.

mon-process-name

is the process name of the MEV monitor.

Cause The MEVMON backup process was stopped.

Effect The MEVMON primary process attempts to create a new backup process after a 10-second delay. MEVMON recovers from this error automatically by trying to create a new backup process every 20 seconds until it succeeds.

Recovery Informational message only; no corrective action is needed.

26008

MEVMON: mon-process-name backup process abended.

mon-process-name

is the process name of the MEV monitor.

Cause The MEV monitor backup process abended.

Recovery Informational message only; no corrective action is needed.

26009

MEVMON: Process mon-process-name successfully started.

mon-process-name

is the process name of the MEV monitor.

Cause MEVMON started successfully.

Effect The MEVMON process is started.

Recovery Informational message only; no corrective action is needed.

26010

MEVMON: mon-process-name, backup created in CPU cpu. Priority priority. Program file filename.

`mon-process-name`	is the process name of the MEV monitor.
`cpu`	is the number of the processor where the MEVMON backup process is executing.
`priority`	is the priority of the MEVMON backup process.
`filename`	is the object file name of MEVMON.

Cause The MEVMON primary process started a new backup process.

Effect The MEVMON backup process is started.

Recovery Informational message only; no corrective action is needed.

26011

MEVMON: mon-process-name, process create error error (error-text) on filename. Error detail error-detail. Process process (process-name) in group-label group, CPU cpu. Priority priority.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the error returned by the PROCESS_CREATE_ procedure.
`error-text`	is the error text corresponding to the previous error code.
`filename`	is the name of the file that has the PROCESS_CREATE_ error.
`error-detail`	is the PROCESS_CREATE_ detail error code.
`process`	is the logical name of the process being started.
`process-name`	is the process name of the process being started.
`group-label`	is the group label for MEV.
`group`	is the logical group name for MEV.
`cpu`	is the processor in which the process is being started.
`priority`	is the priority of the process being started.

Cause The MEV monitor (MEVMON) detected an error while starting a process.

Effect The specified process is not started.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the PROCESS_CREATE_ procedure.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

26012

MEVMON: mon-process-name, process process (process-name) in group-label group stopped by monitor.

`mon-process-name`	is the process name of the MEV monitor.
`process`	is the logical name of the process being started.
`process-name`	is the process name of the process being started.
`group-label`	is the group label for MEV.
`group`	is the logical group name for MEV.

Cause The MEV monitor (MEVMON) detected that a process was not working properly during startup.

Effect The specified process is stopped.

Recovery If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

26013

MEVMON: mon-process-name, max restart max-restart reached for process process in group-label group.

`mon-process-name`	is the process name of the MEV monitor.
`max-restart`	is the maximum restart count for the process being started.
`process`	is the logical name of the process being started.
`group-label`	is the group label for MEV.
`group`	is the logical group name for MEV.

Cause The MAX-RESTART count was reached for a specific process.

Effect MEVMON does not start the specified process.

Recovery If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

26014

MEVMON: mon-process-name, invalid CPU specified for process process in group-label group.

`mon-process-name`	is the process name of the MEV monitor.
`process`	is the logical name of the process being started.
`group-label`	is the group label for MEV.
`group`	is the logical group name for MEV.

Cause The MEV monitor (MEVMON) could not start a process because an invalid processor was specified.

Effect The specified process is not started.

Recovery Specify a valid processor.

26015

MEVMON: mon-process-name, process process (process-name) in group-label group state: state.

`mon-process-name`	is the process name of the MEV monitor.
`process`	is the logical name of the process being started.
`process-name`	is the process name of the process being started.
`group-label`	is the group label for MEV.
`group`	is the logical group name for MEV.
`state`	is the state of the process.

Cause The MEV monitor (MEVMON) could not start a process.

Effect The process is in the state specified in the message.

Recovery MEVMON generates another event message describing in detail the cause of this error. Read this message and take the appropriate recovery action.

26016

MEVMON: mon-process-name, process process (process-name) in group-label group stopped.

`mon-process-name`	is the process name of the MEV monitor.
`process`	is the logical name of the process being stopped.
`process-name`	is the process name of the process being stopped.
`group-label`	is the group label for MEV.
`group`	is the logical group name for MEV.

Cause The MEV monitor (MEVMON) stopped a process.

Effect The specified process is stopped.

Recovery Informational message only; no corrective action is needed.

26017

MEVMON: mon-process-name, process process (process-name) in group-label group down.

`mon-process-name`	is the process name of the MEV monitor.
`process`	is the logical name of the process that is down.
`process-name`	is the process name of the process that is down.
`group-label`	is the group label for MEV.
`group`	is the logical group name for MEV.

Cause The MEV monitor (MEVMON) detected that a process which it started was stopped abnormally.

Effect The specified process is stopped. MEVMON tries to restart the process.

Recovery If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

26018

MEVMON: mon-process-name, process process (process-name) in group-label group started.

`mon-process-name`	is the process name of the MEV monitor.
`process`	is the logical name of the process being started.
`process-name`	is the process name of the process being started.
`group-label`	is the group label for MEV.
`group`	is the logical group name for MEV.

Cause The MEV monitor (MEVMON) started a process.

Effect The specified process is started.

Recovery Informational message only; no corrective action is needed.

27000

MEVMON: mon-process-name, OPEN failed on file filename due to file system error error.

`mon-process-name`	is the process name of the MEV monitor.
`filename`	is the name of the file that did not open.
`error`	is the file-system error, or “0” if there is no file-system error.

Cause The MEV monitor (MEVMON) detected an error as it invoked the FILE_OPEN_ procedure.

Effect MEVMON tries to recover.

Recovery See the Guardian Procedure Errors and Messages Manual for a definition of the specified FILE_OPEN_ error.

27001

MEVMON: mon-process-name, invalid backup CPU cpu.

`mon-process-name`	is the process name of the MEV monitor.
`cpu`	is the number of the invalid backup processor.

Cause The MEV monitor (MEVMON) detected an error in the specified backup processor.

Effect MEVMON abends.

Recovery Specify a valid backup processor.

27002

MEVMON: mon-process-name, unable to create backup in CPU cpu due to process create error error (error-text), error detail error-detail. Priority priority. Program file program-file.

`mon-process-name`	is the process name of the MEV monitor.
`cpu`	is the processor where the backup process is to be created.
`error`	is the PROCESS_CREATE error code.
`error-text`	is the text describing the error.
`error-detail`	is the PROCESS_CREATE_ detail error code.
`priority`	is the priority of the backup process.
`program-file`	is the program file name of the MEVMON.

Cause The MEV monitor (MEVMON) detected an error while creating its backup process.

Effect The MEVMON backup process is not running.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified PROCESS_CREATE_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

27003

MEVMON: Process not named.

Cause The MEV monitor (MEVMON) was started without a name.

Effect MEVMON abends.

Recovery Restart MEVMON as a named process.

27004

MEVMON: mon-process-name, CPU cpu down.

`mon-process-name`	is the process name of the MEV monitor.
`cpu`	is the number of the processor that failed.

Cause The MEV monitor (MEVMON) detected that a processor is down.

Effect No effect if MEVMON does not run on the down processor. If MEVMON runs on the down processor, MEVMON generates other messages and the MEVMON backup process takes over.

Recovery Follow the recommended procedure for recovering from a processor failure.

27007

MEVMON: mon-process-name, nonexistent control file filename.

`mon-process-name`	is the process name of the MEV monitor.
`filename`	is the name of the control file that does not exist.

Cause The MEV monitor (MEVMON) could not find the monitor control file.

Effect MEVMON abends.

Recovery Find a valid control file or start in COLD mode.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

27008

MEVMON: mon-process-name, PURGE control file error error on filename.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the file-system error.
`filename`	is the name of the segment file that the error is against.

Cause The MEV monitor (MEVMON) detected an error when it tried to purge the control file.

Effect MEVMON abends.

Recovery See the Guardian Procedure Errors and Messages Manual for a definition of the specified FILE_PURGE_ error.

27010

MEVMON: mon-process-name, control file name too long filename.

`mon-process-name`	is the process name of the MEV monitor.
`filename`	is the name of the invalid control file.

Cause The MEV monitor (MEVMON) detected that the control file name was too long.

Effect MEVMON abends.

Recovery The file name for the control file is limited to seven characters. Assign a valid file name for the control file and restart MEVMON.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

27011

MEVMON: mon-process-name, unable to decompose control file name, template filename, error error.

`mon-process-name`	is the process name of the MEV monitor.
`filename`	is the name of the control file template.
`error`	is the error code.

Cause The MEV monitor (MEVMON) detected an error when it tried to decompose the control file name.

Effect MEVMON abends.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified FILENAME_DECOMPOSE_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

27012

MEVMON: mon-process-name, unable to build the control file name, template filename, error error.

`mon-process-name`	is the process name of the MEV monitor.
`filename`	is the name of the invalid control file.
`error`	is the error returned by the FILENAME_EDIT_ procedure.

Cause The MEV monitor (MEVMON) could not build the control file name.

Effect MEVMON abends.

Recovery See the Guardian Procedure Errors and Messages Manual for a definition of the specified FILENAME_EDIT_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

27013

MEVMON: mon-process-name, process name create error error.

`mon-process-name`	is the process name of the MEV monitor.
`error`	is the error returned by the PROCESSNAME_CREATE_ procedure.

Cause The MEV monitor (MEVMON) detected an error when it tried to create a process.

Effect MEVMON could not find a process name. The process is not started.

Recovery See the Guardian Procedure Calls Reference Manual for a definition of the specified PROCESSNAME_CREATE_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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

27014

MEVMON: mon-process-name, unable to get info on file filename, error error.

`mon-process-name`	is the process name of the MEV monitor.
`filename`	is the file that MEVMON could not get information about.
`error`	is the error returned by the FILE_GETINFOLISTBYNAME_ procedure.

Cause The MEV monitor (MEVMON) detected an error when it could not get information on a file.

Effect MEVMON abends.

Recovery See the Guardian Procedure Errors and Messages Manual for a definition of the specified FILE_GETINFOLISTBYNAME_ error.

If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information, as follows:

Description of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and processor dump, if applicable.

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