Chapter 49 Measure Messages

Cause  The Measure product version is not compatible with the operating system version.

Effect  MEASCTL stops.

Recovery  Install compatible versions of the Measure product and the operating system.

Cause  An attempt was made to run MEASCTL in a processor that already has MEASCTL running.

Effect  MEASCTL stops.

Recovery  Informational message only; no corrective action is needed.

Cause  An attempt was made to obtain process information on MEASMON. MEASMON might have stopped immediately after starting a MEASCTL, or there might be a system resource problem.

Effect  The Measure subsystem does not work.

Recovery  For error 4, stop and restart the Measure subsystem. For error 5, check the processor status, and then take appropriate action. For information on the detail code and recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  MEASCTL could not obtain certain information about itself.

Effect  MEASCTL in the specified processor stops.

Recovery  Restart the Measure subsystem; if the same error occurs, contact your service provider. See the Guardian Procedure Errors and Messages Manual for information on the detail code.

When contacting your service provider, provide all relevant information:

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

Cause  An attempt to lock memory failed.

Effect  MEASCTL stops.

Recovery  Install more memory.

Cause  MEASCTL in the specified processor could not obtain space from SYSPOOL to store information about itself.

Effect  MEASCTL in the specified processor stops.

Recovery  None. Try restarting the subsystem when the system load is lighter.

Cause  An attempt to lock memory for a write to the data file failed.

Effect  The specified measurement number aborts in the specified processor.

Recovery  Add memory to the system.

Cause  The MEASCTL program file was not named $VOLUME.SYScpu.MEASCTL.

Effect  MEASCTL stops.

Recovery  Assign the correct file name to the MEASCTL program and restart the Measure subsystem.

Cause  An attempt to allocate a segment space failed, probably because of insufficient disk space.

Effect  MEASCTL stops.

Recovery  For information on the specified error, see Appendix F. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If disk space is insufficient, purge unnecessary files or add a disk to the system.

Cause  An attempt to allocate the Private Measure Queue (PMQ) segment failed.

Effect  MEASCTL stops.

Recovery  For information on the specified error, see Appendix F. For information on the detail code and additional recovery actions, see the Guardian Procedure Errors and Messages Manual. Correct the error if possible, then restart the Measure subsystem.

Cause  An attempt to lock memory for counter space failed.

Effect  Some entities are not measured.

Recovery  Install more memory.

Cause  An attempt to lock memory for a structured query language (SQL) control block space failed.

Effect  Some SQL statements are not measured.

Recovery  Install more memory.

Cause  No more counter space was available.

Effect  No new entities are measured.

Recovery  Perform one or more of the following actions:

This event is burst suppressed so that no more than three of these events can occur in a five-minute interval for each MEASCTL process. Burst suppression lasts for a minimum of five minutes. At the end of burst suppression, a 4062 event is generated that displays a count of 4013 events that were suppressed. Conditions that can cause burst suppression are:

Cause  No more structured query language (SQL) control block space was available for measurement.

Effect  Statement entities of newly created SQL processes are not measured.

Recovery  Do not start measurement on new SQL statements until some of the active SQL statement measurements stop.

Cause  A SQL statement control block pool structure was invalid.

Effect  A GETPOOL or PUTPOOL operation fails.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  A file-system error occurred during an attempt to write to a data file.

Effect  MEASCTL aborts the specified measurement in the specified processor. Data is not written to the data file.

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

Cause  An attempt to send a message to an input/output (I/O) process failed. The linker or the listener had too many messages queued.

Effect  MEASCTL aborts the measurement in the specified processor.

Recovery  If this error occurs frequently, contact your service provider and provide all relevant information:

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

Cause  An attempt to read a request failed. The request was canceled or not enough memory could be locked.

Effect  The request is not read, so it cannot be performed.

Recovery  Investigate memory usage. The indicated processor might have insufficient memory.

Cause  A message to the I/O process (IOP) where the measurement data file resides was not completed.

Effect  The measurement aborts in the specified processor.

Recovery  Informational message only; no corrective action is needed. If this problem persists, contact your service provider and provide all relevant information:

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

Cause  A file-system error occurred during an attempt to open a data file.

Effect  The measurement aborts in the specified processor. The data file is not opened.

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

Cause  MEASCTL in the specified processor failed to close the specified measurement data file.

Effect  The data file remains open.

Recovery  Stop the Measure subsystem so the file can be closed when the MEASCTL process terminates.

Cause  An internal message ID associated with the specified measurement had an illegal value.

