ASAP 3.2 Messages Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

HP NonStop Messages Manual Page 1 of 414

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.2

Supported Release Version Updates (RVUs)

This manual supports D43.00 and subsequent D-series RVUs, G06.00 and

subsequent G-series RVUs, and H06.03 and subsequent H-series RVUs until

otherwise indicated by its replacement publication.

Part Number

Published

429917-006

March 2010

Summary of content (414 pages)

PAGE 1
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.2 Supported Release Version Updates (RVUs) This manual supports D43.00 and subsequent D-series RVUs, G06.
PAGE 2
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.0 April 2008 429917-006 ASAP Server Release 3.
PAGE 3
Table of Contents HP NonStop ASAP Messages Manual ................................................................................ 1 Abstract ........................................................................................................................... 1 Product Version ............................................................................................................... 1 Supported Release Version Updates (RVUs) ..................................................................
PAGE 4
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.
PAGE 5
What’s New in This Manual New and Changed Information The ASAP 3.2 version of this manual contains these changes:  Added these EMS events: o 1061:ZASP-EVT-ACTION-NOT-SUPER o 1062:ZASP-EVT-CONTROL-FILE-ERR o 1780:ZASP-EVT-DSK-GMS-ATTRIBUTES o 4002:ZASP-EVT-BOOLEAN-GOAL-FAILED o 4772:ZASP-EVT-CMM-GET-COUNTERS o 4775:ZASP-EVT-CMM-GET-CONFIG-ATTR  Updated Spooler SGP events 4315 and 4316. Previous Changes The ASAP 3.0 version of this manual contains these changes:  Removed references to Query events.
PAGE 6
o 2058: ZASP-EVT-COL-DBAK-RENAME-OPEN o 2059: ZASP-EVT-COL-DBAK-RENAME-ERROR o 2060: ZASP-EVT-COL-DBAK-ALTER-ERRMSG o 4800: ZASP-EVT-SWP-SSG-INITLIZ-ERROR o 4801: ZASP-EVT-SWP-SSG-STARTUP-ERROR o 4802: ZASP-EVT-SWP-SSG-ERRORP-TEXT o 4803: ZASP-EVT-SWP-SWPFILES-EXCEED19 o 4804: ZASP-EVT-SWP-SSG-SHUTDOWN-ERR o 4807: ZASP-EVT-SWP-PARSE-SSG-REPLY o 4809: ZASP-EVT-SWP-SSG-SEND-PRIVATE o 4810: ZASP-EVT-SWP-SSG-SWAP-BUF-FULL o 4811: ZASP-EVT-SWP-MAX-UNKWN-DOMAINS o 4812: ZASP-EVT-SWP-MAX-MNTRD-DOMAINS o 4814: ZASP
PAGE 7
 Removed events 4201 through 4299 from Section 1: ASAP and ASAP Extension Error Messages  Updated the description of the sgpid parameter for events 4601, 4602, 4604, and 4605 The second edition of the manual contains these changes to support ASAP Release 2.
PAGE 8
o 4722 o 4723 o 4747 o 4748 o 4750 o 4751 o 4753 o 4754 o 4756 o 4757 o 4766 o 4772 ASAPCMM Get Counters: err err is the error number returned by Measure. Cause. The ASAP Comm SGP could not access the device due to the error returned by Measure. Effect. The statistics are set to zero for the interval. Recovery. If the error persists contact your HP support representative or attempt to stop and restart the Measure subsystem.
PAGE 9
Recovery. If the error persists contact your HP support representative or attempt to stop and restart the Measure subsystem.
PAGE 10
 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
