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 3.0 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.8 January 2007 429917-005 ASAP Server Release 3.
Table of Contents HP NonStop ASAP Messages Manual ................................................................................ 1 Abstract ........................................................................................................................... 1 Product Version ............................................................................................................... 1 Supported Release Version Updates (RVUs) ..................................................................
List of Figures and Tables Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 1-1. Monitor Messages Logged to EMS and ASAPLOG ............................................ 17 1-2. Disk Messages Logged to EMS and ASAPLOG................................................. 21 1-3. Collect Messages Logged to EMS and ASAPLOG ............................................. 22 1-4.
What’s New in This Manual New and Changed Information The ASAP 3.0 version of this manual contains these changes: Removed references to Query events.
o 4811: ZASP-EVT-SWP-MAX-UNKWN-DOMAINS o 4812: ZASP-EVT-SWP-MAX-MNTRD-DOMAINS o 4814: ZASP-EVT-SWP-CANNOT-START-SSG o 4815: ZASP-EVT-SWP-NO-FILE o 4835: ZASP-EVT-SWP-COLLECT-SEND-ERR o 4851: ZASP-EVT-SWP-ECB-LOAD-ERROR o 4852: ZASP-EVT-SWP-NO-OBJECTIVES o 4853: ZASP-EVT-SWP-READDOMAIN-ERROR o 4854: ZASP-EVT-SWP-LOAD-OBJTVS-ERROR o 4856: ZASP-EVT-SWP-GETOBJTIVES-ERROR o 4857: ZASP-EVT-SWP-RANKVALUES-ERROR o 4865: ZASP-EVT-SWP-SET-SWAP-PARAMS o 4899: ZASP-EVT-SWP-SUPPRESSED-ERRORS Previous Changes The ASAP 2
o 4001: ZASP-EVT-STATE-UP-MSG The effect was updated for Message 1754 These ASAP error messages were added: o 1028 o 1029 o 1030 o 1031 o 1032 o 1033 o 1835 o 4024 o 4606 o 4607 o 4609 o 4700 o 4708 o 4720 o 4721 o o 4715 o 4722 o 4723 o 4747 o 4748 o 4750 o 4751 o 4753 o 4754 o 4756 o 4757 HP NonStop Messages Manual Page 7 of 407
o 4766 o 4799 o 4725 o 4735 o 4742 o 4744 Table 1-12, Communication Messages, was added Table 2-11, COMM Event Messages, was added The effect was updated in Message 1754: ZASP-EVT-DSK-LOAD-OBJTVSERROR HP NonStop Messages Manual Page 8 of 407
These ASAP EMS messages were added: o 1028: ZASP-EVT-MON-INVLD-SYSNAME-RCV o 1029: ZASP-EVT-MON-MISSNG-ACT-SCRIPT o 1030: ZASP-EVT-MON-ACT-START-MSG-FLD o 1031: ZASP-EVT-MON-ACT-NOT-CREATED o 1032: ZASP-EVT-MON-ACT-OPEN-FAILED o 1033: ZASP-EVT-MON-ACT-RPLY-FAILED o 4700: ZASP-EVT-CMM-KERNEL-NOT-D40 o 4708: ZASP-EVT-CMM-DATA-FILE-INUSE o 4715: ZASP-EVT-CMM-SET-CPU-ERROR o 4720: ZASP-EVT-CMM-STARTED o 4721: ZASP-EVT-CMM-NOT-STARTED o 4722: ZASP-EVT-CMM-MEAS-RESTARTED o 4723: ZASP-EVT-CMM-MEASCTL-RESTARTED o 4
Message 1815: ZASP-EVT-API-MAX-DOMAINS was changed Message 1835: ZASP-EVT-API-MAX-AGGREGATES was added. The first edition of this manual was new. It contained message information formerly in the ASAP Server Manual and ASAP Extension Manual.
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.
italic computer type Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: pathname [ ] 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.
M address [ , new-value ]… [ - ] {0|1|2|3|4|5|6|7|8|9}… An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char…" Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
!i and !o In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id , error !i !o ) ; !i,o In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program).
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. For example: p-register process-name [ ] Brackets Brackets enclose items that are sometimes, but not always, displayed.
% 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. For example: %005400 %B101111 %H2F P=%p-register E=%e-register Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual.
Section 1: ASAP and ASAP Extension Error Messages This section describes the ASAP and ASAP Extension error messages: Topic Page ASAP Error Message Summary 17 ASAP Error Messages 34 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.
1015 Startup Can't Open TERM 1016 SGP startup msg fail, FE: 1017 Can't create SGP in cpu: 1018 ASAP Version <> TOSVERSION vers, vers 1019 A SGP didn't Shutdown: cpu, pid 1020 SHUTDOWN Complete! Requestor= pid 1021 Trace 1022 Monitor version started cpu 1023 SGP version started cpu 1024 $RECEIVE read, FE: err 1025 $RECEIVE reply failed, FE: err 1026 Sample missed SecsSinceLast>RateSecs sec, rate 1027 Invalid CPU Sysname Received cpu 1028 Invalid Sys.
1200 Can’t find NetLH = netlh^conf ldev, paths 1210 NewProcess $System.System.Ozexp Error 0:7,8:15: err.0:7, err.
1301 ProcessInfo Returns error err, pin# 1302 Unable to get device name err, pin# 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_ProcessTim e in 10 sec pin#, pt1, pt2 1306 Pin:Alive but No PCB:priority: Last_PTime in .
Table 1-2.
1745 ASAPDSK Optical Disk statistics not collected 1746 Virtual Disk stats collected by Physical Disk 1747 ASAPDSK unable to stop Disk Measurement 1748 ASAPDSK Disk Measurement stopped 1749 ASAPDSK Unexpected Error err 1751 ASAPDSK ECB_Load Error error-text 1752 Unable to report object thresholds 1753 ASAPDSK sgp_readdomain_ Error err 1754 Load Objectives Error: err, Ldev 1756 GetObjectives Error err, Ldev 1757 ASAPEDSK Rank Values error= err, error-detail 1758 Could not purge f
number 1811 Could not obtain process handle , FE: pname, fe 1812 Begintransaction error: , Er: fname, begintrans 1814 Illegal request on $receive: rbuf[0] 1815 Registration rejected, max domains: , Max: domain, max 1816 Cannot restart domain, Dmn in use: , Dmn#: domain, domain number 1817 Terminated COMMIT, excessive errors: err^cnt 1818 Command invalid in: , Line: fname, number 1823 Detected that its server stopped: pname 1824 Detected that its server abended: pname 1825 Process
Table 1-4.
2035 Collector could not read partition ctl file error 2036 parse-error num-chars 2037 Collector could not write partition ctl file error 2038 Unknown suffix entity-suffix 2039 CreatePart filename 2040 CreatePart filename 2041 CreatePart partition status description 2042 Format2 ON, MaxExtents for sec parts not set entity-number entity-number 2043 OpenPart filename file-error, partition index 2050 DB^AltKeyFile^GET call fnamecollapse failed 2051 DB^AltKeyFile^GET call fname expand
3001 NonStop Backup Created Cpu 3002 Unable to checkpoint startup 3003 No backup, no cpu available 3004 --- T A K E O V E R --> cpu 3005 No startup msg received 3099 Error # ....occurred xxxx times cpu err 0:7, err 8:15, pid cpu num, x Table 1-6.
Table 1-8. SPOOLER Messages Message Number Spooler Messages Parameters 4301 SPL ecb loadentities . error-text 4302 SPL sgp readdomain_ Error= FE: error 4303 Invalid Stats^Type in process^minstate for SGP SPL StatsType: numtype 4304 Num Stats overflow in get^free^stats for SGP SPL NumStats: numstats 4305 No type stats entry available in find^entry for SGP SPL. No type stats entry available in check^setup^domain for SGP SPL.
4307 SPL Error loading objectives: FE: error, errordetail 4308 SGP SPL Parsing SGP option cmd 4309 SPL Process Handle FE: error 4310 PL Stats Segment Alloc FE: SPL Xfer Segment Alloc FE: error, errordetail 4311 SPL FILENAME TO PROCESSHANDLE_ Error. FE: error 4312 SPL SpoolerStatus Error= FE: error 4313 Error SET SPL PARAM param-error 4314 SPL loc font array overflow in domain^count^jobs^locs. 4315 SPL Batch Job array overflow in domain^count^jobs^locs.
TAP SPI Last Error: TAP SPI Return Error: TAP SPI Dlist RetCode error: TAP SSNULL error: 4405 TAP could not start . Error= filename, error, error-detail 4406 TAP Rank Value Error FE: error, error-detail 4407 TAP open error on MEDIASRV.
Table 1-10.
4556 ASAPTMF spi-cmd, SPI Error SaveSPIBuf= error 4557 ASAPTMF spi-cmd, SPI Error EnterList= error 4558 ASAPTMF spi-cmd, SPI Error ExitList= error 4559 ASAPTMF spi-cmd, SPI Error Context= error 4592 TMF TMFSERVE stopped, error= error 4593 TMF TMFSERVE started 4594 TMF EDL loaded 4595 TMF Time to : 4596 TMF Reloading previous configuration 4597 TMF Could not load all domains: maximum reached 4598 TMF Autoconfiguration completed 4599 Error # ....
error; error detail 4612 Cannot start server, Process_Launch_error: 4613 Cannot open server, FE: 4614 Message sequence number invalid 4615 Error starting server process 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 error, error detail Table 1-12.
4756 GetObjectives Error: Err 4766 Bad Stats Received err, Ldev 4799 Error #.... occured xxxx times Table 1-13.
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.
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.
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.
1006 Sync, delay too long: err err is the file-system error number associated with the last operation on the file. Cause. An attempt to synchronize with the Server failed because the message request took more than 40 seconds. The system was too busy. Effect. Synchronization with the Server was not accomplished. Recovery. The FILEINFO system call returned this error.
1009 Sync, Clock Corrected: delta delta is the time difference, in seconds. Cause. The synchronization clock is now set correctly. Effect. The synchronization clock is now operating correctly. Recovery. This message is informational only. No corrective action is required. 1010 Sync, Can’t Set Clock: delta delta is the time difference, in seconds. Cause. The system cannot reset the synchronization clock correctly. Effect. Synchronization with the Server is not being accomplished. Recovery.
1012 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. 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.
1015 Startup Can’t Open TERM Cause. The terminal logfile was not opened. Effect. The system could not start up. Recovery. Check your configured terminal file name. The SET TERM command displays information about your terminal. 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.
3 File-system error occurred on program file; error 8:15 = filesystem error number 4 Unable to allocate map 5 File error on swap file; error 8:15 = file-system error number 6 Invalid file format; error 8:14 = error subcode, and 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 n
19 Process device subtype specified in the backup process is not the same as that in the primary process 0 No error, process created 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.
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.
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.Sysname Received Cause. An invalid system name was received Effect.
Effect. User-defined actions will not work. Recovery. Verify that the Action server configuration is correct and restart the ASAP Monitor. If the error persists, contact your HP support representative. 1031 Can't create ACTION Server cpu, err err is the error number. cpu is the CPU number. Cause. The ASAP Monitor could not start the Action server. Effect. Use- defined actions will not work. Recovery. Verify that the Action server configuration is correct and restart the ASAP Monitor.
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. The ASAP ecb_loadentities_ procedure returned the specified error when trying to load the CPU entity. Effect. The CPU entity does not load EDL records. Recovery. This error might be caused by the EDL settings.
1056 ASAPCPU Rank metric metric is the name of the metric that failed in the SGP_RANKVALUE_ procedure. Cause. The ASAP SGP_RankValue procedure returned an error when trying to get the OEM state of affected entity threshold objectives. Effect. The affected entity metric in error will have an OEM state value of 1. Recovery. Make sure that ASAP is configured correctly. For more information about Ranking Objectives, see the ASAP Server Manual.
cpu is the CPU where the SGP process was not started in. Cause. The ASAPMON process could not start the SGP because a process with the same name exists. Effect. The SGP is not started. Recovery. Shut down ASAP. Select a different NSS ID Restart ASAP. 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.
Recovery. Renew or obtain a software license for the ASAP component. 1097 Software License 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.
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.
2 No process control block available 3 File-system error occurred on program file; error 8:15 = filesystem error number 4 Unable to allocate map 5 File error on swap file; error 8:15 = file-system error number 6 Invalid file format; error 8:15 = error subcode, and 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 pr
propagation error. error 8:15 = 3 18 Object file with an invalid process device subtype 19 Process device subtype specified in backup process is not the same as that in the primary process Invalid DEFMOD supplied. Cause. The Expand SGP could not create a new Subsystem Manager process. Effect. The subsystem manager process was not created, and no network statistics can be collected. Recovery. Check the Subsystem Programmatic Interface (SPI) Manager at $SYSTEM.SYSTEM.
Check that the NonStop Kernel Subsystem Manager is secured properly. If the problem persists, contact your HP representative. 1230 Can't Open Subsystem Mgr ($ZEXP), Error: err err is the file-system error number associated with the last operation on the file. Cause. A Subsystem Manager does not exist. Effect. ASAP and the subsystem cannot communicate. Recovery. The FILEINFO system call returned this error.
Effect. No information was returned by SPI. Recovery. Check the NonStop operating system version to make sure all the SPI routines are installed. These routines include SSPUT, SSGET, SSINIT, and others. Retry the request. If the problem persists, contact your HP representative. 1232 Monitor -> ExpMgr ($ZEXP) FS Error: err err is the file-system error number associated with the last operation on the file. Cause. A file-system error occurred in communication between the Expand SGP and the Expand Manager.
-12 Indicates insufficient stack space Cause. A Subsystem Programmatic Interface (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. If the problem persists, contact your HP representative. 1234 Expand SGP -> ExpMgr ($ZEXP) Retry Counts: cnt cnt is the number of retries. Cause. The Expand SGP could not communicate with the Expand manager. Effect.
Cause. The Expand SGP could not obtain Level 4 statistics for an Expand line. Effect. ASAP does not obtain Level 4 statistics from the Expand manager. Recovery. HP uses this error message for problem isolation. Contact your HP representative. 1237 Expand SGP -> Can’t obtain Path information Error: err, ldev err is the SPI error number returned by the $ZEXP process. ldev is the logical device number of the Expand path. Cause. The Expand SGP could not obtain Level 2 statistics for an Expand line. Effect.
err is the SPI error number returned by the $ZEXP process. ldev is the logical device number of the Expand path. Cause. The Expand SGP could not obtain non-6100 line statistics. Effect. ASAP does not obtain non-6100 line statistics from the Expand manager. Recovery. HP uses this error message for problem isolation. Contact your HP representative. 1240 Expand SGP -> Can’t obtain IP stats Error: err, ldev err is the SPI error number returned by the $ZEXP process.
1242 Short request received: count, buf, pid count is the length of the message in bytes. buf contains the first word of the request message received. pid is the requester’s process identification. Cause. An unrecognized message was received because of its short length. Effect. The message was not processed. Recovery. Retry the request. If the problem persists, contact your HP representative. 1243 Illegal request received: count, buf, pid count is the length of the message in bytes.
1244 Cannot Obtain NAM stats Error: err, Ldev err is the SPI error number returned by the Expand manager $ZEXP process. Ldev is the logical device number of the Expand line. Cause. The Expand SGP could not obtain Network access statistics for an Expand line using NAM as the transport. Effect. ASAP could not obtain statistics from the Expand manager. Recovery. HP uses this error message for problem isolation. Contact your HP representative.
Effect. ASAPEXP uses the default values for all parameters. Recovery. Ensure that all parameters contained in the ASAP startup file ASAPCONF are valid; then restart the ASAP Monitor. 1251 ASAPEXP ECB_Load Error error-text error-text is error text returned from Ecb_loadentities_ procedure. Cause. The ASAP ecb_loadentities_ procedure returned the specified error when trying to load the Expand entity. Effect. The Expand entity does not load EDL records. Recovery.
Effect. Expand uses autodiscovery for all Expand line handlers. All Expand lines are monitored. User-defined objects cannot be read from the objectives database. Recovery. Make sure that ASAP is configured correctly. For more information about Ranking Objectives, see the ASAP Server Manual. If the configuration is correct, contact your HP support representative. 1255 Unknown Transport not supported err, Ldev err is the error number returned from the Expand Manager.
err is the error number returned from the SGP_RankValues procedure. error-detail is the error detail number returned from the SGP_RankValues procedure. Cause. The ASAP sgp_rankvalues procedure returned the specified error when trying to rank Expand threshold objectives. Effect. The Expand objectives for all ranked objectives will be equal to a OEM state value of 1 for the sample period. Recovery. Make sure that ASAP is configured correctly.
err is the error returned from the GetPeekPCBs system call. Cause. The system could not obtain process statistics. Effect. A zero value was returned instead of a process statistics value. Recovery. Check that your NonStop operating system version and ASAP version are compatible. If the problem persists, contact your HP representative. 1301 ProcessInfo Returns error: err, pin# err is the outcome of a PROCESSINFO call. pin# is the PIN number of the process.
pin# is the PIN number of the process: 0 Indicates no error 100 Indicates the device is not ready or the controller is not operational Cause. The system could not obtain the device name of the process. The process probably went away before the device name was obtained. Effect. The process information does not include a related device name. Recovery. This message is informational only. No corrective action is required. 1303 pin:ProcessTime delta:Sampletime delta in .
dpt2 is the last word of the process delta 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. 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.
Cause. The process was alive but statistics were not returned, possibly because of an internal NonStop operating system error. 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: 0Current sample array 1 Previous array Cause. The process specified is not in the internal sample array. This is an internal error.
PIN in the specified processor. The four-word process ID of the process for which the status is being returned includes the process ID parameters, if they are present. 2 Indicates the process CPU, PIN does not exist, and no higher CPU, PIN in the specified process that matches the specified criteria exists. 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.
5 Indicates you cannot communicate with the CPU; the CPU might not be present. 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.
Recovery. The CPU_GETINFOLIST 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 your NonStop operating system version and ASAP version are compatible. If the problem persists, contact your HP representative. 1499 ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred. Cause. The error number was suppressed. Effect.
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.
1703 ASAPDSK ASAPmeas file in use err err is the Measure error returned from the Measure subsystem Cause. The Measure subsystem has a measurement data file with the same name as ZASPxxx, where xxx is the ASAP ID. The DISK SGP could not delete it. Effect. ASAPDSK cannot obtain disk counters. Disk device status information is valid when ASAPDSK cannot obtain the disk counters. Recovery. Close the file through MEASCOM. The disk SGP will attempt to start the measurement during the next sample period.
Recovery. Specify a different CPU for the MEASFH process by using the ASAP Conversational Interface (CI) to specify CPU cpu-number in the SET DISK command; then restart the ASAP Monitor. 1706 ASAPDSK Incompatible Measfh Release err err is the Measure error returned from the Measure subsystem Cause. An incompatible MEASFH release was found on $SYSTEM.SYSxx. Effect. ASAPDSK cannot obtain disk counters. Disk device status information is valid when ASAPDSK cannot obtain the disk counters. Recovery.
Recovery. Stop and delete the measurement named ZASPxxx, where xxx is the ASAP ID. Use the Measure interface MEASCOM. 1709 ASAPDSK 64 Measurements Configured err err is the Measure error returned from the Measure subsystem Cause. ASAPDSK could not start a measurement. Maximum measurements were reached. Effect. ASAPDSK cannot obtain disk counters. Disk device status information is valid when ASAPDSK cannot obtain the disk counters. Recovery. If possible, stop and delete unnecessary measurements.
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. Next, restart the ASAP Monitor. An example of the CI command is: SET DISK ON, PARAM "CPU 3" 1712 ASAPDSK Measctl Resources Exceeded err err is the Measure error returned from the Measure subsystem Cause. ASAPDSK could not start a measurement because the MEASCTL process reached its maximum resources. Effect. ASAPDSK cannot obtain disk counters.
Effect. ASAPDSK starts the measurement in the CPU where the ASAPDSK process is running. Recovery. Informational message only; no corrective action is needed. 1720 ASAPDSK ZASAPXXX started. (XXX is the configured ASAP ID) Cause. ASAPDSK started a measurement successfully. Effect. ASAPDSK is operating. Recovery. Informational message only; no corrective action is needed. 1721 ASAPDSK ZASAPXXX NOT started. (XXX is the configured ASAP ID) Cause. ASAPDSK could not start a measurement. Effect.
Cause. The Disk SGP started the Measctl process in a CPU that did not have the measctl process running. Effect. ASAPDSK starts Measctl in the CPU. Recovery. Informational message only; no corrective action is needed. 1730 Error SET DISK PARAM param param is the invalid parameter Cause. ASAPDSK detected an invalid parameter in the SET DISK ON, PARAMETER command. Effect. ASAPDSK uses the default values for all parameters. Recovery.
Recovery. Specify a valid disk volume using the ASAP command SET DISK.param ―swavol <$vol> 1741 Invalid volume specified error error is the measure error number. Cause. An invalid disk volume was entered for the Measure date file. Effect. The ASAP Disk SGP will use the volume where theASAPDSK object resides. 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.
Effect. ASAPDSK cannot collect disk counters. Disk device status information is valid when ASAPDSK cannot obtain the disk counters. Recovery. Contact your HP representative. 1745 ASAPDSK Optical Disk statistics not collected Cause. The Disk SGP will not collect statistics on configured optical disk devices. Effect. ASAPDSK will not report optical disk statistics. Recovery. This message is informational only. No corrective action is needed. 1746 Virtual Disk stats collected by Physical Disk Cause.
err is the Measure error returned from the Measure subsystem Cause. ASAPDSK has a interface problem with the Measure subsystem. Effect. ASAPDSK could not obtain disk counters during a sample interval. Disk statistics are set to null for the sample interval when ASAPDSK cannot get DP2 counters. 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.
Cause. The ASAP sgp_readdomain_ procedure returned the specified error when trying to get the list of Disk domains to monitor. Effect. Disk monitoring of all devices will occur. Recovery. Make sure that ASAP is configured correctly. For more information about configuring domains, see the ASAP Extension Manual. If the configuration is correct, contact your HP support representative.
1757 ASAPDSK Rank Values error= err, error-detail err is the error number returned from the SGP_RankValues procedure error-detail is the error detail number returned from the SGP_RankValues procedure Cause. The ASAP sgp_rankvalues procedure returned the specified error when trying to rank Disk threshold objectives. Effect. The Disk objectives for all ranked objectives will be equal to a OEM state value of 1 for the sample period. Recovery. Make sure that ASAP is configured correctly.
device the device that returned the error ldev is the logical number of the device 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.
1802 File secure error: fname, FE: fe Cause. An error occurred while attempting to resecure an ASAPX extended memory segment file fname. To determine the cause of this problem fe, see a description of file-system error numbers. 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.
Effect. The specified file could not be updated. ASAPXMON failed to update the domain table. It will continue processing to the best of its ability even though it has lost a resource. Recovery. Correct the file-system error and retry the operation. 1806 Duplicate memory slot for domain: domain, Dmn#: domain number Cause. ASAPX detected duplicate Domain table entries while restarting domain for the same memory slot location.
memory. If the applications were shut down, the Domain table is rebuilt over time as they restart and register with ASAPX. 1808 Objectives load failed, domain: domain, Dmn#: domain number 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.
Recovery. Correct the file-system error and retry the operation. 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.
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.
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. (ASAP Release 1 only) An error exists in the ASAPX configuration file fname. ASAPX detected that the METRIC definitions in fname are not contiguous. Effect. ASAPXSGP stops because of the inconsistent configuration. ASAPX is not started. Recovery.
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. To determine the cause of this problem, see a description of file-system error numbers fe. Effect. Applications executing in cpu will not be able to participate in the ASAPX system. Recovery.
Effect. ASAPXSGP will not receive process stop or abend messages for the ASAPXMON process. Recovery. Correct the file-system error and retry the operation. 1829 Server create error: pname, FE: fe Cause. An error fe occurred creating ASAPX process pname. To determine the cause of this problem, see a description of file-system error numbers. Effect. ASAPXSGP failed to start an ASAPXMON process in one of the processors. ASAPX will not be enabled for that processor. Recovery.
Cause. The EDL Compiler returned an error to ASAPX indicating a syntax error in a user-defined EDL file. Effect. Some user-defined entities are not loaded. ASAPX stops loading EDL at the point where the error occurred. Recovery. Correct the EDL error, then restart ASAPX. 1833 ASAP ERR component Error in formula: ename, aname component is the ASAP component affected by the EDL error ename is the name of the entity as defined in EDL aname is the name of the attribute as defined in EDL Cause.
1835 Aggregation rejected, max aggregates: domain, Max: max domain is the name of the first domain that failed aggregation. max is the maximum number of allowed aggregate domains in the processor. Cause. The maximum number of aggregate domains already exist in the processor. Effect. ASAPX cannot aggregate any more domains in the processor. Recovery.
Cause. (ASAP Release 1 only) ASAPX did not find a SET NAMEFILE command in the ASAPXCNF fname file. This could result in reserved names being entered as domain names and could yield unexpected results in ASAP, OEM, and OIL. Effect. ASAPX is not affected; however, using reserved names as domain names can cause a myriad of problems in ASAP, OEM, and OIL. Recovery. ASAPX warns about this problem and continues processing normally. To eliminate this warning message, add a SET NAMEFILE $ISV Volume.ZASAPX.
Effect. ASAPX shuts down. Recovery. None. 1881 ASAPX component INFO version started, cpu Cause. ASAPX component received a start request against PID. Effect. ASAPX starts. Recovery. None. 1899 ASAP ASAP Error num occurred xxxx time(s) num is the number the recurring error xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None.
Effect. The statistical information received is not saved and cannot be written to the database. 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 the database to be sure it is present and secured properly. If the database is full, enlarge it or re-create it according to the installation instructions in the ASAP Server Manual .
2003 Can’t Rename filename, fe: err err is the file-system error number associated with the last operation on the file Cause. The Collector cannot rename the database file names to ZmmddL (where mmdd represents month and day, and L represents the last three letters of the original file). Effect. Database files are not being renamed. Recovery. The FILEINFO system call returned this error.
Cause. The data records were purged successfully. num represents the number of records that have been cleaned. Effect. The database cleanup operation is completed. Recovery. This message is informational only. No corrective action is required. 2006 Short request received: count, buf, pid count is the length of the message, in bytes buf is the first word of the received request message pid is the requester’s process ID Cause. A received message is unrecognizable because of its short length. Effect.
buf is the first word of the received request message 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 problem persists, contact your HP representative. 2009 ENFSV trans code bad Cause. An incomprehensible input request was received. Effect. The Collect server cannot behave as an Enform server because it could not understand the request. Recovery. Check your Enform request and retry it.
2012 Open filename, fe: err, type err is the file-system error number associated with the last operation on the file type is an internal index to the ASAP database with these values: 0 DBSYS 1 DBCPU 2 DBNET 3 DBPCB 5 DBNODE 6 DBAPP 7 DBDSK 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.
2014 SHUTDOWN Complete! Requester = pid pid is the requester’s process ID Cause. The system was shut down by the requester indicated in the message. Effect. The requester was shut down successfully. Recovery. This message is informational only. No corrective action is required. 2015 Trace Cause. The system performed an internal trace. Effect. The system is working correctly. Recovery. This message is informational only. No corrective action is required.
version is the base release version of the ASAP environment Cause. The system is informing you that the Enform server started successfully. Effect. The Enform server is operating. Recovery. This message is informational only. No corrective action is required. 2018 $RECEIVE read, FE: err err is the file-system error number associated with the last operation on the file Cause. A system message was not received or read. Effect. The system did not receive the message. Recovery.
Effect. The system did not reply to 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 . If the problem persists, contact your HP representative. 2020 DB Rename notify table full count count is the count of rename message notifications that are currently pending. Cause.
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. 2025 PURGE trace filename filename is the name of old date base file marked for deletion due to SET DBMAXDAYS. Cause.
Cause. The Collector could not remove an existing partition control file. The cause is most likely a security violation on the partition control file. Effect. The new partition control file is not created. The existing partition control file is used in creating a new database. Recovery. Depends on error. 2031 PCtl Creat filename error filename name of the control file error file-system error number Cause. The Collector could not create a new partition control file.
2033 PCtl Open filename error filename name of the control file error file-system error number Cause. The partition control file could not be opened when the Collector was started. The cause is most likely a security violation on the partition control file or a sharing violation because another application has the control file open. Effect. The Collector cannot get any partitioning settings and creates the database using default settings. Recovery. Depends on error.
Cause. The Collector could not read partitioning settings from the partition control file. Most likely the control file does not exist or could not be accessed because of security or sharing violations. Effect. The Collector cannot get any partitioning settings and creates the database using default settings. Recovery. Depends on error. If an internal ASAP error occurred, contact your support representative.
2038 Unknown suffix entity-suffix entity-suffix suffix for an ASAP entity. Cause. The Collector encountered an unknown ASAP database entity suffix. The cause is an internal Collector error, possibly due to a versioning inconsistency. Effect. The Collector does not create a database for the specified entity. Recovery. Contact your support representative. 2039 CreatePart filename file-error partition-index filename database file that cannot be created. file-error file-system error number.
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. The cause is most likely a system error such as a down target volume or a security violation, or an internal ASAP error. Effect. The Collector does not create a database for the specified entity. Recovery. Depends on error. Enter SET PARTITION to view partitioning settings.
Effect. MaxExtents values defined for secondary partitions are ignored. The MaxExtents value for the base partition of the entity is used for the secondary partitions. Recovery. Either disable Format2 support or do not specify MaxExtents values for secondary partitions. 2043 OpenPart filename file-error partition-index filename database file that cannot be opened. file-error file-system error number. partition-index partition that cannot be opened. Cause.
Recovery. Make sure files are secured properly. 2052 DB^AltKeyFile^SET call fnamecollapse failed Cause. The Collector could not set alternate key file info for the DB. The cause is most likely a security violation. Effect. The Collector cannot set alternate key file info. Recovery. Make sure files are secured properly. 2053 DB^AltKeyFile^NAME filename invalid Cause. The Collector DB file name is invalid. The cause is most likely an invalid database file name specification. Effect.
Cause. The Collector cannot do a Purgedata on . The cause is most likely an invalid database alternate key file. Effect. The Collector cannot purge data in an alternate key file. Recovery. Depends on err. Use FUP to do an INFO , DETAIL and check whether the Alternate key file is valid. If not, then use FUP to correct the AK file specification. 2057 DB^AltKeyFile^GET FILE FE: err Cause. The Collector cannot GET alternate key info for .
Cause. The Collector cannot ALTER alternate key for . The cause is most likely an invalid database alternate key file specification. Effect. The Collector cannot ALTER an alternate key file. Recovery. Depends on err. Use FUP to do an INFO , DETAIL and check whether the Alternate key file is valid. If not, then use FUP to correct the AK file specification. 2099 ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause.
= 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 = filesystem error number 12 Program file and library file specified are same file 13 Extended data segment initialization error; error 8:15 = filesystem error number 14 Extended segment swap file error; error
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.
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. An attribute failed to meet an objective where the objective is defined for event generation. Effect. User-specific. Recovery.
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.
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. If the problem persists, contact the GMCSC.
Recovery. If the problem persists, contact the GMCSC. 4105 RDF Could not resolve P-handle, FE: error error the file-system encountered by the RDF SGP while trying to get or decode its process handle. Cause. The SGP could not determine its own process handle. Effect. The SGP continues processing; however, some fields in RDF statistics records are invalid. Recovery. Create a saveabend file of the RDF SGP, then stop the SGP. Contact the GMCSC.
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. The EDL settings might cause this error might. For more information on EDL, see the ASAP Client Manual. 4302 SPL sgp_readdomain_ Error= FE: error error file-system error returned by the SGP_READDOMAIN_ procedure Cause.
4304 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.
Effect. Depending on the returned error, the entity might not have been ranked. Recovery. Verify that the objective is working properly. For more information about objectives, see the MONITOR and RANK commands in the ASAP Server Manual. 4307 SGP SPL Error loading objectives: FE: error, error-detail error value returned from the LOAD^OBJECTIVES procedure to identify the specific error error-detail more information returned from the LOAD^OBJECTIVES procedure to identify the specific error Cause.
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 Spooler SGP processname and nodename are not defined correctly. Recovery. Contact your system administrator.
4312 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. If it is a spooler problem, the Spooler SGP will recover once you fix the Spooler environment.
4315 SPL Batch Job array overflow in domain^count^jobs^locs. Cause. The array used to temporarily hold the job numbers of the jobs used as part of batch jobs is full. Effect. The BATCH attribute for devices and print processes might not be reported correctly. Recovery. Verify the spoolers being monitored. Count the number of jobs that are part of batch jobs. If this number is high for one spooler, inform your HP support representative of your configuration.
configuration is correct, note the name, create a saveabend file of the Spooler SGP, stop the SGP, and contact your HP support representative. 4393 Timeout error occurred in get^spooler^stats for SGP SPL. Cause. The spooler supervisor was too busy to return information to the SPL SGP. Effect. The Spooler SGP tries five times, in one second intervals, before giving up. Recovery. If this error occurs frequently, check why the spooler supervisor is so busy. 4394 SPL EDL loaded. Cause.
Cause. An error occurred when trying to load the spooler domain names to monitor (see message 4302 on page 123). This message indicates that the last list of domains will be used instead. Effect. The previous spooler configuration is reloaded, and the last list of domains is used. Recovery. Informational message; no corrective action is necessary. However, because this message appears after error 4302 on page 123, see the recovery for that message to fix the problem it indicates.
4401 TAP ecb loadentities error-text error-text error message returned by the ecb_loadentities_ procedure Cause. The ASAP ecb_loadentities_ procedure call returned the specified error when trying to load the tape entity. Effect. The tape entity does not load. Recovery. The EDL settings might cause this error. For more information on EDL, see the ASAP Client Manual. 4402 TAP sgp_readdomain_ Error= FE: error error file-system error returned by the SGP_READDOMAIN_ procedure. Cause.
error error returned by the specified SPI procedure call cmd MediaSRV command used in the SPI buffer when the error occurred token name of the SPI token to obtain or push when the error occurred Cause. The specified SPI command returned error. cmd and token provide more information about where and why the SPI command was executed. Effect. The status operation for the tape device is aborted and set as SPI error. It is retried at the next sampling. Recovery.
error value returned from the SGP_RANKVALUE_ procedure to identify the specific error error-detail detailed information returned from the SGP_RANKVALUE_ procedure to identify the specific error Cause. The ASAP sgp_rankvalue_ procedure call returned the specified error when trying to rank the tape domain. Effect. Depending on the returned error, the entity might not have been ranked. Recovery. Verify that the objective environment is working properly.
4409 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. Contact your system administrator.
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. The Tape SGP sets the status for the domain to UNKNOWN. Recovery. Verify that the specified domain is a valid tape device. If it is, contact your system administrator. 4412 TAP MEDIASRV WRITE error:error error error which occurred when trying to perform a WRITEREAD to the MEDIASRV server process Cause.
error-detail error details returned by the NonStop Kernel GETINFOLIST procedure Cause. The NSK PROCESS_GETINFOLIST_ procedure call returned the specified error when trying to get information about the process that has the tape device open or that is requesting the tape mount. Effect. The user ID and program name are not assigned to the tapemount request or tapedrive status. Recovery. If this error recurs, contact your system administrator. 4415 TAP error finding tape devices.
Cause. The Tape SGP encountered an error while trying to load objectives for a domain or subdomain. Effect. The new objectives are not loaded and the old ones are used. Load is attempted on the next sampling. Recovery. Verify that the EDL and objectives database are correctly installed and configured. 4493 TAP Could not add to last domain table: maximum of num reached. num maximum number of tape domain entries allowed in the Tape SGP Cause.
Effect. None. Recovery. Informational message; no corrective action is necessary. To prevent these messages from appearing, remove the STATS parameter from the ASAPCONF file or reset it from your ASAP session, and restart the Tape SGP. 4496 TAP Reloading previous configuration. Cause. An error occurred when trying to load the tape domain names to be monitored (see message 4402 on page 131). This message indicates that the last list of domains is used instead. Effect. None. Recovery. Informational message.
Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. 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.
Cause. An error occurred while trying to get the state of a domain attribute. Effect. The state of this domain attribute is not obtained, The returned state value is the default value of the Exists state. Recovery. Make sure no problem exists with the ASAP Objectives database. 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.
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.
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. No TMF statistics are collected until the TMF SGP successfully starts the TMFSERVE process. Recovery. Use error-num and error-detail to determine the cause of the error.
4535 ASAPTMF TMFSERVE startup awaitio 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. Recovery.
Effect. The SPI buffer cannot initialize, so the SPI command is not sent to the TMFSERVE process for this sampling. The error is reported against the appropriate domain. Recovery. Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative. 4551 ASAPTMF spi-cmd,SPI Error Send= error-num spi-cmd SPI command on which the error occurred error-num SPI error returned while sending the SPI buffer Cause.
4553 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.
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. The error is reported against the appropriate domain. Recovery. Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative.
4558 ASAPTMF spi-cmd,SPI Error ExitList= error-num spi-cmd 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. The error is reported against the appropriate domain. Recovery. Use spi-cmd and error-num to determine the cause of the error.
Recovery. Informational message; no corrective action is necessary. 4593 TMF TMFSERVE started Cause. The TMFSERVE process started. Effect. The TMFSERVE process starts. Recovery. Informational message; no corrective action is necessary. 4594 TMF EDL loaded Cause. The EDL was correctly loaded for the TMF SGP. Effect. The SGP startup continues. Recovery. Informational message; no corrective action is necessary. 4595 TMF Stats performance messages. Cause.
4598 TMF Autoconfiguration completed. Cause. No domains were defined in the Objectives Database to monitor. Effect. The TMF SGP configures all supported TMF domains by default. Recovery. To modify the list of domains to monitor, use the MONITOR command, then the COMMIT command. Autoconfigured domains are then automatically removed. 4599 ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect.
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. 4603 Returned text from the EDL compiler. Cause.
sgpid is the identifier of the File or Process SGP. Cause. The Process SGP was configured to monitor more than the maximum number of domains. Effect. Only the first 1000 processes listed are monitored. Recovery. Configure ASAP to monitor fewer processes. 4606 Pool Definition error: error Cause. The address_delimit_ procedure returned an error while the SGP was attempting to define pool space for dynamically resolved domains. Effect.
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. 4610 SPI error on SPI Procedure: error SPI procedure is the name of the SPI procedure that returned the error. error is the error number returned by the SPI procedure Cause. The SGP received the indicated SPI error when calling SPI Procedure. Effect.
error detail is the detailed error (if any) encounted when opening the process. 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 then restart ASAP. 4613 Cannot open server, FE: error , error detail server is the name of the server process. error is the file-system error encountered when communicating with the server.
Recovery. Correct the error and restart ASAP. 4616 server start retry limit exhausted server is the object file name of the server process 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. 4617 function-location SPI Error: error function-location is the procedure location within the SGP where the error occurred.
4699 ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. 4700 ASAPCMM NonStop Kernel must be release D40 or Greater Cause. ASAPCMM cannot be started. Effect. ASAPCMM is not operating. Recovery. Shut down the ASAPMON, set CMM off, and restart the ASAP Monitor.
Effect. ASAPCMM starts the measurement in the CPU where the ASAPCMM process is running. Recovery. If the ASAPMON CPU is not desirable, shut down ASAPMON, correct the Comm Param CPU nn to a valid and operational CPU. 4720 ASAPCMM ZCMMXXX started. Cause. ASAPCMM started a measurement successfully. Effect. ASAPCMM is operating. Recovery. Informational message only; no corrective action is needed. 4721 ASAPCMM ZCMMXXX NOT started. Cause. ASAPCMM could not start a measurement. Effect.
cpu is the CPU number. Cause. The Communication SGP started the MEASCTL process in a CPU that did not have the MEASCTL process running. Effect. ASAPCMM starts MEASCTL in the CPU. Recovery. Informational message only; no corrective action is needed. 4725 ASAPCMM Measure error measure err measure is the Measure error. err is the Communication SGP internal error number for ASAP development. Cause. The Communication SGP received an error from the Measure subsystem. Effect.
ldev is the logical device number. Cause. The Communication SGP could not access the device control table. ldev represents the logical number of the device. Effect. ASAPCMM cannot collect communication statistics. Recovery. Contact your HP representative to file an HP Product Case. 4744 ASAPCMM Comm device inaccessible ldev ctrl ldev is the logical device number. ctrl is the controller for D-Series RVUs, or the module for G-Series RVUs. Cause. The Communication SGP could not access the device. Effect.
Cause. The ASAPMON process stopped the ASAPCMM process. Effect. ASAPCMM stops its measurement. Recovery. This message is informational only. No corrective action is required. 4750 Error SET COMM PARAM param param is the invalid parameter. Cause. ASAPCMM detected an invalid parameter in the SET COMM ON, PARAMETER command. Effect. ASAPCMM uses the default values for all parameters. Recovery. Ensure that all parameters in the ASAP startup file ASAPCONF are valid. Then restart the ASAP Monitor.
Recovery. Make sure that ASAP is configured correctly. For more information about configuring domains, see the ASAP Extension Manual. If the configuration is correct, contact your HP support representative. 4754 Load Objectives Error: err, ldev err is the error number returned from the Load^Objectives procedure. ldev is the logical number of the communication line that failed. Cause. The ASAP Load^Objectives procedure returned the specified error when trying to get the list of communication objectives.
err is the error number returned from the SGP_RankValues procedure. error-detail is the error detail number returned from the SGP_RankValues procedure. Cause. The ASAP sgp_rankvalues procedure returned the specified error when trying to rank Comm objectives. Effect. The Comm objectives for all ranked objectives will be equal to an OEM state value of 1 for the sample period. Recovery. Make sure ASAP is configured correctly. For more information about ranking objectives, see the ASAP Server Manual.
4800 SSG Initialize Error = ssg.err, ssg.errdet, ssg.errsubdet Ssg.err is the SSG error returned from the Seeview Server Gateway. Ssg.errdet is the SSG error detail returned from the Seeview Server Gateway. Ssg.errsubdet is the SSG error subdetail returned from the Seeview Server Gateway. Cause. SSG cannot be started. Effect. ASAPSWP is not reporting KMSF statistics Recovery. Shut down the ASAP environment SET SWAP OFF restart ASAP.
4802 SSG ErrorText errortext is the corresponding errot text from the SSG for error numbers 4800-4802,4804, 4809, 4810 Cause. An error occurred with the SSG interface. Effect. ASAPSWP is not reporting KMSF statistics Recovery. Shut down the ASAP environment SET SWAP OFF restart ASAP. Contact the GMCSC or HPVC depending on your geographical location and submit a case include the SSG.err, SSG.errdet, the SSG. Errsubdet and the SSG errortext from the accompaning 4802 message.
Recovery. Contact the GMCSC or HPVC depending on your geographical location and submit a case. Include the SSG.err, SSG.errdet, the SSG. Errsubdet and the SSG errortext from the accompaning 4802 messageif it exists. 4807 Unable to Parse SSG Reply param param is the KMSF token being parsed. Cause. The parser reached the end of the buffer and did not find the KMSF token it was searching for. Effect. ASAPSWP no longer attempts to obtain KMSF statistics. Recovery.
Ssg.errdet is the SSG error detail returned from the Seeview Server Gateway. Ssg.errsubdet is the SSG error subdetail returned from the Seeview Server Gateway. Cause. The SSG buffer is full. Effect. The Swap SGP writes records to the ASAP DB without the KMSF counters. Recovery. Contact the GMCSC or HPVC depending on your geographical location and submit a case. Include the SSG.err, SSG.errdet, the SSG. Errsubdet and the SSG errortext from the accompaning 4802 messageif it exists.
ssgid is the name of the SSG ID being used. Cause. The ID created is the ID of the ASAP environment with the appended letter B to the end of it. Default $ZOOB. The Swap SGP discovered that the process name is in use and is not a valid SSG process. Effect. The ASAP Swap SGP will not report on KMSF records. Recovery. Select a different ASAP ID that is not an existing process name and shut down and restart the ASAP environment. 4815 ASAPSWP No file fname fname Swap file name. Cause.
err 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 Swap entity. Effect. The Swap 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. 4852 ASAPSWP Unable to report Object Thresholds Cause.
cpu is the CPU number. Cause. The ASAP Load^Objectives procedure returned the specified error when trying to get the list of Swap objectives. Effect. Swap SGP monitors all configured communication lines. Recovery. Make sure that ASAP is configured correctly. For more information about Ranking Objectives, see the ASAP Server Manual. If the configuration is correct, contact the GMCSC or HPVC depending on your geographical location and submit a case.
Recovery. Make sure ASAP is configured correctly. For more information about ranking objectives, see the ASAP Server Manual. If the configuration is correct, contact the GMCSC or HPVC depending on your geographical location and submit a case. 4865 Error SET SWAP PARAM param param is the invalid parameter Cause. ASAPSWP detected an invalid parameter in the SET DISK ON, PARAMETER command. Effect. ASAPSWP uses the default values for all parameters. Recovery.
Section 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.
1019 ZASP-EVT-SGP-SHUTDOWN-ERROR cpu, pid 1020 ZASP-EVT-MON-SHUTDOWN-COMPLETE pid 1021 ZASP-EVT-MON-TRACE 1022 ZASP-EVT-MON-STARTED cpu 1023 ZASP-EVT-SGP-STARTED cpu 1024 ZASP-EVT-MON-RCV-READ-ERROR err 1025 ZASP-EVT-MON-RCV-REPLY-ERROR err 1026 ZASP-EVT-MON-SAMPLE-MISSE sec, rate 1027 ZASP-EVT-MON-INVALID-CPU-SYSNAME cpu 1028 ZASP-EVT-MON-INVLD-SYSNAME-RCV 1029 ZASP-EVT-MON-MISSNG-ACT-SCRIPT err 1030 ZASP-EVT-MON-ACT-START-MSG-FLD err 1031 ZASP-EVT-MON-ACT-NOT-CREATED er
1220 ZASP-EVT-EXPDMGR-NOT-CREATED err 1230 ZASP-EVT-EXPDMGR-NOT-OPENED err 1231 ZASP-EVT-SPI-RQST-NOT-BUILT err 1232 ZASP-EVT-MON-EXPDMGR-FS-ERROR err 1233 ZASP-EVT-MON-EXPDMGR-SPI-ERROR err 1234 ZASP-EVT-MON-EXPDMGR-RETRY-CNT cnt 1235 ZASP-EVT-MON-EXPDMGR-NO-PATH ldev 1236 ZASP-EVT-MON-EXPDMGR-PATH-STAT err, ldev 1237 ZASP-EVT-MON-EXPDMGR-PATH-INFO err, ldev 1238 ZASP-EVT-MON-EXPDMGR-CSM-STAT err, ldev 1239 ZASP-EVT-MON-EXPDMGR-NCSM-STAT err, ldev 1240 ZASP-EVT-MON-EXPDMGR
1308 ZASP-EVT-BAD-SMON-SUBSAMPLING 1309 ZASP-EVT-NO-PCB-STATS err 1399 ZASP-EVT-SUPPRESSED-ERRORS num, xxxx 1400 ZASP-EVT-NO-PROCESSOR-INFO err 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 Table 2-2.
err 1735 ZASP-EVT-DSK-COLLECT-ERROR 1740 ZASP-EVT-DSK-INVALID-SWAPFILE 1741 ZASP-EVT-DSK-INVALID-VOLUME 1742 ZASP-EVT-DSK-DCT-ACCESS-ERROR ldev 1743 ZASP-EVT-DSK-MEAS-NOT-RESTARTD err 1744 ZASP-EVT-DSK-DEVICE-INACCESSBL ldev, ctrl 1745 ZASP-EVT-DSK-NO-OPTCL-DSKS-RPT 1746 ZASP-EVT-DSK-NO-VRTUL-DSKS-RPT 1747 ZASP-EVT-DSK-SHUTDWN-INCMPLETE 1748 ZASP-EVT-DSK-SHUTDOWN-COMPLETE 1749 ZASP-EVT-DSK-UNEXPECTED-ERROR err 1751 ZASP-EVT-DSK-ECB-LOAD-ERROR error-text 1752 ZASP-EVT-DSK-LOAD-
charoffset 2010 ZASP-EVT-COL-STARTUP-ERROR 2011 ZASP-EVT-COL-OPEN-TERM-ERROR 2012 ZASP-EVT-OPEN-ERROR err, type 2013 ZASP-EVT-OPEN-INFO type 2014 ZASP-EVT-COL-SHUTDOWN-COMPLETE pid 2015 ZASP-EVT-COL-TRACE 2016 ZASP-EVT-COL-STARTED cpu 2017 ZASP-EVT-ENFSERV-STARTED cpu 2018 ZASP-EVT-COL-RCV-READ-ERROR err 2019 ZASP-EVT-COL-RCV-REPLY-ERROR err, count, buf, pid 2020 ZASP-EVT-COL-RENAME-TABLE-FUL 2022 ZASP-EVT-COL--DST-FALLBACK seconds 2024 ZASP-EVT-COL-PURGE-ERROR error 2025
2050 ZASP-EVT-COL-DBAK-GET-FILE-COL 2051 ZASP-EVT-COL-DBAK-GET-FILE-EXP 2052 ZASP-EVT-COL-DBAK-SET-FILE-COL 2053 ZASP-EVT-COL-DBAK-FILENAME-BAD 2054 ZASP-EVT-COL-DBAK-PURGE-NAMERR error 2055 ZASP-EVT-COL-DBAK-PURGEDATAOPN error 2056 ZASP-EVT-COL-DBAK-PURGEDATAERR error 2057 ZASP-EVT-COL-DBAK-RENAME-GETER error 2058 ZASP-EVT-COL-DBAK-RENAME-OPEN error 2059 ZASP-EVT-COL-DBAK-RENAME-ERROR error 2060 ZASP-EVT-COL-DBAK-ALTER-ERRMSG error 2099 ZASP-EVT-EXP-SUPPRESSED-ERRORS xxxx Ta
4099 ZASP-EVT-EXP-SUPPRESSED-ERRORS Table 2-6. RDF Event Messages Message Number Messages 4101 ZASP-EVT-RDF-FILE-FINDNEXT-ERR 4102 ZASP-EVT-RDF-FILE-FINDSTRT-ERR 4104 ZASP-EVT-RDF-RANK-VALUE-ERR 4105 ZASP-EVT-RDF-RES-PHANDLE-ERR 4106 ZASP-EVT-RDF-LOAD-ENTITIES-ERR 4199 ZASP-EVT-RDF-SUPPRESSED-ERRORS Table 2-7.
4395 ZASP-EVT-SPL-SAMPLESTATS-INF 4396 ZASP-EVT-SPL-RELOADPREV-INF 4397 ZASP-EVT-SPL-DOMAINOVR-INF 4398 ZASP-EVT-SPL-AUTOCONFIG-INF 4399 ZASP-EVT-EXP-SUPPRESSED-ERRORS num num xxxx Table 2-8.
Table 2-9.
4597 ZASP-EVT-TMF-MAXDOMAINS 4598 ZASP-EVT-TMF-AUTOCONFIG-DONE 4599 ZASP-EVT-TMF-SUPPRESSED ERRORS Table 2-10.
4722 ZASP-EVT-CMM-MEAS-RESTARTED err 4723 ZASP-EVT-CMM-MEASCTL-RESTARTED cpu 4725 ZASP-EVT-CMM-MEASURE-ERROR err 4735 ZASP-EVT-CMM-COLLECT-ERROR err 4742 ZASP-EVT-CMM-CONF-ACCESS-ERROR ldev 4743 ZASP-EVT-CMM-MEAS-NOT-RESTARTD err 4744 ZASP-EVT-CMM-DEVICE-INACCESSBL ldev, ctrl 4747 ZASP-EVT-CMM-SHUTDWN-INCMPLETE err 4748 ZASP-EVT-CMM-SHUTDOWN-COMPLETE 4750 ZASP-EVT-CMM-PARAM-ERROR param 4751 ZASP-EVT-CMM-ECB-LOAD-ERROR error-text 4753 ZASP-EVT-CMM-READDOMAIN-ERROR err 4754
4851 ZASP-EVT-SWP-ECB-LOAD-ERROR: err 4852 ZASP-EVT-SWP-NO-OBJECTIVES 4853 ZASP-EVT-SWP-READDOMAIN-ERROR err 4854 ZASP-EVT-SWP-LOAD-OBJTVS-ERROR: err, err 4856 ZASP-EVT-SWP-GETOBJTIVES-ERROR err 4857 ZASP-EVT-SWP-RANKVALUES-ERROR err, err 4865 ZASP-EVT-SWP-SET-SWAP-PARAMS param 4899 ZASP-EVT-SWP-SUPPRESSED-ERRORS num xxxx ASAP Event Tokens ASAP uses standard SPI tokens, standard EMS tokens, and ASAP-specific tokens in each event message.
performance events, it can be set to TRUE using the CRITICAL option of the ASAP Conversational Interface’s SET EVENTS command. ZEMS-TKN-EVENTNUMBER contains the event number for the ASAP event. ZEMS-TKN-GENTIME contains the time (GMT) at which ASAP created the event message. ZEMS-TKN-LOGTIME contains the time (GMT) at which the EMS Collector wrote the event message to the log files. ZEMS-TKN-PIN contains the PIN of the ASAP process that generated the event.
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. ZASP-TKN-ASAP-ATTRIBUTE-FLT2 is present and contains the attribute value for attributes of type REAL64. ZASP-TKN-ASAP-VALUETEXT contains a text representation of the attribute value.
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.
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 ―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.
ZASP-TKN-ASAP-ERRORNUM is ―1003‖. 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.
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 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.
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 ―1007‖.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1009‖. 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.
Cause. The message received was not recognized because of its short length. Effect. The message could not be processed. Recovery. If the problem persists, contact your 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.
count is the length of the message in bytes. pid is the requester’s process identification. Cause. An invalid request was received. Effect. The system does not process the request. Recovery. Retry the request.
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 ―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.
ZASP-TKN-ASAP-ERRORNUM is ―1016‖. 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.
err.<8:15> = file-system error. 15 Invalid home terminal; err.<8:15> = filesystem 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.
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.
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 ―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.
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. The Statistics Gathering process (SGP) started successfully. Effect. The SGP is running.
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 . 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. Data Tokens. ZEMS-TKN-TEXT contains the message text.
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. 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. Data Tokens. ZEMS-TKN-TEXT contains the message text.
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. Effect. User-defined actions will not work Recovery. Correct the ACTSHELL file location. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "1029". 1030: ZASP-EVT-MON-ACT-START-MSG-FLD ACTION startup msg fail, FE err err is the error number. Cause.
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. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "1031". 1032: ZASP-EVT-MON-ACT-OPEN-FAILED ACTION Open failed err err is the error number. Cause.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "1033". 1051: ZASP-EVT-MON-ECB-LOAD-ERROR ASAPCPU ECB_Load Error error-text error-text is error text returned from the Ecb_loadentities_ procedure. Cause. The ASAP ecb_loadentities_ procedure returned the specified error when trying to load the CPU entity. Effect. The CPU entity does not load EDL records. Recovery. This error might be caused by the EDL settings. For more information on ASAP EDL, see the ASAP Client Manual. Data Tokens.
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 all configure System entities. 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 ―1053‖.
ZASP-TKN-ASAP-ERRORNUM is ―1057‖. 1058:ZASP-EVT-MON-SGP-NOT-STARTED Could not start SGPid in CPU nn SGPid is the SGP ID that was not started in the specified cpu. nn is the SGP UD that was not started in the specified cpu. 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. Data Tokens. ZEMS-TKN-TEXT contains the message text.
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. 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‖.
1097: ZASP-EVT-LICENSE HAS EXPIRED Software License 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 #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause. The error number was suppressed. 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 ―1100‖. 1101: ZASP-EVT-BAD-GETPEEKSTATS-LEN GETPEEKSTATS length bad: length length is the length, in bytes, returned from the GET^PEEK^STATISTICS system procedure call. Cause.
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.
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. 5 File error on swap file; err.<8:15> = filesystem error.
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.<8:15> = 3 Invalid DEFMOD supplied. 18 Object file with an invalid process device subtype.
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 . Check that the operating system subsystem manager is present, up, and running.
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 ―1212‖. 1220: ZASP-EVT-EXPDMGR-NOT-CREATED Can’t Create Subsystem Mgr, Error: err err identifies a file-system error. Cause.
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. 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 the Expand Manager is up and running.
-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. The Expand SGP could not build an SPI request buffer. Effect. No information is returned by SPI. Recovery. Check the operating system version to make sure all the SPI routines are installed. These routines include SSPUT, SSGET, SSINIT, and others. Retry 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 . Check that the Expand Manager is up and running.
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.
ZASP-TKN-ASAP-ERRORNUM is ―1234‖. 1235: ZASP-EVT-MON-EXPDMGR-NO-PATH ASAPMON No path found for Expand line ldev: ldev ldev is the logical number of the device. Cause. The Expand SGP could not obtain level-4 statistics for a multiline Expand configuration line. Effect. ASAP does not obtain path 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 ―1236‖. 1237: ZASP-EVT-MON-EXPDMGR-PATH-INFO ASAPMON Can't obtain Path information Error: err, ldev err is the SPI error number returned by the $ZEXP process.
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. ldev is the logical device number of the Expand line. Cause. The Expand SGP could not obtain Communications Subsystem Manager (CSM) line statistics. Effect. ASAP does not obtain CSM statistics from the Expand manager. Recovery. This error message is used for problem isolation.
Recovery. This error message is used for problem isolation. If the problem persists, contact your HP support representative and provide: 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 ―1239‖.
1241: ZASP-EVT-EXP-COLLECT-ERROR ASAPEXP -> COLLECT send error: err err is the returned file-system error number associated with the last operation on the file Cause. ASAPEXP encountered an error while attempting to send a message to the ASAP Collector. Effect. ASAPDEXP cannot complete the request. Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see the Operator Messages Manual, or the Guardian Procedure Errors and Messages Manual . Data Tokens.
1243: ZASP-EVT-EXP-ILLEGAL-RQST-RCVD 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1243‖.
1245: ZASP-EVT-EXP-ATM-CNTRS-UNAVAIL Cannot Obtain ATM stats Error: err, Ldev err is the SPI error number returned by the Expand manager $ZEXP process Ldev is the logical device number of the device of the Expand line Cause. The Expand SGP could not obtain ATM statistics for a Expand line using ATM as the transport. Effect. ASAP could not obtain path statistics from the Expand manager. Recovery. Recovery. This error message is used by HP for problem isolation. Contact your HP representative. Data Tokens.
error-text is error text returned from the Ecb_loadentities_ procedure Cause. The ASAP ecb_loadentities_ procedure returned the specified error when trying to load the Expand entity. Effect. The Expand entity does not load EDL records. Recovery. 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 ―1251‖.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1253‖. 1254: ZASP-EVT-EXP-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 Expand line that failed Cause. The ASAP Load^Objectives procedure returned the specified error when trying to get the list of Expand threshold objectives. Effect. Expand monitoring monitors all configured Expand lines. Recovery.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1255‖. 1256: ZASP-EVT-EXP-GETOBJTIVES-ERR GetObjectives Error: err, Ldev err is the error number returned from the SGP_GETOBJECTIVES_ procedure Ldev is the logical number of the Expand line that failed Cause. The ASAP sgp_Getobjectives procedure returned the specified error when trying to get the list of Expand threshold objectives. Effect. Expand monitoring does not begin. Recovery. Make sure that ASAP is configured correctly.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1257‖. 1266: ZASP-EVT-EXP-BAD-STATS-RCVD ASAPEXP Bad Stats Received ldev ldev is the logical number of the device Cause. The ASAP Expand SGP encountered a bad statistics record. Effect. The bad statistics record is discarded. Recovery. If the error persists, contact your HP support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1266‖.
Cause. The system could not obtain process statistics. Effect. A zero value is returned instead of a process statistics value. Recovery. Check that your operating system version and ASAP version are compatible.
Cause. The system could not get the program file name of the process. A process went away between a GETPEEKPCBs call and a PROCESSINFO call. Effect. The process information does not include a related program file name. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1301‖.
dst is the delta of the sample time for this PIN. Cause. ASAP detected a 100-percent process control block (PCB) busy state, possibly because of an internal interface failure with the operating system. Effect. The PCB busy information is suspect. Recovery.
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 ―1304‖. 1305: ZASP-EVT-PROC-TIMES Pin:This_ProcessTime:Last_ProcessTime in 10 sec: pin#, pt1, pt2 pin# is the process identification number. pt1 is the total process time of this PIN at the current sample time.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1305‖. 1306: ZASP-EVT-ALIVE-BUT-NO-PCB Pin:Alive but No PCB:priority:Last_PTime in .1 sec: pin#, pt2 pri, pin# is the process identification number. pri is the process priority. pt2 is the total process time of this PIN at the last sample time. Cause. The process was alive, but statistics were not returned, possibly due to an internal operating system error. Effect.
pin# is the process identification number. which indicates array information, with either of these values: 0 indicates the current sample array. 1 indicates the previous array. Cause. The process you specified is not in the internal sample array. This is an internal error. Effect. Process control block (PCB) information cannot be returned. Recovery.
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 ―1308‖. 1309: ZASP-EVT-NO-PCB-STATS Unable to collect PCB statistics, error: err err indicates the outcome of a PROCESSINFO system procedure call and returns one of these values: err Meaning 0 Returns the status for process CPU, PIN.
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 ―1309‖. 1399: ZASP-EVT-PCB-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.
CPU_GETINFOLIST_ cannot obtain information from a C-series system. Cause. The Monitor could not retrieve the CPU processor type. The FILEINFO system procedure call returned this error. Effect. A CPU processor type value is not returned. Recovery. For 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 your operating system version and ASAP version are compatible.
8 The specified node is running a C-series version of the operating system; CPU_GETINFOLIST_ cannot obtain information from a C-series system. Cause. The Monitor could not retrieve CPU configuration information or statistics for the specified processor. The CPU_GETINFOLIST_ system procedure call returned this error. Effect. A zero value is returned instead of CPU configuration and statistics information. Recovery. For a definition of the specified error, see the Operator Messages Manual.
ZASP-TKN-ASAP-ERRORNUM is ―1499‖. 1503: ZASP-EVT-NCP-COLLECT-ERROR Send to collect error: error error the file-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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1503‖.
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1519‖. 1530: ZASP-EVT-NCP-PARAM-ERROR Error SET NODE PARAM Cause. An error was found while processing startup parameters. Effect. The startup parameter is ignored. Recovery.
Cause. ASAPDSK cannot be started. Effect. ASAPDSK is not operating. Recovery. Shut down the ASAPMON, set disk to OFF, and restart the ASAP Monitor. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1700‖. 1701: ZASP-EVT-DSK-SECURITY-ERROR 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 group only. Effect. ASAPDSK cannot obtain disk counters. Recovery.
ZASP-TKN-ASAP-ERRORNUM is ―1702‖. 1703: ZASP-EVT-DSK-MEAS-FILE-INUSE ASAPDSK ASAPmeas file in use err err is the Measure error returned from the Measure subsystem. Cause. The Measure subsystem has a measurement data file with the same name as ZASPxxx, where xxx is the ASAP ID. The Disk Statistics Gathering process (SGP) could not delete it. Effect. ASAPDSK cannot obtain disk counters. Recovery. Close the file through MEASCOM. The disk SGP will attempt to start the measurement during the next sample period.
err is the Measure error returned from the Measure subsystem. Cause. The MEASFH process trapped out. 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. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1705‖.
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. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1707‖. 1708: ZASP-EVT-DSK-DATA-FILE-INUSE ASAPDSK Measure Data File In Use err err is the Measure error returned from the Measure subsystem. Cause. ASAPDSK could not create a Measure data file. Effect. ASAPDSK cannot obtain disk counters.
1710: ZASP-EVT-DSK-POOL-SPACE-ERROR 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. 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.
Cause. ASAPDSK could not start a measurement due to the MEASCTL process reaching its maximum resources. 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 ―1712‖.
ZASP-TKN-ASAP-ERRORNUM is ―1715‖. 1720: ZASP-EVT-DSK-STARTED ASAPDSK ZASPXXX started.(XXX is the configured ASAP ID) Cause. ASAPDSK successfully started a measurement. Effect. ASAPDSK is operating. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1720‖. 1721: ZASP-EVT-DSK-NOT-STARTED ASAPDSK ZASPXXX NOT started.(XXX is the configured ASAP ID) Cause. ASAPDSK could not start a measurement. Effect.
ZASP-TKN-ASAP-ERRORNUM is ―1722‖. 1723: ZASP-EVT-DSK-MEASCTL-RESTARTED ASAPDSK started MEASCTL IN CPU cpu cpu specifies the CPU number. Cause. The Disk Statistics Gathering process (SGP) started the Measctl process in a CPU that did not have the Measctl process running. Effect. ASAPDSK starts Measctl in the CPU. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1723‖.
Cause. ASAPDSK encountered an error while attempting to send a message to the ASAP Collector. Effect. ASAPDSK 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. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1735‖.
ZASP-TKN-ASAP-ERRORNUM is ―1742‖. 1742: ZASP-EVT-DSK-DCT-ACCESS-ERROR ASAPDSK DCT access error ldev ldev is the logical number of the device. Cause. The Disk Statistics Gathering process (SGP) could not access the device control table. Effect. ASAPDSK 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‖.
ldev is the logical number of the device. ctrl is the controller number in decimal notation. Cause. The Disk Statistics Gathering process (SGP) could not access the device. Effect. ASAPDSK could not collect disk counters. Disk device status information is still valid even when ASAPDSK cannot obtain the disk counters. Recovery. Contact your HP representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1744‖.
1747: ZASP-EVT-DSK-SHUTDWN-INCMPLETE ASAPDSK unable to stop Disk Measurement err err is the Measure error returned from the Measure subsystem. Cause. ASAPDSK could not stop its measurement. Effect. ASAPDSK could not stop the measurement named ZASPxxx, where xxx is the ASAP ID. Recovery. Stop and delete the measurement named ZASPxxx, where xxx is the ASAP ID. Use the Measure interface MEASCOM. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1747‖.
Recovery. Check the ASAP log for previous ASAPDSK messages and make the appropriate corrections. For corrective action for the specified error, see the Measure Reference Manual . If the problem persists, contact your HP representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1749‖. 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.
err is the error number returned from the SGP_ReadDomain_ procedure Cause. The ASAP sgp_readdomain_ procedure returned the specified error when trying to get the list of Disk domains to monitor. Effect. Disk monitoring of all devices will occur. Recovery. Make sure that ASAP is configured correctly. For more information about configuring domains, see the ASAP Extension Manual. If the configuration is correct, contact your HP support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text.
Ldev is the logical number of the Disk device that failed Cause. The ASAP sgp_Getobjectives procedure returned the specified error when trying to get the list of Disk threshold objectives. Effect. Disk monitors all configured disk devices. Recovery. Make sure that ASAP is configured correctly. For more information about Ranking Objectives, see the ASAP Server Manual. If the configuration is correct, contact your HP support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text.
error is the file-system error number. Cause. The zaspzoo measure file is open. Effect. The ASAP DISK SGP could not purge the zasp measure file. Recovery. The disk SGP will use the existing zasp measure file. Data Tokens. 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.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1766‖. 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‖.
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 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.
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 ―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.
2003: ZASP-EVT-RENAME-ERROR Can’t Rename 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 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.
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 . Make sure the security is correct. Ask Operations whether they have placed Safeguard on the disk. If so, ask them to remove it from the disk. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2004‖.
Cause. A message was received that was unrecognized because of its short length. Effect. The message is not processed. Recovery. Retry the request.
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 does not process the request. Recovery. Retry the request.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2009‖. 2010: ZASP-EVT-COL-STARTUP-ERROR Startup msg parse error: charoffset charoffset is the offset of the message that was not recognized. Cause. An invalid parameter was detected while ASAP was attempting to read its startup message. Effect. The system does not start. Recovery. Correct the startup message in your configuration file. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2010‖.
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 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.
Cause. The system opened the file with the name indicated in the message. Effect. The file was opened successfully. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2013‖. 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.
cpu is the CPU number. Cause. The system is informing you that the Collector started successfully. Effect. The Collector 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 ―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. 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 . 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2018‖.
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 ―2019‖. 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.
2024: ZASP-EVT-COL-PURGE-ERROR Cannot purge filename error filename is the name of old date base file marked for deletion due to SET DBMAXDAYS 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.
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. 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 create a new partition control file. The cause, indicated by error, 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2031‖.
Cause. The partition control file could not be opened when the Collector was started. The cause, indicated by error, is most likely a security violation on the partition control file or a sharing violation because another application has the control file open. Effect. The Collector cannot get any partitioning settings and creates the database using default settings. Recovery. Depends on error. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2033‖.
Effect. The Collector cannot get any partitioning settings and creates the database using default settings. Recovery. Depends on error. If an internal ASAP error occurred, contact your support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. 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.
Effect. The Collector logs the error and continues to run normally. Status information is not written to the control file, but Collector operations are not otherwise affected. Recovery. Depends on error. If an internal ASAP error occurred, contact your support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2037‖. 2038: ZASP-EVT-COL-PART-BAD-SUFFIX Unknown suffix entity-suffix entity-suffix is the suffix for an ASAP entity. Cause.
Effect. The Collector does not create a database for the specified entity. Recovery. Depends on error. Enter SET PARTITION to view partitioning settings. Correct any errors, then restart the Collector from the ASAP CI. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2039‖. 2040: ZASP-EVT-COL-PART-LIST-ERROR CreatePart filename file-error internal-error errorindicator filename database file that cannot be created. file-error file-system error number.
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. Correct any errors, then restart the Collector from the ASAP CI. Data Tokens.
file-error is the file-system error number. partition-index is the partition that cannot be opened. Cause. The Collector could not open the specified database file and partition while trying to create the database for a particular entity. The cause is most likely a security violation. 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.
Recovery. Make sure files are secured properly. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2051‖. 2052: ZASP-EVT-COL-DBAK-SET-FILE-COL DB^AltKeyFile^SET call fnamecollapse failed Cause. The Collector could not set alternate key file info for the DB. The cause is most likely a security violation. Effect. The Collector cannot set alternate key file info. Recovery. Make sure files are secured properly. Data Tokens. ZEMS-TKN-TEXT contains the message text.
Effect. The Collector cannot get alternate key file info. Recovery. Depends on err. Use FUP and do a INFO , DETAIL and double check whether the Alternate key file is valid. If not, then use FUP to correct the file. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2054‖. 2055: ZASP-EVT-COL-DBAK-PURGEDATAOPN PURGEDATA AK OPEN FE: err Cause. The Collector cannot do a Purgedata on . The cause is most likely an invalid database alternate key file.
2057: ZASP-EVT-COL-DBAK-RENAME-GETER DB^AltKeyFile^GET FILE FE: err Cause. The Collector cannot GET alternate key info for . The cause is most likely an invalid database alternate key file specification. Effect. The Collector cannot rename an alternate key file. Recovery. Depends on err. Use FUP to do an INFO , DETAIL and check whether the Alternate key file is valid. If not, then use FUP to correct the AK file specification. Data Tokens.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2059‖. 2060: ZASP-EVT-COL-DBAK-ALTER-ERRMSG ALTER file file error: err Cause. The Collector cannot ALTER alternate key for . The cause is most likely an invalid database alternate key file specification. Effect. The Collector cannot ALTER an alternate key file. Recovery. Depends on err. Use FUP to do an INFO , DETAIL and check whether the Alternate key file is valid.
3000: ZASP-EVT-NO-BACKUP-CREATED Unable to create backup: cpu, err 0:7, err 8:15 cpu is the CPU number. err indicates the outcome of the process creation attempt, where err.<0:7> is one of: 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. 5 File error on swap file; err.
= file-system error. 15 Invalid home terminal; err.<8:15> = filesystem error. 16 I/O error to home terminal; err.<8:15> = filesystem error. 17 DEFINE context propagation error; if: err.<8:15> = 0 Unable to convert a DEFINE name to network form. err.<8:15> = 1, flags.<10> = 1 AND flags.
3001: ZASP-EVT-BACKUP-CREATED 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. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―3001‖. 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.
Cause. The primary process could not send checkpoint information to its backup process. Effect. The backup process might not be able to take over if the primary process fails. Recovery. Decide whether you want to take the chance that the primary process will not fail, and continue to gather your statistics. For more information, see the Operator Messages Manual . Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―3002‖.
3005: ZASP-EVT-STARTUP-MSG-NOT-RCVD No startup msg received Cause. No startup message was received. Effect. Startup information was not displayed. Recovery. Correct the startup message information in your configuration file. 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.
attribute is the name of the relevant attribute. attval text that describes the attribute value. Cause. An attribute failed to meet an objective where the objective is defined for event generation. Effect. User specific. Recovery. User specific. 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-OBJECTNAME contains the physical object name, where known, else it contains the ASAP domain name. 4001: ZASP-EVT-STATE-UP-MSG ASAP INFO component entity domain attribute attval (OK) component is the name of the relevant ASAP component entity is the name of the relevant entity domain is the name of the relevant domain attribute is the name of the relevant attribute attval text that describes the attribute value Cause.
ZASP-TKN-ASAP-ATTRIBUTE-VALUE is present and contains the attribute value when the attribute type is INT. ZASP-TKN-ASAP-ATTRIBUTE-INT32 is present and contains the attribute value when the attribute type is INT32. ZASP-TKN-ASAP-ATTRIBUTE-INT64 is present and contains the attribute value when the attribute type is INT64. ZASP-TKN-ASAP-ATTRIBUTE-CHAR8 is present and contains the attribute value when the attribute type is CHAR.
ZASP-TKN-ASAP-ERRORNUM is ―4021‖. 4022: ZASP-EVT-OBJ-SEGALLOC-ERR ASAP ERR component Segment allocation error: err errordetail component is the name of the relevant ASAP component err is the error returned from SEGMENT_ALLOCATE_ error-detail is detailed information about the error returned from SEGMENT_ALLOCATE_ Cause. The ASAP component failed to obtain extended memory to load objectives. Effect. The objective records for the ASAP component are not loaded. Recovery.
Recovery. Correct the file-system error and restart ASAP. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4023‖. 4024: ZASP-EVT-ACTION-COMM-ERR ASAP ERR component - ACTION Server I/O Error, FE: error component is the name of the relevant ASAP component. 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.
4101: ZASP-EVT-RDF-FILE-FINDNEXT-ERR RDF FILENAME_FINDNEXT_ error: error error the file-system error returned from the call to FILENAME_FINDNEXT_. Cause. FILENAME_FINDNEXT_ returned an error while the SGP was auto-detecting the RDF environments. Effect. The SGP abends. Recovery. ASAP should restart the SGP automatically. If the problem persists, contact the GMCSC.
4105: ZASP-EVT-RDF-RES-PHANDLE-ERR RDF Could not resolve P-handle, FE: error error the file-system encountered by the RDF SGP while trying to get or decode its process handle. Cause. The SGP could not determine its own process handle. Effect. The SGP continues processing; however, some fields in RDF statistics records are invalid. Recovery. Create a saveabend file of the RDF SGP, then stop the SGP. Contact the GMCSC.
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. 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 ―4301‖.
Recovery. This is an internal error. Report this error to your HP support representative. Be ready to report the numtype and the situation where this happened. If this message keeps appearing, create a saveabend file of the Spooler SGP before stopping the Spooler SGP. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4303‖.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4305‖. 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.
Effect. The new objectives are not loaded and the old ones are used. A load will be tried again on the next sample. Recovery. Verify that the EDL and objectives database are correctly installed and configured. 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.
ZASP-TKN-ASAP-ERRORNUM is ―4309‖. 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.
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.
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. 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.
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‖.
Cause. An error occurred when trying to load the spooler domain names to monitor (see Error! Reference source not found. on page Error! Bookmark not defined.). This message indicates that the last list of domains will be used instead. Effect. The previous spooler configuration is reloaded, and the last list of domains is used. Recovery. Informational message; no corrective action is necessary. However, because this message appears after error Error! Reference source not found.
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‖. 4401: ZASP-EVT-TAP-EDLLOAD-ERR TAP ecb loadentities error-text error-text error message returned by the ecb_loadentities_ procedure Cause.
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. If the configuration is correct, contact your HP support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4402‖.
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. 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. 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‖. 4407: ZASP-EVT-TAP-MEDIASRVOPEN-ERR TAP open error on MEDIASRV. Error=error error error returned from the FILE_OPEN_ procedure call Cause.
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. Contact your system administrator. Data Tokens.
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. The Tape SGP sets the status for the domain to UNKNOWN. Recovery.
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‖.
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. If error and error-detail are provided, tape drives might be missing from the display. Recovery.
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. However, if this error recurs, contact your service provider and describe your requirements. Data Tokens. ZEMS-TKN-TEXT contains the message text.
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. 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‖. 4499: ZASP-EVT-EXP-SUPPRESSED-ERRORS ASAP ASAP Error #....
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. When trying to get the list of TMF domains to monitor, the ASAP sgp_readdomain_ procedure call returned the specified error. Effect.
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. 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.
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‖.
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. If the Transactions domain is not configured to be monitored, the TMF SGP should not be affected. Recovery. Use error-num and error-detail to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative. Data Tokens.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4530‖. 4531: ZASP-EVT-TMF-NOTLICENSED-ERR ASAPTMF TMFSERVE not licensed 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 because the process is not licensed. Effect.
Recovery. Use error-num and error-detail to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4532‖. 4533: ZASP-EVT-TMF-TMFSERVEOPEN-ERR ASAPTMF TMFSERVE open error error-num error-num error returned when trying to open the TMFSERVE process Cause. An error occurred when trying to open the TMFSERVE process. Effect. The TMFSERVE process does not open.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4534‖. 4535: ZASP-EVT-TMF-TMFSERVEAWIO-ERR ASAPTMF TMFSERVE startup awaitio 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.
4550: ZASP-EVT-TMF-SPI-INITBUF-ERR 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.
4552: ZASP-EVT-TMF-SPI-SNDBUF-FSERR ASAPTMF spi-cmd,FS Error Send= error-num spi-cmd SPI command on which the error occurred 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.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4553‖. 4554: ZASP-EVT-TMF-SPI-GETTKN-TMFERR ASAPTMF spi-cmd,TMF Error= error-num spi-cmd SPI command on which the error occurred error-num TMF error returned by the TMFSERVE process Cause. The TMFSERVE process returned a TMF error for the requested command. Effect. The associated TMF statistics are not obtained for this sampling. The error is reported against the appropriate domain. Recovery.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4555‖. 4556: ZASP-EVT-TMF-SPI-SAVESPI-ERR ASAPTMF spi-cmd,SPI Error SaveSPIBuf= error-num spi-cmd SPI command on which the error occurred error-num SPI error returned while saving the SPI buffer Cause. When saving the SPI buffer, a SPI error was returned. Effect. The SPI buffer is not interpreted, so the associated TMF statistics are not obtained for this sampling. The error is reported against the appropriate domain. Recovery.
ZASP-TKN-ASAP-ERRORNUM is ―4557‖. 4558: ZASP-EVT-TMF-SPI-EXITLIST-ERR ASAPTMF spi-cmd,SPI Error ExitList= 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. The error is reported against the appropriate domain. Recovery.
4592: ZASP-EVT-TMF-TMFSERVE-STOPPED 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4592‖. 4593: ZASP-EVT-TMF-TMFSERVE-STARTED TMF TMFSERVE started Cause.
4595: ZASP-EVT-TMF-STATS-COUNTS TMF Stats performance messages. Cause. This is a performance statistics message for internal HP use only. Effect. None. Recovery. Informational message; no corrective action is necessary. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4595‖. 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.
Effect. The TMF SGP configures all supported TMF domains by default. Recovery. To modify the list of domains to monitor, use the MONITOR command, then the COMMIT command. Autoconfigured domains are then automatically removed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4598‖. 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.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4601‖. 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.
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. Data Tokens. ZEMS-TKN-TEXT contains the message text.
Cause. The address_delimit_ procedure returned an error while the SGP was attempting to define pool space for dynamically resolved domains. Effect. The ASAP SGP could not allocate pool space to store domains that are dynamically resolved at each interval, such as domains specified using 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.
Data Tokens. 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.
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.
component is the name of the relevant ASAP component. server is the object name of the server process that cannot be started. error is the error returned from the process_launch_ procedure. error detail is the detailed (if any) error returned from the procedure. Cause. The SGP encountered an unknown error when starting its server process. Effect. ASAP might not be able to communicate correctly with its server process. Recovery. Correct the error and restart ASAP. Data Tokens.
4617: ZASP-EVT-PRO-FUNCSPI-ERR ASAP ERR component function-location SPI Error: error component is the name of the relevant ASAP component. function–location is the functional location within the SGP where the error occurred. error is the SPI error encountered. 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. Correct the SPI error or report the problem to HP support. Data Tokens.
ZASP-TKN-ASAP-ERRORNUM is ―4618‖. 4699: 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 ―4699‖. 4700: ZASP-EVT-CMM-KERNEL-NOT-D40 ASAPCMM NonStop Kernel Must be release D40 or Greater Cause. ASAPCMM cannot be started. Effect.
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4708". 4715: ZASP-EVT-CMM-SET-CPU-ERROR ASAPCMM Error SET COMM PARAM CPU cpu cpu is the CPU number. Cause. The Comm Statistics Gathering process (SGP) could not start a measurement in the specified CPU. Effect. ASAPCMM starts the measurement in the CPU that ASAPCMM is running in. Recovery. This message is informational only.
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. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4721". 4722: ZASP-EVT-CMM-MEAS-RESTARTED ASAPCMM restarted err err is the Measure error returned from the Measure subsystem. Cause. ASAPCMM restarted the measurement. Effect. ASAPCMM could not obtain communication line counters during a sample interval.
4725: ZASP-EVT-CMM-MEASURE-ERROR 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. ASAPCMM starts MEASCTL in the CPU. Comm line statistics are set to null for the sample interval when the error occurred. Recovery. Report this as a problem to HP support. Data Tokens. ZEMS-TKN-TEXT contains the message text.
ldev is the logical number of the device. Cause. The Comm Statistics Gathering process (SGP) could not access the device control table. Effect. ASAPCMM could not collect disk statistics. Recovery. Contact your HP representative to file an HP Product Case. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4742". 4743: ZASP-EVT-CMM-MEAS-NOT-RESTARTD ASAPCMM cannot restart measurement err err is the Measure error returned from the Measure subsystem. Cause.
Effect. ASAPCMM could not collect comm line counters. Comm line status information is still valid even when ASAPCMM cannot obtain the comm line counters. Recovery. Contact your HP representative to file an HP Product Case. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4744". 4747: ZASP-EVT-CMM-SHUTDWN-INCMPLETE ASAPCMM unable to stop Disk Measurement err err is the Measure error returned from the Measure subsystem. Cause. ASAPCMM could not stop its measurement. Effect.
param contains the parameter that caused the problem. Cause. ASAPCMM detected an invalid parameter in the SET COMM ON,PARAMETER command. Effect. ASAPCMM 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. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4750".
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 "4753". 4754: ZASP-EVT-CMM-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 Comm line 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 "4756". 4757: ZASP-EVT-CMM-RANKVALUES-ERROR ASAPECMM Rank Values error= err, error-detail err is the error number returned from the SGP_RankValues procedure.
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4766". 4799: ZASP-EVT-CMM-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 "4799".
4800: ZASP-EVT-SWP-SSG-INITLIZ-ERROR SSG Initialize Error = ssg.err, ssg.errdet, ssg.errsubdet Ssg.err is the SSG error returned from the Seeview Server Gateway. Ssg.errdet is the SSG error detail returned from the Seeview Server Gateway. Ssg.errsubdet is the SSG error subdetail returned from the Seeview Server Gateway Cause. SSG cannot be started. Effect. ASAPSWP is not reporting KMSF statistics. Recovery. Shut down the ASAP environment SET SWAP OFF restart ASAP.
Recovery. Shut down the ASAP environment SET SWAP OFF restart ASAP. Contact the GMCSC or HPVC depending on your geographical location and submit a case. Include the SSG.err, SSG.errdet, the SSG. Errsubdet and the SSG errortext from the accompaning 4802 messageif it exists. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4801". 4802: ZASP-EVT-SWP-SSG-ERRORP-TEXT SSG ErrorText errortext is the corresponding errot text from the SSG for error numbers 4800-4802,4804, 4809, 4810.
4804: ZASP-EVT-SWP-SSG-SHUTDOWN-ERR SSG Shutdown Error ssg.err ssg.errdet ssg.errsubdet Ssg.err is the SSG error returned from the Seeview Server Gateway. Ssg.errdet is the SSG error detail returned from the Seeview Server Gateway. Ssg.errsubdet is the SSG error subdetail returned from the Seeview Server Gateway Cause. ASAPSWP could not stop its SSG process. Effect. The SSG session remains running. Should the envionment be restarted using the same ASAP ID the ASAP Swap entity will use the same SSG.
4809: ZASP-EVT-SWP-SSG-SEND-PRIVATE SSG SendPrivate Error. ssg.err ssg.errdet ssg.errsubdet Ssg.err is the SSG error returned from the Seeview Server Gateway. Ssg.errdet is the SSG error detail returned from the Seeview Server Gateway. Ssg.errsubdet is the SSG error subdetail returned from the Seeview Server Gateway. Cause. An error occurred with the SSG interface. Effect. The Swap SGP writes records to the ASAP DB without the KMSF counters Recovery.
Recovery. Contact the GMCSC or HPVC depending on your geographical location and submit a case. Include the SSG.err, SSG.errdet, the SSG. Errsubdet and the SSG errortext from the accompaning 4802 messageif it exists. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4810". 4811: ZASP-EVT-SWP-MAX-UNKWN-DOMAINS Max unknown domains reached Cause. The ASAP Swap SGP exceeded its internal table limits. Too many phantom or incorrect domain names was configured by an ASAP user.
4814: ZASP-EVT-SWP-CANNOT-START-SSG ASAPSWP Cannot start SSG <$nssB> process name in use SSG id ssgid is the name of the SSG ID being used. Cause. The ID created is the ID of the ASAP environment with the appended letter B to the end of it. Default $ZOOB. The Swap SGP discovered that the process name is in use and is not a valid SSG process. Effect. The ASAP Swap SGP will not report on KMSF records. Recovery.
Cause. ASAPSWP encountered an error while attempting to send a message to the ASAP Collector. Effect. ASAPSWP cannot complete the request. 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4835".
4853: ZASP-EVT-SWP-READDOMAIN-ERROR ASAPSWP sgp_readdomain_ Error err err is the error number returned from the SGP_ReadDomain_ procedure. Cause. The ASAP sgp_readdomain_ procedure returned the specified error when trying to get the list of Swap domains to monitor. Effect. Swap monitoring of all Swap files will occur. Recovery. Make sure that ASAP is configured correctly. For more information about configuring domains, see the ASAP Extension Manual. If the configuration is correct.
4856: ZASP-EVT-SWP-GETOBJTIVES-ERROR ASAPSWP Sgp_getobjectives Error err err is the error number returned from the SGP_GETOBJECTIVES_ procedure. Cause. The ASAP sgp_Getobjectives procedure returned the specified error when trying to get the list of Swap objectives. Effect. The Swap SGP monitors all configured swap files. Recovery. Make sure ASAP is configured correctly. For more information about Ranking Objectives, see the ASAP Server Manual.
4865: ZASP-EVT-SWP-SET-SWAP-PARAMS Error SET SWAP PARAM param param is the invalid parameter. Cause. ASAPSWP detected an invalid parameter in the SET DISK ON, PARAMETER command. Effect. ASAPSWP 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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4865". 4899: ZASP-EVT-SWP-SUPPRESSED-ERRORS ASAP ASAP Error #....
Section 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.
1816 Cannot restart domain, Dmn# in use: domain, dmn# 1817 Stopped COMMIT, excessive errors: error^cnt 1818 Command invalid in config file: fname 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, 1899 ASAP ASAP Error occurred component, version, cpu time(s) num, xxxx Error and Critical Information Messages (1801-1859) 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.
ZASP-TKN-ASAPX-ERROR contains the file-system error number. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 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.
error^detail is the detailed error number, if any, returned by the segment_allocate_ procedure. Cause. An error occurred attempting to allocate an extended memory segment. To determine the cause of this problem, see 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 1804. 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.
domain is the name of the domain that cannot be restarted. domain number is the number of the domain that is already restarted. Cause. ASAPX detected duplicate Domain table entries for the same memory slot location. Only the first domain is restarted; all others 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.
1. Make sure all application processes are running and all their domains are registered, or shut down all application processes using ASAPX. If an application process is left executing, one must be executing in each processor with at least one registered domain. To verify this, use the FILEINFO command against the ASAPX swap subvolume or subvolumes. Verify that all shared memory segment files are open.
Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1808. 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 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.
domain is the name of the domain that was rebuilt. domain number is the number of the domain that was rebuilt. Cause. The Domain table was corrupted. 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. ZASP-TKN-ASAPX-FNAME contains the name of the process. ZASP-TKN-ASAPX-ERROR contains the file-system error number. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 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.
Cause. An ASAPX process received an illegal request on $RECEIVE. Another process inadvertently wrote to an ASAPX process. Effect. None. ASAPX ignores the illegal request and continues processing. Recovery. Make sure you have the correct version of all ASAPX object modules. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1814. 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.
1816: ZASP-EVT-API-SLOT-INUSE Cannot restart domain, Dmn in use: domain, Dmn#: domain number domain is the name of the domain that cannot be restarted. domain number is the number of the domain that is already is use. Cause. ASAPX cannot restart domain domain because its slot is already in use by another domain.
Recovery. Correct any file-system errors and retry the operation. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1817. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-ERROR contains the current number of errors found. 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.
Cause. (ASAP Release 1 only) An error was detected in the ASAPX configuration file. The dataitem definitions in fname are not contiguous. Effect. ASAPXGP stops because of the inconsistent configuration. ASAPX is not started. Recovery. Redefine the dataitems in fname to use a contiguous sequence of numbers starting with zero. 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.
1821: ZASP-EVT-API-METRIC-CONT METRIC definitions not contiguous: fname fname is the name of the configuration file containing the metric definitions that are not contiguous. Cause. (ASAP Release 1 only) 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.
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. 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.
ZASP-TKN-ASAP-ERRORNUM is 1824. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-FNAME contains the name of the ASAPXMON process. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 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.
Recovery. Install a TNS/R processor and the D30.02 or later NonStop Kernel operating system or later. Tokens in the Event Buffer. ZASP-TKN-ASAP-ERRORNUM is 1826. 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.
pname is the name of the process for which ASAPX could not obtain the NonStop Kernel MOM identifier. fe is the file-system error number. 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.
ZASP-TKN-ASAP-ERRORNUM is 1829. ZASP-TKN-ASAPX-COMPONENT is the name of the ASAPX component that reported the event. ZASP-TKN-ASAPX-FNAME contains the name of the ASAPXMON process. ZASP-TKN-ASAPX-ERROR contains the file-system error number. 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.
slot is the number of the domain that might be corrupted. Cause. ASAPX could not rebuild domain domain, where memory or the Domain table is corrupted. Something prevented ASAPX from restoring a domain, possibly an error occurred allocating shared memory or accessing the Domain table. 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.
component is the ASAP component affected by the EDL error ename is the name of the entity as defined in EDL aname is the name of the attribute as defined in EDL Cause. There is a formula definition error in a user-defined EDL file. Effect. ASAPX produces a zero value for the calculation. Recovery. Correct the MetricRule formula error, then restart ASAPX. Data Tokens. ZEMS-TKN-TEXT contains the message text given above. ZASP-TKN-ASAP-ERRORNUM is ―1833‖.
ZEMS-TKN-TEXT contains the message text given above. ZASP-TKN-ASAP-ERRORNUM is ―1834‖. ZASP-TKN-ASAP-COMPONENT contains the name of the ASAP component reporting the error. ZASP-TKN-ASAP-FNAME contains the name of the file in error. 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.
Cause. ASAPX found non-SET commands in the ASAPXCNF file. Effect. None. ASAPX ignores the command. Recovery. ASAPX ignores all non-SET commands in the ASAPXCNF file. To eliminate this warning message, remove the non-SET commands from the file. 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.
Cause. (ASAP Release 1 only) ASAPX did not find a SET NAMEFILE command in the ASAPXCNF file. This could result in reserved names being entered as domain names and 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. ASAPX warns about this problem and then continues processing normally. To eliminate this warning message, add a SET NAMEFILE $ISV Volume.ZASAPX.
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.
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. ZASP-TKN-ASAPX-FNAME contains the name of the process that requested the shutdown. ZEMS-TKN-TEXT contains an abbreviated version of the error text. 1881: ZASP-EVT-API-STARTUP-MSG component INFO version started, cpu component is the ASAPX component that started. version is the version of ASAPX.
num is the number the recurring error xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. Data Tokens. ZEMS-TKN-TEXT contains the message text given above. ZASP-TKN-ASAP-ERRORNUM is ―1899‖.
List of Messages 1000 .................................................................................................................................. 34 1001 .................................................................................................................................. 34 1002 .................................................................................................................................. 34 1003 .........................................................................
1096 .................................................................................................................................. 49 1097 .................................................................................................................................. 50 1099 .................................................................................................................................. 50 1100 ..........................................................................................
1400 .................................................................................................................................. 68 1401 .................................................................................................................................. 69 1499 .................................................................................................................................. 70 1503 ..........................................................................................
1759 .................................................................................................................................. 83 1766 .................................................................................................................................. 83 1799 .................................................................................................................................. 84 1801 ..........................................................................................
2001 .................................................................................................................................. 97 2002 .................................................................................................................................. 97 2003 .................................................................................................................................. 98 2004 ..........................................................................................
2058 ................................................................................................................................ 113 2059 ................................................................................................................................ 113 2060 ................................................................................................................................ 113 Recovery. Depends on err.
4396 ................................................................................................................................ 129 4397 ................................................................................................................................ 130 4398 ................................................................................................................................ 130 4399 .............................................................................................
4554 ................................................................................................................................ 146 4555 ................................................................................................................................ 146 4556 ................................................................................................................................ 147 4557 .............................................................................................
4751 ................................................................................................................................ 160 4753 ................................................................................................................................ 160 4754 ................................................................................................................................ 161 4756 .............................................................................................
1018: ZASP-EVT-VERSION-ERROR ............................................................................. 197 1019: ZASP-EVT-SGP-SHUTDOWN-ERROR ............................................................... 198 1020: ZASP-EVT-MON-SHUTDOWN-COMPLETE ........................................................ 199 1021: ZASP-EVT-MON-TRACE ...................................................................................... 199 1022: ZASP-EVT-MON-STARTED ..........................................................
1240: ZASP-EVT-MON-EXPDMGR-IP-STATS............................................................... 223 1241: ZASP-EVT-EXP-COLLECT-ERROR .................................................................... 224 1242: ZASP-EVT-EXP-SHORT-RQST-RCVD ................................................................ 224 1243: ZASP-EVT-EXP-ILLEGAL-RQST-RCVD .............................................................. 225 1244: ZASP-EVT-EXP-NAM-CNTRS-UNAVAIL ..........................................................
1711: ZASP-EVT-DSK-MEMORY-ERROR ..................................................................... 247 1712: ZASP-EVT-DSK-RESOURCES-ERROR .............................................................. 247 1713: ZASP-EVT-DSK-ALLOCATION-ERROR .............................................................. 248 1715: ZASP-EVT-SET-CPU-ERROR.............................................................................. 248 1720: ZASP-EVT-DSK-STARTED ...............................................................
2016: ZASP-EVT-COL-STARTED .................................................................................. 268 2017: ZASP-EVT-ENFSERV-STARTED......................................................................... 269 2018: ZASP-EVT-COL-RCV-READ-ERROR .................................................................. 269 2019: ZASP-EVT-COL-RCV-REPLY-ERROR ................................................................ 270 2020: ZASP_EVT_COL_RENAME_TABLE_FUll.............................................
4023: ZASP-EVT-OBJ-FILESYS-ERR ............................................................................ 293 4024: ZASP-EVT-ACTION-COMM-ERR......................................................................... 294 4099: ZASP-EVT-EXP-SUPPRESSED-ERRORS .......................................................... 294 4101: ZASP-EVT-RDF-FILE-FINDNEXT-ERR ............................................................... 295 4102: ZASP-EVT-RDF-FILE-FINDSTRT-ERR ..................................................
4415: ZASP-EVT-TAP-NOTAPEFOUND-ERR ............................................................... 313 4416: ZASP-EVT-TAP-LOADOBJS-ERR ....................................................................... 314 4493: ZASP-EVT-TAP-LASTDOMOVR-INF ................................................................... 314 4494: ZASP-EVT-TAP-EDLLOADED-INF....................................................................... 315 4495: ZASP-EVT-TAP-SAMPLESTATS-INF ....................................................
4604: ZASP-EVT-PRO-OBJLOAD-ERR ......................................................................... 333 4605: ZASP-EVT-PRO-MAXDOMAIN-ERR .................................................................... 334 4606: ZASP-EVT-PRO-POOLMAXSIZE-ERR ................................................................ 334 4607: ZASP-EVT-PRO-POOLINTERNAL-ERR .............................................................. 335 4608: ZASP-EVT-PRO-POOLINTERNAL-ERR ......................................................
4812: ZASP-EVT-SWP-MAX-MNTRD-DOMAINS .......................................................... 355 4814: ZASP-EVT-SWP-CANNOT-START-SSG ............................................................. 356 4815: ZASP-EVT-SWP-NO-FILE .................................................................................... 356 4835: ZASP-EVT-SWP-COLLECT-SEND-ERR .............................................................. 356 4851: ZASP-EVT-SWP-ECB-LOAD-ERROR..........................................................
1860: ZASP-EVT-API-NON-SET-COMMAND ................................................................ 384 1861: ZASP-EVT-API-FILERESET-MSG........................................................................ 385 1862: ZASP-EVT-API-NONAMEFILE-MSG .................................................................... 385 1863: ZASP-EVT-API-NAMEFILEEDIT-MSG ................................................................. 386 1864: ZASP-EVT-API-NAMEFILEFE-MSG ....................................................