Effect  The processor halts with code %14003.

Recovery  Take the processor dump; then contact your service provider and provide all relevant information:

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

Cause  A call to the USESEGMENT procedure failed because of an internal error.

Effect  The call to USESEGMENT is ignored.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  Space was not available in the counter identification (CID) table; too many entities were already under measurement.

Effect  No new entities are measured.

Recovery  Perform one or more of the following actions:

Cause  An attempt to access disk cache headers failed.

Effect  Some disk cache counters might have incorrect values on the specified logical device.

Recovery  Restart the measurement. If the error persists, check the status of the associated disk volume and bring the device up if it is down.

Cause  An attempt to start PROCESSH sampling failed.

Effect  No PROCESSH measurements are done.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  An attempt to stop PROCESSH sampling failed.

Effect  None.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  MEASCTL received a request with an unknown request type.

Effect  The request is ignored.

Recovery  No user action is needed. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  An attempt to open the specified data file failed.

Effect  The measurement is aborted in the indicated processor.

Recovery  Restart the measurement. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  MEASCTL, in the specified processor, could not lock the memory required to send or receive a message for the measurement with the specified data file.

Effect  The measurement stops.

Recovery  Install more memory if this error occurs frequently. Otherwise, check to see whether you can reduce the memory consumption of other processes, including disk cache size.

Cause  An attempt to lock memory for a message’s control buffer failed.

Effect  The message is not read, so the request cannot be performed.

Recovery  Investigate memory usage. The indicated processor might have insufficient memory.

Cause  An attempt to obtain information about MEASMON failed.

Effect  MEASCTL stops.

Recovery  Stop and restart the Measure subsystem using MEASCOM.

Cause  There was an inconsistency between the entity control block and the counter identification (CID).

Effect  MEASCTL resolves the inconsistency internally. The measurement is not affected.

Recovery  Informational message only; no corrective action is needed.

Cause  There was an inconsistency between the entity control block and the counter identification (CID).

Effect  MEASCTL resolves the inconsistency internally. The measurement is not affected.

Recovery  Informational message only; no corrective action is needed.

Cause  An attempt to obtain controller information failed.

Effect  If a START MEASUREMENT command was issued, controllers are not measured. If a LISTACTIVE command was issued, no record is returned.

Recovery  For recovery information, see the Guardian Procedure Errors and Messages Manual. Correct the error and retry the measurement.

Cause  The call to the DEFINEPOOL procedure failed because of an internal error.

Effect  MEASCTL stops.

Recovery  Restart the subsystem. If the error occurs again, contact your service provider and provide all relevant information:

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

Cause  The MEASCTL object file was compiled with the TARGET TNS/R option, which limits its operation to TNS/R systems only. However, an attempt was made to run MEASCTL on a TNS system.

Effect  MEASCTL stops.

Recovery  To run the program on a TNS/R system, compile the MEASCTL object file with the TARGET TNS/R option. To run the program on a TNS system, compile the MEASCTL object file with the TARGET TNS option.

Cause  The MEASCTL object file was compiled with the TARGET TNS option, which limits its operation to TNS systems only. However, an attempt was made to run MEASCTL on a TNS/R system.

Effect  MEASCTL stops.

Recovery  To run the program on a TNS/R system, compile the MEASCTL object file with the TARGET TNS/R option. To run the program on a TNS system, compile the MEASCTL object file with the TARGET TNS option.

Cause  The call to the DEFINEPOOL procedure failed because of an internal error.

Effect  MEASCTL stops.

Recovery  Restart the subsystem. If the error occurs again, contact your service provider and provide all relevant information:

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

Cause  A call to the Guardian SETMODE procedure failed.

Effect  MEASCTL aborts the measurement in the specified processor.

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

Cause  A request to the input/output process request manager (IOPRM) failed because of an internal error; the XPTR has not been cleared.

Effect  If the problem can be resolved internally, MEASCTL continues and the measurement completes normally. If the problem cannot be resolved, the system will probably halt. This message is one of several that can help identify the problem.

Recovery  If the measurement completes normally, no corrective action is needed. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  A request to the IOPLIB (a set of library routines used by the I/O process) failed because of an internal error; the XPTR has not been cleared.

Effect  If the problem can be resolved internally, MEASCTL continues and the measurement completes normally. If the problem cannot be resolved, the system will probably halt. This message is one of several that can help identify the problem.

Recovery  If the measurement completes normally, no corrective action is needed. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  A request to XIO for module information failed because of an internal error.