PAGE 11
o ASAPCMM Get Counters: err err is the error number returned by Measure. Cause. The ASAP Comm SGP could not access the device due to the error returned by Measure. Effect. The statistics are set to zero for the interval. Recovery. If the error persists contact your HP support representative or attempt to stop and restart the Measure subsystem. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4772.
PAGE 12
the ASAP Server Manual and ASAP Extension Manual.
PAGE 13
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.
PAGE 14
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.
PAGE 15
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.
PAGE 16
!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).
PAGE 17
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.
PAGE 18
% 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.
PAGE 19
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 33 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.
PAGE 20
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.
PAGE 21
1100 GETPEEKCONF length bad length 1101 GETPEEKSTATS length bad length 1199 Error # ....occurred xxxx times 1200 Can’t find NetLH = netlh^conf ldev, paths 1210 NewProcess $System.System.Ozexp Error 0:7,8:15: err.0:7, err.
PAGE 22
ldev 1266 ASAPEXP Bad Stats Received 1299 Error # ....occurred xxxx times 1300 GetPeekPCBs Returns zero length err, ldev 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 .
PAGE 23
Table 1-2.
PAGE 24
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
PAGE 25
1809 Registered process active: , Pin: pnmame, pin 1810 Domain rebuilt from memory: , Dmn#: domain, domain 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, numb
PAGE 26
Table 1-4.
PAGE 27
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
PAGE 28
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.
PAGE 29
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.
PAGE 30
4398 SPL Autoconfiguration completed. 4399 Error # ....occurred xxxx times num, x Table 1-9. TAPE Messages Message Number Tape Messages Parameters 4401 TAP ecb loadentities error-text 4402 TAP sgp readdomain_ Error= FE: error 4404 TAP SSINIT Error: TAP SSGET error: TAP SSGETTKN Get error: TAP SSPUT error: TAP SSPUTTKN error: TAP SPI Last Error: TAP SPI Return Error: TAP SPI Dlist RetCode error: TAP SSNULL error: cmd-token, cmd, token, error 4405 TAP could not start .
PAGE 31
4496 TAP Reloading previous configuration. 4497 TAP Could not load all domains: maximum of num reached. 4498 TAP Autoconfiguration completed. 4499 Error # ....occurred xxxx times num, x Table 1-10.
PAGE 32
4554 ASAPTMF spi-cmd, TMF Error= error 4555 ASAPTMF spi-cmd, SPI Error Map= error 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
PAGE 33
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.
PAGE 34
4756 GetObjectives Error: Err 4766 Bad Stats Received err, Ldev 4772 ASAPCMM Get Counters err 4775 Config Attribute sub, track, cpu, ctrl, type 4799 Error #.... occured xxxx times Table 1-13.
PAGE 35
4899 Error #.... occurred xxxx times xxxx 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.
PAGE 36
1002 Send to SGP pid error: err, type, read^L err is the file-system error number associated with the last operation on the file. type is the request type. read^L is the sum of the length of the SGP structure, in bytes. Cause. The Statistics Gathering process (SGP) is not receiving startup, shutdown, status, or other requests. This error could occur because of a version mismatch between the Monitor and Collect processes.
PAGE 37
1004 Bad SGP stat^sum reply: type, words type is the current statistics type. words is the current statistics words. Cause. The reply from the Statistics Gathering process (SGP) was not valid. Effect. Statistics could not be collected. Recovery. If the problem persists, contact your HP representative. 1005 Sync, COLLECT I/O error: err err is the file-system error number associated with the last operation on the file. Cause. Synchronization between the Server and Collector was not accomplished. Effect.
PAGE 38
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.
PAGE 39
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.
PAGE 40
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.
PAGE 41
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.
PAGE 42
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
PAGE 43
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.
PAGE 44
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.
PAGE 45
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.
PAGE 46
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.
PAGE 47
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.
PAGE 48
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.
PAGE 49
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.
PAGE 50
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.
PAGE 51
1095 license error license error is error text returned from the license validation procedure Cause. An error occurred while trying to validate the software license Effect. The ASAP component will not execute. Recovery. Correct the problem described in license error. 1096 Softare License Expires in xx Days xx is the number of days before the software license will expire. Cause. The software license for the ASAP component is about to expire. Effect. There is no effect until the expiration date. Recovery.
PAGE 52
1100 GETPEEKCONF length bad: length length is the length in bytes returned from the get^peek^statistics system call. Cause. The Monitor could not retrieve CPU configuration information. Effect. A zero value was returned instead of a CPU configuration value. Recovery. Check that your NonStop operating system version and ASAP version are compatible. If the problem persists, contact your HP representative.
PAGE 53
paths is the index to the internal network configuration table. Cause. The Expand SGP could not find the path for this network line-handler device in the network line-handler configuration file. Effect. No statistics were returned for the network line handler. Recovery. Check that the Expand Manager to is present, up, and running. If the problem persists, contact your HP representative. 1210 NewProcess $System.System.
PAGE 54
14 Extended segment swap file error; error 8:15 = file-system error number 15 Invalid home terminal; error 8:15 = file-system error number 16 I/O error to home terminal; error 8:15 = file-system error number 17 DEFINE context propagation error; if: error 8:15 = 0 Cannot convert a DEFINE name to network form.
PAGE 55
Effect. ASAP and the subsystem cannot communicate. Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see the Operator Messages Manual or the Guardian Procedure Errors and Messages Manual . Check that the NonStop Kernel Subsystem Manager is present, up, and running. If the problem persists, contact your HP representative.
PAGE 56
err is one of these SPI error numbers: 0 Indicates there is no error -1 Indicates an invalid buffer format -2 Indicates an invalid parameter value -3 Indicates a missing parameter -4 Indicates an invalid parameter address -5 Indicates the buffer is full -6 Indicates an invalid checksum -7 Indicates an internal error -8 Indicates the list token was not found -9 Indicates an invalid token code or map -10 Indicates an invalid subsystem ID -11 Indicates the operation is not supported -12
PAGE 57
1233 Monitor -> ExpMgr ($ZEXP) SPI Error: err err is one of these SPI error numbers: 0 Indicates there is no error -1 Indicates an invalid buffer format -2 Indicates an invalid parameter value -3 Indicates a missing parameter -4 Indicates an invalid parameter address -5 Indicates the buffer is full -6 Indicates an invalid checksum -7 Indicates an internal error -8 Indicates the list token was not found -9 Indicates an invalid token code or map -10 Indicates an invalid subsystem ID -11
PAGE 58
ldev is the logical device number of the Expand path. Cause. The Expand SGP could not obtain Level 4 statistics for a multiline Expand configuration. Effect. ASAP does not obtain path statistics from the Expand manager. Recovery. This error message is used by HP for problem isolation. Contact your HP representative. 1236 Expand SGP -> Can’t obtain Path statistics Error: ldev err, err is the SPI error number returned by the $ZEXP process. ldev is the logical device number of the Expand path. Cause.
PAGE 59
1238 Expand SGP -> Can’t obtain CSM line stats Error: err, ldev err is the SPI error number returned by the $ZEXP process. ldev is the logical device number of the Expand path. Cause. The Expand SGP could not obtain 6100 line statistics. Effect. ASAP does not obtain CSM statistics from the Expand manager. Recovery. HP uses this error message for problem isolation. Contact your HP representative.
PAGE 60
Effect. ASAP does not obtain Expand IP statistics from the Expand manager. Recovery. HP uses this error message for problem isolation. Contact your HP representative. 1241 ASAPEXP -> COLLECT send error: err err is the returned file-system error number associated with the last operation on the file. Cause. 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.
PAGE 61
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.
PAGE 62
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.
PAGE 63
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.
PAGE 64
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.
PAGE 65
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.
PAGE 66
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.
PAGE 67
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 .
PAGE 68
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.
PAGE 69
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.
PAGE 70
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.
PAGE 71
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.
PAGE 72
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.
PAGE 73
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.
PAGE 74
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.
PAGE 75
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.
PAGE 76
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.
PAGE 77
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.
PAGE 78
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.
PAGE 79
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.
PAGE 80
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.
PAGE 81
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.
PAGE 82
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.
PAGE 83
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.
PAGE 84
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.
PAGE 85
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.
PAGE 86
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.
PAGE 87
xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. 1801 File open error: fname, FE: fe Cause. An error fe occurred opening the specified file fname. To determine the cause of this problem, see a description of file-system error numbers. Effect. The specified file is not opened. If the event is written by ASAPXSGP, it has failed to open and load the ASAPX configuration file (ASAPXCNF).
PAGE 88
1804 File read error: fname, FE: fe Cause. An error occurred while reading from the file fname. To determine the cause of this problem fe, see a description of file-system error numbers. Effect. The specified file is not read. If the event is written by ASAPXSGP, it has failed to read the ASAPX configuration file (ASAPXCNF). ASAPXSGP will stop. If the event is written by ASAPXMON, it has failed to read the domain table, the objectives table, $RECEIVE, or an extended memory segment file.
PAGE 89
Effect. While attempting to reload domains at startup, ASAPX found an error in the name of a domain. The domain is not restarted. Recovery. Manually remove the domain in question. If more than one domain has been corrupted: 1. Make sure that all of the application processes are running and that all of 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.
PAGE 90
1810 Domain rebuilt from memory: domain, Dmn#: domain number Cause. The Domain table was corrupted, possibly by entering the ASAPX CLEANUP DOMAINS command while application processes continued to execute. ASAPX successfully rebuilt a Domain table entry for a domain. This indicates possible corruption of the Domain table. Effect. ASAPX has successfully rebuilt a Domain table entry for a domain. The record for the domain is now correct. Recovery. No action is required. ASAPX successfully rebuilt the domain.
PAGE 91
1815 Registration rejected, max domains: domain, Max: max Cause. Domain domain could not be registered because the maximum max number of domains are already registered in the processor. Effect. ASAPX cannot register the domain in the processor in which it is attempting to register. Recovery. Redistribute domains into other processors or increase the maximum number of domains by using a SET MAXDOMAINS command in the ASAPXCNF file. 1816 Cannot restart domain, Dmn in use: domain, Dmn#: domain number Cause.
PAGE 92
Recovery. Run ASAPX against the configuration file to determine the invalid command, correct the command; then restart ASAPX. 1819 DATAITEM not contiguous: fname Cause. (ASAP Release 1 only) ASAPX detected that the DATAITEM definitions in fname are not contiguous. There is an error in the ASAPX configuration file. Effect. ASAPXSGP stops because of the inconsistent configuration. ASAPX is not started. Recovery. Redefine the DATAITEMS in fname to use a contiguous sequence of numbers starting with zero.
PAGE 93
Recovery. Add at least one SET METRICS command to define at least one METRIC to the ASAPX configuration file. 1823 Detected that its server stopped: pname Cause. ASAPX detected that one of its ASAPXMON server’s pname stopped. Someone stopped the process. Effect. None, unless this problem recurs. If it does, a problem might exist in the ASAPX Monitor (ASAPXMON). Recovery. None. ASAPX automatically restarts the process. 1824 Detected that its server abended: pname Cause. An APPXMON process pname abended.
PAGE 94
1827 File create error: fname, FE: fe Cause. An error occurred creating file fname. To determine the cause of this problem, see a description of file-system error numbers fe. Effect. ASAPXSGP stops without starting ASAPX since it could not create either the Domain or Objectives table. Recovery. Correct the file-system error and retry the operation. 1828 Error obtaining NSK MOM: pname, FE: fe Cause. ASAPX could not get the NonStop Kernel MOM identifier pname for one of its servers.
PAGE 95
1831 Domain rebuild failed: domain, Dmn#: slot Cause. ASAPX failed to rebuild 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.
PAGE 96
1834 ASAP ERR component, Unsupported Type: fname component is the ASAP component affected by the EDL error fname is the name of the file in error Cause. The ASAPX SGP received an unsupported record type from one of the ASAPXMON processes. There is a corrupted reply buffer or a version mismatch between ASAPXSGP and ASAPXMON. Effect. ASAPX might not report data for all domains. Recovery. Make sure ASAPXSGP and ASAPXMON are the same version. Watch the problem for at least three intervals to see if it persists.
PAGE 97
Recovery. ASAPX ignores all non-SET commands in the ASAPXCNF file. To eliminate this warning message, remove the non-SET commands from the file. 1861 Resetting file security: fname Cause. ASAPX found that the security on a segment file fname was incorrect. This message is a warning that the ASAPXMON is going to stop. Restart it to properly reset the file’s security. Effect. ASAPXMON will stop and restart to secure the segment file properly. Recovery. ASAPX automatically corrects the security problem.
PAGE 98
1864 File error on NAMEFILE: fname, FE: error Cause. (ASAP Release 1 only) ASAPX encountered a file error attempting to open the ASAP reserved names file fname. This could result in reserved names being entered as domain names and could yield unexpected results in ASAP, OEM, and OIL. Effect. ASAPX is not affected; however, using reserved names as domain names can cause a myriad of problems in ASAP, OEM, and OIL. Recovery. ASAPX warns about this problem and continues processing normally.
PAGE 99
Effect. The error number suppressed had occurred xxxx times. Recovery. None. 2000 DB^write filename, fe: err, sysno, cpuno err is the error returned from the FILEINFO system call, and is associated with the last operation on the file sysno is the system number cpu is the CPU number Cause. The Collector received statistical information from the Monitor, but cannot perform all database record file I/O. Possibly the database is not secured properly, is not present, or is full. Effect.
PAGE 100
Recovery. If the problem persists, contact your HP representative. 2002 Rollover Open filename, fe: err err is the file-system error number associated with the last operation on the file Cause. The Collector is trying to rename and release new database files, but it cannot read records from the database. Effect. Files are being renamed ZmmddL, where mmdd represents month and day, and L represents the last three letters of the original file. Recovery. The FILEINFO system call returned this error.
PAGE 101
Cause. The system is not performing a needed database cleanup operation. Effect. The purgedata operation is not being executed. The statistics are not being refreshed. Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see the Operator Messages Manual, or the Guardian Procedure Errors and Messages Manual . Make sure the security is correct. Ask Operations if they have placed a Safeguard on the disk. If so, ask them to remove the Safeguard.
PAGE 102
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. 2008 Illegal request received: count, buf, pid count is the length of the message, in bytes buf is the first word of the received request message pid is the requester’s process ID Cause. An invalid request was received. Effect. The system did not process the request. Recovery. Retry the request.
PAGE 103
Cause. An invalid parameter was detected while ASAP was attempting to read its startup message. Effect. The system did not start up. Recovery. Correct the startup message in your configuration file. 2011 Startup Can’t Open TERM Cause. The startup parameters did not open the terminal logfile. Effect. The terminal logfile did not open at startup. Recovery. Correct the terminal file name in your configuration file.
PAGE 104
type is an internal index to the ASAP database with these values: 0 DBSYS 1 DBCPU 2 DBNET 3 DBPCB 5 DBNODE 6 DBAPP 7 DBDSK Cause. The system opened the filename indicated in the message. Effect. The file was opened successfully. Recovery. 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.
PAGE 105
version is the base release version of the ASAP environment Cause. The system is informing you that the Collector started successfully. Effect. The Collector is operating. Recovery. This message is informational only. No corrective action is required. 2017 ENFSERV version started: cpu cpu is the CPU number version is the base release version of the ASAP environment Cause. The system is informing you that the Enform server started successfully. Effect. The Enform server is operating. Recovery.
PAGE 106
err is the file-system error number associated with the last operation on the file count is the length of the message, in bytes buf is the first word of the received request message pid is the requester’s process ID Cause. The system could not reply to a message it received from a READUPDATE(X) call on the $RECEIVE file. Effect. The system did not reply to the message. Recovery. The FILEINFO system call returned this error.
PAGE 107
Cause. Daylight Savings Time fall back has occurred. This message indicates that ASAP is aware that the DST time has changed. Effect. None. Recovery. This is an informative message. No recovery is needed. 2024 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.
PAGE 108
Effect. The ASAP data files are being maintained based on the DBMAX configuration settings. Recovery. This is an informative message. No recovery is needed. 2030 PCtl Purge filename error filename is the name of the control file error is the file-system error number Cause. The Collector could not remove an existing partition control file. The cause is most likely a security violation on the partition control file. Effect. The new partition control file is not created.
PAGE 109
error file-system error number Cause. The partition control file did not exist when the Collector was started. The cause is most likely a down target disk volume or a prior error that prevented the creation of the control file. Effect. The Collector cannot get any partitioning settings and creates the database using default settings. Recovery. Depends on error. 2033 PCtl Open filename error filename name of the control file error file-system error number Cause.
PAGE 110
2035 Collector could not read partition ctl file error error file-system error number. If greater than 0, indicates the encountered file-system error. If less than 0, indicates an internal ASAP error. Cause. The Collector could not 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.
PAGE 111
Effect. The Collector logs the error and continues to run normally. Status information is not written to the control file, but this does not otherwise affect Collector operations. Recovery. Depends on error. If an internal ASAP error occurred, contact your support representative. 2038 Unknown suffix entity-suffix entity-suffix suffix for an ASAP entity. Cause. The Collector encountered an unknown ASAP database entity suffix.
PAGE 112
filename database file that cannot be created. file-error file-system error number. internal-error offset of the internal ASAP structure responsible for the error. error-indicator contents of the internal error. Cause. The Collector could not create the specified database file. 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.
PAGE 113
Cause. Format2 support is ON, and MaxExtents values were specified for one or more secondary partitions. The Collector cannot set MaxExtents values for secondary partitions with Format2 support enabled. Effect. MaxExtents values defined for secondary partitions are ignored. The MaxExtents value for the base partition of the entity is used for the secondary partitions. Recovery. Either disable Format2 support or do not specify MaxExtents values for secondary partitions.
PAGE 114
Cause. The Collector could not get alternate key file info for the DB. The cause is most likely a security violation. Effect. The Collector cannot get alternate key file info. 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.
PAGE 115
2056 PURGE AK FE: err 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.
PAGE 116
2060 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. If not, then use FUP to correct the AK file specification. 2099 ASAP ASAP Error #....
PAGE 117
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 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 init
PAGE 118
Effect. The backup process was not created. Recovery. Make sure the checkpoint information is correct. Check that the CPU is up and running. If the CPU is down, follow the recommended recovery procedure for a CPU failure. 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.
PAGE 119
Cause. The primary process could not send checkpoint information to its backup process. Effect. The backup process might not be able to take over if the primary process fails. Recovery. Decide if you want to take the chance 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.
PAGE 120
xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. 4000 ASAP INFO | ALERT component entity domain attribute attval component is the name of the relevant ASAP component entity is the name of the relevant entity domain is the name of the relevant domain attribute is the name of the relevant attribute attval text that describes the attribute value Cause.
PAGE 121
domain is the name of the relevant domain attribute is the name of the relevant attribute attval text that describes the attribute value Cause. An attribute is meeting its objectives after previously failing to meet them. Effect. User-specific. Recovery. User-specific.
PAGE 122
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. The current EDL does not match the EDL for an objective record. Effect. The objective record is not loaded into the ASAP component. Recovery. Use RANK/OUT x/entity *,OBEYFORM to output the entity’s objectives, then delete the objectives using RANK entity *, DELETE. Then reload the entity definitions using the current EDL by OBEYing x.
PAGE 123
filename is the name of the objectives file error is the file-system error Cause. The ASAP component got a file-system error while attempting to access the objectives file. Effect. The objective records for the ASAP component are not loaded. Recovery. Correct the file-system error and restart ASAP. 4024 Action Server I/O Error, FE: error Cause. An ASAP SGP failed to communicate with the Action server due to file error error. Effect. An ASAP recovery action failed to execute for this interval.
PAGE 124
Recovery. ASAP should restart the SGP automatically. If the problem persists, contact the GMCSC. 4102 RDF FILENAME_FINDSTART_ error: error error the file-system error returned from the call to FILENAME_FINDSTART_. Cause. FILENAME_FINDSTART_ returned an error while the SGP was autodetecting the RDF environments. Effect. The SGP abends. Recovery. ASAP should restart the SGP automatically. If the problem persists, contact the GMCSC.
PAGE 125
4106 RDF error-text error-text describes the nature of the problem. Cause. The RDF SGP encountered a problem loading its entities from the EDL. Effect. The SGP cannot load its EDL, so DOTs cannot correctly produce OEM states for the entity until the EDL problem is corrected. Recovery. The recovery depends on the error specified in error-text. 4199 ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect.
PAGE 126
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.
PAGE 127
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.
PAGE 128
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.
PAGE 129
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.
PAGE 130
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.
PAGE 131
4315 SPL Batch Job array overflow in domain^count^jobs^locs. max batch, num batch max batch the maximum number of batch jobs supported by the Spooler SGP num batch the number of batch jobs processed by the Spooler SGP 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.
PAGE 132
name name of entry being looked for type type of entry being looked for: SP = Supervisor; CL = Collector; DV = Device; PP = Print Process Cause. The Spooler SGP cannot find an entry of type type in its internal memory, but this entry is referenced in another spooler entry. Effect. The spooler tree structure is not correct and sampling information might not add up. Recovery. Verify the spooler name for the specified entry.
PAGE 133
Cause. The Spooler parameter STATS was set when the Spooler SGP was started. Therefore, this message indicates how much time elapsed during the indicated processing. Effect. None. Recovery. Informational message; no corrective action is necessary. To stop these messages from appearing, remove the STATS parameter from the ASAPCONF file or reset it from your ASAP session, then restart the Spooler SGP. 4396 SPL Reloading previous configuration. Cause.
PAGE 134
4399 ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. 4401 TAP ecb loadentities error-text error-text 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.
PAGE 135
TAP SSGETTKN Get token error: error TAP SSPUT token error: error TAP SSPUTTKN cmd token error: error TAP SPI Last Error: error TAP SPI Return Error: error TAP SPI Dlist RetCode error: error TAP SSNULL token error: error error 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.
PAGE 136
Effect. The MEDIASRV server does not start. Recovery. Make sure that MEDIASRV is properly installed and configured. For installation information for the MEDIASRV server, see the DSM/Tape Catalog User’ s Guide . 4406 TAP Rank Value Error FE: error, error-detail error 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.
PAGE 137
option invalid SGP command option that was found Cause. The Tape SGP encountered an invalid option in command while parsing the MONITOR TAPE, LIST, SGP command. Effect. The invalid option is ignored. Recovery. Correct the command with the invalid option. 4409 TAP Process Handle FE: error error NonStop Kernel error returned from the PROCESSHANDLE_DECOMPOSE_ or PROCESSHANDLE_GETMINE_ procedure Cause.
PAGE 138
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. Verify that the specified domain is a valid tape device. If it is, contact your system administrator.
PAGE 139
4414 TAP GETINFOLIST Error: error error-detail error error returned by the NonStop Kernel GETINFOLIST procedure 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.
PAGE 140
error error returned by the LOAD^OBJECTIVES procedure to identify the specific error error-detail error details returned by the LOAD^OBJECTIVES procedure to identify the specific error Cause. The Tape SGP encountered an error while trying to load objectives for a domain or subdomain. Effect. The new objectives are not loaded and the old ones are used. Load is attempted on the next sampling. Recovery. Verify that the EDL and objectives database are correctly installed and configured.
PAGE 141
num elapsed time spent in the processing area Cause. The Tape parameter STATS was set when the Tape SGP was started. This message indicates how many milliseconds have elapsed (not how much time processing took) when doing the indicated processing. Effect. None. Recovery. Informational message; no corrective action is necessary. To prevent these messages from appearing, remove the STATS parameter from the ASAPCONF file or reset it from your ASAP session, and restart the Tape SGP.
PAGE 142
4499 ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. 4501 ASAPTMF error-text error-text 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.
PAGE 143
error-num error code returned by call to sgp_rankvalue_ error-detail detailed error returned by call to sgp_rankvalue_ Cause. An error occurred while trying to get the state of a domain attribute. Effect. The state of this domain attribute is not obtained, The returned state value is the default value of the Exists state. Recovery. Make sure no problem exists with the ASAP Objectives database. errornum and error-detail can help you determine the cause of the problem.
PAGE 144
error-num error returned by the NonStop Kernel processhandle_getmine_ or processhandle_decompose_ procedure call Cause. A NonStop Kernel procedure call returned an error. Effect. The TMF SGP cannot get information about itself, its CPU, pin, nodename, and so on. Recovery. Use error-num to determine the cause of the error.
PAGE 145
Recovery. Use error-num and error-detail to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative. 4509 TMF SET TMF PARAM cmd-option cmd-option an invalid parameter option Cause. An error was detected in the TMF SGP startup PARAM string. Effect. The rest of the PARAM string from the point of the error is ignored. Recovery. Re-enter the TMF SGP startup PARAM string using valid parameters.
PAGE 146
Recovery. Use error-num and error-detail to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative. 4532 ASAPTMF Process create error error-num error-detail error-num error returned by the NonStop Kernel process_create_ procedure call error-detail additional error information returned by the process_create_ procedure call Cause. The NonStop Kernel process_create_ procedure call returned an error when trying to start the TMFSERVE process. Effect.
PAGE 147
Cause. An error occurred when trying to send the startup message to the TMFSERVE process. Effect. The TMFSERVE process is closed since it does not receive the startup message. The TMF SGP will try to open the process again at the next sampling. No TMF statistics are collected until the TMF SGP successfully opens the TMFSERVE process. Recovery. Use error-num to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative.
PAGE 148
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. If you cannot resolve the problem, contact your HP support representative.
PAGE 149
Effect. The SPI buffer is not sent, so the associated TMF statistics are not obtained for this sampling. The error is reported against the appropriate domain. Recovery. Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative.
PAGE 150
4555 ASAPTMF spi-cmd,SPI Error Map= error-num spi-cmd SPI command on which the error occurred error-num SPI error returned while extracting the structured token from the SPI buffer Cause. When extracting the structured token from a SPI buffer, a SPI error was returned. Effect. 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.
PAGE 151
error-num SPI error returned while handling the multiple list tokens Cause. When handling the multiple list tokens, a SPI error was returned. Effect. The SPI buffer is not interpreted, so the associated TMF statistics are not obtained for this sampling. The error is reported against the appropriate domain. Recovery. Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative.
PAGE 152
4592 TMF TMFSERVE stopped, error= error-num error-num is the error returned by TMFSERVE when stopping. Zero means there was no error while stopping. Cause. The TMFSERVE process stopped with the displayed error. Effect. The TMFSERVE process stops. Recovery. Informational message; no corrective action is necessary. 4593 TMF TMFSERVE started Cause. The TMFSERVE process started. Effect. The TMFSERVE process starts. Recovery. Informational message; no corrective action is necessary. 4594 TMF EDL loaded Cause.
PAGE 153
Recovery. Informational message; no corrective action is necessary. 4597 TMF Could not load all domains: maximum reached. Cause. There are more domains defined in the Objectives Database than the TMF SGP can accept. Effect. All domains in the database exceeding the maximum are not monitored. Recovery. Remove some domains from the Objectives Database using the MONITOR TMF, DELETE command, then the COMMIT TMF command. 4598 TMF Autoconfiguration completed. Cause.
PAGE 154
error-detail is the detailed error, if any, returned from the call to SEGMENT_ALLOCATE_. Cause. The Process SGP tried to allocate extended memory to support its processing, but too little disk space is available for the swap file or is configured for the processor in KMSF. Effect. The Process SGP does not allocate the needed extended memory. Recovery. Configure more swap space on disk or in KMSF. 4602 sgpid Process handle error: error sgpid is the identifier of the File or Process SGP.
PAGE 155
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. 4605 sgpid Maximum number of monitored domains exceeded sgpid is the identifier of the File or Process SGP.
PAGE 156
4608 Internal Pool Management Error Cause. The pool header has been corrupted for the block being allocated. Effect. ASAP cannot use the pool block it attempted to allocate. Recovery. The pool block remains unused until the next restart of the ASAP server. 4609 Error SET PARAM: param Cause. The ASAP SGP detected an error with one of its startup parameters. Effect. The parameter in question has no effect and any parameters following the parameter in error are not processed. Recovery.
PAGE 157
Cause. The SGP received a file-system error when communicating with its server process, server. Effect. ASAP cannot effectively communicate with its server process. Recovery. Correct the file-system error or contact HP support to report the problem. 4612 Cannot start EMSDIST, Process_Launch_: error, error detail error is the file-system error encountered when communicating with the server. error detail is the detailed error (if any) encounted when opening the process. Cause.
PAGE 158
server is the name of the server process. error is the file-system error encountered when communicating with the server. error detail is the detailed error (if any) encounted when opening the process. 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. 4616 server start retry limit exhausted server is the object file name of the server process Cause.
PAGE 159
4618 Duplicate domain found during SORT, lowpass: count count is the domain count of the domain found to be a duplicate. Cause. The SGP found a duplicate domain (object) while sorting domains after a reconfiguration operation. Effect. ASAP fixes the new domain by adding a domain suffix or ignores it if it appears to be a real duplicate domain. Recovery. Report the problem to HP support. 4699 ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause.
PAGE 160
Effect. ASAPCMM cannot obtain SWAN communication line counters. Comm line status information is valid when ASAPCMM cannot obtain the communication line counters. Recovery. Stop and delete the measurement named ZCMM xxx, where xxx is the ASAP ID. Use the Measure interface MEASCOM. 4715 ASAPCMM Error SET CMM PARAM CPU nn cpu cpu is the CPU number selected. Cause. The Comm SGP could not start a measurement in the specified CPU. Effect.
PAGE 161
err is the Measure error returned from the Measure subsystem. Cause. ASAPCMM restarted the measurement. Effect. ASAPCMM could not obtain communication line counters during a sample interval. Possibly the Measure subsystem was stopped and restarted. Communication line statistics are set to null for the sample interval when ASAPCMM cannot obtain communication line counters. Recovery. Informational message only; no corrective action is needed. 4723 ASAPCMM started Measctl in CPU nn cpu cpu is the CPU number.
PAGE 162
err is the file-system error number associated with the last operation on the file. Cause. ASAPCMM encountered an error while attempting to send a message to the ASAP Collector. Effect. ASAPCMM cannot complete the request. Recovery. The FILEINFO system call returned this error. For corrective action for the specified error code, see the Operator Messages Manual or the Guardian Procedure Errors and Messages Manual . 4742 ASAPCMM Config access error ldev ldev is the logical device number. Cause.
PAGE 163
err is the Measure error number. Cause. ASAPCMM could not stop its measurement. err represents the Measure error returned from the Measure subsystem. Effect. ASAPCMM could not stop the measurement named ZCMM xxx, where xxx is the ASAP ID. Recovery. Stop and delete the measurement named ZCMMP xxx, where xxx is the ASAP ID. Use the Measure interface MEASCOM. 4748 ASAPCMM Comm Measurement stopped Cause. The ASAPMON process stopped the ASAPCMM process. Effect. ASAPCMM stops its measurement. Recovery.
PAGE 164
Recovery. This error might be caused by the EDL settings. For more information on ASAP EDL, see the ASAP Client Manual. 4753 ASAPCMM sgp_readdomain_ Error err err is the error number returned from the SGP_ReadDomain_ procedure. Cause. The ASAP sgp_readdomain_ procedure returned the specified error when trying to get the list of Comm domains to monitor. Effect. Communication monitoring of all devices will occur. Recovery. Make sure that ASAP is configured correctly.
PAGE 165
ldev is the logical number of the Comm line that failed. Cause. The ASAP sgp_Getobjectives procedure returned the specified error when trying to get the list of Comm objectives. Effect. The Comm SGP monitors all configured comm lines. Recovery. Make sure ASAP is configured correctly. For more information about Ranking Objectives, see the ASAP Server Manual. If the configuration is correct, contact your HP support representative.
PAGE 166
err is the error number returned by Measure. Cause. The ASAP Comm SGP could not access the device due to the error returned by Measure. Effect. The statistics are set to zero for the interval. Recovery. If the error persists contact your HP support representative or attempt to stop and restart the Measure subsystem. 4775 Config Attribute Values Attribute The name of the first attribute in the output list.
PAGE 167
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.
PAGE 168
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.
PAGE 169
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.
PAGE 170
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.
PAGE 171
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.
PAGE 172
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.
PAGE 173
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.
PAGE 174
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.
PAGE 175
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.
PAGE 176
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
PAGE 177
1211 ZASP-EVT-EXPDMGR-OPEN-ERROR err 1212 ZASP-EVT-EXPDMGR-START-ERROR err 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,
PAGE 178
1306 ZASP-EVT-ALIVE-BUT-NO-PCB pin#, pri, pt2 1307 ZASP-EVT-PROCESS-NOT-IN-SAMPLE pin#, which 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-N
PAGE 179
cpu 1723 ZASP-EVT-DSK-MEASCTL-RESTARTED 1730 ZASP-EVT-DSK-PARAM-ERROR 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 1
PAGE 180
2006 ZASP-EVT-COL-SHORT-RQST-RCVD count, buf, pid 2007 ZASP-EVT-COL-SHUTDOWN-RCVD pid 2008 ZASP-EVT-COL-ILLEGAL-RQST-RCVD count, buf, pid 2009 ZASP-EVT-BAD-ENFSV-TRANS-CODE 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 ZAS
PAGE 181
2042 ZASP-EVT-COL-PART-MAXEXTENTSNA entity-number 2043 ZASP-EVT-COL-PART-OPEN-ERROR file-error, partition-index 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
PAGE 182
4002 ZASP-EVT-BOOLEAN-GOAL-FAILED 4021 ZASP-EVT-OBJ-LOAD-FAILURE 4022 ZASP-EVT-OBJ-SEGALLOC-ERR 4023 ZASP-EVT-OBJ-FILESYS-ERR 4024 ZASP-EVT-ACTION-COMM-ERR 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.
PAGE 183
4316 ZASP-EVT-SPL-DEVQOVR-ERR 4317 ZASP-EVT-SPL-ENTRYNOTFND-ERR 4393 ZASP-EVT-SPL-SPOOLTIMEOUT-INF 4394 ZASP-EVT-SPL-EDLLOADED-INF 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 max jobs, num jobs num num xxxx Table 2-8.
PAGE 184
4497 ZASP-EVT-TAP-DOMAINOVR-INF 4498 ZASP-EVT-TAP-AUTOCONFIG-INF 4499 ZASP-EVT-EXP-SUPPRESSED-ERRORS xxxx Table 2-9.
PAGE 185
4593 ZASP-EVT-TMF-TMFSERVE-STARTED 4594 ZASP-EVT-TMF-EDL-LOADED 4595 ZASP-EVT-TMF-STATS-COUNTS 4596 ZASP-EVT-TMF-RELOAD-PREV-CFG 4597 ZASP-EVT-TMF-MAXDOMAINS 4598 ZASP-EVT-TMF-AUTOCONFIG-DONE 4599 ZASP-EVT-TMF-SUPPRESSED ERRORS operation, time-ms Table 2-10.
PAGE 186
4708 ZASP-EVT-CMM-DATA-FILE-INUSE err 4715 ZASP-EVT-CMM-SET-CPU-ERROR cpu 4720 ZASP-EVT-CMM-STARTED 4721 ZASP-EVT-CMM-NOT-STARTED 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-COM
PAGE 187
4809 ZASP-EVT-SWP-SSG-SEND-PRIVATE SSG err, SSG det, SSG sub 4810 ZASP-EVT-SWP-SSG-SWAP-BUF-FULL SSG inx, SSG err, SSG det 4811 ZASP-EVT-SWP-MAX-UNKWN-DOMAINS 4812 ZASP-EVT-SWP-MAX-MNTRD-DOMAINS Index 4814 ZASP-EVT-SWP-CANNOT-START-SSG SSG id 4815 ZASP-EVT-SWP-NO-FILE Fname 4835 ZASP-EVT-SWP-COLLECT-SEND-ERR err 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-E
PAGE 188
ZEMS-TKN-CONSOLE-PRINT is FALSE for all ASAP messages. ZEMS-TKN-CPU contains the CPU number of the ASAP process that generated the event. ZEMS-TKN-CRTPID contains the ID of the ASAP process that generated the event. ZEMS-TKN-EMPHASIS indicates whether the event is flagged as critical. If this value is TRUE, the event is marked as critical. If this value is FALSE, the event is marked as informative. All ASAP subsystem internal events will have this value set to FALSE.
PAGE 189
ZASP-TKN-ASAP-ANAME contains the name of the ASAP attribute as defined in EDL. ZASP-TKN-ASAP-ATTRIBUTE-TYPE contains the data type of the attribute as defined in EDL. ZASP-TKN-ASAP-ATTRIBUTE-VALUE is present and contains the attribute value for attributes of type INT. ZASP-TKN-ASAP-ATTRIBUTE-INT32 is present and contains the attribute value for attributes of type INT32. ZASP-TKN-ASAP-ATTRIBUTE-INT64 is present and contains the attribute value for attributes of type INT64.
PAGE 190
err identifies a file-system error. Cause. The Statistics Gathering process (SGP) did not open. The FILEINFO system procedure call returned this error. Effect. A zero value is returned. Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual .
PAGE 191
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 ―1001‖.
PAGE 192
and the Collect process is not updated, any new statistics types would not be recognized by the Collector. Make sure all ASAP Collector and Server processes are at the same revision level.
PAGE 193
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 ―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.
PAGE 194
Cause. Synchronization between the Server and the Collector was not accomplished. The FILEINFO system procedure call returned this error. Effect. No communication occurred between the Server and Collector when you tried to perform a SYNC operation. Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual . Check the network path connection.
PAGE 195
Cause. An attempt to synchronize with the Server failed because the length of the request message was too short when the system was performing an internal check. Effect. Synchronization with the Server was not accomplished. Recovery.
PAGE 196
Effect. The synchronization clock is now operating correctly. Recovery. Informational message only; no corrective action is needed. Data Tokens. 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.
PAGE 197
pid is the requester’s process identification. Cause. The message received was not recognized because of its short length. Effect. The message could not be processed. Recovery.
PAGE 198
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.
PAGE 199
 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.
