Operator Messages Manual
Chapter 4 ASAP (Availability Statistics and Performance) Messages
The messages in this chapter are sent by the Availability Statistics
and Performance (ASAP) subsystem. The subsystem ID displayed by these
messages includes ASP as the subsystem name. 1000 SGP Open pid error: err | pid | is the requester’s process identification. | err | identifies a file-system error number associated with
the last operation on the file. |
Cause The Statistics Gathering process (SGP) did not open. The FILEINFO
system procedure call returned this error. Effect A zero value is returned. 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. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1001 MONITOR -> COLLECT, error: err | err | identifies a file-system error number associated with
the last operation on the file. |
Cause The Monitor collected statistics from the network and attempted
to open the Collector and pass statistics to it. However, the communications
path was not established. The FILEINFO system procedure call returned
this error. Effect Statistics are not written into the database. 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. Check to see if the Collector is installed. Make sure the Monitor
and Collector are both up and running; you can do this by entering
STAT C for the Collector and STAT for the Monitor. Check the network
path connection. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1002 Send to SGP pid error: err, type, read^L | pid | is the requester’s process identification. | err | identifies a file-system error number associated with
the last operation on the file. | type | identifies the request type. | read^L | is the sum of the length of the Statistics Gathering
process (SGP) structure in bytes. |
Cause The Statistics Gathering process (SGP) is not receiving startup,
shutdown, status, or other requests. This error could occur because
of a version mismatch between the Monitor and Collect processes. For
example, if a new Monitor is installed on one node in an ASAP network
and the Collect process is not updated, the Collector does not recognize
any new statistics types. The FILEINFO system procedure call returned
this error. Effect Statistics are not being collected from the CPU. 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. Make sure all ASAP Collector and Server processes are at the
same revision level. If the problem persists, contact your support
representative to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1003 Send to COLLECT error: err | err | identifies a file-system error number associated with
the last operation on the file. |
Cause The Monitor did not send aggregate summary messages to the Collector.
The FILEINFO system procedure call returned this error. Effect Data cannot be written to the Collector server. 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. Check if the Collector is installed. Make sure the Monitor and
Collector are both up and running; you can do this by entering STAT
C for the Collector and STAT for the Monitor. Check the network path
connection. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1004 Bad SGP stat^sum reply: type, words | type | identifies the current statistics type. | words | identifies the current statistics words. |
Cause The reply from the Statistics Gathering process (SGP) was not
valid. Effect Statistics could not be collected. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1005 Sync, COLLECT I/O error: err | err | identifies a file-system error number associated with
the last operation on the file. |
Cause Synchronization between the Server and the Collector was not
accomplished. The FILEINFO system procedure call returned this error. Effect No communication occurred between the Server and Collector when
you tried to perform a SYNC operation. 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. Check the network path connection. Make sure the Collector is
up and running. Try the SYNC operation later. |
1006 Sync, delay too long: err | err | identifies a file-system error number associated with
the last operation on the file. |
Cause An attempt to synchronize with the Server failed because the
message request took more than 40 seconds. The system was too busy.
The FILEINFO system procedure call returned this error. Effect Synchronization with the Server was not accomplished. 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. Set the synchronization at a time when the system load is not
heavy. This type of operation can be performed only when the system
load is light. |
1007 Sync, msg too short: iol | iol | is the returned message length. |
Cause An attempt to synchronize with the Server failed because the
length of the request message was too short when the system was performing
an internal check. Effect Synchronization with the Server was not accomplished. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1008 Sync, not required: delta | delta | is the time difference in seconds. |
Cause The clock is already in synchronization. Effect Synchronization does not need to occur again. Recovery This message is informational only. No corrective action is
required. |
1009 Sync, Clock Corrected: delta | delta | is the time difference in seconds. |
Cause The synchronization clock is now set correctly. Effect The synchronization clock is now operating correctly. Recovery This message is informational only. No corrective action is
required. |
1010 Sync, Can’t Set Clock: delta | delta | is the time difference, in seconds. |
Cause The system cannot reset the synchronization clock correctly. Effect Synchronization with the Server is not being accomplished. Recovery Be sure you have the right security to perform the SYNC operation;
you must be in the super user group. Retry the request later. If the
problem persists, contact your support representative to file a case
and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1011 Short request received count, buf, pid | count | is the length of the message, in bytes. | buf | contains the first word of the received request message. | pid | is the requester’s process identification. |
Cause The message received was not recognized because of its short
length. Effect The message could not be processed. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1012 Received shutdown request: pid | pid | is the requester’s process identification. |
Cause A shutdown request was received. Effect The ASAP session will end. Recovery This message is informational only. No corrective action is
required. |
1013 Illegal request received: buf, count, pid | buf | contains the first word of the received request message. | count | is the length of the message, in bytes. | pid | is the requester’s process identification. |
Cause An invalid request was received. Effect The system does not process the request. Recovery Retry the request. If the request is valid request but still
does not work, contact your support representative to file a case
and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1014 startup msg error message: charoffset | charoffset | is the offset of the message that was not recognized. |
Cause The startup message syntax is not correct. Effect The system does not process the startup request. Recovery Reset the startup parameters. Change the startup parameters
in the ASAP configuration file. If the problem persists, contact your
support representative to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1015 Startup Can’t Open TERM | Cause The terminal logfile was not opened. Effect The system could not start up. Recovery Check your configured terminal log file name. The SET TERM command
displays information about your terminal. |
1016 SGP startup msg fail, fe: cpu, err | cpu | is the CPU number. | err | identifies a file-system error number associated with
the last operation on the file. |
Cause The Statistics Gathering process (SGP) did not receive the startup
message. The FILEINFO system procedure call returned this error. Effect The SGP does not start. 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. Check your ASAP configuration file (ASAPCONF) and make sure
the initial parameters are set correctly. |
1017 Can’t create SGP in cpu: cpu, err 0:7,
err 8:15 | cpu | is the CPU number. | err | indicates the outcome of the process creation attempt
where err.0:7 is: |
Cause A Statistics Gathering process (SGP) was not returned in this
CPU, probably because the CPU went down. Effect The SGP is not working in this CPU. Recovery Check to see if the CPU failed. Follow the recommended recovery
procedure for a CPU failure and then retry the request. |
1018 ASAP Version <> TOSVERSION: vers, vers | vers | is the NonStop operating system version. | vers | is the ASAP version. |
Cause The ASAP version is out of sync with the NonStop operating system
version. Effect ASAP does not run. Recovery Check that the ASAP version and the operating system version
are compatible. Retry the request. If the problem persists, contact
your support representative to file a case and provide all relevant
information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1019 A SGP didn’t Shutdown: cpu, pid | cpu | is the CPU number. | pid | is the requester’s process identification. |
Cause The Statistics Gathering process (SGP) did not stop on its node
when you issued a shutdown. Effect The SGP is still running. Recovery Stop the SGP process at the TACL prompt. Enter the command STATUS process-name to see if the process is running. If the
problem persists, contact your support representative to file a case
and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1020 SHUTDOWN Complete! Requester= pid | pid | is the requester’s process identification. |
Cause The system is informing you that the shutdown operation is complete. Effect Your ASAP session will now end. Recovery This message is informational only. No corrective action is
required. |
1021 Trace | Cause The system performed an internal trace. Effect The system is working correctly. Recovery This message is informational only. No corrective action is
required. |
1022 Monitor version started: cpu | version | is the operating system version. | cpu | is the CPU number. |
Cause The system is informing you that the Monitor started successfully. Effect The Monitor is operating. Recovery This message is informational only. No corrective action is
required. |
1023 SGP version started: cpu | version | is the operating system version. | cpu | is the CPU number. |
Cause The Statistics Gathering process (SGP) started successfully. Effect The SGP is running. Recovery This message is informational only. No corrective action is
required. |
1024 $RECEIVE read, FE: err | err | identifies a file-system error. |
Cause A system message was not received or read. The FILEINFO system
call returned this error. Effect The system did not receive the message. 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. Retry your operation, but this time pause for awhile between
commands. For example, the system needs a momentary pause if it cannot
process a shutdown command immediately after a startup command. |
1025 $RECEIVE reply failed, FE: err | err | identifies a file-system error number associated with
the last operation on the file. |
Cause The system could not reply to a message it received from a READUPDATE(X)
call on the $RECEIVE file. Effect The system did not reply to the message. 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. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1026 Sample Missed. SecsSinceLast>RateSecs sec,rate | sec | is the number of seconds expired while trying to write
to the collector. | rate | is the the sample rate configured less 20 percent. |
Cause The ASAP collector process is experiencing queueing problems. Effect The sample for the ASAP SGP was not written to the database. Recovery Partition the ASAP database across multiple disk volumes, or
increase the sample interval. |
1027 Invalid CPU Sysname Received cpu | Cause The ASAP Monitor SGP recieved an incorrect system name. Effect The bad statistics record is discarded. Recovery If the error persists, contact your HP support representative. |
1028 Invalid Sys.Sysname Received | Cause An invalid system name was received Effect CPU statistics for the interval are not sent to the ASAP Collector Recovery If the error persists, contact your HP support representative. |
1029 ASAPACT script file missing err | Cause The Action script file is missing. Effect User-defined actions will not work. Recovery Correct the ACTSHELL file location. |
1030 ACTION startup msg fail, FE err | Cause The startup message to the Action server failed Effect User-defined actions will not work. Recovery Verify that the Action server configuration is correct and restart
the ASAP Monitor. If the error persists, contact your HP support
representative. |
1031 Can't create ACTION Server cpu, err | err | is the error number. | cpu | is the CPU number. |
Cause The ASAP Monitor could not start the Action server. Effect Use- defined actions will not work. Recovery Verify that the Action server configuration is correct and restart
the ASAP Monitor. If the error persists, contact your HP support
representative. |
1032 ACTION Open failed err | Cause The ASAP Monitor could not open the Action server. Effect User-defined actions will not work. Recovery Verify that the Action server configuration is correct and restart
the ASAP Monitor. If the error persists, contact your HP support
representative. |
1033 Send to Action Server failed err | Cause The ASAP Monitor did not get a reply message back from the Action
server. Effect User-defined actions will not work. Recovery Verify that the Action server configuration is correct and restart
the ASAP Monitor. If the error persists, contact your HP support
representative. |
1051 ASAPCPU ECB_Load Error error-text | error-text | is error text returned from the Ecb_loadentities_
procedure. |
Cause The ASAP ecb_loadentities_ procedure returned the specified
error when trying to load the CPU entity. Effect The CPU entity does not load EDL records. Recovery This error might be caused by the EDL settings. For more information
on ASAP EDL, see the ASAP Client Manual. |
1052 ASAPCPU Unable to report Object Thresholds | Cause The ASAP ecb_loadentities_ procedure returned the specified
error when trying to load the system entities. Effect The CPU or PCB or System entities cannot load EDL records. Recovery This error might be caused by the EDL settings. For more information
on ASAP EDL, see the ASAP Client Manual. |
1053 ReadDomain Error: err | err | is the error number returned from the Readdomain procedure. |
Cause The ASAP sgp_readdomain_ procedure returned the specified error
when trying to get the list of system domains to monitor. Effect CPU, ProcessBusy or System monitoring monitors use autodiscovery
of the System entities. All CPU’s busiest processes and entities
are monitored. User-defined objectives cannot be read from the objectives
database. Recovery Make sure that ASAP is configured correctly. For more information
about configuring domains, see the ASAP Extension Manual. If the configuration is correct, contact your HP support representative. |
1056 ASAPCPU Rank metric | metric | is the name of the metric that failed in the SGP_RANKVALUE_
procedure. |
Cause The ASAP SGP_RankValue procedure returned an error when trying
to get the OEM state of affected entity threshold objectives. Effect The affected entity metric in error will have an OEM state value
of 1. Recovery Make sure that ASAP is configured correctly. For more information
about Ranking Objectives, see the ASAP Server Manual. If the configuration is correct, contact your HP support representative. |
1099 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
1100 GETPEEKCONF length bad: length | length | is the length in bytes returned from the get^peek^statistics
system call. |
Cause The Monitor could not retrieve CPU configuration information. Effect A zero value was returned instead of a CPU configuration value. Recovery Check that your NonStop operating system version and ASAP version
are compatible. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1101 GETPEEKSTATS length bad: length | length | is the length, in bytes, returned from the get^peek^statistics
system call. |
Cause The Monitor could not retrieve CPU statistics information. Effect A zero value was returned instead of a CPU statistics value. Recovery Check that your NonStop operating system version and ASAP version
are compatible. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1199 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
1200 Can’t find NetLH = netlh^conf: ldev, paths | ldev | is the logical device number. | paths | is the index to the internal network configuration
table. |
Cause The Expand SGP could not find the path for this Network Line
Handler device in the Network Line Handler configuration file. Effect No statistics were returned for the Network Line Handler. Recovery Check that the Expand Manager is present, up, and running. If
the problem persists, contact your support representative to file
a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1210 Subsystem Mgr New Process Error: err.<0:7>,
err.<8:15> | err | indicates the outcome of the process creation attempt,
where err. 0:7 is: |
Cause The Expand SGP could not create a new subsystem manager process. Effect The subsystem manager process was not created and no network
statistics can be collected. Recovery Check the Subsystem Programmatic Interface (SPI) manager at
$SYSTEM.SYSTEM.0ZEXP to be sure that the Expand Manager is secured
properly. Retry the request later. If the problem persists, contact
your support representative to file a case and provide all relevant
information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1212 Subsystem Mgr Startup Msg Error: err | err | identifies a file-system error number associated with
the last operation on the file. |
Cause The Expand SGP could not pass a startup message to the Subsystem
Manager. The FILEINFO system procedure call returned this error. Effect ASAP and the subsystem cannot communicate. 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. Check that the NonStop Kernel Subsystem Manager is present,
up, and running. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1220 Can’t Create Subsystem Mgr, Error: err | err | identifies a file-system error number associated with
the last operation on the file. |
Cause The Expand SGP could not create a Subsystem Manager. The FILEINFO
system procedure call returned this error. Effect ASAP and the subsystem cannot communicate. 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. Check that the NonStop Kernel Subsystem Manager is secured properly.
If the problem persists, contact your support representative to file
a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1230 Can’t Open Subsystem Mgr, Error: err | err | identifies a file-system error number associated with
the last operation on the file. |
Cause A Subsystem Manager does not exist. The FILEINFO system procedure
call returned this error. Effect ASAP and the subsystem cannot communicate. Recovery For corrective action for the specified error code, see Appendix B. For more detailed
information including recovery actions, see the Guardian Procedure
Errors and Messages Manual. Check that the Expand Manager is up and running. Retry the request.
If the problem persists, contact your support representative to file
a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1231 Can’t Build SPI Request, Error: err | err | identifies a Subsystem Programmatic Interface (SPI)
error: |
Cause The Expand SGP could not build an SPI request buffer. Effect No information is returned by SPI. Recovery Check the NonStop operating system version to make sure all
the SPI routines are installed. These routines include SSPUT, SSGET,
SSINIT, and others. Retry the request. If the problem persists, contact
your support representative to file a case and provide all relevant
information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1232 monitor -> ExpMgr FS Error: err | err | identifies a file-system error number associated with
the last operation on the file. |
Cause A file-system error occurred in communication between the Expand
SGP and the Expand Manager. The FILEINFO system procedure call returned
this error. Effect Subsystem Programmatic Interface (SPI) requests could not be
written to the Expand Manager. Recovery For corrective action for the specified error code, see Appendix B. For more detailed
information including recovery actions, see the Guardian Procedure
Errors and Messages Manual. Check the Expand Manager to see whether it is up and running.
If the problem persists, contact your support representative to file
a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1233 monitor -> ExpMgr SPI Error: err | err | identifies a Subsystem Programmatic Interface (SPI)
error: |
Cause There was an SPI error in communication between the Expand SGP
and the Expand Manager. Effect The Monitor cannot communicate with the Expand Manager. Recovery Check that the Expand Manager is up and running. If the problem
persists, contact your support representative to file a case and provide
all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1234 Expand SGP -> ExpMgr ($ZEXP) Retry Counts: cnt | cnt | is the number of retries. |
Cause The Expand SGP could not communicate with the Expand Manager. Effect ASAP and the subsystem cannot communicate. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1235 Expand SGP -> No path found for Expand line
ldev: ldev | ldev | is the logical device number of the Expand path. |
Cause The Expand SGP could not obtain Level 4 statistics for a multiline
Expand configuration. Effect ASAP does not obtain path statistics from the Expand manager. Recovery This error message is used by HP for problem isolation. If the
problem persists, contact your support representative to file a case
and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1236 Expand SGP -> Can't obtain Path statistics Error:
err, ldev | err | is the SPI error number returned by the $ZEXP process. | ldev | is the logical device number of the Expand path. |
Cause The Expand SGP could not obtain Level 4 statistics for an Expand
line. Effect ASAP does not obtain Level 4 statistics from the Expand Manager. Recovery HP uses this error message for problem isolation. If the problem
persists, contact your support representative to file a case and provide
all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1237 Expand SGP -> Can't obtain Path information
Error: err, ldev | err | is the SPI error number returned by the $ZEXP process. | ldev | is the logical device number of the Expand path. |
Cause The Expand SGP could not obtain Level 2 statistics for an Expand
line. Effect ASAP does not obtain Level 2 statistics from the Expand Manager. Recovery HP uses this error message for problem isolation. If the problem
persists, contact your support representative to file a case and provide
all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1238 Expand SGP -> Can't obtain CSM line stats Error:
err, ldev | err | is the SPI error number returned by the $ZEXP process. | ldev | is the logical device number of the Expand path. |
Cause The Expand SGP could not obtain 6100 line statistics. Effect ASAP does not obtain CSM statistics from the Expand Manager. Recovery HP uses this error message for problem isolation. If the problem
persists, contact your support representative to file a case and provide
all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1239 Expand SGP -> Can't obtain NCSM line stats Error:
err, ldev | err | is the SPI error number returned by the $ZEXP process. | ldev | is the logical device number of the Expand path. |
Cause The Expand SGP could not obtain non-6100 line statistics. Effect ASAP does not obtain non-6100 line statistics from the Expand
Manager. Recovery HP uses this error message for problem isolation. If the problem
persists, contact your support representative to file a case and provide
all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1240 Expand SGP -> Can't obtain IP stats Error: err,
ldev | err | is the SPI error number returned by the $ZEXP process. | ldev | is the logical device number of the Expand path. |
Cause The Expand SGP could not obtain Expand Internet Protocol (IP)
statistics. Effect ASAP does not obtain Expand IP statistics from the Expand Manager. Recovery HP uses this error message for problem isolation. If the problem
persists, contact your support representative to file a case and provide
all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1241 ASAPEXP -> COLLECT send error: err | err | is the returned file-system error number associated
with the last operation on the file. |
Cause ASAPEXP encountered an error while attempting to send a message
to the ASAP Collector. Effect ASAPDEXP cannot complete the request. Recovery The FILEINFO system call returned this error. For corrective
action for the specified error code, see Appendix B, or the Guardian Procedure Errors and Messages
Manual. |
1242 AShort request received: count, buf, pid | count | is the length of the message in bytes. | buf | contains the first word of the request message received. | pid | is the requester’s process identification. |
Cause An unrecognized message was received because of its short length. Effect The message was not processed. Recovery Retry the request. If the problem persists, contact your HP
representative to file a case. |
1243 Illegal request received: count, buf, pid | count | is the length of the message in bytes. | buf | contains the first word of the request message received. | pid | is the requester’s process identification. |
Cause An invalid request was received. Effect The system did not process the request. Recovery Retry the request. If the problem persists, contact your HP
representative to file a case. |
1244 Cannot Obtain NAM stats Error: err, Ldev | err | is the SPI error number returned by the Expand manager
$ZEXP process. | Ldev | is the logical device number of the Expand line. |
Cause The Expand SGP could not obtain Network access statistics for
an Expand line using NAM as the transport. Effect ASAP could not obtain statistics from the Expand manager. Recovery HP uses this error message for problem isolation. Contact your
HP representative to file a case. |
1245 Cannot Obtain ATM stats Error: err, Ldev | err | is the SPI error number returned by the Expand manager
$ZEXP process. | Ldev | is the logical device number of the device of the
Expand line. |
Cause The Expand SGP could not obtain ATM statistics for a Expand
line using ATM as the transport. Effect ASAP could not obtain path statistics from the Expand manager. Recovery HP uses this error message for problem isolation. Contact your
HP representative to file a case. |
1250 Error SET EXPAND PARAM param | param | contains the parameter that caused the problem. |
Cause ASAPEXP detected that an invalid parameter was specified in
the ASAP Conversational Interface (CI) SET EXPAND ON, PARAMETER command. Effect ASAPEXP uses the default values for all parameters. Recovery Ensure that all parameters contained in the ASAP startup file
ASAPCONF are valid; then restart the ASAP Monitor. |
1251 ASAPEXP ECB_Load Error error-text | error-text | is error text returned from the Ecb_loadentities_
procedure. |
Cause The ASAP ecb_loadentities_ procedure returned the specified
error when trying to load the Expand entity. Effect The Expand entity does not load EDL records. Recovery This error might be caused by the EDL settings. For more information
on ASAP EDL, see the ASAP Client Manual. |
1253 ReadDomain Error: err | err | is the error number returned from the Readdomain procedure. |
Cause The ASAP sgp_readdomain_ procedure returned the specified error
when trying to get the list of Expand domains to monitor. Effect Expand monitoring monitors all configured Expand lines. Recovery Make sure that ASAP is configured correctly. For more information
about configuring domains, see the ASAP Extension Manual. If the configuration
is correct, contact your HP support representative. |
1254 Load Objectives Error: err, Ldev | err | is the error number returned from the Load^Objectives
procedure. | Ldev | is the logical number of the Expand line that failed. |
Cause The ASAP Load^Objectives procedure returned the specified error
when trying to get the list of Expand threshold objectives. Effect Expand uses autodiscovery for all Expand line handlers. All
Expand lines are monitored. User-defined objects cannot be read from
the objectives database. Recovery Make sure that ASAP is configured correctly. For more information
about Ranking Objectives, see the ASAP Server Manual. If the configuration
is correct, contact your HP support representative. |
1255 Unknown Transport not supported err, Ldev | err | is the error number returned from the Expand Manager. | Ldev | is the logical number of the Expand line that failed. |
Cause An unknown transport was detected that is not currently supported
by the Expand SGP. Effect Expand monitoring does occur on the ldev using the unkown transport. Recovery HP uses this error message for problem isolation. Contact your
HP representative to file a case. |
1256 GetObjectives Error: err, Ldev | err | is the error number returned from the SGP_GETOBJECTIVES_
procedure. | Ldev | is the logical number of the Expand line that failed. |
Cause The ASAP sgp_Getobjectives procedure returned the specified
error when trying to get the list of Expand threshold objectives. Effect Expand monitoring does not begin. Recovery Make sure that ASAP is configured correctly. For more information
about Ranking Objectives, see the ASAP Server Manual. If the configuration
is correct, contact your HP support representative. |
1257 ASAPEXP Rank Values error= err,
error-detail | err | is the error number returned from the SGP_RankValues
procedure. | error-detail | is the error detail number returned from the SGP_RankValues
procedure. |
Cause The ASAP sgp_rankvalues procedure returned the specified error
when trying to rank Expand threshold objectives. Effect The Expand objectives for all ranked objectives will be equal
to a OEM state value of 1 for the sample period. Recovery Make sure that ASAP is configured correctly. For more information
about Ranking Objectives, see the ASAP Server Manual. If the configuration
is correct, contact your HP support representative. |
1266 ASAPEXP Bad Stats Received ldev | ldev | is the logical number of the device. |
Cause The ASAP Expand SGP encountered a bad statistics record. Effect The bad statistics record is discarded. Recovery If the error persists, contact your HP support representative. |
1299 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
1300 GetPeekPCBs Returns error: err | err | is an error returned from the GetPeekPCBs system procedure
call. |
Cause The system could not obtain process statistics. Effect A zero value is returned instead of a process statistics value. Recovery Check that your NonStop operating system version and ASAP version
are compatible. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1301 ProcessInfo Returns error: err, pin# | err | indicates the outcome of the PROCESSINFO call: | pin# | is the process identification number. |
Cause The system could not obtain the program file name of the process.
This is a result of a process going away between a GETPEEKPCBs call
and a PROCESSINFO call. Effect The process information does not include a related program file
name. Recovery This message is informational only. No corrective action is
required. |
1302 Unable to get device name: err, pin# | err | indicates the outcome of a PROCESSINFO call: | pin# | is the process identification number. |
Cause The system could not obtain the device name of the process.
The process probably went away before the device name was obtained. Effect The process information does not include a related device name. Recovery This message is informational only. No corrective action is
required. |
1303 pin:ProcessTime delta:Sampletime delta in .1
sec: pin#, dpt, dst | pin# | is the process identification number. | dpt | is the delta of the process time for this PIN. | dst | is the delta of the sample time for this PIN. |
Cause ASAP detected a 100 percent process control block (PCB) busy
state, possibly because of a NonStop operating system internal interface
failure. Effect The PCB busy information is suspect. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1304 ProcessTime delta too big:last 2 INTs in .1
sec: pin#, dpt1, dpt2 | pin# | is the process identification number. | dpt1 | is the third word of the process delta time for this
PIN. | dpt2 | is the last word of the process delta for this PIN. |
Cause ASAP detected a 100 percent process control block (PCB) busy
state, possibly because of a NonStop operating system internal interface
failure. Effect The PCB busy information is suspect. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1305 Pin:This_ProcessTime:Last_ProcessTime in 10
sec: pin#, pt1, pt2 | pin# | is the process identification number. | pt1 | is the total process time of this PIN at the current
sample time. | pt2 | is the total process time of this PIN at the last
sample time. |
Cause ASAP detected a 100 percent process control block (PCB) busy
state, possibly because of an internal NonStop operating system interface
failure. Effect The PCB busy information in the sample might be distorted. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1306 Pin:Alive but No PCB:priority:Last_PTime in
.1 sec: pin#, pri, pt2 | pin# | is the process identification number. | pri | is the process priority. | pt2 | is the total process time of this PIN at the last
sample time. |
Cause The process was alive but statistics were not returned, possibly
due to an internal NonStop operating system error. Effect The process control block (PCB) busy information in the sample
might be distorted. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1307 Process Not in the Sample Data: pin#, which | pin# | is the process identification number. | which | indicates array information: |
Cause The process you specified is not in the internal sample array.
This is an internal error. Effect Process control block (PCB) information cannot be returned. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1308 bad SMON Subsampling | Cause Internal ASAP algorithms are detecting bad subsampling. Effect Subsample data is not being reported for this sample interval,
or the PCBSTATS data is inaccurate during this sample interval. Recovery The Monitor is designed to readjust itself and recover. However,
if the problem persists, contact your support representative to file
a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1309 Unable to collect PCB statistics, error: err | err | indicates the outcome of a PROCESSINFO system procedure
call and returns one of these values: |
Cause The Monitor could not collect process control block (PCB) information.
The FILEINFO system procedure call returned this error. Effect A zero value is returned rather than the PCB statistics values. Recovery For corrective action for the specified error code, see Appendix B. For more detailed
information including recovery actions, see the Guardian Procedure
Errors and Messages Manual. Retry your request later. If the problem persists, contact your
support representative to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1399 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
1400 Can’t get processor type info, Error:
err | err | indicates the outcome of a CPU_GETINFOLIST_ system
procedure call and returns one of these values: |
Cause The Monitor could not retrieve the CPU processor type. The FILEINFO
system procedure call returned this error. Effect A CPU processor type value is not returned. Recovery For corrective action for the specified error code, see Appendix B. For more detailed
information including recovery actions, see the Guardian Procedure
Errors and Messages Manual. Check that your operating system version and ASAP version are
compatible. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1401 Can’t Call CPU_GETINFOLIST_, Error: err
| err | indicates the outcome of a CPU_GETINFOLIST_ system
procedure call and returns one of these values: |
Cause The Monitor could not retrieve CPU configuration information
or statistics for the specified processor. The CPU_GETINFOLIST_ system
procedure call returned this error. Effect A zero value is returned instead of CPU configuration and statistics
information. Recovery For corrective action for the specified error code, see Appendix B. For more detailed
information including recovery actions, see the Guardian Procedure
Errors and Messages Manual. Check that your operating system version and ASAP version are
compatible. If the problem persists, contact your support representative
to file a case. When contacting your support representative, provide
all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
1499 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
1700 ASAPDSK NonStop Kernel Must be release D10 or
Greater | Cause ASAPDSK cannot be started. Effect ASAPDSK is not operating. Recovery Shut down the ASAPMON, set disk to OFF, and restart the ASAP
Monitor. |
1701 ASAPDSK Measure Access Denied, not Super err | err | is the Measure error returned from the Measure subsystem. |
Cause Measure subsystem access is for the super-user group only. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery Check the following and change the security level to NUNU: $system.sysxx.measctl; $system.sysxx.measfh; $system.sysxx.measmon. |
1702 ASAPDSK Measure Allocate Segment Error err | err | is the Measure error returned from the Measure subsystem. |
Cause The Measure subsystem returned a negative reply to the Measopen
procedure. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery ASAPDSK will reopen Measure during the next sample period. If
the error persists, stop the Measure subsystem. If the object file
(ASAPDSK) is owned by the super-user group, the Disk Statistics Gathering
process (SGP) will restart the Measure subsystem during the next sample
period. If the problem persists, contact your HP representative to
file a case. |
1703 ASAPDSK ASAPmeas file in use err | err | is the Measure error returned from the Measure subsystem. |
Cause The Measure subsystem has a measurement data file with the same
name as ZASPxxx, where xxx is the ASAP ID. The Disk Statistics Gathering
process (SGP) could not delete it. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery Close the file through MEASCOM. The disk SGP will attempt to
start the measurement during the next sample period. You can also
use the ASAP Conversational Interface (CI) and specify another volume,
subvolume, or both. Once you specify another location, restart the
ASAP Monitor. An example of the ASAP CI command is: SET ASAPDSK on,PARAM "$vol.subvol"
|
|
1704 Set Disk param VOLUME/SUBVOL to another location | Cause The Measure subsystem has a measurement data file with the same
name as ZASPxxx, where xxx is the ASAP ID. The Disk Statistics Gathering
process (SGP) could not delete it. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery Use the ASAP Conversational Interface (CI) to set ASAPDSK with
a different volume or subvolume than was previously specified. If
you used the default, try a volume other than $system. |
1705 ASAPDSK MEASFH Trapped err | err | is the Measure error returned from the Measure subsystem. |
Cause The MEASFH process has trapped out. Effect ASAPDSK cannot obtain disk counters. Even though disk utilization
samples cannot be made, the disk device status information is still
valid. Recovery Specify a different CPU for the MEASFH process by using the
ASAP Conversational Interface (CI) to specify CPU cpu-number in the
SET DISK command; then restart the ASAP Monitor. |
1706 ASAPDSK Incompatible Measfh Release err | err | is the Measure error returned from the Measure subsystem. |
Cause An incompatible MEASFH release was found on $SYSTEM.SYSxx. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery Install the correct MEASFH release on $SYSTEM.SYSxx and restart
the ASAP Monitor. |
1707 ASAPDSK Measfh Ext Seg Error err | err | is the Measure error returned from the Measure subsystem. |
Cause The MEASFH process could not obtain the extended segment size
in the CPU. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery Specify a different CPU for the MEASFH process by using the
ASAP Conversational Interface (CI) to specify CPU cpu-number in the
SET DISK command; then restart the ASAP Monitor. |
1708 ASAPDSK Measure Data File In Use err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK could not create a Measure data file. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery Stop and delete the measurement named ZASPxxx, where xxx is
the ASAP ID. Use the Measure interface MEASCOM. |
1709 ASAPDSK Measure Data File In Use err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK could not start a measurement. Maximum measurements
were reached. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery If possible, stop and delete unnecessary measurements. Restart
the ASAP Monitor once the Measure subsystem has fewer than 64 measurements
configured. |
1710 ASAPDSK Measctl Pool Space Error err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK could not start a measurement. The pool space is full
for code range addresses in the MEASCTL process. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery If possible, stop and delete unnecessary measurements. Restart
the ASAP Monitor once the Measure subsystem has fewer than 64 measurements
configured. |
1711 ASAPDSK Measure CPU Memory error err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK could not start a measurement in the specified CPU or
in the default CPU (CPU 0). Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery Specify a different CPU for the MEASFH process by using the
ASAP Conversational Interface (CI) to specify CPU cpu-number in the
SET DISK command; then restart the ASAP Monitor. |
1712 ASAPDSK Measctl Resources Exceeded err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK could not start a measurement because the MEASCTL process
reached its maximum resources. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery If possible, stop and delete unnecessary measurements. Restart
the ASAP Monitor once the Measure subsystem has fewer than 64 measurements
configured. |
1713 ASAPDSK Measctl Resources Exceeded err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK could not start a measurement because the MEASCTL process
reached its maximum internal counter space. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery If possible, stop and delete unnecessary measurements. Restart
the ASAP Monitor once the Measure subsystem has fewer than 64 measurements
configured. |
1715 ASAPDSK Error SET DISK PARAM CPU xx
cpu | cpu | is the CPU number selected. |
Cause The Disk Statistics Gathering process (SGP) could not start
a measurement in the specified CPU. Effect ASAPDSK starts the measurement in the CPU where the ASAPDSK
process is running. Recovery Informational message only; no corrective action is needed. |
1720 ASAPDSK ZASPXXX started.(XXX is the configured
ASAP ID) | Cause ASAPDSK successfully started a measurement. Effect ASAPDSK is operating. Recovery Informational message only; no corrective action is needed. |
1721 ASAPDSK ZASPXXX NOT started.(XXX is the configured
ASAP ID) | Cause ASAPDSK could not start a measurement. Effect ASAPDSK cannot obtain disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery Check for previous ASAP log messages from ASAPDSK and make the
appropriate corrections. |
1722 ASAPDSK restarted err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK restarted the measurement. Effect ASAPDSK could not obtain disk counters during a sample interval.
Possibly the Measure subsystem was stopped and restarted. Disk statistics
are set to null for the sample interval when ASAPDSK could not obtain
the DP2 counters. Recovery Informational message only; no corrective action is needed. |
1723 ASAPDSK started MEASCTL IN CPU
cpu | cpu | specifies the CPU number. |
Cause The Disk Statistics Gathering process (SGP) started the Measctl
process in a CPU that did not have the Measctl process running. Effect ASAPDSK starts Measctl in the CPU. Recovery Informational message only; no corrective action is needed. |
1730 Error SET DISK PARAM param | param | contains the parameter that caused the problem. |
Cause ASAPDSK detected an invalid parameter in the SET DISK ON, PARAMETER
command. Effect ASAPDSK used the default values for all parameters. Recovery Ensure that all parameters in the ASAP startup file ASAPCONF
are valid; then restart the ASAP Monitor. |
1735 ASAPDSK -> COLLECT send error: err | err | is the file-system error number associated with the
last operation of the file. |
Cause ASAPDSK encountered an error while attempting to send a message
to the ASAP Collector. The FILEINFO system call returned this error. Effect ASAPDSK cannot complete the request. Recovery For corrective action for the specified error, see Appendix B, or the Guardian
Procedure Errors and Messages Manual. |
1742 ASAPDSK DCT access error ldev | ldev | is the logical number of the device. |
Cause The Disk Statistics Gathering process (SGP) could not access
the device control table. Effect ASAPDSK cannot collect disk statistics. Recovery Contact your HP representative to file a case. |
1743 ASAPDSK cannot restart measurement err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK could not restart its measurement. Effect ASAPDSK could not obtain disk counters during a sample interval.
Disk statistics are set to null for the sample interval when ASAPDSK
could not obtain DP2 counters. Recovery Check the ASAP log for previous ASAPDSK messages and make the
necessary corrections. For corrective action for the specified error,
see the Measure Reference Manual. |
1744 ASAPDSK Disk device inaccessible
ldev,ctrl | ldev | is the logical number of the device. | ctrl | is the controller number in decimal notation. |
Cause The Disk Statistics Gathering process (SGP) could not access
the device. Effect ASAPDSK cannot collect disk counters. Disk device status information
is valid when ASAPDSK cannot obtain the disk counters. Recovery Contact your HP representative to file a case. |
1745 ASAPDSK Optical Disk statistics not collected | Cause The Disk Statistics Gathering process (SGP) will not collect
statistics on configured optical disk devices. Effect ASAPDSK will not report optical disk statistics. Recovery This message is informational only. No corrective action is
needed. |
1747 ASAPDSK unable to stop Disk Measurement err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK could not stop its measurement. Effect ASAPDSK could not stop the measurement named ZASPxxx where xxx
is the ASAP ID. Recovery Stop and delete the measurement named ZASPxxx where xxx is the
ASAP ID. Use the Measure interface MEASCOM. |
1748 ASAPDSK Disk Measurement stopped | Cause The ASAPMON process stopped ASAPDSK. Effect ASAPDSK stops its measurement. Recovery This message is informational only. No corrective action is
required. |
1749 ASAPDSK Disk Measurement stopped err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPDSK has an interface problem with the Measure subsystem. Effect ASAPDSK could not obtain disk counters during a sample interval.
Disk statistics are set to null for the sample interval when ASAPDSK
could not obtain DP2 counters. Recovery Check the ASAP log for previous ASAPDSK messages and make the
appropriate corrections. For corrective action for the specified error,
see the Measure Reference Manual. If the problem
persists, contact your HP representative to file a case. |
1751 ASAPDSK ECB_Load Error error-text | error-text | is the error text returned from the Ecb_loadentities_
procedure. |
Cause The ASAP ecb_loadentities_ procedure returned the specified
error when trying to load the Disk entity. Effect The Disk entity does not load EDL records. Recovery This error might be caused by the EDL settings. For more information
on ASAP EDL, see the ASAP Client Manual. |
1753 ASAPDSK sgp_readdomain_ Error err | err | is the error number returned from the SGP_ReadDomain_
procedure. |
Cause The ASAP sgp_readdomain_ procedure returned the specified error
when trying to get the list of Disk domains to monitor. Effect Disk monitoring of all devices will occur. Recovery Make sure that ASAP is configured correctly. For more information
about configuring domains, see the ASAP Extension Manual. If the configuration
is correct, contact your HP support representative. |
1754 Load Objectives Error: err, Ldev | err | is the error number returned from the Load^Objectives
procedure. | Ldev | is the logical number of the Disk device that failed. |
Cause The ASAP Load^Objectives procedure returned the specified error
when trying to get the list of Disk threshold objectives. Effect The Disk SGP monitors all configured disk devices. Recovery Make sure that ASAP is configured correctly. For more information
about Ranking Objectives, see the ASAP Server Manual. If the configuration
is correct, contact your HP support representative. |
1756 GetObjectives Error err, Ldev | err | is the error number returned from the SGP_GETOBJECTIVES_
procedure. | Ldev | is the logical number of the Disk device that failed. |
Cause The ASAP sgp_Getobjectives procedure returned the specified
error when trying to get the list of Disk threshold objectives. Effect Disk monitors all configured disk devices. Recovery Make sure that ASAP is configured correctly. For more information
about Ranking Objectives, see the ASAP Server Manual. If the configuration
is correct, contact your HP support representative. |
1757 ASAPEDSK Rank Values error= err, error-detail | err | is the error number returned from the SGP_RankValues
procedure. | error-detail | is the error detail number returned from the SGP_RankValues
procedure. |
Cause The ASAP sgp_rankvalues procedure returned the specified error
when trying to rank Disk threshold objectives. Effect The Disk objectives for all ranked objectives will be equal
to a OEM state value of 1 for the sample period. Recovery Make sure that ASAP is configured correctly. For more information
about Ranking Objectives, see the ASAP Server Manual. If the configuration
is correct, contact your HP support representative. |
1766 ASAPDsk Bad Stats Received ldev | ldev | is the logical number of the device. |
Cause The ASAP Disk SGP encountered a bad statistics record. Effect The bad statistics record is discarded. Recovery If the error persists, contact your HP support representative. |
1799 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
1801 File open error: fname, FE: fe | fname | is the name of the file that could not be opened. | fe | is the file-system error number. |
Cause An error occurred opening the specified file. To determine the
cause of this problem, see Appendix B. Effect The specified file is not opened. If the event is written by
ASAPXSGP, it has failed to open and load the ASAPX configuration file
(ASAPXCNF). ASAPXSGP will stop. If the event is written by ASAPXMON,
it has failed to open the domain table, the objectives table, $RECEIVE,
or an extended memory segment file. ASAPXMON will continue processing
to the best of its ability even though it has lost a resource. Recovery Correct the file-system error and retry the operation. |
1802 File secure error: fname, FE: fe | fname | is the segment file name. | fe | is the file-system error number. |
Cause An error occurred while attempting to resecure an ASAPX extended
memory segment file. To determine the cause of this problem, see Appendix B. Effect ASAPXMON could not resecure an extended segment file. It attempts
to resecure its extended segment file so that all local processes
can access it. Failure to properly resecure a segment file can result
in application processes being excluded from access to shared memory. Recovery Correct the file-system error and restart ASAPX. |
1803 Segment allocation error: fname, Er: error,
error^detail | fname | is the name of the segment file. | error | is the error number returned by the segment_allocate_
procedure. | error^detail | is the detailed error number, if any, returned by
the segment_allocate_ procedure. |
Cause An error occurred attempting to allocate an extended memory
segment. To determine the cause of this problem, see a description
of errors returned by the segment_allocate_ procedure. Effect ASAPXMON or ASAPXSGP failed in its attempt to allocate a shared
memory segment. The process will terminate. Recovery Correct the problem and restart ASAPX. |
1804 File read error: fname, FE: fe | fname | is the name of the file. | fe | is the file-system error number. |
Cause An error occurred while reading from the file. To determine
the cause of this problem, see Appendix B. Effect The specified file is not read. If the event is written by ASAPXSGP,
it has failed to read the ASAPX configuration file (ASAPXCNF). ASAPXSGP
will stop. If the event is written by ASAPXMON, it has failed to read
the domain table, the objectives table, $RECEIVE, or an extended memory
segment file. ASAPXMON will continue processing to the best of its
ability even though it has lost a resource. Recovery Correct the file-system error and retry the operation. |
1805 File write error: fname, FE: fe | fname | is the name of the file. | fe | is the file-system error number. |
Cause An error occurred while writing from the file. To determine
the cause of this problem, see Appendix B Effect The specified file could not be updated. ASAPXMON failed to
update the domain table. It will continue processing to the best of
its ability even though it has lost a resource. Recovery Correct the file-system error and retry the operation. |
1806 Duplicate memory slot for domain: domain, Dmn#:
domain number | domain | is the name of the domain that cannot be restarted. | domain number | is the number of the domain that is already restarted. |
Cause ASAPX detected duplicate Domain table entries for the same memory
slot location. Only the first domain is restarted; all others cause
this error message to be generated. This error should not occur, although
it might after CPU failures and subsequent loss of shared memory. Effect ASAPX could not restart a domain because its domain record referred
to a domain number that is already in use. The domain is not restarted. Recovery If the domain ASAPX restarted is not the correct one, manually
remove the domain using the ASAPX REMOVE command and restart ASAPX. |
1807 Domain name error in record: domain, Dmn#: domain
number | domain | is the domain name found to be in error. | domain number | is the domain number of the domain found to be in
error. |
Cause The Domain table has been corrupted. ASAPX detected an error
in the domain name field for the specified domain in the Domain table. Effect While attempting to reload domains at startup, ASAPX found an
error in the name of a domain. The domain is not restarted. Recovery Manually remove the domain in question. If more than one domain
has been corrupted: Make sure that all application processes are running and
that all their domains are registered, or shut down all application
processes using ASAPX. If an application process is left executing,
one must be executing in each processor with at least one registered
domain. To verify this, run a FILEINFO command against the ASAPX swap
subvolume or subvolumes. Verify that all shared memory segment files
are open. These files are named Zasapid Cn where asap id is the ASAP
ID from the ASAPCONF file, and n is the CPU number. If one shared
memory segment file is open, they all must be open. Stop ASAP using the ASAP SHUTDOWN command. Enter the ASAPX CLEANUP DOMAINS command to purge the Domain
table. Restart ASAP with the ASAP START command. If the application
processes remained executing, ASAPX will completely rebuild the Domain
table from shared memory. If the applications were shut down, the
Domain table is rebuilt over time as they restart and register with
ASAPX.
|
1808 Objectives load failed, domain: domain, Dmn#:
domain number | domain | is the name of the domain for which the objectives
load process failed. | domain number | is the number of the domain for which the objectives
load process failed. |
Cause ASAPX detected an error trying to load objectives for domain
domain. To determine the cause of this event, see the accompanying
file-system error message. Effect The correct objectives are not loaded for the domain. Recovery Correct the file-system error and retry the operation. |
1809 Registered process active: pname, Pin: pin | pname | is the process name of the process found to be active. | pin | is the PIN number of the process found to be active. |
Cause The application process was restarted before ASAPX after a processor
or system failure. ASAPX detected that it needed to rebuild the shared
memory slot for a domain but found the process that registered the
domain was executing at the time. Effect ASAPX does not rebuild the shared memory slot for the domain
because an attempt to do so might cause MUTEX problems. Recovery First, stop the process in question. Second, restart ASAPX.
Finally, restart the process. |
1810 Domain rebuilt from memory: domain, Dmn#: domain
number | domain | is the name of the domain that was rebuilt. | domain number | is the number of the domain that was rebuilt. |
Cause The Domain table was corrupted, possibly by entering the ASAPX
CLEANUP DOMAINS command while application processes continued to execute.
ASAPX has successfully rebuilt a Domain table entry for a domain.
This indicates possible corruption of the Domain table. Effect ASAPX has successfully rebuilt a Domain table entry for a domain.
The record for the domain is now correct. Recovery None. ASAPX successfully rebuilt the domain. |
1811 Could not obtain process handle pname, FE: fe | pname | is the name of the process for which ASAPX could not
obtain the process handle. | fe | is the file-system error number. |
Cause ASAPX could not obtain the process handle of process pname.
To determine the cause of this problem, see Appendix B. Effect ASAPX might report an incorrect status for a domain. Recovery Correct the file-system error and retry the operation. |
1812 Begintransaction error: fname, Er: begintrans | fname | is the name of the file that ASAPX was attempting
to update. | begintrans | is the error returned from BEGINTRANSACTION. |
Cause ASAPX could not obtain a transaction ID from TM/MP in an attempted
operation against file fname. To determine the cause of this problem,
see a description of BEGINTRANSACTION procedure error numbers. Effect ASAPX could not access the Domain table. This causes domain
registration and removal failures. Recovery Correct the TM/MP error and retry the operation. |
1814 Illegal request on $receive: rbuf[0] | rbuf[0] | is the first word of the illegal buffer received. |
Cause An ASAPX process received an illegal request on $RECEIVE. Another
process has inadvertently written to an ASAPX process or a possible
versioning problem exists. Effect None. ASAPX ignores the illegal request and continues processing. Recovery None. The ASAPX process rejects the request. If this indicates
a versioning problem, obtain the correct version of all ASAPX object
modules. |
1815 Registration rejected, max domains: domains,
Max: max | domains | is the number of domains currently registered in that
processor. | max | is the maximum number of allowed registrations in
the processor. |
Cause The maximum number of domains are already registered in the
processor. ASAPX cannot register the domain in the processor in which
it is attempting to register because the maximum number of domains
are already registered in that processor. Effect ASAPX cannot register the domain in the processor in which it
is attempting to register. Recovery Register the domain in another processor. |
1816 Cannot restart domain, Dmn in use: domain, Dmn#:
domain number | domain | is the name of the domain that cannot be restarted. | domain number | is the number of the domain that is already is use. |
Cause ASAPX cannot restart domain domain because its slot is already
in use by another domain. Effect The domain found in the domain table cannot be restarted. Recovery Manually remove the domain using the ASAPX REMOVE command; then
reregister the domain with ASAPX, or stop the process using the slot
and restart the domain. |
1817 Terminated COMMIT, excessive errors: error^cnt | error^cnt | is the number of errors found. |
Cause ASAPX terminated its commit operation because of excessive errors
trying to read the Objectives table. To determine the cause of this
event, see the accompanying file-system error message. Effect ASAPX cannot reload objectives for all domains. It terminates
the COMMIT operation to avoid event flooding. Recovery Correct the file-system errors and retry the operation. |
1818 Command invalid in: fname, Line: number | fname | is the name of the configuration file containing the
invalid command. | number | is the line number in error. |
Cause ASAPX detected an invalid command in the configuration file
used to start ASAPX. Effect ASAPXSGP stops after writing this event message. The ASAPX subsystem
is not started. Recovery Run ASAPX against the configuration file to determine the invalid
command, correct the command; then restart ASAPX. |
1819 DATAITEM not contiguous: fname | fname | is the name of the configuration file containing the
DATAITEM definitions that are not contiguous. |
Cause (ASAP Release 1 only) ASAPX detected that the DATAITEM definitions
in fname are not contiguous. An error exists in the ASAPX configuration
file. Effect ASAPXSGP stops because of the inconsistent configuration. ASAPX
is not started. Recovery Redefine the DATAITEMS in fname to use a contiguous sequence
of numbers starting with zero. |
1820 DATAITEM definition(s) not defined: fname | fname | is the name of the configuration file containing the
DATAITEM definitions that are not defined. |
Cause (ASAP Release 1 only) ASAPX did not find DATAITEM definitions
in fname. An error has been detected in the ASAPX configuration file. Effect ASAPXSGP stops because of the inconsistent configuration. ASAPX
is not started. Recovery Add at least one SET DATAITEMS command to define at least one
DATAITEM to the ASAPX configuration file. |
1821 METRIC definitions not contiguous: fname | fname | is the name of the configuration file containing the
METRIC definitions that are not contiguous. |
Cause (ASAP Release 1 only) An error exists in the ASAPX configuration
file. ASAPX detected that the METRIC definitions in fname are not
contiguous. Effect ASAPXSGP stops because of the inconsistent configuration. ASAPX
is not started. Recovery Redefine the METRICS in fname to use a contiguous sequence of
numbers starting with zero. |
1822 METRIC definitions(s) not defined: fname | fname | is the name of the configuration file containing the
METRIC definitions that are not defined. |
Cause (ASAP Release 1 only) An error exists in the ASAPX configuration
file. ASAPX has detected that the METRIC definitions in fname are
not defined. Effect ASAPXSGP stops because of the inconsistent configuration. ASAPX
is not started. Recovery Add at least one SET METRICS command to define at least one
METRIC to the ASAPX configuration file. |
1823 Detected that its server stopped: pname | pname | is the name of the process that stopped. |
Cause ASAPX detected that one of its ASAPXMON servers stopped. Someone
stopped the process. Effect None, unless this problem recurs. If it does, a problem might
exist in the ASAP Monitor (ASAPXMON). Recovery None. ASAPX automatically restarts the process. |
1824 Detected that its server abended: pname | pname | is the name of the process that abended. |
Cause An APPXMON process abended. ASAPX detected that one of its ASAPXMON
servers abended. Effect None, ASAPXSGP restarts the failed process. Recovery Find the SAVEABEND file produced by the abend of the APPXMON
process and send it to the Global NonStop Solution Center (GNSC) for
analysis. |
1825 Processor getinfo failure: cpu, fe | cpu | is the number of the CPU where the error occurred. | fe | is the file error that occurred. |
Cause ASAPX could not obtain information from a processor. To determine
the cause of this problem, see Appendix B. Effect Applications executing in cpu will not be able to participate
in the ASAPX system. Recovery Correct the file-system error and retry the operation. |
1826 Requires TNS/R and D30.02+ NSK | Cause The processor or NonStop operating system version is earlier
than D30.02. ASAPX determined that it cannot execute in a processor
because the processor or NonStop operating system versions do not
support shared flat extended memory segments. Effect ASAPX cannot execute. Recovery Install a TNS/R processor and the D30.02 NonStop operating system
or later. |
1827 File create error: fname, FE: fe | fname | is the name of the file that could not be created. | fe | is the file-system error number. |
Cause An error occurred creating the file fname. To determine the
cause of this problem, see Appendix B. Effect ASAPXSGP stops without starting ASAPX because it could not create
the Domain or the Objectives table. Recovery Correct the file-system error and retry the operation. |
1828 Error obtaining NSK MOM: pname, FE: fe | pname | is the name of the process for which ASAPX could not
obtain the NonStop operating system MOM identifier. | fe | is the file-system error number. |
Cause ASAPX could not get the NonStop operating system MOM identifier
for one of its servers. To determine the cause of this problem, see Appendix B. Effect ASAPXSGP will not receive process stop or abend messages for
the ASAPXMON process. Recovery Correct the file-system error and retry the operation. |
1829 Server create error: pname, FE: fe | pname | is the name of the process that ASAPX could not create. | fe | is the file-system error number. |
Cause An error occurred creating the ASAPX process pname. To determine
the cause of this problem, see Appendix B. Effect ASAPXSGP failed to start an ASAPXMON process in one of the processors.
ASAPX is not enabled for that processor. Recovery Correct the file-system error and retry the operation. |
1830 Server I/O error: pname, FE: fe | pname | is the name of the ASAPX process that the originator
of the message had trouble communicating with. | fe | is the file-system error number. |
Cause An error occurred communicating with ASAPX process pname. To
determine the cause of this problem, see Appendix B. Effect ASAPXSGP did not receive a complete set of statistics from the
ASAPXMON process for this statistics interval. Recovery Correct the file-system error and retry the operation. |
1831 Domain rebuild failed: domain, Dmn#: slot | domain | is the name of the domain that could not be rebuilt. | slot | is the number of the domain that could be corrupted. |
Cause ASAPX failed to rebuild the domain where memory or the Domain
table is corrupted. Something prevented ASAPX from restoring a domain.
Possibly an error allocating shared memory or an error accessing the
Domain table. Effect The domain is not automatically restarted. Recovery Manually remove the domain in question and reregister it, or
fix the file system or segment allocation error associated with this
event. |
1832 error-text | error-text | is the text of the actual EDL error (it can vary). |
Cause The EDL Compiler returned an error to ASAPX indicating a syntax
error in a user-defined EDL file. Effect Some user-defined entities are not loaded. ASAPX stops loading
EDL at the point where the error occurred. Recovery Correct the EDL error, then restart ASAPX. |
1833 ASAP ERR component Error in formula: ename, aname | component | is the ASAP component affected by the EDL error. | ename | is the name of the entity as defined in EDL. | aname | is the name of the attribute as defined in EDL. |
Cause There is a formula definition error in a user-defined EDL file. Effect ASAPX produces a zero value for the calculation. Recovery Correct the MetricRule formula error and then restart ASAPX. |
1834 ASAP ERR component, Unsupported Type: fname | component | is the ASAP component affected by the EDL error. | fname | is the name of the file in error. |
Cause The ASAPX SGP received an unsupported record type from one of
the ASAPXMON processes. There is a corrupted reply buffer or a version
mismatch between ASAPXSGP and ASAPXMON. Effect ASAPX might not report data for all domains. Recovery Make sure ASAPXSGP and ASAPXMON are the same version. Watch
the problem for at least three intervals to see if it persists. If
it does, contact HP Support for assistance. |
1835 Aggregation rejected, max aggregates: domain, Max: max | domain | is the name of the first domain that failed aggregation. | max | is the maximum number of allowed aggregate domains
in the processor. |
Cause The maximum number of aggregate domains already exist in the
processor. Effect ASAPX cannot aggregate any more domains in the processor. Recovery Modify the SET AGGREGATE statements in ASAPXCNF to product fewer
aggregate domains, register application domains in another processor,
or use the SET MAXAGGREGATES command in the ASAPXCNF file to increase
the number of allowed aggregate domains. |
1860 Non-SET commands not executed: fname | fname | is the name of the ASAPXCNF file that contains non-SET
commands. |
Cause ASAPX found non-SET commands in the ASAPXCNF file. Effect None. ASAPX ignores the command. Recovery ASAPX ignores all non-SET commands in the ASAPXCNF file. To
eliminate this warning message, remove the non-SET commands from the
file. |
1861 Resetting file security: fname | fname | is the name of the segment file that ASAPX needs to
resecure. |
Cause ASAPX found that the security on a segment file was incorrect.
This message is a warning that the ASAPXMON is going to stop. Restart
it to properly reset the file’s security. Effect ASAPXMON will stop and restart to secure the segment file properly. Recovery ASAPX automatically corrects the security problem. To eliminate
this warning message, change the default NonStop operating system
security string for the user ID that starts ASAP to AAnn. |
1862 No SET NAMEFILE command found in: fname | fname | is the name of the ASAPXCNF file. |
Cause (ASAP Release 1 only) ASAPX did not find a SET NAMEFILE command
in the ASAPXCNF file. This could result in reserved names being entered
as domain names and could yield unexpected results in ASAP, OEM, and
OIL. Effect ASAPX is not affected; however, using reserved names as domain
names can cause a myriad of problems in ASAP, OEM, and OIL. Recovery ASAPX warns about this problem and continues processing normally.
To eliminate this warning message, add a SET NAMEFILE $ISV Volume.ZASAPX.ZASPXNAM
command to ASAPXCNF. |
1863 EDITREAD error on NAMEFILE: fname, Er: error | fname | is the name of the ASAP reserved names file. |
Cause (ASAP Release 1 only) ASAPX encountered an EDITREAD or EDITREADINIT
error while processing the ASAP reserved names file. This could result
in reserved names being entered as domain names and could yield unexpected
results in ASAP, OEM, and OIL. Effect ASAPX is not affected; however, using reserved names as domain
names can cause a myriad of problems in ASAP, OEM, and OIL. Recovery ASAPX warns about this problem and continues processing normally.
To eliminate this warning message, correct the problem indicated by
the EDITREAD error number and restart ASAPX. |
1864 File error on NAMEFILE: fname, FE: error | fname | is the name of the ASAP reserved names file. |
Cause (ASAP Release 1 only) ASAPX encountered a file error attempting
to open the ASAP reserved names file. This could result in reserved
names being entered as domain names and could yield unexpected results
in ASAP, OEM, and OIL. Effect ASAPX is not affected; however, using reserved names as domain
names can cause a myriad of problems in ASAP, OEM, and OIL. Recovery ASAPX warns about this problem and continues processing normally.
To eliminate this warning message, correct the problem indicated by
the file error number, and restart ASAPX. |
1880 ASAPX Shutdown complete, Requestor= pid | pid | is the process ID of the process that requested the
shutdown operation. |
Cause ASAPX received a shutdown request. Effect ASAPX shuts down. Recovery None. |
1881 ASAPX component INFO version started, cpu | component | is the ASAPX component that started. | version | is the ASAPX version number. | cpu | is the CPU component ASAPX started in. |
Cause ASAPX received a start request. Effect ASAPX starts. Recovery None. |
1899 ASAP ASAP Error num occurred xxxx time(s) | num | is the number the recurring error. | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
1901 ASAP INFO HYBRID version date started name cpu | version | is the version of the ASAP component; for example,
V01. | date | is the release date of this version. | name | is the process name of the starting component. | cpu | is the processor where the component started. |
Cause Someone started ASAP. Effect ASAP starts. Recovery Not applicable. |
1902 ASAP ERR HYBRID name Error Creating Process pname, Error:
err errdetail | name | is the name of the Proxy SGP process. | pname | is the name of the process that failed to start. | err | is the error returned by the process_create_ procedure. | errdetail | is the detailed error returned by the process_create_
procedure. |
Cause The Proxy SGP encountered a process creation error while attempting
to start an ASAP Hybrid Gateway process. Effect The Hybrid Gateway process is not started. Recovery Correct the process creation error and restart ASAP. |
1903 ASAP ERR HYBRID name Server I/O Error pname, FE: err | name | is the name of the Proxy SGP process. | pname | is the name of the process that the SGP was attempting
to communicate with. | err | is the file error encountered by the file-system operation. |
Cause The Proxy SGP encountered a file error while attempting to communicate
with an ASAP Hybrid Gateway process. Effect The Proxy SGP cannot communicate with the Gateway process. Recovery Correct the file-system error and retry the operation. |
1904 ASAP ERR HYBRID name cname EditReadInit: err | name | is the process name of the ASAP Hybrid component. | cname | is the name of the configuration file that ASAP was
attempting to process. | err | is the error returned by the editreadinit procedure. |
Cause The ASAP Hybrid component encountered an error with the editreadinit
procedure. Effect The ASAP Hybrid component cannot read its configuration file. Recovery Correct the editreadinit error and restart ASAP. |
1905 ASAP ERR HYBRID name cname, FE: err | name | is the process name of the ASAP Hybrid component. | cname | is the name of the configuration file that ASAP was
attempting to process. | err | is the file-system error number. |
Cause The ASAP Hybrid component encountered a file-system error. Effect The ASAP Hybrid component cannot successfully process its configuration
file. Recovery Correct the file-system error and restart ASAP. |
1906 ASAP ERR HYBRID name Unknown Config Opt: text | name | is the process name of the ASAP Hybrid component. | text | is the incorrect configuration option. |
Cause The ASAP Hybrid component encountered an error within its configuration
file. Effect The ASAP Hybrid component could not process all its configuration
options. Recovery Correct the error in the option text and restart ASAP. |
1907 ASAP ERR HYBRID name Unknown Param: text | name | is the process name of the ASAP Hybrid component. | text | is the incorrect parameter. |
Cause The ASAP Hybrid component encountered an error with a startup
parameter. Effect The ASAP Hybrid component could not process all its startup
parameters. Recovery Correct the error in the parameter text and restart ASAP. |
1908 ASAP ERR HYBRID name $Receive Error, FE: err | name | is the process name of the ASAP Hybrid component. | err | is the file error encountered by the file-system operation. |
Cause An ASAP Hybrid component encountered a file error on $Receive. Effect The $Receive operation is not completed. Failure to open $Receive
causes the process to abnormally terminate. Recovery Correct the file-system error and retry the operation. |
1909 ASAP ERR HYBRID name domain operation Err: err errdetail | name | is the name of the ASAP Hybrid Gateway process. | domain | is the domain name of the failed operation. | operation | is the type of operation that failed: Register, Update,
or Remove. | err | is the ASAP error encountered by the operation. | errdetail | is the ASAP error detail information encountered by
the operation. |
Cause An ASAP Hybrid Gateway could not register, update, or remove
a domain because of an ASAP error. Effect The operation is not completed. Recovery Correct the ASAP error and retry the operation. For a list of
possible ASAP errors returned for the type of operation, see the ASAP Extension Manual. For example, see the ASAP_REGISTER_
procedure for a description of registration errors and the ASAP_UPDATE_
procedure for a list of update errors. |
1910 ASAP ERR HYBRID name Datagram Error: text err | name | is the name of the ASAP Hybrid Gateway process. | text | is a brief text description of the error found in
the datagram. | err | is the incorrect value. |
Cause The datagram has probably been corrupted. Effect The Gateway stops processing the datagram. Recovery Attempt to identify and correct network problems that could
corrupt network data. |
1911 ASAP ERR HYBRID name Unknown Datagram Received from ipaddr | name | is the name of the ASAP Hybrid Gateway process. | ipaddr | is the IP address and port number of the sending system. |
Cause The ASAP Hybrid Gateway received a datagram that it was not
expecting. Effect The gateway does not process the datagram. Recovery Ensure the gateway is configured with a unique IP address and
port number. |
1912 ASAP INFO HYBRID name Sender ipaddr is UpRev, Version version | name | is the name of the ASAP Hybrid Gateway process. | ipaddr | is the IP address and port number of the sending system. | version | is the sender's version number. |
Cause A newer version of ASAP Hybrid has been installed on a remote
system. Effect Some of the features in the newer version might not be supported. Recovery Install the new version of ASAP Hybrid on the NonStop server. |
1913 ASAP ERR HYBRID name Error operation Socket, errno: errno | name | is the name of the ASAP Hybrid Gateway process. | operation | is the operation that encountered the error. | errno | is the socket error number. |
Cause TCP/IP returned an error when creating, configuring, setting,
binding, getting information about, receiving from, or sending to
a socket. Effect The socket operation does not complete. Recovery Correct the socket error and retry the operation. |
1914 ASAP ERR HYBRID name Unknown Request on $Receive: buf | name | is the name of the ASAP Hybrid Gateway process. | buf | is the first word of the buffer received. |
Cause An ASAP Hybrid component received a request buffer that it could
not decode. Effect ASAP Hybrid ignores the message. Recovery Identify and stop the message sender. |
2000 DB^write filename, fe: err, sysno, cpuno | filename | is the file name of the file in which the error occurred. | err | is the error returned from the FILEINFO system call
and is associated with the last operation on the file. | sysno | is the system number. | cpuno | is the CPU number. |
Cause The Collector received statistical information from the Monitor,
but it cannot perform all database record file I/O. Possibly the database
is not secured properly, is not present, or is full. The FILEINFO
system procedure call returned this error. Effect The statistical information received is not saved and cannot
be written to the database. 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. Check the database to be sure it is present and secured properly.
If the database is full, enlarge it or re-create it according to the
installation instructions in the installation chapter of the ASAP
Server Manual. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
2001 Unknown stat^sum^msg: type, words | type | is the current statistics type. | words | indicates the current statistics words. |
Cause The Collector cannot recognize the statistics type, and therefore
cannot query it. Effect Statistical information is not written to the database. Recovery If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
2002 Rollover Open filename, fe: err | filename | is the file name for the file in which the error occurred. | err | is the file-system error number associated with the
last operation on the file. |
Cause The Collector is trying to rename and release new database files,
but it cannot read records from the database. The FILEINFO system
procedure call has returned this error. Effect Files are being renamed Zmmddlll, where mmdd represents month
and day, and lll is the last three letters of the original file name. 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. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
2003 Can’t Rename filename, fe: err | filename | is the file name for the file in which the error occurred. | err | is the file-system error number associated with the
last operation on the file. |
Cause The Collector cannot rename the database file names to Zmmddlll,where
mmdd represents month and day, and lll is the last three letters of
the original file name. The FILEINFO system procedure call returned
this error. Effect Database files are not being renamed. 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. Check that the disk has enough space. Make sure your security
is correct. Ask Operations if they have placed a Safeguard on the
disk. If so, ask them to remove it from the disk. |
2004 Can’t Purgedata filename, fe: err | filename | is the file name for the file in which the error occurred. | err | is the file-system error number associated with the
last operation on the file. |
Cause The system is not performing a database cleanup operation. The
FILEINFO system procedure call returned this error. Effect The purgedata operation is not executed. The statistics are
not being refreshed. 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. Make sure the security is correct. Ask Operations if they have
placed a Safeguard on the disk. If so, ask them to remove it from
the disk. |
2005 filename Records Cleaned: num | filename | is the file name for the file in which the error occurred. | num | is the number of records that have been cleaned. |
Cause The data records were purged successfully. Effect The database cleanup operation is complete. Recovery This message is informational only. No corrective action is
required. |
2006 Short request received: count, buf, pid | count | is the length of the message in bytes. | buf | is the first word of the received request message. | pid | is the requester’s process identification. |
Cause A received message is unrecognizable because of its short length. Effect The message is not processed. Recovery Retry the request. If the problem persists, contact your support
representative to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
2007 Received shutdown request: pid | pid | is the requester’s process identification. |
Cause A shutdown request was received. Effect Your ASAP session terminates. Recovery This message is informational only. No corrective action is
required. |
2008 Illegal request received: count, buf, pid | count | is the length of the message, in bytes. | buf | is the first word of the received request message. | pid | is the requester’s process identification. |
Cause An invalid request was received. Effect The system does not process the request. Recovery Retry the request. If the problem persists, contact your support
representative to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
2009 ENFSV trans code bad | Cause An incomprehensible input request was received. Effect The Collect server cannot behave as an Enform server because
it cannot understand the request. Recovery Check your Enform request and retry it. If the problem persists,
contact your support representative to file a case and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
2010 Startup msg parse error: charoffset | charoffset | is the offset of the message that was not recognized. |
Cause An invalid parameter was detected while ASAP was attempting
to read its startup message. Effect The system does not start up. Recovery Correct the startup message in your configuration file. |
2011 Startup Can’t Open TERM | Cause The startup parameters did not open the terminal logfile. Effect The terminal logfile did not open at start. Recovery Correct the terminal file name in your configuration file. |
2012 Open filename, fe: err, type | filename | is the file name for the file in which the error occurred. | err | is the file-system error number associated with the
last operation on the file. | type | is an internal index to the ASAP database, with these
values: |
Cause The Collector has information to put in the database, but cannot
open a database file. The FILEINFO system procedure call returned
this error. Effect The information is not put in the database. 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. Make sure that you have the proper security. |
2013 Open filename, INFO: type | filename | is the file being opened. | type | is an internal index to the ASAP database, with these
values: |
Cause The system opened the file with the name indicated in the message. Effect The file was opened successfully. Recovery This message is informational only. No corrective action is
required. |
2014 SHUTDOWN Complete! Requester = pid | pid | is the requester’s process identification. |
Cause The system was shut down by the requester indicated in the message. Effect The requester was shut down successfully. Recovery This message is informational only. No corrective action is
required. |
2015 Trace | Cause The system performed an internal trace. Effect The system is working correctly. Recovery This message is informational only. No corrective action is
required. |
2016 COLLECT version started cpu | version | is the base release version of the ASAP environment. | cpu | is the CPU number. |
Cause The system is informing you that the Collector started successfully. Effect The Collector is operating. Recovery This message is informational only. No corrective action is
required. |
2017 ENFSERV version started: cpu | version | is the base releave version of the ASAP environment. | cpu | is the CPU number. |
Cause The system is informing you that the Enform server started successfully. Effect The Enform server is operating. Recovery This message is informational only. No corrective action is
required. |
2018 $RECEIVE read, FE: err | err | is the file-system error number associated with the
last operation on the file. |
Cause A system message was not received or read. The FILEINFO system
call returned this error. Effect The system did not receive the message. 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. Retry your operation, but this time pause between commands.
For example, the system cannot process a shutdown command immediately
after a startup command; it needs a momentary pause. |
2019 $RECEIVE reply failed, FE: err, count, buf,
pid | err | is the file-system error number associated with the
last operation on the file. | count | is the length of the message, in bytes. | buf | contains the first word of the request message received. | pid | is the requester’s process identification. |
Cause The system could not reply to a message it received from a READUPDATE(X)
call on the $RECEIVE file. The FILEINFO system call returned this
error. Effect The system did not reply to the message. 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. If the problem persists, contact your support representative
to file a case and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message(s) generated Numbers and versions of all related products Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a CPU dump, if applicable
|
2030 PCtl Purge filename error | filename | is the name of the control file. | error | is the file-system error number. |
Cause The Collector could not remove an existing partition control
file. The cause is most likely a security violation on the paritition
control file. Effect The new partition control file is not created. The existing
partition control file is used in creating a new database. Recovery Depends on error. |
2031 PCtl Creat filename error | filename | is the name of the control file. | error | is the file-system error number. |
Cause The Collector could not create a new partition control file.
The cause is most likely a security violation on the paritition control
file or a down target disk volume. Effect The new partition control file is not created. The Collector
creates the database using default settings. Recovery Depends on error. |
2032 PCtl Exist filename error | filename | is the name of the control file. | error | is the file-system error number. |
Cause The partition control file did not exist when the Collector
was started. The cause is most likely a down target disk volume or
a prior error that prevented the creation of the control file. Effect The Collector cannot get any partitioning settings and creates
the database using default settings. Recovery Depends on error. |
2033 PCtl Open filename error | filename | is the name of the control file. | error | is the file-system error number. |
Cause The partition control file could not be opened when the Collector
was started. The cause is most likely a security violation on the
paritition control file or a sharing violation because another application
has the control file open. Effect The Collector cannot get any partitioning settings and creates
the database using default settings. Recovery Depends on error. |
2034 Collector could not build part ctl file name
error | error | is the file-system error number. If greater than 0,
indicates the encountered file system error. If less than 0, indicates
an internal ASAP error. |
Cause The Collector could not determine the name of the partition
control file for the current ASAP ID. If a file system error occurred,
it is most likely a transient system problem such as a resource shortage. Effect The Collector cannot get any partitioning settings and creates
the database using default settings. Recovery Depends on error. If an internal
ASAP error occurred, contact your support representative. |
2035 Collector could not read partition ctl file
error | error | is the file-system error number. If greater than 0,
indicates the encountered file system error. If less than 0, indicates
an internal ASAP error. |
Cause The Collector could not read partitioning settings from the
partition control file. Most likely the control file does not exist
or could not be accessed because of security or sharing violations. Effect The Collector cannot get any partitioning settings and creates
the database using default settings. Recovery Depends on error. If an internal
ASAP error occurred, contact your support representative. |
2036 parse-error num-chars | parse-error | is the text of the parsing error, which describes
the error. | num-chars | is the offset within the line that caused the error. |
Cause The Collector encountered an error parsing partitioning settings
read from the partition control file due to illegal data in the file.
The file might be corrupt or invalid. Effect The Collector logs the error and continues to process the control
file. If the entire file is corrupt or invalid, the database is created
using default settings. If some entries in the file are good, they
are used to create the database. Recovery Shut down and restart the Collector to re-create the partition
control file. |
2037 Collector could not write partition ctl file
error | error | is the file-system error number. If greater than 0,
indicates the encountered file system error. If less than 0, indicates
an internal ASAP error. |
Cause The Collector could not write status information to the partition
control file after reading the file. Most likely a security violation
occurred. Effect The Collector logs the error and continues to run normally.
Status information is not written to the control file, but this does
not otherwise affect Collector operations. Recovery Depends on error. If an internal
ASAP error occurred, contact your support representative. |
2038 Unknown suffix entity-suffix | entity-suffix | is the suffix for an ASAP entity. |
Cause The Collector encountered an unknown ASAP database entity suffix.
The cause is an internal Collector error, possibly due to a versioning
inconsistency. Effect The Collector does not create a database for the specified entity. Recovery Contact your support representative. |
2039 CreatePart filename file-error partition-index | filename | is the database file that cannot be created. | file-error | is the file system error number. | partition-index | if between 0 and the number of partitions defined,
indicates which partition definition is incorrect. If greater than
the number of partitions defined, the partition definitions are correct,
and a system error occurred while trying to create the file. |
Cause The Collector could not create the specified database file.
The cause is most likely a system error such as a down target volume
or a security violation. Effect The Collector does not create a database for the specified entity. Recovery Depends on error. Enter SET PARTITION
to view partitioning settings. Correct any errors, then restart the
Collector from the ASAP CI. |
2040 CreatePart filename file-error internal-error error-indicator | filename | is the database file that cannot be created. | file-error | is the file-system error number. | internal-error | is the offset of the internal ASAP structure responsible
for the error. | error-indicator | is the contents of the internal error. |
Cause The Collector could not create the specified database file.
The cause is most likely a system error such as a down target volume
or a security violation, or an internal ASAP error. Effect The Collector does not create a database for the specified entity. Recovery Depends on error. Enter SET PARTITION
to view partitioning settings. Correct any errors, then restart the
Collector from the ASAP CI. |
2041 CreatePart partition status description | description | is the detailed information about the exact error
that caused a partition creation to fail, generating message 2039
or 2040. |
Cause The Collector encountered an error trying to create a database
for a particular entity. This error is usually logged with error 2039
or 2040. Effect The Collector does not create a database for the specified entity. Recovery Enter SET PARTITION to view partitioning settings. Correct any
errors, then restart the Collector from the ASAP CI. |
2042 Format2 ON, MaxExtents for sec parts not set
entity-number | entity-number | is the index of the entity to which this message applies. |
Cause Format2 support is ON, and MaxExtents values were specified
for one or more secondary partitions. The Collector cannot set MaxExtents
values for secondary partitions with Format2 support enabled. Effect MaxExtents values defined for secondary partitions are ignored.
The MaxExtents value for the base partition of the entity is used
for the secondary partitions. Recovery Either disable Format2 support or do not specify MaxExtents
values for secondary partitions. |
2043 OpenPart filename file-error partition-index | filename | is the database file that cannot be opened. | file-error | is the file-system error number. | partition-index | is the partition that cannot be opened. |
Cause The Collector could not open the specified database file and
partition while trying to create a database for a particular entity.
Most likely a security violation occurred. Effect The Collector cannot set the specified MaxExtents value for
the partition. The default value, from the base partition definition,
is used. Recovery Depends on error. Enter SET PARTITION
to view partitioning settings. Correct any errors, then restart the
Collector from the ASAP CI. |
2099 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
3000 Unable to create backup: cpu, err 0:7, err 8:15 | cpu | is the CPU number. | err | indicates the outcome of the process creation attempt,
where err 0:7 is one of: |
Cause A NEWPROCESS error and a file-system error occurred while a
primary process was trying to create a backup process. Effect The backup process is not created. Recovery Make sure the checkpoint information is correct. Check that
the CPU is up and running. If the CPU is down, follow the recommended
recovery procedure for a CPU failure. For more information on file-system
errors, see Appendix B. For more information on NEWPROCESS errors, see Appendix B. |
3001 NonStop Backup Created Cpu: cpu | Cause The primary process created a backup process in the CPU indicated
in the message. Effect The backup process was created successfully. Recovery This message is informational only. No corrective action is
required. |
3002 Unable to checkpoint startup err
0:7, err 8:15, pid | err | returns a status word of the form: | pid | is a four-word array where NEWPROCESS returns the
process ID of the requester’s new process. |
Cause The primary process could not send checkpoint information to
its backup process. Effect The backup process might not be able to take over if the primary
process fails. Recovery Decide if you want to take the chance that the primary process
will not fail, and continue to gather your statistics. For more information,
see Appendix B. |
3003 No backup, no cpu available | Cause The primary process did not create a new backup process because
no CPU was available. Effect The primary process is running without a backup process. Recovery Decide if you want to take the chance that the primary process
will not fail, and continue to gather your statistics. |
3004 --- TAKEOVER --> cpu: cpu | Cause The primary process quit, and the backup process took over.
The CPU of the primary process probably went down. Effect The backup process is now the primary process. Recovery Check whether the primary CPU failed. If so, follow the recommended
recovery procedure for a CPU failure. |
3005 No startup msg received | Cause A startup message was not received. Effect Startup information was not displayed. Recovery Correct the startup message information in your configuration
file. |
3099 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
4000 ASAP INFO | ALERT component entity
domain attribute attval | component | is the name of the relevant ASAP component. | entity | is the name of the relevant entity. | domain | is the name of the relevant domain. | attribute | is the name of the relevant attribute. | attval | is the text that describes the attribute value. |
Cause An attribute failed to meet an objective where the objective
is defined for event generation. Effect User-specific. Recovery User-specific. |
4001 ASAP INFO component entity domain
attribute attval (OK) | component | is the name of the relevant ASAP component. | entity | is the name of the relevant entity. | domain | is the name of the relevant domain. | attribute | is the name of the relevant attribute. | attval | is the text that describes the attribute value. |
Cause An attribute is meeting its objectives after previously failing
to meet them. Effect User-specific. Recovery User-specific. |
4021 ASAP ERR component recnum entity objective record(s) not loaded, reason | component | is the name of the relevant ASAP component. | recnum | is the number of records not loaded. | entity | is the name of the relevant entity. | reason | an EDL mismatch occurred or MaxObjectives was reached. |
Cause The current EDL does not match the EDL for an objective record
or the maximum number of objective records have been loaded. Effect The objective record is not loaded into the ASAP component. Recovery For an EDL Mismatch error, use RANK/OUT x/entity *,OBEYFORM to output the entity’s
objectives, then delete the objectives using RANK entity *, DELETE. Then reload the entity definitions using the current
EDL by OBEYing x. For a MaxObjectives error,
use hierarchal ranking to reduce the number of objective records or
increase MaxObjectives in the EDL definition. |
4022 ASAP ERR component Segment allocation error: err error-detail | component | is the name of the relevant ASAP component. | err | is the error returned from SEGMENT_ALLOCATE_. | error-detail | is detailed information about the error returned from
SEGMENT_ALLOCATE_. |
Cause The ASAP component failed to obtain extended memory to load
objectives. Effect The objective records for the ASAP component are not loaded. Recovery Increase the amount of extended memory available by extending
the available swap space. |
4023 ASAP ERR component filename, FE: error | component | is the name of the relevant ASAP component. | filename | is the name of the objectives file. | error | is the file-system error. |
Cause The ASAP component got a file system error while attempting
to access the objectives file. Effect The objective records for the ASAP component are not loaded. Recovery Correct the file system error and restart ASAP. |
4024 Action Server I/O Error, FE: error | Cause An ASAP SGP failed to communicate with the Action server due
to file error error. Effect An ASAP recovery action failed to execute for this interval.
It will be retried at the next interval if the condition persists. Recovery Correct the file error condition. |
4099 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
4101 RDF FILENAME_FINDNEXT_ error : error | error | the file system error returned from the call to FILENAME_FINDNEXT_. |
Cause FILENAME_FINDNEXT_ returned an error while the SGP was auto-detecting
the RDF environments. Effect The SGP abends. Recovery ASAP should restart the SGP automatically. If the problem persists,
contact the Global Mission Critical Solution Center (GMCSC). |
4102 RDF FILENAME_FINDSTART_ error : error | error | the file system error returned from the call to FILENAME_FINDSTART_. |
Cause FILENAME_FINDSTART_ returned an error while the SGP was auto-detecting
the RDF environments. Effect The SGP abends. Recovery ASAP should restart the SGP automatically. If the problem persists,
contact the Global Mission Critical Solution Center (GMCSC). |
4104 RDF SGP_RANKVALUE_ error : error | error | is the parameter error returned from SGP_RANKVALUE_
to the RDF SGP. The absolute value of this variable is the parameter
in error. |
Cause An error was returned when the RDF SGP tried to rank a value
derived from an RDF environment. Effect The ranking of the value is incorrect, but the SGP continues
processing. Recovery If the problem persists, contact the Global Mission Critical
Solution Center (GMCSC). |
4105 RDF Could not resolve P-handle, FE: error | error | is the file system encountered by the RDF SGP while
trying to get or decode its process handle. |
Cause The SGP could not determine its own process handle. Effect The SGP continues processing; however, some fields in RDF statistics
records are invalid. Recovery Create a saveabend file of the RDF SGP, then stop the SGP. Contact
the Global Mission Critical Solution Center (GMCSC). |
4106 RDF error-text | error-text | describes the nature of the problem. |
Cause The RDF SGP encountered a problem loading its entities from
the EDL. Effect The SGP cannot load its EDL, so DOTs cannot correctly produce
OEM states for the entity until the EDL problem is corrected. Recovery The recovery depends on the error specified in error-text. |
4199 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
4201 ASAPFIL error-text | error-text | is the text of error returned by the ecb_loadentities_
call. |
Cause When trying to load the File entity, the ASAP ecb_loadentities_
procedure call returned the specified error, most likely caused by
a problem with the EDL settings. Effect The File entity does not load. The File SGP continues to try
to load the entity at each sampling until it succeeds. Recovery Check your EDL settings. For more information on EDL, see the
ASAP Client Manual. |
4202 ASAPFIL sgp_readdomain_ Error= error-num | error-num | is the error code returned by the sgp_readdomain_
call. |
Cause When trying to get the list of File domains to monitor, the
ASAP sgp_readdomain_ procedure call returned the specified error. Effect The file domains list is not obtained, and no domains are monitored.
If this error occurs after a COMMIT command, the previous list is
used. Recovery Make sure the file domains are configured correctly in the ASAP
Objectives Database. See the MONITOR command in the ASAP Server Manual. |
4203 ASAPFIL filename_findstart_ Error= error-num | error-num | is the error code returned by the NonStop operating
system filename_findstart_ call. |
Cause An error occurred when trying to initiate an inventory of files
in a subvolume. Effect The subvolume domain is flagged as Unknown and with a Warning
state. error-num is reported as the Error
attribute value. The File SGP tries to monitor this domain again at
the next sampling. Recovery Make sure no problem exists with this disk subvolume. error-num might also indicate what recovery to use. |
4204 ASAPFIL filename_findnext_ Error= error-num | error-num | is the error code returned by the NonStop operating
system filename_findnext_ call. |
Cause An error occurred when trying to get an inventory of files in
a subvolume, possibly because the device does not exist. Effect The subvolume domain is flagged as Unknown and with a Warning
state. error-num is reported as the Error
attribute value. The File SGP tries to monitor this domain again at
the next sampling. Recovery Make sure no problem exists with this disk subvolume. error-num might also indicate what recovery to use. |
4205 ASAPFIL filename_findfinish_ Error= error-num | error-num | is the error code returned by the NonStop operating
system filename_findfinish_ call. |
Cause An error was occurred when trying to terminate an inventory
of files in a subvolume. Effect The subvolume domain is flagged as Unknown and with a Warning
state. error-num is reported as the Error
attribute value. The File SGP tries to monitor this domain again at
the next sampling. Recovery Make sure no problem exists with this disk subvolume. error-num might also indicate what recovery to use. |
4206 ASAPFIL Rank Values Error= error-num error-detail | error-num | is the error code returned by the call to sgp_rankvalues_. | error-detail | is the detailed error returned by sgp_rankvalues_. |
Cause An error occurred when trying to get the state of a domain attribute. Effect The state of this domain attribute is not obtained. The state
value is initialized to the default value of Exists. Recovery Make sure no problem exists with the ASAP Objectives Database. error-num and error-detail might also indicate what recovery to use. |
4207 ASAPFIL Compare^tables: aborting Dynamic Configuration | Cause An error occurred when dynamically changing the list of domains
to monitor. Effect The File SGP list of domains to monitor might not be consistent
with the contents of the Objectives Database. The File SGP might be
missing some domains to monitor. Recovery Issue a COMMIT FILE command to force a reload of the list of
domains into File SGP memory. If the problem persists, contact your
HP support representative. |
4208 ASAPFIL Parsing SGP option cmd-option | cmd-option | is the command option that caused the error. |
Cause An invalid command option was specified. Effect The specified option is ignored. Recovery Correct the syntax of your command and try it again. |
4209 ASAPFIL Process handle: error-num | error-num | is the error returned by a NonStop operating system
procedure call. |
Cause An error was returned by either the NonStop operating system
processhandle_getmine_ or processhandle_decompose_ procedure call. Effect The File SGP cannot obtain information about itself, its CPU,
PIN, nodename, and so forth. Recovery error-num should indicate what recovery
to use. |
4210 ASAPFIL Segment alloc: error-num
error-detail | error-num | is the error returned by the NonStop operating system
segment_allocate_ procedure call. | error-detail | is more information returned by the NonStop operating
system segment_allocate_ procedure call. |
Cause An error occurred while trying to allocate an extended segment. Effect The File SGP does not have an extended segment to store and
send the file statistics to the ASAP Collector. This is a major error. Recovery Use error-num and error-detail to identify the recovery. If you cannot resolve the problem, contact
your HP support representative. |
4211 ASAPFIL Children Segment alloc: error-num error-detail | error-num | is the error returned by the NonStop operating system
segment_allocate_ procedure call. | error-detail | is more information returned by the NonStop operating
system segment_allocate_ procedure call. |
Cause An error occurred while trying to allocate an extended segment. Effect The File SGP does not have an extended segment to store the
statistics of the children files of a subvolume domain. If no subvolume
domains are configured, this should not affect the File SGP. Recovery Use error-num and error-detail to identify the recovery. If you cannot resolve the problem, contact
your HP support representative. |
4212 ASAPFIL file_getinfolistbyname_ Error= error-num error-detail | error-num | is the error returned by the NonStop operating system
file_getinfolistbyname_ procedure call. | error-detail | is the item in error in the procedure call. |
Cause An error occurred while trying to get statistics about a file. Effect This file domain is identified as being incorrect. The File
SGP tries to get statistics at the next sampling. Recovery Use the Status and Error attributes of the file domain to determine
the cause of the error. |
4213 Error SET FIL PARAM cmd-option | cmd-option | is an invalid parameter option. |
Cause An error was detected in the File SGP startup PARAM string. Effect The rest of the PARAM string is ignored. Recovery Correct the startup PARAM. For a list of valid PARAM values,
see the SET FILE command. |
4214 ASAPFIL Error loading objectives error-num error-detail | error-num | is the error returned by the call to load^objectives. | error-detail | is additional error information returned by load^objectives. |
Cause An error occurred when trying to load the objectives list. Effect The objectives list is not loaded from the Objectives database.
State values obtained by the File SGP might not correspond to Objectives
defined in the database. Recovery Use error-num and error-detail to identify the recovery, then use the COMMIT FILE command to force
a reload of the objectives. If you cannot resolve the problem, contact
your HP support representative. |
4215 ASAPFIL Sgp_getobjectives_ Error= error-num | error-num | is the error returned by the call to sgp_getobjectives_. |
Cause An error occurred while trying to get the objectives list. Effect The objectives list is not obtained from the DOTs infrastructure.
State values obtained by the File SGP might not correspond to Objectives
defined in the database. Recovery Use error-num to identify the recovery,
then use the COMMIT FILE command to force a reload of the objectives.
If you cannot resolve the problem, contact your HP support representative. |
4294 FIL EDL loaded | Cause The EDL was correctly loaded for the File SGP. Effect None. Recovery Informational message only; no corrective action is required. |
4295 FIL Stats performance messages. | Cause Performance statistics messages were sent for HP internal use
only. Effect None. Recovery Informational message only; no corrective action is required. |
4296 FIL Reloading previous configuration. | Cause The previous list of monitored domains is being reloaded after
an error occurred while trying to load a new list of domains. Effect None. Recovery Informational message only; no corrective action is required.
For recovery for the preceding error on loading a new domain list,
see the description of that error. |
4297 FIL Could not load all domains: maximum reached. | Cause More domains are defined in the Objectives database than the
File SGP can accept. Effect Domains exceeding the maximum are not monitored. Recovery Use the MONITOR FILE, DELETE command to remove some domains
from the Objectives database, then use COMMIT FILE to load the new
domain list. |
4298 FIL Autoconfiguration completed. | Cause No domains were defined to monitor in the Objectives database,
so the File SGP configured one domain by default. Effect None. Recovery To monitor more domains, use the MONITOR FILE, ADD command to
add them to the Objectives database. Then use the COMMIT FILE command
to load the new domain list. The autoconfigured domain is automatically
removed. |
4299 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
4301 SPL ecb_loadentities_ error-text | error-text | is the error message returned by the ecb_loadentities_
procedure. |
Cause The ASAP ecb_loadentities_ procedure returned the specified
error when trying to load the spooler entity. Effect The spooler entity does not load. Recovery The EDL settings might cause this error might. For more information
on EDL, see the ASAP Client Manual. |
4302 SPL sgp_readdomain_ Error= FE: error | error | is the file system error returned by the SGP_READDOMAIN_
procedure. |
Cause The ASAP sgp_readdomain_ procedure returned the specified error
when trying to get the list of spooler domains to monitor. Effect Spooler monitoring does not begin. Recovery Make sure that ASAP is configured correctly. For more information
about configuring domains, see the MONITOR command in the ASAP Server
Manual. If the configuration is correct, contact your HP support representative. |
4303 Invalid Stats^Type in process^minstate for SGP
SPL StatsType: numtype | numtype | is the value of the found Spooler statistics type. |
Cause The Spooler SGP encountered an invalid statistic entry type
in its internal structures. Effect The entry in error is ignored. Recovery This is an internal error. Report this error to your HP support
representative. Be ready to report the numtype and the scenario where this occurred. If possible, if this message
keeps appearing, create a saveabend file of the Spooler SGP before
stopping the Spooler SGP. |
4304 Num Stats overflow in get^free^stats for SGP
SPL NumStats: numstats | numstats | is the value of Spooler type entry that was dropped
because of an overflow. |
Cause The internal statistics area of the Spooler SGP is full, and
entry is needed. Effect The entry is not added to the internal table; therefore, sampling
information might be incomplete. Recovery Report this error to your HP support representative. Be ready
to report the numstats and the list of
spooler domains being monitored. Create a saveabend file of the Spooler
SGP before stopping the Spooler SGP. |
4305 No type stats entry
available in find^entry for SGP SPL. No type stats entry available in check^setup^domain for SGP SPL. | type | is the Spooler type entry which could not be created
due to the error. |
Cause The internal statistics area of the Spooler SGP is full, and
entry is needed. Effect The Spooler entry is not added to the internal table; therefore,
sampling information might be incomplete. Recovery If this error occurs, message 4304 should also appear. See the
recovery procedure for that message. |
4306 SPL Rank Value Error FE: error,
errordetail | error | is the value returned from the SGP_RANKVALUE_ procedure
to identify the specific error. | error-detail | is more information from the SGP_RANKVALUE_ procedure
to identify the specific error. |
Cause The ASAP sgp_rankvalue_ procedure call returned the specified
error and details when trying to rank the spooler entries. Effect Depending on the returned error, the entity might not have been
ranked. Recovery Verify that the objective is working properly. For more information
about objectives, see the MONITOR and RANK commands in the ASAP Server
Manual. |
4307 SGP SPL Error loading objectives: FE: error, error-detail | error | is the value returned from the LOAD^OBJECTIVES procedure
to identify the specific error. | error-detail | is more information returned from the LOAD^OBJECTIVES
procedure to identify the specific error. |
Cause The Spooler SGP encountered an error when trying to load objectives
for a tape domain. Effect The new objectives are not loaded and the old ones are used.
A load will be tried again on the next sample. Recovery Verify that the EDL and objectives database are correctly installed
and configured. |
4308 SGP SPL Parsing SGP option cmd | cmd | is the invalid SGP command option found. |
Cause The SPL SGP encountered an invalid command option while parsing
the MONITOR SPOOLER, LIST, SGP command. Effect The specified option is ignored. Recovery Verify and correct the command. |
4309 SPL Process Handle FE: error | error | is the NonStop operating system error returned from
the PROCESSHANDLE_DECOMPOSE or PROCESSHANDLE_GETMINE_ procedure. |
Cause The NonStop operating system PROCESSHANDLE_DECOMPOSE_ or PROCESSHANDLE_GETMINE_
procedure call returned the specified error when trying to get information
about the SGP. Effect The Spooler SGP processname and nodename are not defined correctly. Recovery Contact your system administrator. |
4310 SPL Stats Segment Alloc FE: error
error-detail SPL Xfer Segment Alloc FE: error error-detail | error | is the error value returned by the NonStop operating
system SEGMENT_ALLOCATE_ procedure. | error-detail | is the error-detail value returned by the NonStop
operating system SEGMENT_ALLOCATE_ procedure. |
Cause The specified error occurred when trying to allocate memory
for the statistics or transfer segments. Effect The needed extended segments are not allocated. Sampling is
not possible. Recovery Contact your system administrator to verify why memory is not
available. Check the swap space settings. |
4311 SPL FILENAME_TO_PROCESSHANDLE_ Error. FE: error | error | is the error returned from the FILENAME_TO_PROCESSHANDLE
procedure call. |
Cause The NonStop operating system FILENAME_TO_PROCESSHANDLE_ procedure
call returned the specified error when trying to get information about
the spooler supervisor process. Effect The Spooler SGP treats that spooler entity as if it is not running. Recovery This might be a timing error. The information is only fetched
once the spooler supervisor is opened and should therefore exist.
However, the supervisor might have been stopped or failed between
when it was opened and queried. Verify that the supervisor is up and
running. If this error persists, contact your HP support representative. |
4312 SPL SpoolerStatus Error= FE: error | error | is the error returned from the SPOOLERSTATUS or SPOOLERSTATUS2
procedure call. |
Cause The NonStop operating system SPOOLERSTATUS or SPOOLERSTATUS2
procedure call returned the specified error. The Spooler SGP cannot
handle this error. Effect None. Recovery Convert error to octal and see the
Spooler manual to find out what the error means. If it is a spooler
problem, the Spooler SGP will recover once you fix the Spooler environment.
If it is not a spooler problem, contact your HP support representative.
Be ready to provide error, and create a
saveabend file for the Spooler SGP before stopping it. |
4313 Error SET SPL PARAM param-error | param-error | is the parameter being parsed when the error occured. |
Cause The specified parameter is not a valid parameter for the Spooler
SGP. Effect The parameter is ignored. Recovery Verify and correct the SET SPOOLER PARAMETER that caused the
problem. |
4314 SPL loc font array overflow in domain^count^jobs^locs. | Cause The array used to temporarily hold the location entries that
have an associated device and font is full. Effect The FONTS attribute for devices might not be reported correctly. Recovery Verify the spoolers being monitored. Count the number of locations
associated with both a device and a font job. If this number is high
for one spooler, inform your HP support representative of your configuration.
If this number is not high, create a saveabend file of the Spooler
SGP and contact your HP support representative. |
4315 SPL Batch Job array overflow in domain^count^jobs^locs. | Cause The array used to temporarily hold the job numbers of the jobs
used as part of batch jobs is full. Effect The BATCH attribute for devices and print processes might not
be reported correctly. Recovery Verify the spoolers being monitored. Count the number of jobs
that are part of batch jobs. If this number is high for one spooler,
inform your HP support representative of your configuration. If this
number is not high, create a saveabend file of the Spooler SGP and
contact your HP support representative. |
4316 SPL DevQ Job array overflow in domain^count^jobs^locs. | Cause The array used to temporarily hold the job numbers of the jobs
queued to devices is full. Effect The DevQs attribute for the spooler supervisor might not be
reported correctly. Recovery Verify the spoolers being monitored. Count the number of jobs
currently queued to devices to be printed. If this number is high
for one spooler, inform your HP support representative of your configuration.
If this number is not high, create a saveabend file of the Spooler
SGP and contact your HP support representative. |
4317 Print Proc entry name not found in SGP SPL. type entry name not found in SGP SPL. | name | is the name of entry being looked for. | type | is the type of entry being looked for: SP = Supervisor;
CL = Collector; DV = Device; PP = Print Process. |
Cause The Spooler SGP cannot find an entry of type type in its internal memory, but this entry is referenced in another
spooler entry. Effect The spooler tree structure is not correct and samplling information
might not add up. Recovery Verify the spooler name for the specified
entry. A job, device, or location in that spooler is referencing the
specified entry, which does not exist. If the spooler configuration
is correct, note the name, create a saveabend
file of the Spooler SGP, stop the SGP, and contact your HP support
representative. |
4393 Timeout error occurred in get^spooler^stats
for SGP SPL. | Cause The spooler supervisor was too busy to return information to
the SPL SGP. Effect The Spooler SGP tries five times, in one second intervals, before
giving up. Recovery If this error occurs frequently, check why the spooler supervisor
is so busy. |
4394 SPL EDL loaded. | Cause The Spooler EDL loaded correctly on startup of ASAP. Effect The Spooler SGP runs normally. Recovery Informational message; no corrective action is necessary. |
4395 SPL Sampling delay processing: num | processing | is the processing area for elapsed time. | num | is the amount of elapsed time, in milliseconds, the
specified processing took. This is the elapsed time during processing,
not the time the processing itself took. |
Cause The Spooler parameter STATS was set when the Spooler SGP was
started. Therefore, this message indicates how much time elapsed during
the indicated processing. Effect None. Recovery Informational message; no corrective action is necessary. To
stop these messages from appearing, remove the STATS parameter from
the ASAPCONF file or reset it from your ASAP session, then restart
the Spooler SGP. |
4396 SPL Reloading previous configuration. | Cause An error occurred when trying to load the spooler domain names
to monitor. (See 4302.) This message indicates that the last list
of domains will be used instead. Effect The previous spooler configuration is reloaded, and the last
list of domains is used. Recovery Informational message; no corrective action is necessary. However,
because this message appears after error 4302, see the recovery for
that message to fix the problem it indicates. |
4397 SPL Could not load all domains: maximum of num reached. | num | is the maximum number of spooler domains to monitor
previously set in ASAP. |
Cause The maximum number of spooler domains to monitor was reached. Effect The overflow spooler domains are not monitored. Recovery Monitor fewer spooler domains. If this becomes a significant
issue, contact your HP support representative. |
4398 SPL Autoconfiguration completed. | Cause No spooler domains are specified in the objective database;
therefore, the Spooler SGP has autoconfigured to monitor the $SPLS
spooler. Effect The Spooler is configured to monitor only the $SPLS spooler. Recovery Informational message; no corrective action is necessary. |
4399 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
4401 TAP ecb loadentities error-text | error-text | is the error message returned by the ecb_loadentities_
procedure. |
Cause The ASAP ecb_loadentities_ procedure call returned the specified
error when trying to load the tape entity. Effect The tape entity does not load. Recovery The EDL settings might cause this error. For more information
on EDL, see the ASAP Client Manual. |
4402 TAP sgp_readdomain_ Error= FE: error | error | is the file-system error returned by the SGP_READDOMAIN_
procedure. |
Cause The ASAP sgp_readdomain_ procedure returned the specified error
when trying to get the list of tape domains to monitor. Effect Tape monitoring does not begin. Recovery Make sure that ASAP is configured correctly. For more information
about configuring domains, see the MONITOR command in the ASAP Server
Manual. If the configuration is correct, contact your HP support representative. |
4404 TAP SSINIT Error: error TAP SSGET cmd token error: error TAP SSGETTKN Get token error: error TAP SSPUT token error: error TAP SSPUTTKN cmd token error: error TAP
SPI Last Error: error TAP SPI Return Error: error TAP SPI Dlist RetCode error: error TAP SSNULL token error: error | error | is the error returned by the specified SPI procedure
call. | cmd | is the MediaSRV command used in the SPI buffer when
the error occurred. | token | is the name of the SPI token to obtain or push when
the error occurred. |
Cause The specified SPI command returned error. cmd and token provide more information about where and why the SPI command was
executed. Effect The status operation for the tape device is aborted and set
as SPI error. It is retried at the next sampling. Recovery Make sure your version of MEDIASRV is compatible with ASAP.
If it is and you still get this error, contact your service provider. |
4405 TAP could not start filename. Error=error error-detail | filename | is the file name used to create the MEDIASRV server
process. | error | is the error information returned by the PROCESS_CREATE_
procedure. | error-detail | is the detailed error information returned by the
PROCESS_CREATE_ procedure. |
Cause The NonStop operating system PROCESS_CREATE_ procedure call
returned this error when trying to start the MEDIASRV server. Effect The MEDIASRV server does not start. Recovery Make sure that MEDIASRV is properly installed and configured.
For installation information for the MEDIASRV server, see the DSM/Tape
Catalog User’s Guide. |
4406 TAP Rank Value Error FE: error, error-detail | error | is the value returned from the SGP_RANKVALUE_ procedure
to identify the specific error. | error-detail | is the detailed information returned from the SGP_RANKVALUE_
procedure to identify the specific error. |
Cause The ASAP sgp_rankvalue_ procedure call returned the specified
error when trying to rank the tape domain. Effect Depending on the returned error, the entity might not have been
ranked. Recovery Verify that the objective environment is working properly. For
more information about objectives, see the MONITOR and RANK commands
in the ASAP Server Manual. |
4407 TAP open error on MEDIASRV. Error=error | error | is the error returned from the FILE_OPEN_ procedure
call. |
Cause The MEDIASRV server was started but the Tape SGP could not open
it. The NonStop operating system FILE_OPEN_ procedure call returned
the specified error. Effect The MEDIASRV server stops. A new one is created and opened at
the next sampling. Recovery Make sure MEDIASRV is properly installed and configured. For
installation information for the MEDIASRV server, see the DSM/Tape
Catalog User’s Guide. |
4408 SGP TAP Parsing SGP option cmd | option | is the invalid SGP command option that was found. |
Cause The Tape SGP encountered an invalid option in command while parsing the MONITOR TAPE, LIST, SGP command. Effect The invalid option is ignored. Recovery Correct the command with the invalid option. |
4409 TAP Process Handle FE: error | error | is the NonStop operating system error returned from
the PROCESSHANDLE_DECOMPOSE_ or PROCESSHANDLE_GETMINE_ procedure. |
Cause The NonStop operating system PROCESSHANDLE_DECOMPOSE_ or PROCESSHANDLE_GETMINE_
procedure call returned the specified error when trying to get information
about the SGP. Effect The Tape SGP processname and nodename are not defined correctly. Recovery Contact your system administrator. |
4410 TAP Xfer Segment Alloc FE: error
error-detail | error | is the error value returned by the NonStop operating
system SEGMENT_ALLOCATE_ procedure. | error-detail | is the error-detail value returned by the NonStop
operating system SEGMENT_ALLOCATE_ procedure. |
Cause The specified error was returned when trying to allocate memory
for the transfer segments. Effect The needed extended segments are not allocated. Sampling is
not possible. Recovery To verify why memory is not available, contact your system administrator.
Check the swap space settings. |
4411 TAP DEVICE_GETINFOBYNAME_ on domain Error=error error-detail | domain | is the tape device name for which the error occurred. | error | is the error information returned from the DEVICE_GETINFOBYNAME_
procedure. | error-detail | is the error details returned from the DEVICE_GETINFOBYNAME_
procedure. |
Cause The specified error was returned when trying to obtain information
about the specified tape device. Effect The Tape SGP sets the status for the domain to UNKNOWN. Recovery Verify that the specified domain is a valid tape device. If
it is, contact your system administrator. |
4412 TAP MEDIASRV WRITE error:error | error | is the error which occurred when trying to perform
a WRITEREAD to the MEDIASRV server process. |
Cause The specified error occurred when sending a SPI request to MEDIASRV. Effect The MEDIASRV process is closed and a new one is created at the
next sampling. All affected tape devices in the current sample are
given a status of SPIError. Recovery Make sure your version of MEDIASRV is compatible with ASAP and
MEDIASRV is properly installed. |
4413 Error TAP SPL PARAM param-error | param-error | is the parameter being parsed when the error occurred. |
Cause The specified parameter is not a valid parameter for the Tape
SGP. Effect The parameter is ignored. Recovery Verify and correct the SET TAPE PARAMETER parameter that caused
the problem. |
4414 TAP GETINFOLIST Error: error error-detail | error | is the error returned by the NonStop operating system
GETINFOLIST procedure. | error-detail | is the error details returned by the NonStop operating
system GETINFOLIST procedure. |
Cause The NSK PROCESS_GETINFOLIST_ procedure call returned the specified
error when trying to get information about the process that has the
tape device open or that is requesting the tape mount. Effect The user ID and program name are not assigned to the tapemount
request or tapedrive status. Recovery If this error recurs, contact your system administrator. |
4415 TAP error finding tape devices. Error=error, error-detail TAP can’t find any tape devices. | error | is the error returned by the NonStop operating system
DEVICE_GETINFOBYLDEV_ procedure. | error-detail | is the error detail returned by the NonStop operating
system DEVICE_GETINFOBYLDEV_ procedure. |
Cause The Tape SGP is in autoconfiguration mode and is trying to find
tape devices on the system. The NonStop operating system DEVICE_GETINFOBYLDEV_
procedure call returned the specified error. Effect If error and error-detail are provided, tape drives might be missing from the display. Recovery If there are no tape devices on your system, turn off the Tape
SGP. If there are tape devices, contact your system administrator
to find out why they cannot be found. |
4416 TAP Error Loading objectives error
error-detail | error | is the error returned by the LOAD^OBJECTIVES procedure
to identify the specific error. | error-detail | is the error details returned by the LOAD^OBJECTIVES
procedure to identify the specific error. |
Cause The Tape SGP encountered an error while trying to load objectives
for a domain or subdomain. Effect The new objectives are not loaded and the old ones are used.
Load is attempted on the next sampling. Recovery Verify that the EDL and objectives database are correctly installed
and configured. |
4493 TAP Could not add to last domain table: maximum
of num reached. | num | is the maximum number of tape domain entries allowed
in the Tape SGP. |
Cause A node domain entry is being deleted but the last domain table
has overflowed. Effect The domain is not deleted with this sample. Recovery None. This should fix itself. However, if this error recurs,
contact your service provider and tell them your requirements. |
4494 TAP EDL loaded. | Cause The Tape EDL was loaded correctly on startup. Effect The Tape SGP runs normally. Recovery Informational message; no corrective action is necessary. |
4495 TAP Sampling delay processing: num | processing | is the processing area for elapsed time. | num | is the elapsed time spent in the processing area. |
Cause The Tape parameter STATS was set when the Tape SGP was started.
This message indicates how many milliseconds have elapsed (not how
much time processing took) when doing the indicated processing. Effect None. Recovery Informational message; no corrective action is necessary. To
prevent these messages from appearing, remove the STATS parameter
from the ASAPCONF file or reset it from your ASAP session, and restart
the Tape SGP. |
4496 TAP Reloading previous configuration. | Cause An error occurred when trying to load the tape domain names
to be monitored. (See message 4402.) This message indicates that the
last list of domains is used instead. Effect None. Recovery Informational message. See recovery for message 4402. |
4497 TAP Could not load all domains: maximum of num reached. | num | is the maximum number of tape domain entries allowed
in the Tape SGP. |
Cause The maximum number of tape domains to be monitored was reached. Effect The overflow tape domains are not monitored. Recovery Monitor fewer tape domains. If this becomes an issue, contact
your support representative and provide your requirements. |
4498 TAP Autoconfiguration completed. | Cause No tape domains are specified in the objective database, so
the Tape SGP autoconfigured to monitor all tape devices found on the
system. Effect None. Recovery Informational message; no corrective action is necessary. |
4499 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
4501 ASAPTMF error-text | error-text | is the error returned by ecb_loadentities_ call. |
Cause The ASAP ecb_loadentities_ procedure returned the specified
error when trying to load the TMF entity. Effect The TMF entity does not load. The TMF SGP tries the load again
at the next sampling until it succeeds. Recovery The EDL settings might cause this error. For more information
on ASAP EDL, see the ASAP Client Manual. |
4502 ASAPTMF sgp_readdomain_ Error= error-num | error-num | is the error code returned by the sgp_readdomain_
call. |
Cause When trying to get the list of TMF domains to monitor, the ASAP
sgp_readdomain_ procedure call returned the specified error. Effect The TMF domains list is not obtained, and no domains are monitored.
If this error occurs after a COMMIT command, the previous list is
used. Recovery Make sure the TMF domains are configured correctly in the ASAP
Objectives database. See the MONITOR command in the ASAP Server Manual. |
4503 ASAPTMF Rank Value Error= error-num
error-detail | error-num | is the error code returned by call to sgp_rankvalue_. | error-detail | is the detailed error returned by call to sgp_rankvalue_. |
Cause An error occurred while trying to get the state of a domain
attribute. Effect The state of this domain attribute is not obtained, The returned
state value is the default value of the Exists state. Recovery Make sure no problem exists with the ASAP Objectives database. error-num and error-detail can help you determine the cause of the problem. |
4504 ASAPTMF Compare^tables: aborting Dynamic Configuration | Cause An unexpected error occurred while dynamically changing the
list of domains to monitor. Effect The TMF SGP’s list of domains to monitor might not be
consistent with the contents of the Objectives database. That is,
the TMF SGP might be missing some domains to monitor. Recovery Issue a COMMIT TMF command to force a reload of the domains
list into the TMF SGP memory. If the problem persists, contact your
HP support representative. |
4505 ASAPTMF Parsing SGP option cmd-option | cmd-option | is the command option that caused the error. |
Cause An invalid command option was specified. Effect The specified option is ignored. Recovery Correct the syntax of your command and try it again. |
4506 ASAPTMF Process handle Error= error-num | error-num | is the error returned by the NonStop operating system
processhandle_getmine_ or processhandle_decompose_ procedure call. |
Cause A NonStop operating system procedure call returned an error. Effect The TMF SGP cannot get information about itself, its CPU, pin,
nodename, and so on. Recovery Use error-num to determine the cause
of the error. |
4507 ASAPTMF Segment alloc: error-num
error-detail | error-num | is the error returned by the NonStop operating system
segment_allocate_ procedure call. | error-detail | is additional error information returned by the segment_allocate_
procedure call. |
Cause The NonStop operating system segment_allocate_ procedure call
returned an error when trying to allocate an extended segement. Effect This is a major error. The TMF SGP does not have any extended
segment to store and send TMF statistics to the ASAP Collector. Recovery Use error-num and error-detail to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4508 ASAPTMF Transac Segment alloc: error-num error-detail | error-num | is the error returned by the NonStop operating system
segment_allocate_ procedure call. | error-detail | is additional error information returned by the segment_allocate_
procedure call. |
Cause The NonStop operating system segment_allocate_ procedure call
returned an error when trying to allocate an extended segement. Effect The TMF SGP does not have any extended segment to store the
statistics of TMF transactions. If the Transactions domain is not
configured to be monitored, the TMF SGP should not be affected. Recovery Use error-num and error-detail to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4509 TMF SET TMF PARAM cmd-option | cmd-option | is an invalid parameter option. |
Cause An error was detected in the TMF SGP startup PARAM string. Effect The rest of the PARAM string from the point of the error is
ignored. Recovery Reenter the TMF SGP startup PARAM string using valid parameters. |
4530 ASAPTMF Process name create error= error-num | error-num | is the error returned by the NonStop operating system
processname_create_ procedure call. |
Cause An error occurred while trying to get a process name from the
system. Effect The TMFSERVE process cannot start since no process name is obtained.
The TMF SGP will try to get a process name again at the next sampling.
No TMF statistics are collected until the TMF SGP successfully starts
the TMFSERVE process. Recovery Use error-num to determine the cause
of the error. If you cannot resolve the problem and it persists, contact
your HP support represenatitive. |
4531 ASAPTMF TMFSERVE not licensed error-num
error-detail | error-num | error returned by the NonStop operating system process_create_
procedure call. | error-detail | is additional error information returned by the process_create_
procedure call. |
Cause The NonStop operating system process_create_ procedure call
returned an error when trying to start the TMFSERVE process because
the process is not licensed. Effect The TMFSERVE process does not start. The TMF SGP will try to
start it again at the next sampling. No TMF statistics are collected
until the TMF SGP successfully starts the TMFSERVE process. Recovery Use error-num and error-detail to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4532 ASAPTMF Process create error error-num
error-detail | error-num | is the error returned by the NonStop operating system
process_create_ procedure call. | error-detail | is additional error information returned by the process_create_
procedure call. |
Cause The NonStop operating system process_create_ procedure call
returned an error when trying to start the TMFSERVE process. Effect The TMFSERVE process does not start. The TMF SGP will try to
start it again at the next sampling. No TMF statistics are collected
until the TMF SGP successfully starts the TMFSERVE process. Recovery Use error-num and error-detail to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4533 ASAPTMF TMFSERVE open error error-num | error-num | is the error returned when trying to open the TMFSERVE
process. |
Cause An error occurred when trying to open the TMFSERVE process. Effect The TMFSERVE process does not open. The TMF SGP will try to
open it again at the next sampling. No TMF statistics are collected
until the TMF SGP successfully opens the TMFSERVE process. Recovery Use error-num to determine the cause
of the error. If you cannot resolve the problem, contact your HP support
representative. |
4534 ASAPTMF TMFSERVE startup writeread error error-num | error-num | is the error returned when trying to send the startup
message to the TMFSERVE process. |
Cause An error occurred when trying to send the startup message to
the TMFSERVE process. Effect The TMFSERVE process is closed since it does not receive the
startup message. The TMF SGP will try to open the process again at
the next sampling. No TMF statistics are collected until the TMF SGP
successfully opens the TMFSERVE process. Recovery Use error-num to determine the cause
of the error. If you cannot resolve the problem, contact your HP support
representative. |
4535 ASAPTMF TMFSERVE startup awaitio error error-num | error-num | is the error returned when trying to send the startup
message to the TMFSERVE process. |
Cause An error occurred when trying to send the startup message to
the TMFSERVE process. Effect The TMFSERVE process is closed since it does not receive the
startup message. The TMF SGP will try to open the process again at
the next sampling. No TMF statistics are collected until the TMF SGP
successfully opens the TMFSERVE process. Recovery Use error-num to determine the cause
of the error. If you cannot resolve the problem, contact your HP support
representative. |
4536 ASAPTMF TMFSERVE close error error-num | error-num | is the error returned when trying to close the TMFSERVE
process. |
Cause An error occurred when trying to close the TMFSERVE process. Effect The TMFSERVE process cannot close after receiving its startup
message. The TMF SGP will try to close the process again at the next
sampling. No TMF statistics are collected until the TMF SGP successfully
communicates with the TMFSERVE process. Recovery Use error-num to determine the cause
of the error. If you cannot resolve the problem, contact your HP support
representative. |
4550 ASAPTMF spi-cmd ,SPI
Error Init= error-num | spi-cmd | is the SPI command on which the error occurred. | error-num | is the SPI error returned by SSINIT on a SPI buffer. |
Cause When trying to initialize a SPI buffer, a SPI error was returned. Effect The SPI buffer cannot initialize, so the SPI command is not
sent to the TMFSERVE process for this sampling. The error is reported
against the appropriate domain. Recovery Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4551 ASAPTMF spi-cmd ,SPI
Error Send= error-num | spi-cmd | is the SPI command on which the error occurred. | error-num | is the SPI error returned while sending the SPI buffer. |
Cause When sending a SPI buffer to the TMFSERVE process, a SPI error
was returned. Effect The SPI buffer is not sent, so the associated TMF statistics
are not obtained for this sampling. The error is reported against
the appropriate domain. Recovery Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4552 ASAPTMF spi-cmd ,FS
Error Send= error-num | spi-cmd | is the SPI command on which the error occurred. | error-num | is the file-system error returned while sending the
SPI buffer. |
Cause When sending a SPI buffer to the TMFSERVE process, a file-system
error was returned. Effect The SPI buffer is not sent, so the associated TMF statistics
are not obtained for this sampling. The error is reported against
the appropriate domain. Recovery Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4553 ASAPTMF spi-cmd ,SPI
Error token= error-num | spi-cmd | is the SPI command on which the error occurred. | token | is the token on which the error occurred. | error-num | is the SPI error returned while extracting a token
from the SPI buffer. |
Cause When extracting a simple token from a SPI buffer, a SPI error
was returned. Effect The SPI buffer is not interpreted, so the associated TMF statistics
are not obtained for this sampling. The error is reported against
the appropriate domain. Recovery Use spi-cmd, token, and error-num to determine the cause
of the error. If you cannot resolve the problem, contact your HP support
representative. |
4554 ASAPTMF spi-cmd ,TMF
Error= error-num | spi-cmd | is the SPI command on which the error occurred. | error-num | is the TMF error returned by the TMFSERVE process. |
Cause The TMFSERVE process returned a TMF error for the requested
command. Effect The associated TMF statistics are not obtained for this sampling.
The error is reported against the appropriate domain. Recovery Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4555 ASAPTMF spi-cmd ,SPI
Error Map= error-num | spi-cmd | is the SPI command on which the error occurred. | error-num | is the SPI error returned while extracting the structured
token from the SPI buffer. |
Cause When extracting the structured token from a SPI buffer, a SPI
error was returned. Effect The SPI buffer is not interpreted, so the associated TMF statistics
are not obtained for this sampling. The error is reported against
the appropriate domain. Recovery Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4556 ASAPTMF spi-cmd ,SPI
Error SaveSPIBuf= error-num | spi-cmd | is the SPI command on which the error occurred. | error-num | is the SPI error returned while saving the SPI buffer. |
Cause When saving the SPI buffer, a SPI error was returned. Effect The SPI buffer is not interpreted, so the associated TMF statistics
are not obtained for this sampling. The error is reported against
the appropriate domain. Recovery Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4557 ASAPTMF spi-cmd ,SPI
Error EnterList= error-num | spi-cmd | is the SPI command on which the error occurred. | error-num | is the SPI error returned while handling the multiple
list tokens. |
Cause When handling the multiple list tokens, a SPI error was returned. Effect The SPI buffer is not interpreted, so the associated TMF statistics
are not obtained for this sampling. The error is reported against
the appropriate domain. Recovery Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4558 ASAPTMF spi-cmd ,SPI
Error ExitList= error-num | spi-cmd | is the SPI command on which the error occurred. | error-num | is the SPI error returned while handling the multiple
list tokens. |
Cause When handling the multiple list tokens, a SPI error was returned. Effect The SPI buffer is not interpreted, so the associated TMF statistics
are not obtained for this sampling. The error is reported against
the appropriate domain. Recovery Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4559 ASAPTMF spi-cmd ,SPI
Error Context= error-num | spi-cmd | is the SPI command on which the error occurred. | error-num | is the SPI error returned while handling the context
token. |
Cause When handling the context token, a SPI error was returned. Effect The SPI buffer is not interpreted, so the associated TMF statistics
are not obtained for this sampling. The error is reported against
the appropriate domain. Recovery Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem,
contact your HP support representative. |
4592 TMF TMFSERVE stopped, error= error-num | error-num | is the error returned by TMFSERVE when stopping. Zero
means there was no error while stopping. |
Cause The TMFSERVE process stopped with the displayed error. Effect The TMFSERVE process stops. Recovery Informational message; no corrective action is necessary. |
4593 TMF TMFSERVE started | Cause The TMFSERVE process started. Effect The TMFSERVE process starts. Recovery Informational message; no corrective action is necessary. |
4594 TMF EDL loaded | Cause The EDL was correctly loaded for the TMF SGP. Effect The SGP startup continues. Recovery Informational message; no corrective action is necessary. |
4595 TMF Stats performance messages. | Cause This is a performance statistics message for internal HP use
only. Effect None. Recovery Informational message; no corrective action is necessary. |
4596 TMF Reloading previous configuration. | Cause An error occurred when trying to load a new domain list. Effect The previous list of monitored domains is loaded. Recovery Informational message; no corrective action is necessary. |
4597 TMF Could not load all domains: maximum reached. | Cause More domains are defined in the Objectives Database than the
TMF SGP can accept. Effect Domains in the database exceeding the maximum are not monitored. Recovery Remove some domains from the Objectives Database using the MONITOR
TMF, DELETE command and then the COMMIT TMF command. |
4598 TMF Autoconfiguration completed. | Cause No domains were defined in the Objectives Database to monitor. Effect The TMF SGP configures all supported TMF domains by default. Recovery To modify the list of domains to monitor, use the MONITOR command
and then the COMMIT command. Autoconfigured domains are then automatically
removed. |
4599 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
4601 sgpid Segment allocation
error: error error-detail | sgpid | is the identification number of the Process SGP. | error | is the error code returned from the call to SEGMENT_ALLOCATE_. | error-detail | is the detailed error, if any, returned from the call
to SEGMENT_ALLOCATE_. |
Cause The Process SGP tried to allocate extended memory to support
its processing, but too little disk space is available for the swap
file or is configured for the processor in KMSF. Effect The Process SGP does not allocate the needed extended memory. Recovery Configure more swap space on disk or in KMSF. |
4602 sgpid Process handle
error: error | sgpid | is the identification number of the Process SGP. | error | is the file-system error that prevented the ASAPX
SGP from obtaining the process handle. |
Cause A file system error prevented ASAPXSGP from obtaining the handle
of a process that the Process SGP is trying to monitor. Effect ASAP does not monitor the process. Recovery Correct the file-system error. |
4603 Returned text from the EDL compiler. | Cause Either a syntax error on EDL or missing or corrpted EDL files
caused an error when the Process SGP tried to load and compile ASAP
EDL. Effect ASAP EDL is not loaded and compiled. Recovery Check the EDL files to ensure they exist and are accurate, and
restart the Process SGP. |
4604 sgpid Error loading
objects to monitor, FE: error | sgpid | is the identification number of the Process SGP. | error | is the file-system error that causes the objects load
to fail. |
Cause A corrupt or missing Objectives2 database or another error caused
a file system error when the Process SGP tried to load its set of
monitored objects. Effect The Process SGP does not load its set of monitored objects.
Monitoring does not begin. Recovery Check the ASAPCONF OBJECTIVESDB file name and then restart the
SGP. |
4605 sgpid Maximum number
of monitored domains exceeded | sgpid | is the identification number of the Process SGP. |
Cause The Process SGP was configured to monitor more than the maximum
number of domains. Effect Only the first 1000 processes listed are monitored. Recovery Configure ASAP to monitor fewer processes. |
4606 Pool Definition error: error | Cause The address_delimit_ procedure returned an error while the SGP
was attempting to define pool space for dynamically resolved domains. Effect The ASAP SGP could not allocate pool space to store domains
that are dynamically resolved at each interval, such as domains specified
using wild-card specifiers. Recovery Correct the error condition and restart ASAP. |
4607 No more Pool Space, Max Domains reached | Cause The pool space allocated for dynamically resolved domains has
been depleted. Effect ASAP stops processing any more dynamically resolved domains
for that interval. Recovery Redefine domains so they are not dynamically resolved or increase
the pool space using the MBYTES SET parameter. |
4609 Error SET PARAM: param | Cause The ASAP SGP detected an error with one of its startup parameters. Effect The parameter in question has no effect and any parameters following
the parameter in error are not processed. Recovery Correct the parameter and restart ASAP. |
4699 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed had occurred xxxx times. Recovery None. |
4700 ASAPCMM NonStop Kernel must be release D40 or
Greater | Cause ASAPCMM cannot be started. Effect ASAPCMM is not operating. Recovery Shut down the ASAPMON, set CMM off, and restart the ASAP Monitor. |
4708 ASAPCMM Measure Data File In Use err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPCMM could not create a Measure data file. Effect ASAPCMM cannot obtain SWAN communication line counters. Comm
line status information is valid when ASAPCMM cannot obtain the communication
line counters. Recovery Stop and delete the measurement named ZCMM xxx, where xxx is the ASAP ID. Use the Measure
interface MEASCOM. |
4715 ASAPCMM Error SET CMM PARAM CPU nn cpu | cpu | is the CPU number selected. |
Cause The Comm SGP could not start a measurement in the specified
CPU. Effect ASAPCMM starts the measurement in the CPU where the ASAPCMM
process is running. Recovery If the ASAPMON CPU is not desirable, shut down ASAPMON, correct
the Comm Param CPU nn to a valid and operational
CPU. |
4720 ASAPCMM ZCMMXXX started. | Cause ASAPCMM started a measurement successfully. Effect ASAPCMM is operating. Recovery Informational message only; no corrective action is needed. |
4721 ASAPCMM ZCMMXXX NOT
started. | Cause ASAPCMM could not start a measurement. Effect ASAPCMM cannot obtain communication line counters. Communication
line status information is valid when ASAPCMM cannot obtain the communication
counters. Recovery Check for previous ASAP log messages from ASAPCMM and make appropriate
corrections. |
4722 ASAPCMM restarted err | err | is the Measure error returned from the Measure subsystem. |
Cause ASAPCMM restarted the measurement. Effect ASAPCMM could not obtain communication line counters during
a sample interval. Possibly the Measure subsystem was stopped and
restarted. Communication line statistics are set to null for the sample
interval when ASAPCMM cannot obtain communication line counters. Recovery Informational message only; no corrective action is needed. |
4723 ASAPCMM started Measctl in CPU nn cpu | Cause The Communication SGP started the MEASCTL process in a CPU that
did not have the MEASCTL process running. Effect ASAPCMM starts MEASCTL in the CPU. Recovery Informational message only; no corrective action is needed. |
4725 ASAPCMM Measure error measure err | measure | is the Measure error. | err | is the Communication SGP internal error number for
ASAP development. |
Cause The Communication SGP received an error from the Measure subsystem. Effect Communication line statistics are set to null for the sample
interval when the error occurred. Recovery Report this problem to HP support. |
4735 ASAPCMM -> COLLECT send error: err | err | is the file-system error number associated with the
last operation on the file. |
Cause ASAPCMM encountered an error while attempting to send a message
to the ASAP Collector. Effect ASAPCMM cannot complete the request. Recovery The FILEINFO system call returned this error. For corrective
action for the specified error code, see Appendix B or the Guardian Procedure Errors
and Messages Manual. |
4742 ASAPCMM Config access error ldev | ldev | is the logical device number. |
Cause The Communication SGP could not access the device control table. ldev represents the logical number of the device. Effect ASAPCMM cannot collect communication statistics. Recovery Contact your HP representative to file an HP Product Case. |
4744 ASAPCMM Comm device inaccessible ldev ctrl | ldev | is the logical device number. | ctrl | is the controller for D-series RVUs or the module
for G-series RVUs. |
Cause The Communication SGP could not access the device. Effect ASAPCMM cannot collect Communication line counters. Communication
line status information is valid when ASAPCMM cannot obtain the communication
counters. Recovery Contact your HP representative to file an HP Product Case. |
4747 ASAPCMM unable to stop Comm Measurement. err | err | is the Measure error number. |
Cause ASAPCMM could not stop its measurement. err represents the Measure error returned from the Measure subsystem. Effect ASAPCMM could not stop the measurement named ZCMM xxx, where xxx is the ASAP
ID. Recovery Stop and delete the measurement named ZCMMP xxx, where xxx is the ASAP ID. Use the Measure
interface MEASCOM. |
4748 ASAPCMM Comm Measurement stopped | Cause The ASAPMON process stopped the ASAPCMM process. Effect ASAPCMM stops its measurement. Recovery This message is informational only. No corrective action is
required. |
4750 Error SET COMM PARAM param | param | is the invalid parameter. |
Cause ASAPCMM detected an invalid parameter in the SET COMM ON, PARAMETER
command. Effect ASAPCMM uses the default values for all parameters. Recovery Ensure that all parameters in the ASAP startup file ASAPCONF
are valid. Then restart the ASAP Monitor. |
4751 ASAPCMM ECB_Load Error error-text | error-text | is the error text returned from the Ecb_loadentities_
procedure. |
Cause The ASAP ecb_loadentities_ procedure returned the specified
error when trying to load the Comm entity. Effect The Comm entity does not load EDL records. Recovery This error might be caused by the EDL settings. For more information
on ASAP EDL, see the ASAP Client Manual. |
4753 ASAPCMM sgp_readdomain_ Error err | err | is the error number returned from the SGP_ReadDomain_
procedure. |
Cause The ASAP sgp_readdomain_ procedure returned the specified error
when trying to get the list of Comm domains to monitor. Effect Communication monitoring of all devices will occur. Recovery Make sure that ASAP is configured correctly. For more information
about configuring domains, see the ASAP Extension Manual. If the configuration is correct, contact your HP support representative. |
4754 Load Objectives Error: err, ldev | err | is the error number returned from the Load^Objectives
procedure. | ldev | is the logical number of the communication line that
failed. |
Cause The ASAP Load^Objectives procedure returned the specified error
when trying to get the list of communication objectives. Effect Comm SGP monitors all configured communication lines. Recovery Make sure that ASAP is configured correctly. For more information
about Ranking Objectives, see the ASAP Server Manual. If the configuration is correct, contact your HP support representative. |
4756 GetObjectives Error err, ldev | err | is the error number returned from the SGP_GETOBJECTIVES_
procedure. | ldev | is the logical number of the Comm line that failed. |
Cause The ASAP sgp_Getobjectives procedure returned the specified
error when trying to get the list of Comm objectives. Effect The Comm SGP monitors all configured comm lines. Recovery Make sure ASAP is configured correctly. For more information
about Ranking Objectives, see the ASAP Server Manual. If the configuration is correct, contact your HP support representative. |
4757 ASAPCMM Rank Values error= err, error-detail | err | is the error number returned from the SGP_RankValues
procedure. | error-detail | is the error detail number returned from the SGP_RankValues
procedure. |
Cause The ASAP sgp_rankvalues procedure returned the specified error
when trying to rank Comm objectives. Effect The Comm objectives for all ranked objectives will be equal
to an OEM state value of 1 for the sample period. Recovery Make sure ASAP is configured correctly. For more information
about ranking objectives, see the ASAP Server Manual. If the configuration is correct, contact your HP support representative. |
4766 ASAPCMM Bad Stats Received ldev | ldev | is the logical number of the device. |
Cause The ASAP Comm SGP encountered a bad statistics record. Effect The bad statistics record is discarded. Recovery If the error persists, contact your HP support representative. |
4799 ASAP ASAP Error #.... occurred xxxx time(s) | xxxx | is the number of times the error occurred. |
Cause The error number was suppressed. Effect The error number suppressed occurred xxxx times. Recovery None. |
|