Effect  Only the SERVERNET IPC node class is measured; other SERVERNET entities are not measured.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  A request to WAN for configuration information failed because of an internal error.

Effect  SERVERNET entities in the WAN node class are not measured.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  A request to the SCSI interface monitor for configuration information failed because of an internal error.

Effect  SERVERNET entities in the SCSI node class are not measured.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  A request to the file system failed because of an internal error.

Effect  The measurement continues.

Recovery  If the measurement completes normally, no corrective action is needed. If the problem persists, additional messages will appear. Contact your service provider and provide all relevant information:

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

Cause  A request to the IOPLIB (a set of library routines used by the I/O process) failed because of an internal error; the XPTR had not been set or cleared.

Effect  If the problem can be resolved internally, MEASCTL continues and the measurement completes normally. If the problem cannot be resolved, the system will probably halt. This message is one of several that can help identify the problem.

Recovery  If the measurement completes normally, no corrective action is needed. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  A request to the input/output process request manager (IOPRM) failed because of an internal error.

Effect  If the problem can be resolved internally, MEASCTL continues and the measurement completes normally. If the problem cannot be resolved, the system will probably halt. This message is one of several that can help identify the problem.

Recovery  If the measurement completes normally, no corrective action is needed. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  A request to the IOPLIB (a set of library routines used by the I/O process) failed because of an internal error.

Effect  If the problem can be resolved internally, MEASCTL continues and the measurement completes normally. If the problem cannot be resolved, the system will probably halt. This message is one of several that can help identify the problem.

Recovery  If the measurement completes normally, no corrective action is needed. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  A request to the IOPLIB (a set of library routines used by the I/O process) failed because of an internal error.

Effect  If the problem can be resolved internally, MEASCTL continues and the measurement completes normally. If the problem cannot be resolved, the system will probably halt. This message is one of several that can help identify the problem.

Recovery  If the measurement completes normally, no corrective action is needed. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  A request to the IOPLIB (a set of library routines used by the I/O process) failed because of an internal error.

Effect  If the problem can be resolved internally, MEASCTL continues and the measurement completes normally. If the problem cannot be resolved, the system will probably halt. This message is one of several that can help identify the problem.

Recovery  If the measurement completes normally, no corrective action is needed. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  An attempt to allocate a segment for the queue for deferred events (SSRQ) failed.

Effect  MEASCTL stops.

Recovery  For information on the specified error, see Appendix F. For information on the detail code and additional recovery actions, see the Guardian Procedure Errors and Messages Manual. Correct the error if possible, then restart the Measure subsystem.

Cause  The MEASCTL queue (SSRQ) for incoming requests is full. This event indicates serious MEASCTL performance problems. This can happen if there is extreme CPU and disk activity in the MEASCTL CPU and rapid configuration changes in the subsystems under measurement. MEASCTL itself can cause high disc activity if there are many (tens of thousands) of entities being measured and a low interval (like one second) is specified.

Effect  The incoming requests are rejected. The requests are from subsystems under measurement.

Recovery  Address the cause of the CPU, disk or configuration activity. Any measurements run when this event occurred could be missing some data because of missed subsystem configuration changes.

Cause  Event suppression of the specified event number had occurred and is now ending. Currently, only event 4013 can be suppressed.

Effect  The specified event is no longer suppressed.

Recovery  None for this event. Look at the Recovery section for the event that was suppressed.

Cause  CID usage for the CPU exceeded the specified threshold.

Effect  None for this event; informational message only.

Recovery  None for this event; informational message only.

Cause  A call to an internal NSK API failed. This is for diagnostics purposes only.

Effect  No visible effect.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  When specifying a secondary USERDEF measurement for a process, the INDEX value for a specific counter must be the same as what was previously specified. This event indicates that it was not the case.

Effect  The specified USERDEF measurement will not be started.

Recovery  Correct the INDEX or the counter name and start the measurement again.

Cause  An attempt to lock memory for a write from the ANSI journal to the data file failed.

Effect  The specified measurement number aborts in the specified processor.

Recovery  Add memory to the system.

Cause  A file-system error occurred during an attempt to write the ANSI journal to a data file.

Effect  MEASCTL aborts the specified measurement in the specified processor. Data is not written to the data file.

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

Cause  An attempt to send a message to an input/output (I/O) process failed. The linker or the listener had too many messages queued.

Effect  MEASCTL aborts the measurement in the specified processor.

Recovery  If this error occurs frequently, contact your service provider and provide all relevant information:

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