PAGE 200
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.
PAGE 201
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.
PAGE 202
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.
PAGE 203
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.
PAGE 204
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. Recovery.
PAGE 205
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 ―1024‖.
PAGE 206
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.
PAGE 207
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.
PAGE 208
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.
PAGE 209
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.
PAGE 210
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‖.
PAGE 211
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.
PAGE 212
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‖. 1061: ZASP-EVT-ACTION-NOT-SUPER Action Server not started as SUPER.SUPER Cause.
PAGE 213
1095: ZASP-EVT-LICENSE-ERROR license error license error is error text returned from the license validation procedure Cause. An error occurred while trying to validate the software license Effect. The ASAP component will not execute. Recovery. Correct the problem described in license error. DATA ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1095‖. 1096: ZASP-EVT-LICENSE-WILL-EXPIRE Softare License Expires in xx Days xx is the number of days before the software license will expire.
PAGE 214
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. The error number suppressed occurred xxxx times. Recovery. None. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1099‖. 1100: ZASP-EVT-BAD-GETPEEKCONF-LEN GETPEEKCONF length bad: length length is the length, in bytes, returned from the GET^PEEK^STATISTICS system procedure call. Cause.
PAGE 215
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. The Monitor could not retrieve CPU statistics information. Effect. A zero value is returned instead of a CPU statistics value. Recovery. Check that your operating system version and ASAP version are compatible.
PAGE 216
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. The Expand SGP could not find the path for this Network Line Handler (NetLH) device in the Network Line Handler configuration file. Effect. No statistics are returned for the Network Line Handler. Recovery. Check that the Expand Manager is present, up, and running.
PAGE 217
4 Cannot allocate map. 5 File error on swap file; err.<8:15> = filesystem error. 6 Invalid file format; err.<8:14> = error subcode err.<15> = 0, program file is in error err.<15> = 1, library file is in error 7 Unlicensed privileged program. 8 Process name error; err.<8:15> = filesystem error. 9 Library conflict. 10 Cannot communicate with system Monitor process; err.<8:15> = filesystem error. 11 File-system error occurred on library file; err.<8:15> = file-system error.
PAGE 218
19 Process device subtype specified in backup process is not the same as that in the primary process. Cause. The Expand SGP could not create a new subsystem manager process. Effect. No network statistics can be collected. Recovery. Check the Subsystem Programmatic Interface (SPI) manager at $SYSTEM.SYSTEM.0ZEXP to be sure that the Expand Manager is secured properly. Retry the request later.
PAGE 219
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 ―1211‖. 1212: ZASP-EVT-EXPDMGR-START-ERROR Subsystem Mgr Startup Msg Error: err err identifies a file-system error. Cause. The Expand SGP could not pass a startup message to the subsystem manager.
PAGE 220
1220: ZASP-EVT-EXPDMGR-NOT-CREATED Can’t Create Subsystem Mgr, Error: err err identifies a file-system error. Cause. The Expand SGP could not create a subsystem manager. The FILEINFO system procedure call returned this error. Effect. ASAP and the subsystem cannot communicate. Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual .
PAGE 221
Check that the Expand Manager is up and running. Retry the request. 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.
PAGE 222
request. 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 ―1231‖.
PAGE 223
ZASP-TKN-ASAP-ERRORNUM is ―1232‖.
PAGE 224
1234: ZASP-EVT-MON-EXPDMGR-RETRY-CNT ASAPMON ExpMgr ($ZEXP) Retry Counts: cnt cnt is the number of retries. Cause. The Expand SGP could not communicate with the Expand Manager process line. Effect. ASAP and the subsystem cannot communicate. Recovery.
PAGE 225
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 ―1235‖. 1236: ZASP-EVT-MON-EXPDMGR-PATH-STAT ASAPMON Can't obtain Path statistics Error: err, ldev err is the SPI error number returned by the $ZEXP process. ldev is the logical device number of the Expand line. Cause.
PAGE 226
ldev is the logical device number of the Expand line. Cause. The Expand SGP could not obtain level-2 statistics for an Expand line. Effect. ASAP does not obtain level-2 statistics from the Expand manager. Recovery. This error message is used for problem isolation.
PAGE 227
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 ―1238‖. 1239: ZASP-EVT-MON-EXPDMGR-NCSM-STAT ASAPMON Can't obtain NCSM line stats Error: err, ldev err is the SPI error number returned by the $ZEXP process. ldev is the logical device number of the Expand line. Cause. The Expand SGP could not obtain non-6100 line statistics. Effect.
PAGE 228
ldev is the logical device number of the Expand line. Cause. The Expand SGP could not obtain Expand Internet Protocol (IP) statistics. Effect. ASAP does not obtain Expand IP statistics from the Expand Manager. Recovery. This error message is used for problem isolation.
PAGE 229
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1242‖.
PAGE 230
1244: ZASP-EVT-EXP-NAM-CNTRS-UNAVAIL 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. This error message is used by HP for problem isolation. Contact your HP representative. Data Tokens.
PAGE 231
1250: ZASP-EVT-EXP-PARAM-ERROR Error SET EXPAND PARAM param param contains the parameter that caused the problem Cause. ASAPEXP detected that an invalid parameter was specified in the ASAP Conversational Interface (CI) SET EXPAND ON, PARAMETER command. Effect. ASAPEXP uses the default values for all parameters. Recovery. Ensure that all parameters contained in the ASAP startup file ASAPCONF are valid; then restart the ASAP Monitor. Data Tokens. ZEMS-TKN-TEXT contains the message text.
PAGE 232
Recovery. Verify that the ASAP objectivesdb is valid. Contact HP support to report the problem. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1252‖. 1253: ZASP-EVT-EXP-READDOMAIN-ERROR ReadDomain Error: err err is the error number returned from the Readdomain procedure Cause. The ASAP sgp_readdomain_ procedure returned the specified error when trying to get the list of Expand domains to monitor. Effect. Expand monitoring monitors all configured Expand lines. Recovery.
PAGE 233
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1254‖. 1255: ZASP-EVT-EXP-UNKNOWN-TRANSPORT Unknown Transport not supported err, Ldev err is the error number returned from the Expand Manager Ldev is the logical number of the Expand line that failed Cause. An unknown transport was detected that is not currently supported by the Expand SGP. Effect. Expand monitoring does occur on the ldev using the unknown transport. Recovery.
PAGE 234
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1256‖. 1257: ZASP-EVT-EXP-RANKVALUES-ERROR ASAPEXP Rank Values error= err, error-detail err is the error number returned from the SGP_RankValues procedure error-detail is the error detail number returned from the SGP_RankValues procedure Cause. The ASAP sgp_rankvalues procedure returned the specified error when trying to rank Expand threshold objectives. Effect.
PAGE 235
1299: ZASP-EVT-EXP-SUPPRESSED-ERRORS ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1299‖. 1300: ZASP-EVT-GETPEEKPCBS-ZERO-LEN GetPeekPCBs Returns error: err err is an error returned from the GetPeekPCBs system procedure call. Cause.
PAGE 236
1301: ZASP-EVT-PROCESSINFO-ERROR ProcessInfo Returns error: err, pin# err indicates the outcome of the PROCESSINFO call: err Meaning 0 Returns the status of the process CPU, PIN. 1 The process CPU, PIN does not exist or does not match the specified criteria. The status for the next higher CPU, PIN in the specified processor is returned. The four-word process ID for which status is being returned reflects the process ID parameters, if present.
PAGE 237
pin# is the process identification number. Cause. The system could not obtain the device name of the process. The process probably went away before the device name was obtained. Effect. The process information does not include a related device name. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1302‖. 1303: ZASP-EVT-DELTA-TIMES pin:ProcessTime delta:Sampletime delta in .
PAGE 238
ZEMS-TK7N-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1303‖. 1304: ZASP-EVT-DELTA-TOO-BIG ProcessTime delta too big:last 2 INTs in .1 sec: pin#, dpt1, dpt2 pin# is the process identification number. dpt1 is the third word of the process delta time for this PIN. dpt2 is the last word of the process delta time for this PIN. Cause. ASAP detected a 100-percent process control block (PCB) busy state, possibly because of an internal interface failure with the operating system. Effect.
PAGE 239
pt1 is the total process time of this PIN at the current sample time. pt2 is the total process time of this PIN at the last sample time. Cause. ASAP detected a 100-percent process control block (PCB) busy state, possibly due to an internal interface failure with the operating system. Effect. The PCB busy information in the sample might be distorted. Recovery.
PAGE 240
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.
PAGE 241
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.
PAGE 242
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.
PAGE 243
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.
PAGE 244
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.
PAGE 245
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.
PAGE 246
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‖.
PAGE 247
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.
PAGE 248
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.
PAGE 249
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.
PAGE 250
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‖.
PAGE 251
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.
PAGE 252
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.
PAGE 253
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‖.
PAGE 254
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.
PAGE 255
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‖.
PAGE 256
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‖.
PAGE 257
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‖.
PAGE 258
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‖.
PAGE 259
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‖.
PAGE 260
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.
PAGE 261
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.
PAGE 262
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.
PAGE 263
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.
PAGE 264
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―1766‖. 1780: ZASP-EVT-DSK-GMS-ATTRIBUTES ASAP GMS Attribute Values Attribute is the name of the first GMS attribute in the output list Values is the value of the GMS attribute or attributes Cause. The ASAP Disk SGP could not access the device. This is preceded by an error 1744. The following attributes are written to the ASAP log file for diagnostic purposes: Logical device; Group; Module; Slot; Fabric; and SCSI ID. Effect.
PAGE 265
2000: ZASP-EVT-DB-WRITE-ERROR DB^write filename, fe: err, sysno, cpuno filename is the file name for the file in which the error occurred. err identifies a file-system error. system is the system number. cpuno is the CPU number. Cause. The Collector received statistical information from the Monitor, but it cannot perform all database record file I/O. The database might not be secured properly, might not be present, or might be full. The FILEINFO system procedure call returned this error. Effect.
PAGE 266
2001: ZASP-EVT-UNKNOWN-STAT-SUM-MSG Unknown stat^sum^msg: type, words type is the current statistics type. words indicates the current statistics words. Cause. The Collector cannot recognize the statistics type, so it cannot query it. Effect. Statistical information is not being written to the database. Recovery.
PAGE 267
Effect. Files are being renamed Zmmddlll, where mmdd represents month and day, and lll is the last three letters of the original file name. Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual .
PAGE 268
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2003‖. 2004: ZASP-EVT-PURGEDATA-ERROR Can’t Purgedata filename, fe: err filename is the file name for the file in which the error occurred. err identifies a file-system error. Cause. The system is not performing a database cleanup operation, as it should. The FILEINFO system procedure call returned this error. Effect. The purge-data operation is not being executed. The statistics are not being refreshed. Recovery.
PAGE 269
Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2005‖. 2006: ZASP-EVT-COL-SHORT-RQST-RCVD 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. A message was received that was unrecognized because of its short length. Effect. The message is not processed.
PAGE 270
pid is the requester’s process identification. Cause. A shutdown request was received. Effect. Your ASAP session terminates. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2007‖. 2008: ZASP-EVT-COL-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.
PAGE 271
2009: ZASP-EVT-BAD-ENFSV-TRANS-CODE ENFSV trans code bad Cause. An incomprehensible input request was received. Effect. The Collect server cannot behave as an Enform server because it cannot understand the request. Recovery. Check your Enform request and retry it.
PAGE 272
Cause. The startup parameters did not open the terminal logfile. Effect. The terminal logfile did not open at startup. Recovery. Correct the terminal file name in your configuration file. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2011‖. 2012: ZASP-EVT-OPEN-ERROR Open filename, fe: err, type filename is the file name for the file in which the error occurred. err identifies a file-system error.
PAGE 273
2013: ZASP-EVT-OPEN-INFO Open filename, INFO: type filename is the file being opened. type is an internal index to the ASAP database, with these values: 0 DBSYS 1 DBCPU 2 DBNET 3 DBPCB 5 DBNODE 6 DBAPP 7 DBDSK Cause. The system opened the 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‖.
PAGE 274
2015: ZASP-EVT-COL-TRACE Trace Cause. The system performed an internal trace. Effect. The system is working correctly. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2015‖. 2016: ZASP-EVT-COL-STARTED COLLECT version started cpu version is the operating system version. cpu is the CPU number. Cause. The system is informing you that the Collector started successfully. Effect. The Collector is operating.
PAGE 275
Effect. The Enform server is operating. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2017‖. 2018: ZASP-EVT-COL-RCV-READ-ERROR $RECEIVE read, FE: err err identifies a file-system error. Cause. A NonStop Kernel error occurred while trying to read a system message. The FILEINFO system call returned this error. Effect. The ASAP Collect process did not receive the message. Recovery.
PAGE 276
pid is the requester’s process identification. Cause. A NonStop Kernel error occurred while trying to reply to a system message. The FILEINFO system call returned this error. Effect. The ASAP Collect process could not reply to 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 .
PAGE 277
ZASP-TKN-ASAP-ERRORNUM is ―2020‖. 2022: ZASP_EVT_COL_DST_FALLBACK DST fallback delta detected: seconds seconds is the number of seconds that the DST time will fall back Cause. Daylight Savings Time fall back has occurred. This message indicates that ASAP is aware that the DST time has changed. Effect. None. Recovery. This is an informative message. No recovery is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2022‖.
PAGE 278
filename is the name of old date base file marked for deletion due to SET DBMAXDAYS. Cause. The ASAP collector is executing database clean up and tracing is enabled. Effect. The ASAP date files are being maintained based on the DBMAX configuration settings. This message is informational only. Recovery. This message is informative. No recovery is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2025‖.
PAGE 279
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2030‖. 2031: ZASP-EVT-COL-CTL-CREATE-ERROR PCtl Creat filename error filename is the name of the control file. error is the file-system error number. Cause. The Collector could not create a new partition control file.
PAGE 280
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 ―2032‖. 2033: ZASP-EVT-COL-CTL-OPEN-ERROR PCtl Open filename error filename is the name of the control file. error is the file-system error number. Cause. The partition control file could not be opened when the Collector was started.
PAGE 281
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 ―2034‖. 2035: ZASP-EVT-COL-CTL-READ-ERROR Collector could not read partition ctl file error error is the file-system error number. If greater than 0, it indicates the encountered filesystem error. If less than 0, it indicates an internal ASAP error. Cause.
PAGE 282
Effect. The Collector logs the error and continues to process the control file. If the entire file is corrupt or invalid, the database is created using default settings. If some entries in the file are good, they are used to create the database. Recovery. Shut down and restart the Collector to re-create the partition control file. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2036‖.
PAGE 283
ZASP-TKN-ASAP-ERRORNUM is ―2038‖. 2039: ZASP-EVT-COL-PART-CREATE-ERROR CreatePart filename file-error partition-index filename is the database file that cannot be created. file-error is the file-system error number. partition-index if between 0 and the number of partitions defined, indicates which partition definition is in error. If greater than the number of partitions defined, the partition definitions are correct, and a system error occurred while trying to create the file. Cause.
PAGE 284
error-indicator contents of the internal error. Cause. The Collector could not create the specified database file. Most likely a system error occurred, such as a down target volume or a security violation, or an internal ASAP error. Effect. 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.
PAGE 285
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2042‖. 2043: ZASP-EVT-COL-PART-OPEN-ERROR OpenPart filename file-error partition-index filename is the database file that cannot be opened.
PAGE 286
Effect. The Collector cannot get alternate key file info. Recovery. Make sure files are secured properly. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2050‖. 2051: ZASP-EVT-COL-DBAK-GET-FILE-EXP DB^AltKeyFile^GET call fname expand failed Cause. The Collector could not get alternate key file info for the DB. The cause is most likely a security violation. Effect. The Collector cannot get alternate key file info. Recovery. Make sure files are secured properly. Data Tokens.
PAGE 287
Cause. The Collector DB file name is invalid. The cause is most likely an invalid database file name specification. Effect. The Collector cannot get alternate key file info. Recovery. Make sure SET DB command settings arecorrect. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2053‖. 2054: ZASP-EVT-COL-DBAK-PURGE-NAMERR DB^AltKeyFile^NAME ERR: err Cause. The Collector cannot determine the name of the alternate key file for root .
PAGE 288
2056: ZASP-EVT-COL-DBAK-PURGEDATAERR PURGE AK FE: err 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. Data Tokens. ZEMS-TKN-TEXT contains the message text.
PAGE 289
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2058‖. 2059: ZASP-EVT-COL-DBAK-RENAME-ERROR DB^AltKeyFile^RENAME AK RENAME FE: err Cause. The Collector cannot RENAME alternate key . 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.
PAGE 290
2099: ZASP-EVT-EXP-SUPPRESSED-ERRORS ASAP ASAP Error #.... occurred xxxx time(s) xxxx is the number of times the error occurred Cause. The error number was suppressed. Effect. The error number suppressed had occurred xxxx times. Recovery. None. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―2099‖. 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.
PAGE 291
file is in error err.<15> = 1, library file is in error 7 Unlicensed privileged program. 8 Process name error; err.<8:15> = file-system error. 9 Library conflict. 10 Cannot communicate with system Monitor process; err.<8:15> = filesystem error. 11 File-system error occurred on library file; err.<8:15> = file-system error. 12 Program file and library file specified are same file. 13 Extended data segment initialization error; err.<8:15> = file-system error.
PAGE 292
the same as in primary process. Cause. A NEWPROCESS error and a file-system error occurred while a primary process was trying to create a backup process. Effect. The backup process is not created. Recovery. Make sure the checkpoint information is correct. Check that the CPU is up and running. If the CPU is down, follow the recommended recovery procedure for a CPU failure. For more information on file-system errors, see the Operator Messages Manual .
PAGE 293
2 Takeover from primary; then err.<8:15> = 0 primary stopped = 1 primary ended abnormally = 2 primary’s process failed = 3 primary called CHECKSWITCH 3 Invalid parameter; then err.<8:15> = number of parameter in error Is a four-word array where NEWPROCESS returns the process identification of the requester’s new process. pid is a four-word array where NEWPROCESS returns the process identification of the requester’s new process. Cause.
PAGE 294
3004: ZASP-EVT-TAKEOVER --- TAKEOVER --> cpu: cpu cpu is the CPU number. Cause. The primary process quit, and the backup process took over. The CPU of the primary process probably went down. Effect. The backup process is now the primary process. Recovery. Check whether the primary CPU failed. If so, follow the recommended recovery procedure for a CPU failure. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―3004‖.
PAGE 295
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―3099‖. 4000:ZASP-EVT-STATE-DOWN-MSG 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.
PAGE 296
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.
PAGE 297
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4001‖. ZASP-TKN-ASAP-COMPONENT contains the name of the ASAP component reporting this condition. ZASP-TKN-ASAP-ENAME contains the name of the entity, for example ―Disk‖. ZASP-TKN-ASAP-DNAME contains the name of a domain, for example ―$Data‖. ZASP-TKN-ASAP-ANAME contains the name of an attribute, for example ―Busy‖. ZASP-TKN-ASAP-VALUETEXT contains the attribute value in ASCII text.
PAGE 298
entity is the name of the relevant entity domain is the name of the relevant domain goal-name is the name of the Boolean goal Cause. A Boolean goal has failed to meet its stated objectives. Effect. User-specific. Recovery. User-specific. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4002‖.
PAGE 299
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.
PAGE 300
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.
PAGE 301
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.
PAGE 302
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.
PAGE 303
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‖.
PAGE 304
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‖.
PAGE 305
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.
PAGE 306
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.
PAGE 307
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.
PAGE 308
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.
PAGE 309
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.
PAGE 310
4316: ZASP-EVT-SPL-DEVQOVR-ERR SPL DevQ Job array overflow in domain^count^jobs^locs. max jobs, num jobs max jobs the maximum number of DevQ jobs supported by the Spooler SGP num jobs the number of DevQ jobs processed by the Spooler SGP Cause. The array used to temporarily hold the job numbers of the jobs queued to devices is full. Effect. The DevQs attribute for the spooler supervisor might not be reported correctly. Recovery. Verify the spoolers being monitored.
PAGE 311
configuration is correct, note the name, create a saveabend file of the Spooler SGP, stop the SGP, and contact your HP support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4317‖. 4393: ZASP-EVT-SPL-SPOOLTIMEOUT-INF 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.
PAGE 312
Cause. The Spooler parameter STATS was set when the Spooler SGP was started. Therefore, this message indicates how much time elapsed during the indicated processing. Effect. None. Recovery. Informational message; no corrective action is necessary. To stop these messages from appearing, remove the STATS parameter from the ASAPCONF file or reset it from your ASAP session, then restart the Spooler SGP. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4395‖.
PAGE 313
ZASP-TKN-ASAP-ERRORNUM is ―4397‖. 4398: ZASP-EVT-SPL-AUTOCONFIG-INF SPL Autoconfiguration completed. Cause. No spooler domains are specified in the objective database; therefore, the Spooler SGP has autoconfigured to monitor the $SPLS spooler. Effect. The Spooler is configured to monitor only the $SPLS spooler. Recovery. Informational message; no corrective action is necessary. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4398‖.
PAGE 314
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4401‖. 4402: ZASP-EVT-TAP-READDOM-ERR TAP sgp_readdomain_ Error= FE: error error file-system error returned by the SGP_READDOMAIN_ procedure. Cause. The ASAP sgp_readdomain_ procedure returned the specified error when trying to get the list of tape domains to monitor. Effect. Tape monitoring does not begin. Recovery. Make sure ASAP is configured correctly.
PAGE 315
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. Make sure your version of MEDIASRV is compatible with ASAP. If it is and you still get this error, contact your service provider. Data Tokens.
PAGE 316
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.
PAGE 317
option invalid SGP command option that was found Cause. The Tape SGP encountered an invalid option in command while parsing the MONITOR TAPE, LIST, SGP command. Effect. The invalid option is ignored. Recovery. Correct the command with the invalid option. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4408‖.
PAGE 318
Cause. The specified error was returned when trying to allocate memory for the transfer segments. Effect. The needed extended segments are not allocated. Sampling is not possible. Recovery. Contact your system administrator to verify why memory is not available. Check the swap space settings. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4410‖.
PAGE 319
Cause. The specified error occurred when sending a SPI request to MEDIASRV. Effect. The MEDIASRV process is closed and a new one is created at the next sampling. All affected tape devices in the current sample are given a status of SPIError. Recovery. Make sure your version of MEDIASRV is compatible with ASAP, and that MEDIASRV is properly installed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4412‖.
PAGE 320
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4414‖. 4415: ZASP-EVT-TAP-NOTAPEFOUND-ERR TAP error finding tape devices. Error=error, error-detail TAP can’t find any tape devices.
PAGE 321
error-detail error details returned by the LOAD^OBJECTIVES procedure to identify the specific error Cause. The Tape SGP encountered an error while trying to load objectives for a domain or subdomain. Effect. The new objectives are not loaded and the old ones are used. Load is attempted on the next sampling. Recovery. Verify that the EDL and objectives database are correctly installed and configured. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4416‖.
PAGE 322
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4494‖. 4495: ZASP-EVT-TAP-SAMPLESTATS-INF TAP Sampling delay processing: num processing processing area for elapsed time num elapsed time spent in the processing area Cause. The Tape parameter STATS was set when the Tape SGP was started. This message indicates how many milliseconds elapsed (not how much time processing took) when doing the indicated processing. Effect. None. Recovery.
PAGE 323
num maximum number of tape domain entries allowed in the Tape SGP Cause. The maximum number of tape domains to be monitored was reached. Effect. The overflow tape domains are not monitored. Recovery. Monitor fewer tape domains. If this becomes an issue, contact your support representative and describe your requirements. 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.
PAGE 324
4501: ZASP-EVT-TMF-LOADENTITIES-ERR 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. 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.
PAGE 325
error-detail detailed error returned by call to sgp_rankvalue_ Cause. An error was returned 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 there is no problem with the ASAP Objectives Database. error-num and error-detail can help you determine the cause of the problem. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4503‖.
PAGE 326
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4505‖. 4506: ZASP-EVT-TMF-PROCHANDLE-ERR ASAPTMF Process handle Error= error-num error-num error returned by the NonStop Kernel processhandle_getmine_ or processhandle_decompose_ procedure call Cause. A NonStop Kernel procedure call returned an error. Effect. The TMF SGP cannot get information about itself, its CPU, pin, nodename, and so on. Recovery. Use error-num to determine the cause of the error. Data Tokens.
PAGE 327
4508: ZASP-EVT-TMF-SEGALLOCSUBD-ERR ASAPTMF Transac Segment alloc: error-num error-detail error-num error returned by the NonStop Kernel segment_allocate_ procedure call error-detail additional error information returned by the segment_allocate_ procedure call Cause. The NonStop Kernel segment_allocate_ procedure call returned an error when trying to allocate an extended segment. Effect. The TMF SGP does not have any extended segment to store the statistics of TMF transactions.
PAGE 328
error-num error returned by the NonStop Kernel processname_create_ procedure call Cause. An error occurred while trying to get a process name from the system. Effect. The TMFSERVE process cannot start since no process name is obtained. The TMF SGP will try to get a process name again at the next sampling. No TMF statistics are collected until the TMF SGP successfully starts the TMFSERVE process. Recovery. Use error-num to determine the cause of the error.
PAGE 329
error-num error returned by the NonStop Kernel process_create_ procedure call error-detail additional error information returned by the process_create_ procedure call Cause. The NonStop Kernel process_create_ procedure call returned an error when trying to start the TMFSERVE process. Effect. The TMFSERVE process does not start. The TMF SGP will try to start it again at the next sampling. No TMF statistics are collected until the TMF SGP successfully starts the TMFSERVE process. Recovery.
PAGE 330
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. Use error-num to determine the cause of the error.
PAGE 331
Cause. An error occurred when trying to close the TMFSERVE process. Effect. The TMFSERVE process cannot close after receiving its startup message. The TMF SGP will try to close the process again at the next sampling. No TMF statistics are collected until the TMF SGP successfully communicates with the TMFSERVE process. Recovery. Use error-num to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text.
PAGE 332
error-num SPI error returned while sending the SPI buffer Cause. When sending a SPI buffer to the TMFSERVE process, a SPI error was returned. Effect. The SPI buffer is not sent, so the associated TMF statistics are not obtained for this sampling. The error is reported against the appropriate domain. Recovery. Use spi-cmd and error-num to determine the cause of the error. If you cannot resolve the problem, contact your HP support representative. Data Tokens. ZEMS-TKN-TEXT contains the message text.
PAGE 333
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. Use spi-cmd, token, and error-num to determine the cause of the error.
PAGE 334
spi-cmd SPI command on which the error occurred error-num SPI error returned while extracting the structured token from the SPI buffer Cause. When extracting the structured token from a SPI buffer, a SPI error was returned. Effect. The SPI buffer is not interpreted, so the associated TMF statistics are not obtained for this sampling. The error is reported against the appropriate domain. Recovery. Use spi-cmd and error-num to determine the cause of the error.
PAGE 335
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. If you cannot resolve the problem, contact your HP support representative.
PAGE 336
spi-cmd SPI command on which the error occurred error-num SPI error returned while handling the context token Cause. When handling the context token, a SPI error was returned. Effect. The SPI buffer is not interpreted, so the associated TMF statistics are not obtained for this sampling. The error is reported against the appropriate domain. 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. Data Tokens.
PAGE 337
ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4593‖. 4594: ZASP-EVT-TMF-EDL-LOADED TMF EDL loaded Cause. The EDL was correctly loaded for the TMF SGP. Effect. The SGP startup continues. Recovery. Informational message; no corrective action is necessary. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4594‖. 4595: ZASP-EVT-TMF-STATS-COUNTS TMF Stats performance messages. Cause. This is a performance statistics message for internal HP use only. Effect.
PAGE 338
Cause. There are more domains defined in the Objectives Database than the TMF SGP can accept. Effect. All domains in the database exceeding the maximum are not monitored. Recovery. Remove some domains from the Objectives Database using the MONITOR TMF, DELETE command, then the COMMIT TMF command. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4597‖. 4598: ZASP-EVT-TMF-AUTOCONFIG-DONE TMF Autoconfiguration completed. Cause.
PAGE 339
sgpid is the identifier of the File or Process SGP. error is the error code returned from the call to SEGMENT_ALLOCATE_. error-detail is the detailed error, if any, returned from the call to SEGMENT_ALLOCATE_. Cause. The Process SGP tried to allocate extended memory to support its processing, but too little disk space is available for the swap file or is configured for the processor in KMSF. Effect. The Process SGP does not allocate the needed extended memory. Recovery.
PAGE 340
4603: ZASP-PRO-EDL-ERR Returned text from the EDL compiler. Cause. Either a syntax error on EDL or missing or corrupted EDL files caused an error when the Process SGP tried to load and compile ASAP EDL. Effect. ASAP EDL is not loaded and compiled. Recovery. Check the EDL files to ensure they exist and are accurate, and restart the Process SGP. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4603‖.
PAGE 341
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. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4605‖. 4606: ZASP-EVT-PRO-POOLMAXSIZE-ERR ASAP ERR component Pool Definition error: error component is the name of the relevant ASAP component. error is the error returned from the address_delimit_ procedure. Cause.
PAGE 342
Effect. ASAP stops processing any more dynamically resolved domains for that interval. Recovery. Redefine domains so they are not dynamically resolved or increase the pool space using the MBYTES SET parameter. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4607‖. 4608: ZASP-EVT-PRO-POOLINTERNAL-ERR ASAP ERR component Internal Pool Management Error component is the name of the relevant ASAP component. Cause. The pool header has been corrupted for the block being allocated.
PAGE 343
ZASP-TKN-ASAP-ERRORNUM is ―4609‖. 4610: ZASP-EVT-PRO-SPIPROC-ERR ASAP ERR component SPI error on SPI Procedure: error component is the name of the relevant ASAP component. SPI Procedure is the name of the SPI procedure that returned the error. error is the SPI error returned from the procedure call. Cause. The SGP received the indicated SPI error when calling SPI Procedure. Effect. The effect of this problem varies but could result in the SGP being unable to obtain statistics for a domain. Recovery.
PAGE 344
Recovery. Correct the file-system error or contact HP support to report the problem. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4611‖. 4612: ZASP-EVT-PRO-PLAUNCH-ERR ASAP ERR component Cannot start EMSDIST, Process_Launch_: error, error detail component is the name of the relevant ASAP component. SPI Procedure is the name of the process_launch_procedure. error detail is the detailed (if any) error returned from the procedure. Cause.
PAGE 345
error is the file-system error encountered when opening the process. error detail is the detailed error (if any) encountered when opening the process. Cause. The ASAP SGP cannot open its server process. Effect. ASAP cannot obtain the statistics it normally obtains from its server process. Recovery. Correct the file-system error, and then restart ASAP. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4613‖.
PAGE 346
4616: ZASP-EVT-PRO-STARTRETRY-ERR ASAP ERR component server start retry limit exhausted component is the name of the relevant ASAP component. server is the name of the server process that cannot be restarted. Cause. The SGP attempted to restart its failed server the maximum number of times. Effect. ASAP quits trying to restart its server. Recovery. Fix the server startup problem, and then restart ASAP. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is ―4616‖.
PAGE 347
4618: ZASP-EVT-PRO-DUPDOMAIN-ERR ASAP ERR component Duplicate domain found during SORT, lowpass: count component is the name of the relevant ASAP component. count is the domain count when the duplicate domain was detected. Cause. The SGP found a duplicate domain (object) while sorting domains after a reconfiguration operation. Effect. ASAP fixes the new domain by adding a domain suffix or ignores it if it appears to be a real duplicate domain. Recovery. Report the problem to HP support. Data Tokens.
PAGE 348
Recovery. Shut down the ASAPMON, set communication to OFF, and restart the ASAP Monitor. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4700". 4708: ZASP-EVT-CMM-DATA-FILE-INUSE ASAPCMM Measure Data File In Use err err is the Measure error returned from the Measure subsystem. Cause. ASAPCMM could not create a Measure data file. Effect. ASAPCMM cannot obtain communication linecounters. Recovery. Stop and delete the measurement named ZCMMxxx, where xxx is the ASAP ID.
PAGE 349
4720: ZASP-EVT-CMM-STARTED ASAPCMM ZCMMxxx started. Cause. ASAPCMM successfully started a measurement. Effect. ASAPCMM 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 "4720". 4721: ZASP-EVT-CMM-NOT-STARTED ASAPCMM ZCMMxxx NOT started. Cause. ASAPCMM could not start a measurement. Effect. ASAPCMM cannot obtain disk counters. Recovery.
PAGE 350
ZASP-TKN-ASAP-ERRORNUM is "4722". 4723: ZASP-EVT-CMM-MEASCTL-RESTARTED ASAPCMM started MEASCTL IN CPU cpu cpu specifies the CPU number. Cause. The Comm Statistics Gathering process (SGP) started the MEASCTL process in a CPU that did not have the MEASCTL process running. Effect. ASAPCMM starts MEASCTL in the CPU. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4723".
PAGE 351
err is the file-system error returned from the Measure subsystem. Cause. ASAPCMM encountered an error while attempting to send a message to the ASAP Collector. Effect. ASAPCMM cannot complete the request. Recovery. For a definition of the specified error, see the Operator Messages Manual. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual . Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4735".
PAGE 352
Recovery. Check the ASAP log for previous ASAPCMM messages and make the necessary corrections. For corrective action for the specified error, see the Measure Reference Manual. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4743". 4744: ZASP-EVT-CMM-DEVICE-INACCESSBL ASAPCMM Comm line inaccessible ldev,ctrl ldev is the logical number of the device. ctrl is the D-Series controller number, or the G-Series module. Cause.
PAGE 353
ZASP-TKN-ASAP-ERRORNUM is "4747". 4748: ZASP-EVT-CMM-SHUTDWN-COMPLETE ASAPCMM Disk Measurement stopped Cause. ASAPCMM was stopped by the ASAPMON process. Effect. ASAPCMM stops its measurement. Recovery. Informational message only; no corrective action is needed. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4748". 4750: ZASP-EVT-CMM-PARAM-ERROR Error SET Comm PARAM param param contains the parameter that caused the problem. Cause.
PAGE 354
Recovery. This error might be caused by the EDL settings. For more information on ASAP EDL, see the ASAP Client Manual. Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4751". 4753: ZASP-EVT-CMM-READDOMAIN-ERROR ASAPCMM sgp_readdomain_ Error err err is the error number returned from the SGP_ReadDomain_ procedure. Cause. The ASAP sgp_readdomain_ procedure returned the specified error when trying to get the list of Comm domains to monitor. Effect.
PAGE 355
Data Tokens. ZEMS-TKN-TEXT contains the message text. ZASP-TKN-ASAP-ERRORNUM is "4754". 4756: ZASP-EVT-CMM-GETOBJTIVES-ERROR GetObjectives Error err, ldev err is the error number returned from the SGP_GETOBJECTIVES_ procedure. ldev is the logical number of the Disk device that failed. Cause. The ASAP sgp_Getobjectives procedure returned the specified error when trying to get the list of Comm objectives. Effect. The Comm SGP monitors all configured Comm lines. Recovery.
PAGE 356
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 "4757". 4766: ZASP-EVT-CMM-BAD-STATS-RCVD ASAPCMM Bad Stats Received ldev ldev is the logical number of the device. Cause. The ASAP Comm SGP encountered a bad statistics record. Effect. The bad statistics record is discarded.
PAGE 357
4775: ZASP-EVT-CMM-GET-CONFIG-ATTR Config Attribute Values Attribute The name of the first attribute in the output list. Values Attributes values written to the ASAP Log for diagnostic purposes: Device Name; TrackID; Cpu; Clip; Type; and SubType. Cause. The ASAP Comm SGP encountered a bad statistics record. Effect. The statistics are set to zero for the interval. Recovery. If the error persists contact your HP support representative or attempt to stop and restart the Measure subsystem. Data Tokens.
PAGE 358
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.
PAGE 359
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.
PAGE 360
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.
PAGE 361
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.
PAGE 362
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.
PAGE 363
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.
PAGE 364
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".
PAGE 365
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.
PAGE 366
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.
PAGE 367
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 #....
PAGE 368
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.
PAGE 369
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.
PAGE 370
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.
PAGE 371
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.
PAGE 372
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.
PAGE 373
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.
PAGE 374
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.
PAGE 375
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.
PAGE 376
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.
PAGE 377
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.
PAGE 378
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.
PAGE 379
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.
PAGE 380
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.
PAGE 381
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.
PAGE 382
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.
PAGE 383
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.
PAGE 384
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.
PAGE 385
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.
PAGE 386
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.
PAGE 387
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.
PAGE 388
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.
PAGE 389
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.
PAGE 390
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‖.
PAGE 391
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.
PAGE 392
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.
PAGE 393
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.
PAGE 394
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.
PAGE 395
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.
PAGE 396
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‖.
PAGE 397
List of Messages 1000 .................................................................................................................................. 33 1001 .................................................................................................................................. 33 1002 .................................................................................................................................. 34 1003 .........................................................................
PAGE 398
1062 .................................................................................................................................. 48 1095 .................................................................................................................................. 49 1096 .................................................................................................................................. 49 1097 ..........................................................................................
PAGE 399
1309 .................................................................................................................................. 67 1399 .................................................................................................................................. 68 1400 .................................................................................................................................. 68 1401 ..........................................................................................
PAGE 400
1757 .................................................................................................................................. 83 1758 .................................................................................................................................. 83 1759 .................................................................................................................................. 83 1766 ..........................................................................................
PAGE 401
1881 .................................................................................................................................. 96 1899 .................................................................................................................................. 96 2000 .................................................................................................................................. 97 2001 ..........................................................................................
PAGE 402
2055 ................................................................................................................................ 112 2056 ................................................................................................................................ 113 2057 ................................................................................................................................ 113 2058 .............................................................................................
PAGE 403
4394 ................................................................................................................................ 130 4395 ................................................................................................................................ 130 4396 ................................................................................................................................ 131 4397 .............................................................................................
PAGE 404
4552 ................................................................................................................................ 146 4553 ................................................................................................................................ 147 4554 ................................................................................................................................ 147 4555 .............................................................................................
PAGE 405
4748 ................................................................................................................................ 161 4750 ................................................................................................................................ 161 4751 ................................................................................................................................ 161 4753 .............................................................................................
PAGE 406
1014: ZASP-EVT-MON-STARTUP-ERROR ................................................................... 196 1015: ZASP-EVT-MON-OPEN-TERM-ERROR .............................................................. 197 1016: ZASP-EVT-SGP-STARTUP-FAILURE.................................................................. 197 1017: ZASP-EVT-SGP-CREATE-ERROR ...................................................................... 198 1018: ZASP-EVT-VERSION-ERROR ................................................................
PAGE 407
1234: ZASP-EVT-MON-EXPDMGR-RETRY-CNT .......................................................... 222 1235: ZASP-EVT-MON-EXPDMGR-NO-PATH .............................................................. 222 1236: ZASP-EVT-MON-EXPDMGR-PATH-STAT ........................................................... 223 1237: ZASP-EVT-MON-EXPDMGR-PATH-INFO ........................................................... 223 1238: ZASP-EVT-MON-EXPDMGR-CSM-STAT ............................................................
PAGE 408
1705: ZASP-EVT-DSK-MEASFH-TRAPPED .................................................................. 247 1706: ZASP-EVT-DSK-MEAS-INCOMPATIBLE ............................................................. 248 1707: ZASP-EVT-DSK-MEASFH-SEG-ERROR ............................................................. 248 1708: ZASP-EVT-DSK-DATA-FILE-INUSE .................................................................... 249 1709: ZASP-EVT-DSK-MAX-MEAS-REACHED ..........................................................
PAGE 409
2009: ZASP-EVT-BAD-ENFSV-TRANS-CODE .............................................................. 269 2010: ZASP-EVT-COL-STARTUP-ERROR .................................................................... 269 2011: ZASP-EVT-COL-OPEN-TERM-ERROR ............................................................... 269 2012: ZASP-EVT-OPEN-ERROR ................................................................................... 270 2013: ZASP-EVT-OPEN-INFO .............................................................
PAGE 410
3004: ZASP-EVT-TAKEOVER ........................................................................................ 292 3005: ZASP-EVT-STARTUP-MSG-NOT-RCVD ............................................................. 292 3099: ZASP-EVT-EXP-SUPPRESSED-ERRORS .......................................................... 292 4000:ZASP-EVT-STATE-DOWN-MSG ........................................................................... 293 4001: ZASP-EVT-STATE-UP-MSG ........................................................
PAGE 411
4407: ZASP-EVT-TAP-MEDIASRVOPEN-ERR .............................................................. 314 4408: ZASP-EVT-TAP-INVLSGPOPT-ERR.................................................................... 314 4409: ZASP-EVT-TAP-HANDLE-ERR ............................................................................ 315 4410: ZASP-EVT-TAP-SEGMENT-ERR ......................................................................... 315 4411: ZASP-EVT-TAP-DEVINFOLIST-ERR ................................................
PAGE 412
4595: ZASP-EVT-TMF-STATS-COUNTS ....................................................................... 335 4596: ZASP-EVT-TMF-RELOAD-PREV-CFG ................................................................ 335 4597: ZASP-EVT-TMF-MAXDOMAINS .......................................................................... 335 4598: ZASP-EVT-TMF-AUTOCONFIG-DONE ............................................................... 336 4599: ZASP-EVT-TMF-SUPPRESSED-ERRORS ...................................................
PAGE 413
4799: ZASP-EVT-CMM-SUPPRESSED-ERRORS ......................................................... 355 4800: ZASP-EVT-SWP-SSG-INITLIZ-ERROR ............................................................... 356 4801: ZASP-EVT-SWP-SSG-STARTUP-ERROR........................................................... 356 4802: ZASP-EVT-SWP-SSG-ERRORP-TEXT ................................................................ 357 4803: ZASP-EVT-SWP-SWPFILES-EXCEED19 ............................................................
PAGE 414
1826: ZASP-EVT-API-FLATSEG-ERROR ...................................................................... 383 1827: ZASP-EVT-API-FILECREATE-ERROR ................................................................ 384 1828: ZASP-EVT-API-SRVMOM-ERROR ...................................................................... 384 1829: ZASP-EVT-API-SRVCREATE-ERROR ................................................................ 385 1830: ZASP-EVT-API-SRVCOMM-ERROR .......................................................