HP NonStop ASAP Messages Manual Abstract This manual documents the messages produced by the Availability Statistics and Performance Monitor (ASAP)—an availability, state, and performance statistics collection infrastructure for HP NonStop™ operating system and application resources. It also documents messages for the ASAP Extension. Product Version ASAP Server Release 2.8 Supported Release Version Updates (RVUs) This manual supports D43.00 and subsequent D-series RVUs, G06.
Document History Part Number Product Version Published 429917-001 ASAP Server N.A. June 2001 429917-002 ASAP Server Release 2.5 October 2004 429917-003 ASAP Server Release 2.7 May 2006 429917-004 ASAP Server Release 2.
HP NonStop ASAP Messages Manual Index Tables What’s New in This Manual iii Manual Information iii New and Changed Information About This Manual ix Notation Conventions iii ix 1. ASAP and ASAP Extension Error Messages ASAP Error Message Summary ASAP Error Messages 1-15 1-1 2. ASAP EMS Messages ASAP Event Tokens 2-11 ASAP Event Message Descriptions 2-13 3.
Tables (continued) Contents Tables (continued) Table 1-12. Table 2-1. Table 2-2. Table 2-3. Table 2-4. Table 2-5. Table 2-6. Table 2-7. Table 2-8. Table 2-9. Table 2-10. Table 2-11. Table 3-1. Table 3-2. Table 3-3.
What’s New in This Manual Manual Information HP NonStop ASAP Messages Manual Abstract This manual documents the messages produced by the Availability Statistics and Performance Monitor (ASAP)—an availability, state, and performance statistics collection infrastructure for HP NonStop™ operating system and application resources. It also documents messages for the ASAP Extension. Product Version ASAP Server Release 2.8 Supported Release Version Updates (RVUs) This manual supports D43.
Previous Changes What’s New in This Manual • • Removed events 4201 through 4299 from Section 1, ASAP and ASAP Extension Error Messages Updated the description of the sgpid parameter for events 4601 on page 1-131, 4602 on page 1-132, 4604 on page 1-133, and 4605 on page 1-133 The second edition of the manual contains these changes to support ASAP Release 2.
Previous Changes What’s New in This Manual • • • • ° ° ° ° ° ° ° ° ° ° ° ° ° 4735 on page 1-140 4742 on page 1-140 4744 on page 1-141 4747 on page 1-141 4748 on page 1-141 4750 on page 1-142 4751 on page 1-142 4753 on page 1-142 4754 on page 1-143 4756 on page 1-143 4757 on page 1-143 4766 on page 1-144 4799 on page 1-144 Table 1-12, Communication Messages, on page 1-14, was added. Table 2-11, COMM Event Messages, on page 2-11, was added.
Previous Changes What’s New in This Manual • • ° ° ° ° ° ° ° ° ° ° ° ° ° ° ° 4725: ZASP-EVT-CMM-MEASURE-ERROR on page 2-171 4735: ZASP-EVT-CMM-COLLECT-ERROR on page 2-171 4742: ZASP-EVT-DSK-CONF-ACCESS-ERROR on page 2-172 4743: ZASP-EVT-CMM-MEAS-NOT-RESTARTD on page 2-172 4744: ZASP-EVT-CMM-DEVICE-INACCESSBL on page 2-172 4747: ZASP-EVT-CMM-SHUTDWN-INCMPLETE on page 2-173 4748: ZASP-EVT-CMM-SHUTDWN-COMPLETE on page 2-173 4750: ZASP-EVT-CMM-PARAM-ERROR on page 2-174 4751: ZASP-EVT-CMM-ECB-LOAD-ERROR on p
Previous Changes What’s New in This Manual • • ° ° ° ° ° DOTs event messages (4000, 4001, 4021 through 4023, and 4099) ° TMF event messages (4501 through 4509, 4530 through 4536, 4550 through 4559, and 4592 through 4599) ° PROCESS event messages (4601 through 4605, and 4699) RDF event messages (4101, 4102, 4104 through 4106, and 4199) FILE event messages (4201 through 4215, and 4294 through 4299) SPOOLER event messages (4301 through 4317, and 4393 though 4399) TAPE event messages (4401, 4402, 4404
Previous Changes What’s New in This Manual HP NonStop ASAP Messages Manual— 429917-004 viii
About This Manual This manual documents the event messages generated by the Availability Statistics and Performance (ASAP) software, and the ASAP Extension (ASAPX). For more information about the ASAP Client interface, see the ASAP Client Manual. For more information about the ASAP Server software, see the ASAP Server Manual. For more information about the ASAP Extension, see the ASAP Extension Manual. Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text.
General Syntax Notation About This Manual [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces.
Notation for Messages About This Manual Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.#su-name Line Spacing.
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
Notation for Management Programming Interfaces About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number.
Change Bar Notation About This Manual HP NonStop ASAP Messages Manual— 429917-004 xiv
1 ASAP and ASAP Extension Error Messages This section describes the ASAP and ASAP Extension error messages: Topic Page ASAP Error Message Summary 1-1 ASAP Error Messages 1-15 ASAP Error Message Summary Table 1-1 shows Monitor messages logged to EMS and ASAPLOG. Basic text messages of this format are always logged to the ASAPLOG file. In addition, these same messages are logged to EMS. If the SET EVENTS option is set to NOEMS, a non-tokenized, simple text message is logged.
Table 1-1.
Table 1-1. Monitor Messages Logged to EMS and ASAPLOG (page 3 of 4) Message Number Monitor Messages Parameters 1210 NewProcess $System.System.Ozexp Error 0:7,8:15: err.0:7, err.
Table 1-1. Monitor Messages Logged to EMS and ASAPLOG (page 4 of 4) Message Number Monitor Messages Parameters 1303 pin:ProcessTime delta:Sampletime delta in .1 sec pin#, dpt, dst 1304 ProcessTime delta too big:last 2 INTs in .1 sec pin#, dpt1, dpt2 1305 Pin:This_ProcessTime:Last_ProcessTime in 10 sec pin#, pt1, pt2 1306 Pin:Alive but No PCB:priority: Last_PTime in .
Table 1-2.
Table 1-3.
Table 1-3. Collect Messages Logged to EMS and ASAPLOG (page 2 of 2) Message Number APP Messages Parameters 1880 Shutdown Complete! Requestor = pid 1881 ASAPX INFO started, component, version, cpu 1899 Error # ....occurred xxxx times num, x Table 1-4.
Table 1-4.
Table 1-6. DOTs Messages Logged to EMS Message Number DOTs Messages Parameters 4000 ASAP INFO | ALERT component, entity, domain, attribute, attval 4001 ASAP INFO (OK) component, entity, domain, attribute, attval 4021 ASAP ERR objective record(s) not loaded, EDL mismatch component, recnum, entity 4022 ASAP ERR Segment allocation error: component, err, error-detail 4023 ASAP ERR , FE: component, filename, error 4024 Action Server I/O Error, FE: error 4099 Error # ....
Table 1-8. SPOOLER Messages (page 2 of 2) Message Number Spooler Messages Parameters 4305 No type stats entry available in find^entry for SGP SPL. No type stats entry available in check^setup^domain for SGP SPL.
Table 1-9. TAPE Messages (page 1 of 2) Message Number Tape Messages Parameters 4401 TAP ecb loadentities error-text 4402 TAP sgp readdomain_ Error= FE: error 4404 TAP SSINIT Error: TAP SSGET error: TAP SSGETTKN Get error: TAP SSPUT error: TAP SSPUTTKN error: TAP SPI Last Error: TAP SPI Return Error: TAP SPI Dlist RetCode error: TAP SSNULL error: cmd-token, cmd, token, error 4405 TAP could not start .
Table 1-9. TAPE Messages (page 2 of 2) Message Number Tape Messages 4497 TAP Could not load all domains: maximum of num reached. 4498 TAP Autoconfiguration completed. 4499 Error # ....occurred xxxx times Parameters num, x Table 1-10.
Table 1-10.
Table 1-11. File, Query, Process, and TCP/IP Messages Message Number File and PROCESS Messages Parameters 4615 Error starting server process error, error detail 4616 server start retry limit exhausted 4617 function-location SPI Error: error 4618 Duplicate Domain found during SORT, lowpass Count 4699 Error # ....occurred xxxx times Table 1-12. Communication Messages Message Number Communication Messages Parameters 4700 ASAPCMM NonStop Kernel Must be release D40 or Greater.
ASAP Error Messages This subsection contains a detailed description of the ASAP Server messages: 1000 SGP Open pid error: err err is the file-system error number associated with the last operation on the file. Cause. The Statistics Gathering process (SGP) did not open. Effect. Instead of an SGP process, a zero value was returned. Recovery. The FILEINFO system call returned this error.
1002 Send to SGP pid error: err, type, read^L err is the file-system error number associated with the last operation on the file. type is the request type. read^L is the sum of the length of the 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.
1004 Bad SGP stat^sum reply: type, words type is the current statistics type. words is 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 HP representative. 1005 Sync, COLLECT I/O error: err err is the file-system error number associated with the last operation on the file. Cause. Synchronization between the Server and Collector was not accomplished. Effect.
Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see file-system errors in the Operator Messages Manual or 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.
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 HP representative. 1011 Short request received count, buf, pid count is the length of the message, in bytes.
1013 Illegal request received: buf, count, pid buf is the first word of the received request message. count is the length of the message, in bytes. pid is the requester’s process ID. Cause. An invalid request was received. Effect. The system did not process the request. Recovery. Retry the request. If the request is valid but still does not work, contact your HP representative. 1014 startup msg error message: charoffset charoffset offset of the message that was not recognized Cause.
1016 SGP startup msg fail, fe: cpu, err err is the file-system error number associated with the last operation on the file. cpu is the CPU number. Cause. The Statistics Gathering process (SGP) did not receive the startup message. Effect. The SGP did not start up. Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see the Operator Messages Manual or the Guardian Procedure Errors and Messages Manual.
0 No error, process created error 15 = 0, program file is in error = 1, library file is in error 7 Unlicensed privileged program 8 Process name error; error 8:15 = file-system error number 9 Library conflict 10 Unable to communicate with system Monitor process; error 8:15 = file-system error number 11 File-system error occurred on library file; error 8:15 = filesystem error number 12 Program file and library file specified are same file 13 Extended data segment initialization error; error 8:
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. Cause. The ASAP version is out of sync with the NonStop operating system version. Effect. ASAP will not run. Recovery.
1020 SHUTDOWN Complete! Requester= pid pid is the requester’s process ID. 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.
1024 $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. Effect. The system did not receive the message. Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see the Operator Messages Manual or the Guardian Procedure Errors and Messages Manual. Retry your operation, but this time pause for awhile between commands.
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 cpu is the CPU number. Cause. The ASAP Monitor SGP received an incorrect system name. Effect. The bad statistics record is discarded. Recovery. If the error persists, contact your HP support representative. 1028 Invalid Sys.
1030 ACTION startup msg fail, FE err err is the error number. 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.
1033 Send to Action Server failed err err is the error number. 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 the error text returned from Ecb_loadentities_ procedure. Cause.
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.
Cause. The ASAPMON process could not start the SGP in the user specified cpu. Effect. THE ASAPMIN will start the SGP in the cpu where the ASAP monitor process recides. Recovery. Specify an avialable cpu using the set SgpID cpu nn. 1060 ASAPACT script file missing error error file-system error number Cause. The ASAP Action server file ASAPACT is missing. This file is always installed, this error indicates ASAP was not properly installed. Effect. The Action server cannot be started. Actions will not occur.
1097 Software License Expired xx Days ago xx is the number of days the software license has been expired. Cause. The software license for the ASAP component has expired. Effect. There is no effect until the epiration date. Recovery. Renew or obtain a software license for the ASAP component. 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.
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 HP representative. 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.
1210 NewProcess $System.System.
error 8:15 = 1 - flags 10 = 1 AND flags 12 <> 0 AND If the process creation attempt is on a remote system that is a NonStop 1+, or any other NonStop system operating under a NonStop operating system version B20 or earlier, use of DEFINEs is disallowed. error 8:15 = 2 Internal context propagation error. error 8:15 = 3 Invalid DEFMOD supplied.
1220 Can't create Subsystem Mgr ($ZEXP), Error: err err is the file-system error number associated with the last operation on the file. Cause. The Expand SGP could not create a Subsystem Manager. Effect. ASAP and the subsystem cannot communicate. Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see the Operator Messages Manual or the Guardian Procedure Errors and Messages Manual. Check that the NonStop Kernel Subsystem Manager is secured properly.
-4 Indicates an invalid parameter address -5 Indicates the buffer is full -6 Indicates an invalid checksum -7 Indicates an internal error -8 Indicates the list token was not found -9 Indicates an invalid token code or map -10 Indicates an invalid subsystem ID -11 Indicates the operation is not supported -12 Indicates insufficient stack space Cause. The Expand SGP could not build a Subsystem Programmatic Interface (SPI) request buffer. Effect. No information was returned by SPI. Recovery.
1233 Monitor -> ExpMgr ($ZEXP) SPI Error: err err is one of these SPI error numbers: 0 Indicates there is no error -1 Indicates an invalid buffer format -2 Indicates an invalid parameter value -3 Indicates a missing parameter -4 Indicates an invalid parameter address -5 Indicates the buffer is full -6 Indicates an invalid checksum -7 Indicates an internal error -8 Indicates the list token was not found -9 Indicates an invalid token code or map -10 Indicates an invalid subsystem ID -11
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. Contact your HP representative. 1236 Expand SGP -> Can’t obtain Path statistics Error: err, ldev err is the SPI error number returned by the $ZEXP process.
Recovery. HP uses this error message for problem isolation. Contact your HP representative. 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. Contact your HP representative.
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. Contact your HP representative. 1241 ASAPEXP -> COLLECT send error: err err is the returned file-system error number associated with the last operation on the file. Cause.
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. 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 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. 1250 Error SET EXPAND PARAM param param contains the parameter that caused the problem. Cause.
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.
1256 GetObjectives Error: err, Ldev err is the error number returned from 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.
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 zero length err is the error returned from the GetPeekPCBs system call. Cause.
pin# is the PIN number of the process. 0 Indicates the status of the process CPU, PIN returns. 1 Indicates the process CPU, PIN does not exist or does not match the specified criteria. The status for the next higher CPU, PIN in the specified processor is returned. The four-word process ID for which status is being returned reflects the process ID parameters, if present. 2 Indicates the process CPU, PIN does not exist, and no higher CPU, PIN exists in the process that matches the specified criteria.
1303 pin:ProcessTime delta:Sampletime delta in .1 sec: pin#, dpt, dst pin# is the PIN of the process. 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 PCB busy, possibly because of a NonStop operating system internal interface failure. Effect. The PCB busy information is suspect. Recovery. If the problem persists, contact your HP representative. 1304 ProcessTime delta too big:last 2 INTs in .
1305 Pin:This_ProcessTime:Last_ProcessTime in 10 sec: pin#, pt1, pt2 pin# is the PIN number of the process. 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 PCB busy, 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 HP representative.
1307 Process Not in the Sample Data: pin#, which pin# represents the PIN number of the process. which represents: 0 Current sample array 1 Previous array Cause. The process specified is not in the internal sample array. This is an internal error. Effect. PCB information cannot be returned. Recovery. If the problem persists, contact your HP representative. 1308 bad SMON Subsampling Cause. Internal ASAP algorithms are detecting bad subsampling. Effect.
3 Indicates the Monitor cannot communicate with the CPU. 4 Indicates the CPU does not exist. 5 Indicates that the system specified by sysnum could not be accessed. 99 Indicates a parameter error. Cause. The Monitor could not collect PCB information. Effect. A zero value was returned rather than the PCB statistics values. Recovery. The FILEINFO system call returned this error.
6 Indicates you cannot communicate with the node. 7 Indicates an invalid return attribute was supplied. 8 Indicates the specified node is running a C-series RVU; this system call cannot obtain information from a system running a C-series RVU. Cause. The Monitor could not retrieve the CPU processor type. Effect. A CPU processor type value was not returned. Recovery. The FILEINFO system call returned this error.
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 occurred xxxx times. Recovery. None. 1503 Send to collect error: error error the file-systemfile-system error encountered when sending stats to the server Cause. An error occurred when writing to the ASAP Collector process. Effect. The statistics cannot be sent to the Collector. Recovery. Correct the file-system error.
1519 SGP sgp-pid detected that its server abended server-pid sgp-pid the prcess ID of the sending process. server-pid the process ID of the server process Cause. The server process abended. Effect. Statistics cannot be collected from the server process. Recovery. Restart the server process if it is not automaticall restarted. 1530 Error SET NODE PARAM Cause. An error was found while processing startup parameters. Effect. The startup parameter is ignored. Recovery.
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 to NUNU: $system.sysxx.measctl; $system.sysxx.measfh; $system.sysxx.measmon.
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 SGP could not delete it. Effect. ASAPDSK cannot obtain 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 was not able to 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.
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.
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 Counter Allocation error err err is the Measure error returned from the Measure subsystem Cause.
1721 ASAPDSK ZASAPXXX 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 appropriate corrections. 1722 ASAPDSK restarted err err is the Measure error returned from the Measure subsystem Cause. ASAPDSK restarted the measurement. Effect.
Cause. ASAPDSK detected an invalid parameter in the SET DISK ON, PARAMETER command. Effect. ASAPDSK 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. 1735 ASAPDSK -> COLLECT send error: err err is the file-system error number associated with the last operation on the file Cause. ASAPDSK encountered an error while attempting to send a message to the ASAP Collector. Effect.
Recovery. Specify a valid disk volume using the ASAP command SET DISK,PARAM “Volume<$vol>. 1742 ASAPDSK DCT access error ldev Cause. The Disk SGP could not access the device control table. ldev represents the logical number of the device. Effect. ASAPDSK cannot collect disk statistics. Recovery. Contact your HP representative. 1743 ASAPDSK cannot restart measurement.err Cause. ASAPDSK could not restart its measurement. err represents the Measure error returned from the Measure subsystem. Effect.
Recovery. This message is informational only. No corrective action is needed. 1746 Virtual Disk stats collected by Physical Disk Cause. Virtual disk discovered on the node. Effect. Disk statistics reported are against the physical volume name and not against each virtual disk configured on the physical volume. Recovery. None. 1747 ASAPDSK unable to stop Disk Measurement.err Cause. ASAPDSK could not stop its measurement. err represents the Measure error returned from the Measure subsystem. Effect.
Recovery. Check the ASAP log for previous ASAPDSK messages and make the appropriate corrections. For corrective action for the specified error, see Appendix B of the Measure Reference Manual. If the problem persists, contact your HP representative. 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.
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.
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.
state the operational state value of the device monitored if monitored, the value equals 1. Cause. Internal statistics integrity check failed. Effect. The availability and performance statistics for the device are not written to the ASAP data base. Recovery. Contact HP support to report the problem. 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.
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 Cause. An error/error^detail occurred attempting to allocate an extended memory segment.
1806 Duplicate memory slot for domain: domain, Dmn#: domain number Cause. ASAPX detected duplicate Domain table entries while restarting domain for the same memory slot location. Only the first domain is restarted; all others cause this error message to be generated. This 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.
1808 Objectives load failed, domain: domain, Dmn#: domain number 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 Cause. The application process pname was restarted before ASAPX after a processor or system failure.
1812 Begintransaction error: fname, Er: begintrans 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 begintrans 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] Cause.
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 Cause. ASAPX terminated its commit operation because of excessive errors Error^cnt 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.
1820 DATAITEM definition(s) not defined: fname Cause. (ASAP Release 1 only) ASAPX did not find DATAITEM definitions in fname. An error was 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 Cause.
Recovery. None. ASAPX automatically restarts the process. 1824 Detected that its server abended: pname Cause. An APPXMON process pname abended. ASAPX detected that one of its ASAPXMON servers abended. Effect. None, ASAPXSGP restarts the failed process. Recovery. Locate the SAVEABEND file produced by the abend of the APPXMON process and send it to the GMCSC for analysis. 1825 Processor getinfo failure: cpu, fe Cause. ASAPX could not obtain information from a processor cpu.
Effect. ASAPXSGP stops without starting ASAPX since it could not create either the Domain or Objectives table. Recovery. Correct the file-system error and retry the operation. 1828 Error obtaining NSK MOM: pname, FE: fe Cause. ASAPX could not get the NonStop Kernel MOM identifier pname for one of its servers. To determine the cause of this problem, see a description of file-system error numbers fe. Effect. ASAPXSGP will not receive process stop or abend messages for the ASAPXMON process. Recovery.
Effect. The domain is not automatically restarted. Recovery. Manually remove the domain in question and reregister it, or fix the filesystem 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.
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.
1861 Resetting file security: fname Cause. ASAPX found that the security on a segment file fname 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 Kernel security string for the user ID that starts ASAP to AAnn.
1864 File error on NAMEFILE: fname, FE: error Cause. (ASAP Release 1 only) ASAPX encountered a file error attempting to open the ASAP reserved names file fname. 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.
Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. 2000 DB^write filename, fe: err, sysno, cpuno 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 cpu is the CPU number Cause. The Collector received statistical information from the Monitor, but cannot perform all database record file I/O.
Effect. Statistical information is not being written to the database. Recovery. If the problem persists, contact your HP representative. 2002 Rollover Open filename, fe: err 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. Effect.
2004 Can’t Purgedata filename, fe: err err is the file-system error number associated with the last operation on the file Cause. The system is not performing a needed database cleanup operation. Effect. The purgedata operation is not being executed. The statistics are not being refreshed. Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see the Operator Messages Manual, or the Guardian Procedure Errors and Messages Manual.
Cause. A received message is unrecognizable because of its short length. Effect. The message was not processed. Recovery. Retry the request. If the problem persists, contact your HP representative. 2007 Received shutdown request: pid pid is the requester’s process ID Cause. A shutdown request was received. Effect. Your ASAP session will end. Recovery. This message is informational only. No corrective action is required.
Recovery. Check your Enform request and retry it. If the problem persists, contact your HP representative. 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 did 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.
Cause. The Collector has information to put in the database, but cannot open a database file. Effect. The file was opened successfully. Recovery. This message is informational only. No corrective action is required. 2013 Open filename, INFO: type type is an internal index to the ASAP database with these values: 0 DBSYS 1 DBCPU 2 DBNET 3 DBPCB 5 DBNODE 6 DBAPP 7 DBDSK Cause. The system opened the filename indicated in the message. Effect. The file was opened successfully. Recovery.
Effect. The system is working correctly. Recovery. This message is informational only. No corrective action is required. 2016 COLLECT version started cpu cpu is the CPU number version is the base release version of the ASAP environment 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.
Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see the Operator Messages Manual, or 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; the system needs a momentary pause.
Effect. One or more ASAP command interpreters may not be notified that the data base has ben renamed or rolled over, and will continue to acces the old “Stale” data base. Recovery. Stop/shutdown ASAP command interpreters that are no longer being used. 2022 DST fallback delta detected: seconds seconds is the number of seconds that the DST time will fall back Cause. Daylight Savings Time fall back has occurred. This message indicates that ASAP is aware that the DST time has changed. Effect. None. Recovery.
Effect. The ASAP date files are being maintained based on the DBMAX configuration settings. This message is informational only. Recovery. This message is informative. No recovery is needed. 2026 DBMaxDays files cleaned count count is the number of database file sets that have been purged. Cause. The ASAP Collector is executing database clean up. Effect. The ASAP data files are being maintained based on the DBMAX configuration settings. Recovery. This is an informative message. No recovery is needed.
Cause. The Collector could not create a new partition control file. The cause is most likely a security violation on the partition 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 name of the control file error file-system error number Cause. The partition control file did not exist when the Collector was started.
2034 Collector could not build part ctl file name error error 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.
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.
file-error 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.
2041 CreatePart partition status description description 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.
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 #....
error 15 = 0, program file is in error = 1, library file is in error 7 Unlicensed privileged program 8 Process name error; error 8:15 = file-system error number 9 Library conflict 10 Cannot communicate with system Monitor process; error 8:15 = file-system error number 11 File-system error occurred on library file; error 8:15 = file-system error number 12 Program file and library file specified are same file 13 Extended data segment initialization error; error 8:15 = file-system error number
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. 3001 NonStop Backup Created Cpu: cpu cpu is the CPU number 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.
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 the primary process will not fail, and continue to gather your statistics. 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.
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 text that describes the attribute value Cause.
attribute is the name of the relevant attribute attval 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, EDL mismatch 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 Cause.
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.
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 filesystem 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.
4104 RDF SGP_RANKVALUE_ error: error error 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 GMCSC.
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. 4301 SPL ecb_loadentities_ error-text error-text 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.
4303 Invalid Stats^Type in process^minstate for SGP SPL StatsType: numtype numtype 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.
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 value returned from the SGP_RANKVALUE_ procedure to identify the specific error error-detail 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.
4308 SGP SPL Parsing SGP option cmd cmd 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 NonStop Kernel error returned from the PROCESSHANDLE_DECOMPOSE or PROCESSHANDLE_GETMINE_ procedure Cause.
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 error returned from the FILENAME_TO_PROCESSHANDLE procedure call Cause. The NonStop Kernel 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.
Cause. The specified param is not a valid parameter for the Spooler SGP. Effect. The param 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.
4317 Print Proc entry name not found in SGP SPL. type entry name not found in SGP SPL. name name of entry being looked for type 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 sampling information might not add up. Recovery. Verify the spooler name for the specified entry.
4395 SPL Sampling delay processing: num processing processing area for elapsed time num 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.
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 #....
4402 TAP sgp_readdomain_ Error= FE: error error 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.
4405 TAP could not start filename. Error=error error-detail filename filename used to create the MEDIASRV server process error error information returned by the PROCESS_CREATE_ procedure error-detail detailed error information returned by the PROCESS_CREATE_ procedure Cause. The NonStop Kernel 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.
4407 TAP open error on MEDIASRV. Error=error error error returned from the FILE_OPEN_ procedure call Cause. The MEDIASRV server was started but the Tape SGP could not open it. The NonStop Kernel 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.
4410 TAP Xfer Segment Alloc FE: error error-detail error error value returned by the NonStop Kernel SEGMENT_ALLOCATE_ procedure error-detail error-detail value returned by the NonStop Kernel 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.
4412 TAP MEDIASRV WRITE error:error error 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 that MEDIASRV is properly installed.
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 error returned by the NonStop Kernel DEVICE_GETINFOBYLDEV_ procedure error-detail error detail returned by the NonStop Kernel DEVICE_GETINFOBYLDEV_ procedure Cause. The Tape SGP is in autoconfiguration mode and is trying to find tape devices on the system. The NonStop Kernel DEVICE_GETINFOBYLDEV_ procedure call returned the specified error.
4493 TAP Could not add to last domain table: maximum of num reached. num 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.
4496 TAP Reloading previous configuration. Cause. An error occurred when trying to load the tape domain names to be monitored (see message 4402 on page 1-112). This message indicates that the last list of domains is used instead. Effect. None. Recovery. Informational message. See recovery for message 4402 on page 1-112. 4497 TAP Could not load all domains: maximum of num reached. num maximum number of tape domain entries allowed in the Tape SGP Cause.
4501 ASAPTMF error-text error-text 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.
Recovery. Make sure no problem exists with the ASAP Objectives database. errornum 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.
4507 ASAPTMF Segment alloc: error-num error-detail error-num error returned by the NonStop Kernel segment_allocate_ procedure call error-detail additional error information returned by the segment_allocate_ procedure call Cause. The NonStop Kernel segment_allocate_ procedure call returned an error when trying to allocate an extended segment. 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.
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. Re-enter the TMF SGP startup PARAM string using valid parameters. 4530 ASAPTMF Process name create error= error-num error-num error returned by the NonStop Kernel 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.
4532 ASAPTMF Process create error error-num error-detail error-num error returned by the NonStop Kernel process_create_ procedure call error-detail additional error information returned by the process_create_ procedure call Cause. The NonStop Kernel 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.
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.
4550 ASAPTMF spi-cmd,SPI Error Init= error-num spi-cmd SPI command on which the error occurred error-num 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.
error-num 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.
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 SPI command on which the error occurred error-num 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.
error-num 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.
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.
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. There are more domains defined in the Objectives Database than the TMF SGP can accept. Effect. All domains in the database exceeding the maximum are not monitored. Recovery. Remove some domains from the Objectives Database using the MONITOR TMF, DELETE command, then the COMMIT TMF command.
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.
4604 sgpid Error loading objects to monitor, FE: error sgpid is the identifier of the File or 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 filesystem 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, then restart the SGP.
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. 4608 Internal Pool Management Error Cause. The pool header has been corrupted for the block being allocated. Effect.
Recovery. Correct the SPI error or contact HP support to report the problem. 4611 Server I/O Error on server: error server is the name of the server process. error is the file-system error encountered when communicating with the server. Cause. The SGP received a file-system error when communicating with its server process, server. Effect. ASAP cannot effectively communicate with its server process. Recovery. Correct the file-system error or contact HP support to report the problem.
error detail is the detailed error (if any) encounted when opening the process. Cause. The ASAP SGP cannot open its server process. Effect. ASAP cannot obtain the statistics it normally obtains from its server process. Recovery. Correct the file-system error and then restart ASAP. 4614 Message Sequence Number Invalid Cause. The Query SGP received a message through EMS where the sequence number is not in order. Effect. ASAP does not process the EMS event. Recovery.
Effect. ASAP quits trying to restart its server. Recovery. Fix the server startup problem, and then restart ASAP. 4617 function-location SPI Error: error function-location is the procedure location within the SGP where the error occurred. error is the SPU error encountered by the procedure Cause. The procedure identified by function-location received an error on its SPI interface. Effect. ASAP cannot obtain information about a domain or it statistics. Recovery.
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.
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.
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 as a 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.
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.
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.
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.
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.
2 ASAP EMS Messages This appendix lists the tokenized Event Management Service (EMS) messages generated by ASAP and describes the tokens contained in each message. Event messages of this format are generated if the EVENTS option is set to OFF, ON, INFORMATIVE, or CRITICAL when the Collect or Monitor process is started. Tokenized event messages are not generated if the EVENTS option is set to NOEMS.
Table 2-1.
Table 2-1.
Table 2-1. ASAP Monitor Event Messages (page 4 of 4) Message Number Monitor Messages 1401 ZASP-EVT-CPU-GETINFOLIST-ERROR 1499 ZASP-EVT-EXP-SUPPRESSED-ERRORS xxxx 1503 ZASP-EVT-NCP-COLLECT-ERROR error 1518 ZASP-EVT-SERVER-STOPPED server-pid 1519 ZASP-EVT-SERVER-ABENDED server-pid 1530 ZASP-EVT-NCP-PARAM-ERROR 1599 ZASP-EVT-NCPSUPPRESSED-ERRORS Parameters Table 2-2.
Table 2-2.
Table 2-3.
Table 2-4. ASAP NonStop Event Messages Message Number CPU Statistics Threshold Events Parameters 3000 ZASP-EVT-NO-BACKUP-CREATED cpu, err 0:7, err 8:15 3001 ZASP-EVT-BACKUP-CREATED cpu 3002 ZASP-EVT-NO-CHECKPOINT err 0:7, err 8:15, pid 3003 ZASP-EVT-NO-CPU-AVAILABLE 3004 ZASP-EVT-TAKEOVER 3005 ZASP-EVT-STARTUP-MSG-NOT-RCVD 3099 ZASP-EVT-EXP-SUPPRESSED-ERRORS cpu xxxx Table 2-5.
Table 2-7.
Table 2-8.
Table 2-9.
Table 2-10.
Table 2-11.
ZEMS-TKN-CRTPID contains the ID of the ASAP process that generated the event. ZEMS-TKN-EMPHASIS indicates whether the event is flagged as critical. If this value is TRUE, the event is marked as critical. If this value is FALSE, the event is marked as informative. All ASAP subsystem internal events will have this value set to FALSE. For performance events, it can be set to TRUE using the CRITICAL option of the ASAP Conversational Interface’s SET EVENTS command.
ZASP-TKN-ASAP-ATTRIBUTE-VALUE is present and contains the attribute value for attributes of type INT. ZASP-TKN-ASAP-ATTRIBUTE-INT32 is present and contains the attribute value for attributes of type INT32. ZASP-TKN-ASAP-ATTRIBUTE-INT64 is present and contains the attribute value for attributes of type INT64. ZASP-TKN-ASAP-ATTRIBUTE-CHAR8 is present and contains the attribute value for attributes of type CHAR.
Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual.
• • Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1001”. 1002: ZASPEVT-SGP-SEND-ERROR Send to SGP pid error: err, type, read^L pid is the requester’s process identification. err identifies a file-system error. type identifies the request type.
• • • System number Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1002”. 1003: ZASP-EVT-COLLECT-SEND-ERROR Send to COLLECT error: err err identifies a file-system error. Cause. The Monitor did not send aggregate summary messages to the Collector. The FILEINFO system procedure call returned this error. Effect.
1004: ZASP-EVT-BAD-SGP-STATS 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.
Check the network path connection. Make sure the Collector is up and running. Try the SYNC operation later. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1005”. 1006: ZASP-EVT-SYNC-DELAY-TOO-LONG Sync, delay too long: err err identifies a file-system error. 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.
• • • • Details from the messages generated System number Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1007”. 1008: ZASP-EVT-SYNC-NOT-REQUIRED Sync, not required: delta delta is the time difference in seconds. Cause. The clock is already in synchronized. Effect. Synchronization does not need to occur again.
1010: ZASP-EVT-SYNC-CLOCK-NOT-SET 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. Check that you have the correct security to perform the SYNC operation; you must be in the super group. Retry the request later.
Recovery. If the problem persists, contact your HP support representative and provide all relevant information: • • • • • Descriptions of the problem and accompanying symptoms Details from the messages generated System number Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1011”.
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.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1014”. 1015: ZASP-EVT-MON-OPEN-TERM-ERROR Startup Can’t Open TERM Cause. The terminal log file could not be opened. Effect. The system could not start. Recovery. Check your configured terminal log file name. The SET TERM command displays information about your terminal. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1015”.
1017: ZASP-EVT-SGP-CREATE-ERROR 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 one of these values: Err.<0:7> Meaning 0 No error; process created. 1 Warning that the process had undefined externals, but was started. 2 No process control block (PCB) available. 3 File-system error occurred on program file; err.<8:15> = file-system error. 4 Unable to allocate map. 5 File error on swap file; err.
Err.<0:7> Meaning 15 Invalid home terminal; err.<8:15> = file-system error. 16 I/O error to home terminal; err.<8:15> = file-system error. 17 DEFINE context propagation error; if: err.<8:15> = 0 Cannot convert a DEFINE name to network form. err.<8:15> = 1, flags.<10> = 1 AND flags.<12> <> 0 AND If the process-creation attempt is on a remote system that is a NonStop 1+ system, or any other NonStop system operating under operating system version B20 or earlier, use of DEFINEs is disallowed. err.
vers is the ASAP version. Cause. The ASAP version is out of sync with the operating system version. Effect. ASAP does not run. Recovery. Check that the ASAP version and the operating system version are compatible. Retry the request.
• • Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1019”. 1020: ZASP-EVT-MON-SHUTDOWN-COMPLETE SHUTDOWN Complete! Requester= pid pid is the requester’s process identification. Cause. The shutdown operation is complete. Effect. The ASAP session now terminates. Recovery.
1022: ZASP-EVT-MON-STARTED Monitor version started: cpu version is the operating system version. cpu is the CPU number. Cause. The Monitor started successfully. Effect. The Monitor is operating. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1022”. 1023: ZASP-EVT-SGP-STARTED SGP version started: cpu version is the operating system version. cpu is the CPU number. Cause.
1024: ZASP-EVT-MON-RCV-READ-ERROR $RECEIVE read, FE: err err identifies a file-system error. Cause. A NonStop Kernel error occurred while trying to read a system message. The FILEINFO system call returned this error. Effect. The ASAP Monitor or SGP did not receive the message. Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual.
• • Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1025”. 1026: ZASP-EVT-MON-SAMPLE-MISSE Sample Missed. SecsSinceLast>RateSecs sec,rate sec is the number of seconds expired while trying to write to the collector rate is the sample rate configured less 20 percent Cause.
ZASP-TKN-ASAP-ERRORNUM is “1027”. 1028: ZASP-EVT-MON-INVLD-SYSNAME-RCV Invalid Sys.Sysname Received Cause. The ASAP Monitor SGP received an incorrect system name. Effect. The bad statistics record is discarded. Recovery. If the error persists, contact your HP support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "1028". 1029: ZASP-EVT-MON-MISSNG-ACT-SCRIPT ASAPACT script file missing err err is the error number. Cause. The Action script file is missing.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "1030". 1031: ZASP-EVT-MON-ACT-NOT-CREATED Can't create ACTION Server err cpu err is the error number. cpu is the error number. Cause. The ASAP Monitor could not start 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. Data Tokens.
1033: ZASP-EVT-MON-ACT-RPLY-FAILED Send to Action Server failed err err is the error number. 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "1033".
Recovery. This error might be caused by the EDL settings. For more information on ASAP EDL, see the ASAP Client Manual. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1052”. 1053: ZASP-EVT-MON-READDOMAIN-ERROR 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.
ZASP-TKN-ASAP-ERRORNUM is “1056”. 1057:ZASP-EVT-LOG SUPRRESS-OFF Log supression not enabled Cause. Log supression is not enabled. Effect. All error messages will be written to the ASAPLOG file. Recovery. If the user does not intend to see all the error messages written to the log as they occur enter the command SET LOGSUPRESS ON. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1057”.
Cause. The ASAP Action server file ASAPACT is missing. This file is always installed, this error indicates ASAP was not properly installed. Effect. The Action server cannot be started. Actions will not occur. Recovery. Reinstall ASAP and verify that file ASAPACT is present. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1060”. 1095: ZASP-EVT-LICENSE-ERROR license error license error is error text returned from the license validation procedure Cause.
1097: ZASP-EVT-LICENSE HAS EXPIRED Software License Expired xx Days ago xx is the number of days the software license has been expired. Cause. The software license for the ASAP component has expired. Effect. There is no effect until the epiration date. Recovery. Renew or obtain a software license for the ASAP component. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1097”. 1099: ZASP-EVT-MON-SUPPRESSED-ERRORS ASAP ASAP Error #....
Recovery. Check that your operating system version and ASAP version are compatible. If the problem persists, contact your HP support representative and provide all relevant information: • • • • • Descriptions of the problem and accompanying symptoms Details from the messages generated System number Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens.
1199: ZASP-EVT-EXP-SUPPRESSED-ERRORS 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1199”. 1200: ZASP-EVT-LH-NOT-FOUND 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.
ZASP-TKN-ASAP-ERRORNUM is “1200”. 1210: ZASP-EVT-EXPDMGR-CREATE-ERROR 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 one: Err.<0:7> Meaning 0 No error; process created. 1 Warning that the process had undefined externals but was started. 2 No process control block (PCB) available. 3 File-system error occurred on program file; err.<8:15> = file-system error. 4 Cannot allocate map.
Err.<0:7> Meaning 16 I/O error to home terminal; err.<8:15> = file-system error. 17 DEFINE context propagation error; if: err.<8:15> = 0 Cannot convert a DEFINE name to network form. err.<8:15> = 1, flags.<10> = 1 AND flags.<12> <> 0 AND If the process creation attempt is on a remote system that is a NonStop 1+ system or any other NonStop Kernel system operating under operating system version B20 or earlier, use of DEFINEs is disallowed. err.<8:15> = 2 Internal context propagation error. err.
1211: ZASP-EVT-EXPDMGR-OPEN-ERROR Subsystem Mgr Open Error: err err identifies a file-system error. Cause. The Expand SGP could not open 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 the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual.
Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Check the operating system subsystem manager to see whether it is present, up, and running.
• Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1220”. 1230: ZASP-EVT-EXPDMGR-NOT-OPENED Can’t Open Subsystem Mgr, Error: err err identifies a file-system error. Cause. A subsystem manager does not exist. The FILEINFO system procedure call returned this error. Effect. ASAP and the subsystem cannot communicate. Recovery.
1231: ZASP-EVT-SPI-RQST-NOT-BUILT Can’t Build SPI Request, Error: err err identifies a Subsystem Programmatic Interface (SPI) error: err Meaning 0 No error -1 Invalid buffer format -2 Invalid parameter value -3 Missing parameter -4 Invalid parameter address -5 Buffer is full -6 Invalid checksum -7 Internal error -8 List token not found -9 Invalid token code or map -10 Invalid subsystem ID -11 Operation not supported -12 Insufficient stack space Cause.
1232: ZASP-EVT-MON-EXPDMGR-FS-ERROR Expand SGP -> ExpMgr FS Error: err err identifies a file-system error. 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 a definition of the specified error, see the Operator Messages Manual.
err Meaning -4 Invalid parameter address -5 Buffer is full -6 Invalid checksum -7 Internal error -8 List token not found -9 Invalid token code or map -10 Invalid subsystem ID -11 Operation not supported -12 Insufficient stack space Cause. An SPI error occurred 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.
Recovery. If the problem persists, contact your HP support representative and provide all relevant information: • • • • • Descriptions of the problem and accompanying symptoms Details from the messages generated System number Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1234”.
1236: ZASP-EVT-MON-EXPDMGR-PATH-STAT ASAPMON 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 line. 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. This error message is used for problem isolation.
• • • • • Descriptions of the problem and accompanying symptoms Details from the messages generated System number Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1237”. 1238: ZASP-EVT-MON-EXPDMGR-CSM-STAT ASAPMON Can't obtain CSM line stats Error: err, ldev err is the SPI error number returned by the $ZEXP process.
1239: ZASP-EVT-MON-EXPDMGR-NCSM-STAT ASAPMON 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 line. 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. This error message is used for problem isolation.
• • • • • Descriptions of the problem and accompanying symptoms Details from the messages generated System number Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1240”.
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1242”.
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. This error message is used by HP for problem isolation. Contact your HP representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1244”.
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1250”. 1251: ZASP-EVT-EXP-ECB-LOAD-ERROR ASAPEXP ECB_Load Error error-text error-text is error text returned from the Ecb_loadentities_ procedure Cause.
1253: ZASP-EVT-EXP-READDOMAIN-ERROR 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.
1255: ZASP-EVT-EXP-UNKNOWN-TRANSPORT 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 unknown transport. Recovery. This error message is used by HP for problem isolation. Contact your HP representative. Data Tokens.
1257: ZASP-EVT-EXP-RANKVALUES-ERROR 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.
1299: ZASP-EVT-EXP-SUPPRESSED-ERRORS 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1299”. 1300: ZASP-EVT-GETPEEKPCBS-ZERO-LEN GetPeekPCBs Returns error: err err is an error returned from the GetPeekPCBs system procedure call. Cause.
1301: ZASP-EVT-PROCESSINFO-ERROR ProcessInfo Returns error: err, pin# err indicates the outcome of the PROCESSINFO call: err Meaning 0 Returns the status of the process CPU, PIN. 1 The process CPU, PIN does not exist or does not match the specified criteria. The status for the next higher CPU, PIN in the specified processor is returned. The four-word process ID for which status is being returned reflects the process ID parameters, if present.
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. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1302”. 1303: ZASP-EVT-DELTA-TIMES pin:ProcessTime delta:Sampletime delta in .
ZASP-TKN-ASAP-ERRORNUM is “1303”. 1304: ZASP-EVT-DELTA-TOO-BIG 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 time for this PIN. Cause. ASAP detected a 100-percent process control block (PCB) busy state, possibly because of an internal interface failure with the operating system. Effect. The PCB busy information is suspect. Recovery.
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 due to an internal interface failure with the operating system. Effect. The PCB busy information in the sample might be distorted. Recovery.
Recovery. If the problem persists, contact your HP support representative and provide all relevant information: • • • • • Descriptions of the problem and accompanying symptoms Details from the messages generated System number Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1306”.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1307”. 1308: ZASP-EVT-BAD-SMON-SUBSAMPLING 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.
err Meaning 3 The Monitor cannot communicate with the CPU. 4 The CPU does not exist. 5 The system specified by sysnum could not be accessed. 99 A parameter error occurred. 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 a definition of the specified error, see the Operator Messages Manual.
ZASP-TKN-ASAP-ERRORNUM is “1399”. 1400: ZASP-EVT-NO-PROCESSOR-INFO 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: err Meaning 0 Information for the specified process. 1 File-system error. 2 Parameter error. 3 Bounds error. 4 (Reserved.) 5 You cannot communicate with the CPU; the CPU might not be present. 6 You cannot communicate with the node. 7 An invalid return attribute was supplied.
ZASP-TKN-ASAP-ERRORNUM is “1400”. 1401: ZASP-EVT-CPU-GETINFOLIST-ERROR Can’t Call CPU_GETINFOLIST_, Error: err err indicates the outcome of a CPU_GETINFOLIST_ system procedure call and returns one of these values: err Meaning 0 Information for the specified process. 1 File-system error. 2 Parameter error. 3 Bounds error. 4 (Reserved.) 5 You cannot communicate with the CPU; the CPU might not be present. 6 You cannot communicate with the node. 7 An invalid return attribute was supplied.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1401”. 1499: ZASP-EVT-EXP-SUPPRESSED-ERRORS 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1499”.
server-pid the process UD of the server process. Cause. The server process was stopped. Effect. Statistics cannot be collected from the server process. Recovery. Restart the server process if it is not automatically restarted. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1518”. 1519: ZASP-EVT-SERVER-ABENDED SGP sgp-pid detected that its server abended server-pid sgp-pid the prcess ID of the sending process. server-pid the process ID of the server process Cause.
1599: ZASP-EVT-NCP-SUPPRESSED-ERRORS Error #....occurred xxxx times 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1599”. 1700: ZASP-EVT-DSK-KERNEL-NOT-D10 ASAPDSK NonStop Kernel Must be release D10 or Greater Cause. ASAPDSK cannot be started. Effect. ASAPDSK is not operating. Recovery.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1701”. 1702: ZASP-EVT-DSK-ALLOCAT-SEG-ERROR 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. Recovery. ASAPDSK will reopen Measure during the next sample period. If the error persists, stop the Measure subsystem.
ZASP-TKN-ASAP-ERRORNUM is “1703”. 1704: ZASP-EVT-DSK-BAD-VOLUME-SUBVOL 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. Recovery. Use the ASAP Conversational Interface (CI) to set ASAPDSK with a different volume or subvolume than previously specified.
Cause. An incompatible MEASFH release was found on $System.sysxx. Effect. ASAPDSK cannot obtain disk counters. Recovery. Install the correct MEASFH release on $System.sysxx and restart the ASAP Monitor. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1706”. 1707: ZASP-EVT-DSK-MEASFH-SEG-ERROR ASAPDSK Measfh Ext Seg Error err err is the Measure error returned from the Measure subsystem. Cause. The MEASFH process was not able to obtain the extended segment size in the CPU.
ZASP-TKN-ASAP-ERRORNUM is “1708”. 1709: ZASP-EVT-DSK-MAX-MEAS-REACHED 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 have been reached. Effect. ASAPDSK cannot obtain disk counters. Recovery. If possible, stop and delete unnecessary measurements. Restart the ASAP Monitor once the Measure subsystem has fewer than 64 measurements configured. Data Tokens.
1711: ZASP-EVT-DSK-MEMORY-ERROR 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. 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. Data Tokens.
Cause. ASAPDSK could not start a measurement because the MEASCTL process reached its maximum internal counter space. Effect. ASAPDSK cannot obtain disk counters. Recovery. If possible, stop and delete unnecessary measurements. Restart the ASAP Monitor once the Measure subsystem has fewer than 64 measurements configured. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1713”. 1715: ZASP-EVT-SET-CPU-ERROR ASAPDSK Error SET DISK PARAM CPU xx cpu cpu is the CPU number. Cause.
1721: ZASP-EVT-DSK-NOT-STARTED ASAPDSK ZASPXXX NOT started.(XXX is the configured ASAP ID) Cause. ASAPDSK could not start a measurement. Effect. ASAPDSK cannot obtain disk counters. Recovery. Check for previous ASAP log messages from ASAPDSK and make the appropriate corrections. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1721”. 1722: ZASP-EVT-DSK-MEAS-RESTARTED ASAPDSK restarted err err is the Measure error returned from the Measure subsystem. Cause.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1723”. 1730: ZASP-EVT-DSK-PARAM-ERROR 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 contained in the ASAP startup file ASAPCONF are valid. Then restart the ASAP Monitor. Data Tokens.
1740: ZASP-EVT-DSK-INVALID-SWAPFILE Invalid swapfile specified error error is the measure error number. Cause. An invalid disk volume was entered for the Measfh swap volume. Effect. An ASAP Disk SGP will use the volume where the ASAPDSK object resides. Recovery. Specify a valid disk volume using the ASAP command SET DISK.param “swavol <$vol> Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1740”.
Effect. ASAPDSK could not collect disk statistics. Recovery. Contact your HP representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1742”. 1743: ZASP-EVT-DSK-MEAS-NOT-RESTARTD 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.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1744”. 1745: ZASP-EVT-DSK-NO-OPTCL-DSKS-RPT 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. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1745”.
Recovery. Stop and delete the measurement named ZASPxxx, where xxx is the ASAP ID. Use the Measure interface MEASCOM. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1747”. 1748: ZASP-EVT-DSK-SHUTDWN-COMPLETE ASAPDSK Disk Measurement stopped Cause. ASAPDSK was stopped by the ASAPMON process. Effect. ASAPDSK stops its measurement. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text.
1751: ZASP-EVT-DSK-ECB-LOAD-ERROR 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1751”.
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1753”. 1754: ZASP-EVT-DSK-LOAD-OBJTVS-ERROR 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.
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1756”.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1758”. 1759: ZASP_EVT_DSK_MAX_DOMAINS Reached the maximum monitored disks Cause. More than 2000 physical devices (1000 mirrored volumes) exist on the node. Effect. The disk SGP will report on the first 2000 devices. Recovery. Contact HP support to report the problem. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1759”.
1799: ZASP-EVT-DSK-SUPPRESSED-ERRORS 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “1799”. 2000: ZASP-EVT-DB-WRITE-ERROR DB^write filename, fe: err, sysno, cpuno filename is the file name for the file in which the error occurred. err identifies a file-system error.
Check that the database is present and secured properly. If the database is full, enlarge it or recreate it according to the installation instructions in section 2, Installing ASAP on the Server, in the ASAP Server Manual.
ZASP-TKN-ASAP-ERRORNUM is “2001”. 2002: ZASP-EVT-ROLLOVER-ERROR Rollover Open filename, fe: err filename is the file name for the file in which the error occurred. err identifies a file-system error. 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.
err identifies a file-system error. 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 the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual.
2005: ZASP-EVT-RECORDS-CLEANED 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. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2005”.
• Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2006”. 2007: ZASP-EVT-COL-SHUTDOWN-RCVD Received shutdown request: pid pid is the requester’s process identification. Cause. A shutdown request was received. Effect. Your ASAP session terminates. Recovery. Informational message only; no corrective action is needed. Data Tokens.
• • • • Details from the messages generated System number Numbers and versions of all related products Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2008”. 2009: ZASP-EVT-BAD-ENFSV-TRANS-CODE ENFSV trans code bad Cause. An incomprehensible input request was received. Effect.
Effect. The system does not start. Recovery. Correct the startup message in your configuration file. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2010”. 2011: ZASP-EVT-COL-OPEN-TERM-ERROR Startup Can’t Open TERM Cause. The startup parameters did not open the terminal logfile. Effect. The terminal logfile did not open at startup. Recovery. Correct the terminal file name in your configuration file. Data Tokens. ZEMS-TKN-TEXT contains the message text.
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 added to the database. Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Check that you have the correct security to perform this operation. Data Tokens.
2014: ZASP-EVT-COL-SHUTDOWN-COMPLETE SHUTDOWN Complete! Requester = pid pid is the requester’s process identification. Cause. The system shut down the requester indicated in the message. Effect. The requester was shut down successfully. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2014”. 2015: ZASP-EVT-COL-TRACE Trace Cause. The system performed an internal trace. Effect.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2016”. 2017: ZASP-EVT-ENFSERV-STARTED ENFSERV version started: cpu version is the operating system version. cpu is the CPU number. Cause. The Enform server has started successfully. Effect. The Enform server is operating. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2017”.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2018”. 2019: ZASP-EVT-COL-RCV-REPLY-ERROR $RECEIVE reply failed, FE: err, count, buf, pid err identifies a file-system error. 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. A NonStop Kernel error occurred while trying to reply to a system message. The FILEINFO system call returned this error. Effect.
2020: ZASP_EVT_COL_RENAME_TABLE_FUll DB Rename notify table full count count is the count of rename message notifications that are currently pending. Cause. ASAPCOL data base collecor identified that there are too many running ASAP command interpresters and seconday ASAPCOL collectors. Since there are too many of these, not all of them can be notified, and ASAPCOL logs this error message. Effect.
error is the file-system error explaining why file could not be deleted. Cause. The ASAP collector is processing old date base files marked for deletion due to SET DBMAXDAYS exceeded for this file. Effect. Old data base file is not deleted. Recovery. Manually delete this file, or close any ASAP command interpreters accessing this file. Allow ASAP data base to clean the file at the next database Clean Time. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2024”.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2026”. 2030: ZASP-EVT-COL-CTL-PURGE-ERROR 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, indicated by error, is most likely a security violation on the partition control file. Effect. The new partition control file is not created.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2031”. 2032: ZASP-EVT-COL-CTL-VERIFY-ERROR 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, indicated by error, is most likely a down target disk volume or a prior error that prevented the creation of the control file. Effect.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2033”. 2034: ZASP-EVT-COL-CTL-NAME-ERROR Collector could not build part ctl file name error error is the file-system error number. If greater than 0, it indicates the encountered filesystem error. If less than 0, it indicates an internal ASAP error. Cause. The Collector could not determine the name of the partition control file for the current ASAP ID.
ZASP-TKN-ASAP-ERRORNUM is “2035”. 2036: ZASP-EVT-COL-CTL-PARSE-ERROR 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 while 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.
2038: ZASP-EVT-COL-PART-BAD-SUFFIX 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2038”.
2040: ZASP-EVT-COL-PART-LIST-ERROR CreatePart filename file-error internal-error error-indicator filename database file that cannot be created. file-error file-system error number. internal-error offset of the internal ASAP structure responsible for the error. error-indicator contents of the internal error. Cause. The Collector could not create the specified database file. Most likely a system error occurred, such as a down target volume or a security violation, or an internal ASAP error. Effect.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2041”. 2042: ZASP-EVT-COL-PART-MAXEXTENTSNA 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.
Recovery. Depends on error. Enter SET PARTITION to view partitioning settings. Correct any errors, then restart the Collector from the ASAP CI. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “2043”. 2099: ZASP-EVT-EXP-SUPPRESSED-ERRORS 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. Data Tokens.
5 File error on swap file; err.<8:15> = filesystem error. 6 Invalid file format; err.<8:14> = error subcode and err.<15> = 0, program file is in error err.<15> = 1, library file is in error 7 Unlicensed privileged program. 8 Process name error; err.<8:15> = file-system error. 9 Library conflict. 10 Cannot communicate with system Monitor process; err.<8:15> = file-system error. 11 File-system error occurred on library file; err.<8:15> = file-system error.
err.<8:15> = 3 Invalid DEFMOD supplied. 18 Object file with an invalid process device subtype. 19 Process device subtype in backup process is not the same as in primary process. 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.
3002: ZASP-EVT-NO-CHECKPOINT Unable to checkpoint startup err 0:7, err 8:15, pid err returns a status word of the form: err.<0:7> Meaning 0 No error. 1 No backup or cannot communicate with backup; then err.<8:15> = file-system error. Takeover from primary; then err.<8:15> = 0 primary stopped 2 = 1 primary ended abnormally = 2 primary’s process failed = 3 primary called CHECKSWITCH 3 Invalid parameter; then err.
3003: ZASP-EVT-NO-CPU-AVAILABLE 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 whether you want to take the chance that the primary process will not fail, and continue to gather your statistics. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “3003”. 3004: ZASP-EVT-TAKEOVER --- TAKEOVER --> cpu: cpu cpu is the CPU number.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “3005”. 3099: ZASP-EVT-EXP-SUPPRESSED-ERRORS 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “3099”.
Recovery. User specific. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4000”. ZASP-TKN-ASAP-COMPONENT contains the name of the ASAP component reporting this condition. ZASP-TKN-ASAP-ENAME contains the name of the entity; for example “Disk”. ZASP-TKN-ASAP-DNAME contains the name of a domain; for example “$Data”. ZASP-TKN-ASAP-ANAME contains the name of an attribute; for example “Busy”. ZASP-TKN-ASAP-VALUETEXT contains the attribute value in ASCII text.
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 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4001”. ZASP-TKN-ASAP-COMPONENT contains the name of the ASAP component reporting this condition.
ZASP-TKN-ASAP-STATE contains the current ASAP state (1 through 8) for the domain and attribute values. ZASP-TKN-ASAP-LASTSTATE contains the ASAP state (1 through 8) for the domain and attribute values at the last ASAP sample. ZASP-TKN-ASAP-OBJECTNAME contains the physical object name, where known, else it contains the ASAP domain name.
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4022”.
error is the file-system error. Cause. An ASAP SGP failed to communicate with the Action server due to a filesystem 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-system error condition. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4024”. 4099: ZASP-EVT-EXP-SUPPRESSED-ERRORS ASAP ASAP Error #....
4102: ZASP-EVT-RDF-FILE-FINDSTRT-ERR 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 GMCSC. 4104: ZASP-EVT-RDF-RANK-VALUE-ERR RDF SGP_RANKVALUE_ error: error error the parameter error returned from SGP_RANKVALUE_ to the RDF SGP.
4106: ZASP-EVT-RDF-LOAD-ENTITIES-ERR 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: ZASP-EVT-RDF-SUPPRESSED-ERRORS ASAP ASAP Error #....
4302: ZASP-EVT-SPL-READDOM-ERR SPL sgp_readdomain_ Error= FE: error error 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.
4304: ZASP-EVT-SPL-STATSOVR-ERR Num Stats overflow in get^free^stats for SGP SPL NumStats: numstats numstats 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.
4306: ZASP-EVT-SPL-RANK-ERR SPL Rank Value Error FE: error, errordetail error value returned from the SGP_RANKVALUE_ procedure to identify the specific error error-detail 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. Recovery. Verify that the objective is working properly.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4307”. 4308: ZASP-EVT-SPL-INVLSGPOPT-ERR SGP SPL Parsing SGP option cmd option invalid SGP command option found Cause. The SPL SGP encountered an invalid option in command while parsing the MONITOR SPOOLER, LIST, SGP command. Effect. The specified option is ignored. Recovery. Verify and correct the command. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4308”.
4310: ZASP-EVT-SPL-SEGMENT-ERR SPL Stats Segment Alloc FE: error error-detail SPL Xfer Segment Alloc FE: error error-detail error error value returned by the NonStop Kernel SEGMENT_ALLOCATE_ procedure error-detail error-detail value returned by the NonStop Kernel SEGMENT_ALLOCATE_ procedure Cause. The specified error was returned when trying to allocate memory for the statistics or transfer segments. Effect. The needed extended segments are not allocated. Sampling is not possible. Recovery.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4311”. 4312: ZASP-EVT-SPL-SPOOLSTATUS-ERR SPL SpoolerStatus Error= FE: error error error returned from the SPOOLERSTATUS or SPOOLERSTATUS2 procedure call Cause. The NonStop Kernel 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.
4314: ZASP-EVT-SPL-FONTOVR-ERR 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.
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4316”. 4317: ZASP-EVT-SPL-ENTRYNOTFND-ERR Print Proc entry name not found in SGP SPL.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4393”. 4394: ZASP-EVT-SPL-EDLLOADED-INF 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4394”.
4396: ZASP-EVT-SPL-RELOADPREV-INF SPL Reloading previous configuration. Cause. An error occurred when trying to load the spooler domain names to monitor (see 4302: ZASP-EVT-SPL-READDOM-ERR on page 2-122). 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.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4398”. 4399: ZASP-EVT-EXP-SUPPRESSED-ERRORS 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4399”.
4402: ZASP-EVT-TAP-READDOM-ERR TAP sgp_readdomain_ Error= FE: error error 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 ASAP is configured correctly. For more information about configuring domains, see the MONITOR command in the ASAP Server Manual.
Recovery. Make sure your version of MEDIASRV is compatible with ASAP. If it is and you still get this error, contact your service provider. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4404”. 4405: ZASP-EVT-TAP-MEDIASRTSTRT-ERR TAP could not start filename.
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4406”.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4408”. 4409: ZASP-EVT-TAP-HANDLE-ERR TAP Process Handle FE: error error NonStop Kernel error returned from the PROCESSHANDLE_DECOMPOSE_ or PROCESSHANDLE_GETMINE_ procedure Cause. The NonStop Kernel 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.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4410”. 4411: ZASP-EVT-TAP-DEVINFOLIST-ERR TAP DEVICE_GETINFOBYNAME_ on domain Error=error error-detail domain tape device name for which the error occurred error error information returned from the DEVICE_GETINFOBYNAME_ procedure error-detail 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.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4412”. 4413: ZASP-EVT-TAP-STARTPARM-ERR Error TAP SPL PARAM param-error param-error 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4413”.
4415: ZASP-EVT-TAP-NOTAPEFOUND-ERR TAP error finding tape devices. Error=error, error-detail TAP can’t find any tape devices. error error returned by the NonStop Kernel DEVICE_GETINFOBYLDEV_ procedure error-detail error detail returned by the NonStop Kernel DEVICE_GETINFOBYLDEV_ procedure Cause. The Tape SGP is in autoconfiguration mode and is trying to find tape devices on the system. The NonStop Kernel DEVICE_GETINFOBYLDEV_ procedure call returned the specified error. Effect.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4416”. 4493: ZASP-EVT-TAP-LASTDOMOVR-INF TAP Could not add to last domain table: maximum of num reached. num 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.
num 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 elapsed (not how much time processing took) when doing the indicated processing. Effect. None. Recovery. Informational message; no corrective action is necessary. To eliminate these messages from appearing, remove the STATS parameter from the ASAPCONF file or reset it from your ASAP session, and restart the Tape SGP. Data Tokens.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4497”. 4498: ZASP-EVT-TAP-AUTOCONFIG-ERR TAP Autoconfiguration completed. Cause. No tape domains are specified in the Objectives 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4498”.
Effect. The TMF entity does not load. The TMF SGP tries the load again at the next sampling until it succeeds. Recovery. This error might be caused by the EDL settings. For more information on ASAP EDL, see the EDL section of the ASAP Client Manual. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4501”. 4502: ZASP-EVT-TMF-READDOMAIN-ERR ASAPTMF sgp_readdomain_ Error= error-num error-num error code returned by the sgp_readdomain_ call Cause.
Recovery. Make sure there is no problem with the ASAP Objectives Database. error-num and error-detail can help you determine the cause of the problem. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4503”. 4504: ZASP-EVT-TMF-DYNAMICCONF-ERR ASAPTMF Compare^tables: aborting Dynamic Configuration Cause. An unexpected error occurred while dynamically changing the list of domains to monitor. Effect.
4506: ZASP-EVT-TMF-PROCHANDLE-ERR ASAPTMF Process handle Error= error-num error-num error returned by the NonStop Kernel processhandle_getmine_ or processhandle_decompose_ procedure call Cause. A NonStop Kernel 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4506”.
4508: ZASP-EVT-TMF-SEGALLOCSUBD-ERR ASAPTMF Transac Segment alloc: error-num error-detail error-num error returned by the NonStop Kernel segment_allocate_ procedure call error-detail additional error information returned by the segment_allocate_ procedure call Cause. The NonStop Kernel segment_allocate_ procedure call returned an error when trying to allocate an extended segment. Effect. The TMF SGP does not have any extended segment to store the statistics of TMF transactions.
4530: ZASP-EVT-TMF-PNAMECREATE-ERR ASAPTMF Process name create error= error-num error-num error returned by the NonStop Kernel 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.
4532: ZASP-EVT-TMF-PROCCREATE-ERR ASAPTMF Process create error error-num error-detail error-num error returned by the NonStop Kernel process_create_ procedure call error-detail additional error information returned by the process_create_ procedure call Cause. The NonStop Kernel 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.
4534: ZASP-EVT-TMF-TMFSERVEWR-ERR ASAPTMF TMFSERVE startup writeread error error-num error-num 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.
4536: ZASP-EVT-TMF-TMFSERVECLOS-ERR ASAPTMF TMFSERVE close error error-num error-num 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.
4551: ZASP-EVT-TMF-SPI-SNDBUF-SPIERR ASAPTMF spi-cmd,SPI Error Send= error-num spi-cmd SPI command on which the error occurred error-num 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.
4553: ZASP-EVT-TMF-SPI-GETTKN-SPIERR ASAPTMF spi-cmd,SPI Error token= error-num spi-cmd SPI command on which the error occurred token token on which the error occurred error-num 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.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4554”. 4555: ZASP-EVT-TMF-SPI-GETMAP-SPIERR ASAPTMF spi-cmd,SPI Error Map= error-num spi-cmd SPI command on which the error occurred error-num 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.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4556”. 4557: ZASP-EVT-TMF-SPI-ENTERLIST-ERR ASAPTMF spi-cmd,SPI Error EnterList= error-num spi-cmd SPI command on which the error occurred error-num 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.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4558”. 4559: ZASP-EVT-TMF-SPI-CONTEXT-ERR ASAPTMF spi-cmd,SPI Error Context= error-num spi-cmd SPI command on which the error occurred error-num 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.
4593: ZASP-EVT-TMF-TMFSERVE-STARTED TMF TMFSERVE started Cause. The TMFSERVE process started. Effect. The TMFSERVE process starts. Recovery. Informational message; no corrective action is necessary. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4593”. 4594: ZASP-EVT-TMF-EDL-LOADED 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. Data Tokens.
4596: ZASP-EVT-TMF-RELOAD-PREV-CFG 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4596”. 4597: ZASP-EVT-TMF-MAXDOMAINS TMF Could not load all domains: maximum reached. Cause.
4599: ZASP-EVT-TMF-SUPPRESSED-ERRORS 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4599”. 4601: ZASP-EVT-PRO-SEGALLOC-ERR sgpid Segment allocation error: error error-detail sgpid is the identifier of the File or Process SGP.
4602: ZASP-EVT-PRO-PHANDLE-ERR sgpid Process handle error: error sgpid is the identifier of the File or 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4602”.
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 filesystem 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, then restart the SGP. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4604”.
Effect. The ASAP SGP could not allocate pool space to store domains that are dynamically resolved at each interval, such as domains specified using wildcard specifiers. Recovery. The ASAP SGP could not allocate pool space to store domains that are dynamically resolved at each interval, such as domains specified using wildcard specifiers. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4606”.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4608”. 4609: ZASP-EVT-PRO-STARTPARM-ERR ASAP Error SET component PARAM parameter component is the name of the relevant ASAP component. parameter is the parameter in error. 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. Data Tokens.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4610”. 4611: ZASP-EVT-PRO-SERVERIO-ERR ASAP ERR component Server I/O Error on server: error component is the name of the relevant ASAP component. SPI Procedure is the name of the server process. error is the file-system error. Cause. The SGP received a file-system error when communicating with its server process, server. Effect. ASAP cannot effectively communicate with its server process. Recovery.
Cause. The SGP could not start an EMS Distributor process due to an error when calling the PROCESS_LAUNCH_ procedure. Effect. ASAP cannot start one of its server processes. Recovery. Correct the PROCESS_LAUNCH_ error, and then restart ASAP. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4612”. 4613: ZASP-EVT-PRO-SERVEROPEN-ERR ASAP ERR component Cannot open server, FE: detail error, error component is the name of the relevant ASAP component.
Cause. The Query SGP has received a message through EMS where the sequence number is not in order. Effect. ASAP does not process the EMS event. Recovery. Correct the originating subsystem to send messages in the proper order. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4614”. 4615: ZASP-EVT-PRO-STARTSERV-ERR ASAP ERR component Error starting server process: error , error detail component is the name of the relevant ASAP component.
server is the name of the server process that cannot be restarted. Cause. The SGP attempted to restart its failed server the maximum number of times. Effect. ASAP quits trying to restart its server. Recovery. Fix the server startup problem, and then restart ASAP. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4616”. 4617: ZASP-EVT-PRO-FUNCSPI-ERR ASAP ERR component function-location SPI Error: error component is the name of the relevant ASAP component.
count is the domain count when the duplicate domain was detected. Cause. The SGP found a duplicate domain (object) while sorting domains after a reconfiguration operation. Effect. ASAP fixes the new domain by adding a domain suffix or ignores it if it appears to be a real duplicate domain. Recovery. Report the problem to HP support. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is “4618”. 4699: ZASP-EVT-EXP-SUPPRESSED-ERRORS ASAP ASAP Error #....
4708: ZASP-EVT-CMM-DATA-FILE-INUSE 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 communication linecounters. Recovery. Stop and delete the measurement named ZCMMxxx, where xxx is the ASAP ID. Use the Measure interface MEASCOM. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4708".
Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4720". 4721: ZASP-EVT-CMM-NOT-STARTED ASAPCMM ZCMMxxx NOT started. Cause. ASAPCMM could not start a measurement. Effect. ASAPCMM cannot obtain disk counters. Recovery. Check for previous ASAP log messages from ASAPCMM and make the appropriate corrections. If the problem persists, contact your HP support personnel. Data Tokens.
4723: ZASP-EVT-CMM-MEASCTL-RESTARTED ASAPCMM started MEASCTL IN CPU cpu cpu specifies the CPU number. Cause. The Comm Statistics Gathering process (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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4723".
4735: ZASP-EVT-CMM-COLLECT-ERROR ASAPCMM -> COLLECT send error:err err is the file-system error returned from the Measure subsystem. Cause. ASAPCMM encountered an error while attempting to send a message to the ASAP Collector. Effect. ASAPCMM cannot complete the request. Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Data Tokens.
Cause. ASAPCMM could not restart its measurement. Effect. ASAPCMM could not obtain disk counters during a sample interval. Comm statistics are set to null for the sample interval when ASAPCMM could not obtain the COMM IOP counters. Recovery. Check the ASAP log for previous ASAPCMM messages and make the necessary corrections. For corrective action for the specified error, see the Measure Reference Manual. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4743".
Recovery. Stop and delete the measurement named ZCMMxxx, where xxx is the ASAP ID. Use the Measure interface MEASCOM. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4747". 4748: ZASP-EVT-CMM-SHUTDWN-COMPLETE ASAPCMM Disk Measurement stopped Cause. ASAPCMM was stopped by the ASAPMON process. Effect. ASAPCMM stops its measurement. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text.
4751: ZASP-EVT-CMM-ECB-LOAD-ERROR 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4751".
ldev is the logical number of the Comm line that failed. Cause. The ASAP Load^Objectives procedure returned the specified error when trying to get the list of Comm objectives. Effect. Comm monitoring monitors all configured Comm 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. Data Tokens. ZEMS-TKN-TEXT contains the message text.
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 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.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4799".
3 ASAP Extension EMS Messages The ASAP Extension (ASAPX) writes messages to EMS as tokenized event messages and to the ASAP log. Because of text size restrictions in the ASAP log format, ASAPX does not include all of the information for certain messages that it writes to that log. For example, ASAPX never writes a domain name to the ASAP log because the length of the domain name could be longer that the allowable length of a text message to the log.
Table 3-1. ASAPX Error and Critical Information Messages (page 2 of 2) Message Number Message Text Parameters 1819* DATAITEM not contiguous: fname 1820* DATAITEM defintion(s) not defined: fname 1821* METRIC definitions not contiguous: fname 1822* METRIC definition(s) not defined: fname 1823 Detected that its server stopped: pid 1824 Detected that its server abended: pid 1825 Processor getinfo failure, fe: fe 1826 Requires TNS/R and D30.
Table 3-3. ASAPX Information-Only Event Messages Message Number Message Text Parameters 1880 ASAPX Shutdown complete, Requestor: pid 1881 ASAPX INFO started, component, version, cpu 1899 ASAP ASAP Error occurred time(s) num, xxxx Error and Critical Information Messages (18011859) 1801: ZASP-EVT-API-FILEOPEN-ERR 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.
1802: ZASP-EVT-API-FILESECURE-ERROR File secure error: fname, FE: fe fname is the segment filename. 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 the description of file-system error numbers in the Guardian Procedure Errors and Messages Manual. Effect. ASAPXMON could not resecure an extended segment file.
Cause. An error occurred attempting to allocate an extended memory segment. To determine the cause of this problem, see the description of errors returned by the segment_allocate_ procedure in the Guardian Procedure Errors and Messages Manual. Effect. ASAPXMON or ASAPXSGP failed in its attempt to allocate a shared memory segment. The process terminates. Recovery. Correct the problem and restart ASAPX. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1803.
ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-FNAME contains the name of the file. ZASP-TKN-ASAPX-ERROR contains the file-system error number. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1805: ZASP-EVT-API-FILEWRITE-ERROR File write error: fname, FE: fe fname is the name of the file in error. fe is the file-system error number. Cause. An error occurred while writing from the file.
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 generate this error message. This error should not occur, but 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.
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. 2. Stop ASAP using the ASAP SHUTDOWN command. 3. Enter the ASAPX CLEANUP DOMAINS command to purge the Domain table. 4. Restart ASAP with the ASAP START command.
ZASP-TKN-ASAPX-DNAME contains the name of the domain. ZASP-TKN-ASAPX-ERROR contains the file-system error number. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1809: ZASP-EVT-API-EXECPROCESS-ERROR 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.
Cause. The Domain table was corrupted. You might have entered the ASAPX CLEANUP DOMAINS command while application processes continued to execute. 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. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1810. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event.
1812: ZASP-EVT-API-BEGINTRANS-ERROR 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 TMF in an attempted operation against file fname. To determine the cause of this problem, see the description of BEGINTRANSACTION procedure error numbers in the Guardian Procedure Errors and Messages Manual. Effect.
ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-ERROR contains the contents of word 0 of the illegal message. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1815: ZASP-EVT-API-MAX-DOMAINS Registration rejected, max domains: domain, Max: max domain is the name of the domain that failed to register. max is the maximum number of allowed registrations in the processor. Cause.
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. This error should not occur except in extreme cases; for example, after a processor or system failure corrupts ASAPX extended memory segments and the Domain table, then a domain that never registered in the processor starts before all domains active at the time of the failure are restarted. Effect.
ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1818: ZASP-EVT-API-INVALID-COMMAND Command invalid in: fname fname is the name of the configuration file containing the invalid command. 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 and then restart ASAPX.
Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1819. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-FNAME contains the name of the ASAPXCNF configuration file. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1820: ZASP-EVT-API-DATAITEM-MISSING DATAITEM definition(s) not defined: fname fname is the name of the configuration file containing the dataitem definitions that are not defined. Cause.
Cause. (ASAP Release 1 only) There is an error in the ASAPX configuration file. 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. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1821. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event.
1823: ZASP-EVT-API-SERVER-STOPPED 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, which might indicate a problem in ASAPXMON. Recovery. None. ASAPX automatically restarts the process. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1823. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event.
1825: ZASP-EVT-API-PGETINFO-ERROR 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 the description of file-system error numbers in the Guardian Procedure Errors and Messages Manual. Effect. The operation fails. No domain statistics can be received that are executing in cpu. Recovery.
ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1827: ZASP-EVT-API-FILECREATE-ERROR 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 while creating file fname. To determine the cause of this problem, see the description of file-system error numbers in the Guardian Procedure Errors and Messages Manual.
Cause. ASAPX could not obtain the NonStop Kernel MOM identifier for one of its servers. To determine the cause of this problem, see the description of file-system error numbers in the Guardian Procedure Errors and Messages Manual. Effect. ASAPXSGP does not receive process stop or abend messages for the ASAPXMON process. Recovery. Correct the file-system error and retry the operation. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1828.
ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1830: ZASP-EVT-API-SRVCOMM-ERROR 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 the description of file-system error numbers in the Guardian Procedure Errors and Messages Manual. Effect.
Effect. The domain is not automatically restarted. Recovery. Manually remove the domain in question and reregister it, or fix the filesystem or segment allocation error associated with this event. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1831. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-DNAME contains the name of the domain. ZASP-TKN-ASAPX-ERROR contains the domain number. ZEMS-TKN-TEXT contains an abbreviated version of the error text.
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, then restart ASAPX. Data Tokens. ZEMS-TKN-TEXT contains the message text given above. ZASP-TKN-ASAP-ERRORNUM is “1833”. ZASP-TKN-ASAP-COMPONENT contains the name of the ASAP component reporting the error. ZASP-TKN-ASAP-ENAME contains the name of the entity.
1835: ZASP-EVT-API-MAX-AGGREGATES 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.
Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1860. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-FNAME contains the name of the ASAPXCNF file. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1861: ZASP-EVT-API-FILERESET-MSG Resetting file security: fname fname is the name of the segment file that ASAPX needs to resecure. Cause. The security on a segment file is incorrect.
Recovery. ASAPX warns about this problem and then continues processing normally. To eliminate this warning message, add a SET NAMEFILE $ISV Volume.ZASAPX.ZASPXNAM command to ASAPXCNF. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1862. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-FNAME contains the name of the ASAPXCNF file. ZEMS-TKN-TEXT contains an abbreviated version of the error text.
1864: ZASP-EVT-API-NAMEFILEFE-MSG File error on NAMEFILE: fname, FE: error fname is the name of the ASAP reserved names file. Cause. ASAPX encountered a file error while attempting to open the ASAP reserved names file. This could result in reserved names being entered as domain names and yield unexpected results in ASAP, OEM and OIL. Effect. This does not affect ASAPX; however, using reserved names as domain names can cause problems in ASAP, OEM, and OIL. Recovery.
Information Only Messages (1880-1899) 1880: ZASP-EVT-API-SHUTDOWN-MSG component Shutdown Complete! Requestor = pid component is the ASAPX component that is shut down. 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. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1880. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event.
Recovery. None. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1881. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-DNAME contains the version of ASAPX. ZASP-TKN-ASAPX-ERROR contains the processor number. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1899: ZASP-EVT-API-SUPPRESSED-ERRORS 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.
HP NonStop ASAP Messages Manual— 429917-004 3-30
Index C Collect event messages 2-5 D DISK event messages 2-5, 2-7 E EMS messages 2-1 Error messages 3-3 event messages Collect 2-5 DISK 2-5, 2-7 Monitor 2-1 NonStop 2-6 I information messages 3-28 M Messages 3-1 Monitor event messages 2-1 N NonStop event messages 2-6 W warning messages 3-24 HP NonStop ASAP Messages Manual— 429917-004 Index -1
W Index HP NonStop ASAP Messages Manual— 429917-004 Index -2