Cause  A message to the I/O process (IOP) where the measurement data file resides was not completed.

Effect  The measurement aborts in the specified processor.

Recovery  Informational message only; no corrective action is needed. If this problem persists, contact your service provider and provide all relevant information:

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

Cause  A file-system error occurred during an attempt to open a data file.

Effect  The measurement aborts in the specified processor. The data file is not opened.

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

Cause  MEASCTL in the specified processor failed to close the specified measurement data file.

Effect  The data file remains open.

Recovery  Stop the Measure subsystem so the file can be closed when the MEASCTL process terminates.

Cause  An attempt to open the specified data file failed.

Effect  The measurement is aborted in the indicated processor.

Recovery  Restart the measurement. If the problem persists, contact your service provider and provide all relevant information:

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

Cause  MEASCTL, in the specified processor, could not lock the memory required to send or receive a message for the measurement with the specified data file.

Effect  The measurement stops.

Recovery  Install more memory if this error occurs frequently. Otherwise, check to see whether you can reduce the memory consumption of other processes, including disk cache size.

Cause  The temporary ANSI log file is full.

Effect  Some ANSI SQL names may not be found in the ANSI SQL journal, resulting in “*** Translation Not Available ***” output.

Recovery  Free up space on the disk and retry the measurement. When starting a measurement, verify that there is sufficient available disk space for the temporary ANSI log file (up to 64MB).

Cause  The call to the POOL_DEFINE_ procedure failed because of an internal error.

Effect  MEASCTL stops.

Recovery  Restart the subsystem. If the error occurs again, contact your service provider and provide relevant information:

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

Cause  No more 64-bit counter space is available.

Effect  New entities that require counters in 64-bit memory will not be measured.

Recovery  Reduce the number of measurement entities in the configuration.

Cause  Invalid Process record pointer found during measurement.

Effect  Some SQLSTMT/SQLPROC/OSSNS entities are not measured.

Recovery  Reduce the scope of the specified measurement and retry the operation, or increase the number of CIDs and retry the operation.

Cause  Invalid pointer to SQLPROC Control block or SQLSTMT pool space is found during measurement.

Effect  Some SQLSTMT/SQLPROC/OSSNS entities are not measured.

Recovery  Reduce the scope of the specified measurement and retry the operation.

Cause  Specified entity descriptor is not found in contab.

Effect  Some SQLSTMT/SQLPROC/OSSNS entities are not measured.

Recovery  Reduce the scope of the specified measurement and retry the operation.

Cause  Specified entity measurement is not active.

Effect  Some SQLSTMT/SQLPROC/OSSNS entities are not measured.

Recovery  Retry the operation.

Cause  There is an internal inconsistency between Measure and DP2.

Effect  The CPU on which MEASCTL is running will halt.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  A file-system error occurred during an attempt to write to the backup process.

Effect  The existing backup process stops; MEASMON continues without a backup.

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

Cause  The backup process could not process a message from the primary process.

Effect  The backup process stops; MEASMON continues without a backup.

Recovery  Informational message only; no corrective action is needed.

Cause  An attempt to create the MEASMON backup process failed.

Effect  The MEASMON process has no backup process at this time.

Recovery  If possible, correct the error specified and restart the subsystem. For a definition of the PROCESS_CREATE_ error, see Appendix D. For a definition of the file-system error, seeAppendix B. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  An attempt to obtain information about the MEASCTL process in the specified processor failed. The zmsr-tkn-pname contains the name of the MEASMON process where -P indicates the primary MEASMON process and -B indicates the backup MEASMON process.

Effect  There is no communication between MEASMON and the MEASCTL process in the specified processor.

Recovery  Check the status of the specified processor, then take appropriate action.

Cause  Another process was running under the MEASCTL-reserved name $XMcpu in the specified processor. P indicates the primary MEASMON process. The zmsr-tkn-pname contains the name of the MEASMON process where -P indicates the primary MEASMON process and -B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  Stop $XMcpu, then start the Measure subsystem again.

Cause  An attempt to create a MEASCTL process in the specified processor failed. P indicates the primary MEASMON process. The zmsr-tkn-pname contains the name of the MEASMON process where -P indicates the primary MEASMON process and -B indicates the backup MEASMON process.

Effect  There are no measurements in the specified processor.

Recovery  If possible, correct the error specified and restart the subsystem. For a definition of the process creation error, see Appendix D. For a definition of the file-system error, see Appendix B. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  MEASMON could not lock the memory needed to send a message to MEASCTL. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  The Measure subsystem stops.

Recovery  Add more memory to the system.

Cause  The message size was too large. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  The message request or reply control size was larger than the message system allows.

Effect  The subsystem cannot run.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  An attempt to communicate with the MEASCTL process in the specified processor failed. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  All measurements in the specified processor abort.

Recovery  Check the status of the specified processor and take appropriate action. If nothing can be done externally, contact your service provider and provide all relevant information:

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

Cause  The specified measurement could not be started. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  The measurement is aborted.

Recovery  Check the error number reported in the message. For information on the specified error, see the Measure Reference Manual.

Cause  The indicated processor ran out of counter identification (CID) entries. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  Some of the entity information for the specified measurement will not be collected, but the measurement remains active.

Recovery  For information on the specified error, see the Measure Reference Manual.

Cause  The indicated processor ran out of counter space. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  Some of the entity information for the specified measurement will not be collected, but the measurement remains active.

Recovery  For information on the specified error, see the Measure Reference Manual.

Cause  The access ID of the MEASMON creator or the access ID of MEASMON itself was not a super-group user (255, nn). P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  The Measure subsystem does not start.

Recovery  Only a super-group user (255, nn) can start the Measure subsystem. Have a super-group user start the Measure subsystem.

Cause  The MEASMON process name was not $XMM. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  Use the callable interface or MEASCOM to start the Measure subsystem.

Cause  The extended-segment allocation failed because of insufficient disk space. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  Purge any unnecessary files or add an additional disk.

Cause  The MEASMON process could not open $RECEIVE because of resource problems. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  Run fewer processes or use another processor.

Cause  MEASMON encountered a file-system error while trying to read $RECEIVE. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

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

Cause  An unexpected duplicate message was received. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  The content of the message is ignored.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  A call to the DEFINEPOOL procedure failed. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  The configuration table space that contains the entity descriptors to be measured overflowed. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  The measurement is not started.

Recovery  Start the measurement after some active measurements have stopped.

Cause  The primary process stopped before updating the backup process, resulting in a double failure. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  Restart the Measure subsystem.

Cause  The backup process died before the primary process could open it.

Effect  MEASMON runs without a backup process.

Recovery  Contact your service provider and provide all relevant information:

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

Cause  The backup process failed too many times. P indicates the primary MEASMON process. B indicates the backup MEASMON process. The message issued prior to this message indicates why the backup process failed.

Effect  The primary process runs without a backup process.

Recovery  Check the message displayed prior to this message, then correct the problem.

Cause  The MEASMON object file was compiled with the TARGET TNS/R option, which limits its operation to TNS/R systems only. However, an attempt was made to run MEASMON on a TNS system. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  To run the program on a TNS/R system, compile the MEASMON object file with the TARGET TNS/R option. To run the program on a TNS system, compile the MEASMON object file with the TARGET TNS option.

Cause  The MEASMON object file was compiled with the TARGET TNS option, which limits its operation to TNS systems only. However, an attempt was made to run MEASMON on a TNS/R system. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  To run the program on a TNS/R system, compile the MEASMON object file with the TARGET TNS/R option. To run the program on a TNS system, compile the MEASMON object file with the TARGET TNS option.

Cause  You have issued a command that started the Measure subsystem.

Effect  The Measure subsystem has started.

Recovery  Informational message only; no corrective action is needed.

Cause  You have issued a command that stopped the Measure subsystem.

Effect  The Measure subsystem has stopped.

Recovery  Informational message only; no corrective action is needed.

Cause  An attempt was made to run the Measure product with an incompatible version of the operating system. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  Install a compatible version of the Measure product.

Cause  The MEASMON program file name was not SYSnn.MEASMON. P indicates the primary MEASMON process. B indicates the backup MEASMON process.

Effect  MEASMON stops.

Recovery  Correct the MEASMON program file name.

Cause  At START MEASSUBSYS, a DEFINE was present specifying the indicated CID table size. This DEFINE is passed on to each MEASCTL process.

Effect  The CID table size in each processor is set as specified.

Recovery  Informational message. To verify CID table size, examine CPU.ending-free-cids. A small number of CIDs are used in internal table management.

Cause  At START MEASSUBSYS, a DEFINE was present specifying the indicated CID table size. This DEFINE is passed on to each MEASCTL process.

Effect  The CID table size in each processor is set as specified.

Recovery  Informational message. To verify CID table size, examine CPU.ending-free-cids. A small number of CIDs are used in internal table management.

Cause  At START MEASSUBSYS, a DEFINE was present specifying the indicated CID table size. This DEFINE is passed on to each MEASCTL process.

Effect  The CID table size in each processor is set as specified.

Recovery  Informational message. To verify CID table size, examine CPU.ending-free-cids. A small number of CIDs are used in internal table management.

Cause  At START MEASSUBSYS, a DEFINE was present specifying the indicated CID table size. This DEFINE is passed on to each MEASCTL process.

Effect  The CID table size in each processor is set as specified.

Recovery  Informational message. To verify CID table size, examine CPU.ending-free-cids. A small number of CIDs are used in internal table management.

Cause  At START MEASSUBSYS, a DEFINE was present specifying the indicated CID table size. This DEFINE is passed on to each MEASCTL process.

Effect  The CID table size in each processor is set a specified.

Recovery  Informational message. To verify CID table size, examine CPU.ending-free-cids. A small number of CIDs are used in internal table management.

Cause  At START MEASSUBSYS, a DEFINE was present specifying the indicated CID table size. This DEFINE is passed on to each MEASCTL process.

Effect  The CID table size in each processor is set as specified.

Recovery  Informational message. To verify CID table size, examine CPU.ending-free-cids. A small number of CIDs are used in internal table management.

Cause  At START MEASSUBSYS, a DEFINE was present specifying the indicated CID table size. This DEFINE is passed on to each MEASCTL process.

Effect  The CID table size in each processor is set as specified.

Recovery  Informational message. To verify CID table size, examine CPU.ending-free-cids. A small number of CIDs are used in internal table management.

Cause  At START MEASSUBSYS, a DEFINE was present specifying the indicated CID table size. This DEFINE is passed on to each MEASCTL process.

Effect  The CID table size in each processor is set as specified.

Recovery  Informational message. To verify CID table size, examine CPU.ending-free-cids. A small number of CIDs are used in internal table management.

Cause  Failed to create or access MEASFH for ANSI SQL journal recovery with the possible loss of name translation data.

Effect  There will be no ANSI SQL journal in the data file.

Recovery  If an ANSI SQL journal is required, the measurement has to be redone.

Cause  An attempt to obtain information about the MEASIP process in the specified processor failed. The zmsr-tkn-pname contains the name of the MEASMON process where -P indicates the primary MEASMON process and -B indicates the backup MEASMON process.

Effect  There is no communication between MEASMON and the MEASIP process in the specified processor. No ProcessH measurement is possible.

Recovery  Check the status of the specified processor, then take appropriate action.

Cause  Some other process is running under MEASIP's reserved name.

Effect  No ProcessH measurement is possible.

Recovery  Stop that process and start the Measure subsystem again.

Cause  Process_Create failed to create a MEASIP process. Measure runs without the MEASIP process in this CPU.

Effect  No ProcessH measurement is possible.

Recovery  Take action appropriate to the process create error.

Cause  Backup MEASMON failed to open the datafile.

Effect  The existing backup process stops; MEASMON continues without a backup.

Recovery  Take action appropriate to the reported file-system error.

Cause  MEASMON has asked all MEASCTL and MEASIP processes to go away, but after an interval there is still one or more of these processes alive.

Effect  MEASMON stops.

Recovery  Restart the Measure subsystem; if the same error occurs, contact your service provider.

Cause  This is displayed every time MEASIP stops due to an abnormal event. The internal code shows where it happened. Zero means normal stop.

Effect  No ProcessH measurement is possible.

Recovery  If errnum = 0, no corrective action is needed. If the problem persists, contact your service provider and provide all relevant information.

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

Cause  MEASFH was unable to open a home terminal.

Effect  MEASFH writes its messages to the console.

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

Cause  The MEASFH process has trapped out.

Effect  The MEASFH process stops abruptly, and a saveabend file is created.

Recovery  If the trap number is 12, check the disk where the MEASFH work files were created. If the disk is full or very fragmented, use the MEASCOM SWAPVOL command or the SWAP parameter in the Tandem Advanced Command Language (TACL) RUN command to request the MEASFH work files to be created on another disk. If the trap is not caused by the inability to create an extent, the CPU is short of memory, in which case try running the MEASFH process in a CPU with more memory.

For traps other than trap 12, contact your service provider and provide all relevant information:

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

Cause  MEASFH received the specified error code from AWAITIOX.

Effect  MEASFH abends.

Recovery  Take action appropriate to the reported file-system error.