|
|
|
The following messages are produced by the Event Management function.
Reason:
Every message that has a reply outstanding is assigned a reply identifier. The reply identifier is a numeric integer and must be specified as such. This message indicates that the replyid you specified was not numeric. The probable cause is that you omitted replyid, and the first token of the reply text was interpreted as the replyid.
Action:
Correct the replyid and attempt the reply again.
Reason:
The message you want to reply to (identified by the reply ID you specified) is not currently waiting for a reply. Probable causes are that you did not enter the reply ID correctly, or another console user has already replied to the outstanding message.
Action:
If an invalid reply ID was specified, correct the reply ID and resubmit. If another user has already replied, no further action is necessary.
Reason:
An unexpected error occurred.
Action:
This message is typically accompanied by additional messages that more fully describe the nature of the error. For assistance, contact CA Support at http://ca.com/support.
Reason:
An unexpected error occurred.
Action:
Investigate Action text, processing Actions, and the return code.
Reason:
An error occurred attempting to communicate with the console process through the CAICCI services.
Action:
Start console node xx or correct node xx so it can receive.
For NetWare:
Reason:
Event Management services are not running on the Windows NT server nnnnnnnn.
Action:
Start Event Management on the servers using the following commands:
Retry the operation. If it continues to fail, test the network connection from NetWare to the Windows NT server by using the following command:
LOAD OPRPING nnnnnnnn 2 Hello Substitute nnnnnnnnnn
with the name of the Windows NT server to which you need to check connectivity.
For assistance, contact CA Support at http://ca.com/support.
Reason:
An error occurred attempting to execute an Action.
Action:
Investigate the Action text and the return code.
Reason:
$CAIGLBL0000/opr/config/hostname/actnode.prf policy file denies this node or RUNID to submit UNIXSH or UNIXCMD message actions.
Action:
Modify the actnode.prf file to allow that node or user to submit UNIXSH or UNIXCMD type message actions.
Reason:
The specified message ID is already on the database.
Action:
Check the spelling of the message ID or select a different ID and reissue the command.
Reason:
$CAIGLBL0000/opr/config/hostname/actnode.prf policy file denies this node or runid to submit UNIXSH or UNIXCMD message Actions.
Action:
Modify the actnode.prf file to allow that node or user to submit UNIXSH or UNIXCMD type message Actions.
Reason:
The node specified is not defined, or you are sending to the same node that you are on.
Action:
Make sure the node is defined, and it is not the same node as the one you are on. Resubmit your request.
Reason:
The $CAIGLBL0000/opr/config/hostname/actnode.prf file has incorrect permissions. A nonroot user has write authority.
Action:
Change the actnode.prf permissions to -rw-r--r--.
Reason:
The value specified for the wildcard multiple character is invalid.
Action:
Correct the value entered for WCMANY and resubmit your request.
Reason:
The value specified for the wildcard single character is invalid.
Action:
Correct the value entered for WCSINGLE and resubmit your request.
Reason:
Invalid prefix option was specified for command.
Action:
Use only the following options before cmd:
Reason:
Event Manager could not start command <cmd>. Common Reasons: <rc>=2 means <cmd> not found.
Action:
For rc=2, specify the right command name, including path if not in system PATH var. Use 'net helpmsg <rc>' for more info.
Reason:
Previous command was not executed because the users were not authorized to execute command.
Action:
If user can enter commands from Event Console and Event Management security is active, create a permission rule for user for asset-type CA-CONSOLE-COMMAND.
Reason:
Too many Event Manager threads were active at one time.
Action:
If this recurs, increase 'Max # of threads' setting. For assistance, contact CA Support at http://ca.com/support.
Reason:
Event Manager could not create thread to perform Actions.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
User <user> does not have the permission to define or alter msg Actions to run on behalf of different user id.
Action:
If user should be able to do that, add permission (asset-type - CA-EVENT-RUNID).
Reason:
User <user> does not belong to Administrators group and does not have the permission to define, alter, delete, rename, and copy database records for <component>.
Action:
If the user should be able to do that, add <user> to the Administrators group.
Reason:
Command <cmd> does not support the option <opt>.
Action:
Review the documentation for the command and correct or omit the option.
Reason:
While processing an external action, Event Manager intercepted an error code <code> in function <func> in library <lib>.
Action:
Action is ignored. Correct the problem in function.
Reason:
Event Manager cannot load the Decision Support Binary (policies) file <name> that contains the msgrec and msgact definitions. Most common <rc> is 2 - file not found.
Action:
Give the correct path of the DSB file ('Copy of msg_db' setting), and restart Event.
Reason:
Event Manager could not save a copy of the policies to the specified <file>.
Action:
Verify the directory exists, drive has enough space, and userid can create file in directory.
Reason:
While processing an External Action the Event Manager could not find the requested function <func> in library <lib>.
Action:
Action is bypassed. Make sure function in Action text is correctly spelled (case sensitive).
Reason:
While processing an External Action, or 'emlib load' command the Event Manager could load the requested library <lib>. The most common reason for this message to appear is that the system cannot find the file specified. Either <lib> is misspelled or cannot be located using system PATH.
Action:
Correct the spelling, put library in the product 'bin' directory, or add a directory where library is located to system PATH.
Reason:
Event Manager user exits library <name> could not be loaded. Common <rc> 126 = The specified module could not be found.
Action:
For rc=126 correct the name in 'Name of user exits library' to name of library that exists, or make sure the directory where library located is in the system path.
Reason:
While loading user exits library <lib>, the required function <name> could not be found in library.
Action:
If the exit is not needed, then disable it by changing the setting '<name> exit control' to OFF; otherwise, add this function to library.
Reason:
Event Manager captured a program error (exception) <code> in user exit <name>.
Action:
Correct the problem in exit <name>.
Reason:
'EMEXIT <name> ON' could not be executed, the function is not defined in library.
Action:
Create a function in user exit library.
Reason:
OPRFIX program found an invalid or corrupt log record at offset <offset>.
Action:
No action is required.
Reason:
Event Manager WorldView Status Change connection to repository <name> failed.
Action:
Verify 'Repository Name' is set correctly, and consult the WorldView documentation for <rc>.
Reason:
WorldView function <name> failed with rc <rc>.
Action:
Consult the WorldView documentation for <rc>.
Reason:
Event Manager call to WIN32 function <name> failed wit rc <rc>.
Action:
Normally accompanied by other messages. Use 'net helpmsg <rc>' for more info.
Reason:
Event Manager encountered an error while processing backquote data, either because of an unmatched backquote, a command failure or timeout, an excessively long output string, or a memory shortage condition.
Action:
Modify the backquote text to correct the problem and retry.
Some common reasons and the actions to take are as follows:
Reason 1:
The message displayed due to an extract error.
Action:
No password was defined for RUNID or ‘default pswd’, and pswd cannot be extracted for Event Management Security. The userid was not defined through Event Management Security.
Reason 2:
The message displayed due to a required privilege not held by client.
Action:
Reason 3:
The message displayed due to a logon failure: unknown user name or bad password.
Action:
Provide the correct userid and password in the RUNID and RUNPSWD fields of msg-Action, or “Default user id for running cmds”/”Default pswd for running cmds” in settings.
Reason:
The expression could not be successfully evaluated due to one or more errors, such as missing parentheses, premature end of expression, or invalid operators.
Action:
Correct the expression text and retry.
Reason:
The expression could not be successfully evaluated due to one or more errors, such as missing parentheses, premature end of expression, or invalid operators.
Action:
Correct the expression text and retry.
Reason:
Option specified is not valid for CMD_NAME.
Action:
Try CMD_NAME with no options for help. See the online Reference Guide for CMD_NAME.
Reason:
The option OPTION needs a value.
Action:
Supply the missing value. Example: cawto -n -k Hello No value was supplied for option –n.
Reason:
The VALUE is not valid for option OPTION.
Action:
Supply the correct value. Example: cawto -c Indigo Hello Indigo is valid for -c option.
Reason:
Event Process or utility could not load the specified library.
Action:
This is a probable installation error, configuration error, or the product BIN directory is not in the path.
Reason:
The specified database function could not be found in library.
Action:
This is a probable installation error, configuration error, or the product BIN directory is not in the path.
Reason:
Unexpected I/O error.
Action:
This message is typically accompanied by additional messages that more fully describe the nature of the error. For assistance, contact CA Support at http://ca.com/support.
Reason:
An internal SPI error has occurred.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Unexpected error calling the named system service.
Action:
This message is typically accompanied by additional messages that more fully describe the nature of the error. For assistance, contact CA Support at http://ca.com/support.
Reason:
The sequence number is less than one or greater than 32767.
Action:
Enter a sequence number that is within the range of 1-32767.
Reason:
The indicated action cannot be performed because it requires that an associated MESSAGE RECORD profile be identified, and no identification (through MSGID or MSGTKN) was provided.
Action:
Supply a valid message ID or message token and resubmit the command.
Reason:
The valid message types are command and message; the value you specified is not one of these valid types.
Action:
Supply a valid type and resubmit the command.
Reason:
The database cannot be accessed at this time. Two common reasons are:
Action:
Using the CAIDB STATUS CAIOPRDB command, verify that the database CAIOPRDB has been started. If it has not been started, you can start it using the command:
CAIDB START CAIOPRDB
This message is typically accompanied by additional messages that more fully describe the nature of the error. Contact your system administrator to assist you in resolving the problem. For assistance, contact CA Support at http://ca.com/support.
Reason:
An error occurred while attempting to process your request as a Logical Unit of Work. This is usually indicative of a problem accessing the Event Management database CAIOPRDB.
Action:
Contact your system administrator. Typically, terminating and restarting the process that is issuing this message corrects the problem. CA Support should also be contacted because this message is usually indicative of a subtle programming error. For assistance, contact CA Support at http://ca.com/support.
Reason:
An error occurred while attempting to complete your request as a Logical Unit of Work. This is usually indicative of a problem accessing the database CAIOPRDB.
Action:
Contact your system administrator. Typically, terminating and restarting the process that is issuing this message corrects the problem. CA Support should also be contacted because this message is usually indicative of a subtle programming error. For assistance, contact CA Support at http://ca.com/support.
Reason:
This message could have multiple causes.
Action:
Verify that the database has been started. If the database has not been started, you will not be able to issue the CLOSE command. If the database has already been started, check the SQL messages and return codes and take the appropriate action.
Reason:
Command failed on the specified message ID.
Action:
Check the preceding messages and take appropriate action.
Reason:
This command failed on the specified message token.
Action:
Check the preceding messages and take appropriate action.
Reason:
An attempt was made to add a message without specifying the message ID.
Action:
Include the message ID and retry the DEFINE command.
Reason:
The message that you want to copy cannot be found.
Action:
Make sure the token for the message you want to copy is correct. If the MODEL token is correct, there could be a database problem; check the preceding messages and take appropriate action.
Reason:
This message may be the result of database contention due to heavy system usage and multiple, successive reads from the database.
Action:
Try again later.
Reason:
An invalid message token ID was probably specified.
Action:
Check the message token ID and resubmit the command.
Reason:
An error occurred while attempting to start your request as a Logical Unit of Work. This is usually indicative of a problem accessing the Event Management database CAIOPRDB.
Action:
Contact your system administrator. Typically, terminating and restarting the process that is issuing this message corrects the problem. CA Support should also be contacted because this message is usually indicative of a subtle programming error. For assistance, contact CA Support at http://ca.com/support.
Reason:
An error occurred while attempting to start your request as a Logical Unit of Work. This is usually indicative of a problem accessing the Event Management database CAIOPRDB.
Action:
Contact your system administrator. Typically, terminating and restarting the process that is issuing this message corrects the problem. CA Support should also be contacted because this message is usually indicative of a subtle programming error. For assistance, contact CA Support at http://ca.com/support.
Reason:
An error occurred while attempting to complete your request as a Logical Unit of Work. This is usually indicative of a problem accessing the database CAIOPRDB.
Action:
Contact your system administrator. Typically, terminating and restarting the process that is issuing this message corrects the problem. CA Support should also be contacted because this message is usually indicative of a subtle programming error. For assistance, contact CA Support at http://ca.com/support.
Reason:
Caused by database irregularities.
Action:
Check the SQL messages and return codes that follow to take the appropriate action.
Reason:
A request to allocate virtual memory required to generate the report you requested has failed. Typically, failures of this nature are caused by insufficient memory available to process this request. It is highly probable that additional system swap space must be allocated, or this request should be run when the system is less busy and typically, system virtual memory limits are less stressed.
Action:
Consult your system administrator. Additional swap space may need to be defined. For assistance, contact CA Support at http://ca.com/support.
Reason:
An error was encountered while attempting to process your request. The return codes indicate the probable cause.
Action:
This message is typically accompanied by additional messages that more fully describe the nature of the error. For assistance, contact CA Support at http://ca.com/support.
Reason:
The report was not initialized prior to executing the command.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Processing of the message Action indicated by message token and sequence number has failed.
Action:
This message is typically accompanied by additional messages that more fully describe the nature of the error. For assistance, contact CA Support at http://ca.com/support.
Reason:
Processing of the message Action has failed because the message Action was not properly identified. The complete message Action name, message token (MSGTKN), and sequence number (SEQNO) are required.
Action:
Supply the message token and sequence number and resubmit the command.
Reason:
An attempt to process the indicated command has failed, as an invalid value was specified for a field or consolend.
Action:
Correct the invalid field and resubmit the command.
Reason:
The message token you specified, as part of the identification of the message record with which this message Action is associated, is invalid.
Action:
Correct the token ID and resubmit your command. For assistance, contact CA Support at http://ca.com/support.
Reason:
The sequence number you specified as part of the identification of the message Action is invalid.
Action:
Correct the sequence number and resubmit your command. For assistance, contact CA Support at http://ca.com/support.
Reason:
The record to be updated cannot be found. The probable cause is that you have incorrectly identified the record to be updated.
Action:
Correct the invalid field and resubmit the ALTER command.
Reason:
The MODEL consolend can be used to identify an existing record that should be used as a template, or model, when defining a new record. The record you specified as being the model record does not exist. The probable cause is that you have incorrectly identified the record to be updated.
Action:
Correct the invalid field and resubmit the DEFINE command.
Reason:
You supplied a selection criteria that does not match any available records.
Action:
Adjust your criteria, then resubmit the SELECT command.
Reason:
Your requested template file does not exist; it may have been erased.
Action:
Make sure that the $CA_REPORT environment variable is valid. If it is and the problem persists, save the return code and contact CA Support. For assistance, contact CA Support at http://ca.com/support.
Reason:
This is an internal error.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
This is a general failure. See the accompanying message for more information.
Action:
See the Action of the accompanying message.
Reason:
User specified MSGID and MSGID on <cmd>.
Action:
User MSGID or MSGTKN to qualify record.
Reason:
The ALTER, DEFINE, or DELETE command failed, msg-token was not numeric.
Action:
Reenter the numeric msg-token.
Reason:
OPRFIX encountered an error while copying to, or renaming back a set of backup log files.
Action:
Make sure there is enough space on drive, or user running OPRFIX has write access to directory.
Reason:
OPRFIX: An error occurred attempting to open Log file <file> for processing. The path name given was wrong, the file header data was invalid, or Event Management is active.
Action:
Shutdown the Event Manager if the current log file is given or retry OPRFIX with the correct path name for log:
'c:\tngem\logs\20010215.LOG'
Reason:
An error occurred attempting to open Log file <file> for processing. The probable cause is either the path name given was wrong or the log file does not exist.
Action:
Make sure CAI_CONLOG is set correctly to $CAIGLBL0000/opr/logs in the $CAIGLBL0000/opr/scripts/envusr file and that the four $CAIGLBL0000/opr/logs/pfx.CMyymmdd files exist for the applicable date.
Note: pfx represents the log file prefix, opano, opldx, oplog, or opldx. CMyyddmm represents the year, month, and day the log file was created.
Reason:
OPRFIX encountered an error while fixing the log file because of space or because other processes were using the file.
Action:
Make sure that Event Manager is not active or make sure enough space is available on the drive for a copy of log files. Correct and retry.
Reason:
OPRFIX could not fix log file <file> because of one or more previous errors.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
OPRFIX could not truncate a corrupted log file.
Action:
Make sure that Event Manager is not active or make sure enough space is available on the drive for a copy of log files. Correct and retry.
Reason:
OPRFIX was given too many parameters.
Action:
Supply \path\filename or omit arguments for current log file, and rerun.
Reason:
An attempt was made to start a system that is already active.
Action:
This is an information message; no action is required.
Reason:
The CAOPT parameter that is set for this feature may be set to an invalid value.
Action:
Check the parameter in CAOPT script and verify the value. If a change is needed an OPRELOAD will have to be run to make the changes effective. For assistance, contact CA Support at http://ca.com/support.
Reason:
This message indicates that an error was returned by the CAICCI.
Action:
This message is typically accompanied by additional messages that more fully describe the nature of the error. For assistance, contact CA Support at http://ca.com/support. For error code definitions, see Primary, Secondary and Error Codes.
Reason:
The prelog filtering or burst suppression detection process could not open the specified collector.
Action:
Check the error code returned by the message and take the appropriate action.
Reason:
An attempt to reload the incore images of the Event Management policies defined in the CAIOPRDB database has failed.
Action:
This message is typically accompanied by additional messages that more fully describe the nature of the error. For assistance, contact CA Support at http://ca.com/support.
Reason:
This will only occur the first time you run Event Management on NetWare and indicates that Event Management has not been started on the Windows NT server.
Action:
Start Event Management on the Windows NT server.
Reason:
The Event Management function has detected that one of the environment variables that identify key processing control options is not properly set. This is usually indicative of Event Management not being started properly.
Action:
Contact your system administrator who should confirm that the Event Management function was started correctly. For assistance, contact CA Support at http://ca.com/support. If Event Management was started correctly, then examine Event Management configuration options, accessible from the Configuration folder window.
Reason:
An unexpected internal error condition has been detected.
Action:
This message is typically accompanied by additional messages that more fully describe the nature of the error. For assistance, contact CA Support at http://ca.com/support.
Reason:
This occurs when CAICCI is not started on the NetWare machine.
Note: This error can also occur on the Windows NT machine.
Action:
Start CAICCI on the platform on which the error occurred through the following command: LOAD UNISTART
Reason:
A request to allocate virtual memory required to process has failed. Typically, failures of this nature are caused by insufficient memory available to process this request.
Action:
Consult your system administrator. For assistance, contact CA Support at http://ca.com/support.
Reason:
One or more of the valid SPI tokens entered for the message records was invalid.
Action:
Verify that all of the SPI tokens are valid, and fix the message record definitions. Issue another OPRELOAD command. For assistance, contact CA Support at http://ca.com/support.
Reason:
There was an error code in the filtering process.
Action:
Check the sqlcode error code by using the SQLCI interface or in the TANDEM documentation for SQL errors. Fix the problem and reissue.
Reason:
The Event Management service provider deleted the specified console log file during clean-up processing. The log file name can be defined as follows:
Action:
This is an informational message; no action is required.
Reason:
This message displays the syntax of the command entered.
Action:
This is an informational message; no action is required.
Reason:
This message displays the syntax of the command entered.
Action:
This is an informational message; no action is required.
Reason:
This message displays the syntax of the command entered.
Action:
This is an informational message; no action is required.
Reason:
This message displays syntax of the command entered.
Action:
This is an informational message; no action is required.
Reason:
This message is issued when a user wants to simulate an Action in response to a console message. The effect of the Action is shown without actually performing the Action.
Action:
This is an informational message; no action is required.
Reason:
This message is issued when a user wants to simulate an Action in response to a console message. The effect of the Action is shown without actually performing the Action.
Action:
This is an informational message; no action is required.
Reason:
The OPRFIX utility has completed processing and the status of the identified log file is displayed. The OPRFIX utility can be used to repair damaged console log files. If the log file is successfully fixed, the number of patches applied to the file is displayed in the message.
Action:
This is an informational message; no action is required.
Reason:
Response after start-up or OPRELOAD command. Event Manager was directed to load policies from a DSB file and not from database.
Action:
This is an informational message; no action is required.
Reason:
Response to 'emlib status' command. <used> specifies the number of times the library was used by an EXTERNAL action.
Action:
This is an informational message; no action is required.
Reason:
Response to 'emlib free' command, or during shutdown.
Action:
This is an informational message; no action is required.
Reason:
Response to 'emlib load ' command.
Action:
This is an informational message; no action is required.
Reason:
Response to "EMEXIT <name> ON' command.
Action:
This is an informational message; no action is required.
Reason:
Response to "EMEXIT <name> OFF' command.
Action:
This is an informational message; no action is required.
Reason:
Response to "EMEXIT status' command.
Action:
This is an informational message; no action is required.
Reason:
Response to "EMEXIT status' command.
Action:
This is an informational message; no action is required.
Reason:
Response to "EMEXIT status' command. <Reason> can be:
Action:
For ExitError, correct exit <name> in the library.
Reason:
Response to "EMEXIT status' command.
Action:
Examine exits that have <#errors> greater than 0.
Reason:
Response to 'EMEXIT status' or during start-up. <errors> indicates the maximum number of errors allowed before any exit in library is disabled.
Action:
This is an information message; no action is required.
Reason:
OPRFIX did not find any errors in the log file; its index files were compressed and rebuilt.
Action:
This is an informational message; no action is required.
Reason:
EMUSER logoff or Event Management shutdown.
Action:
This is an informational message; no action is required.
Reason:
EMUSER status response.
Action:
This is an informational message; no action is required.
Reason:
Command <cmd> could find a match for <object> or <mask>.
Action:
No object exists. Reenter the new <mask> or <object> if not typed correctly.
Reason:
Event Manager WorldView Status Change monitors reports status change for <object>.
Action:
No Event Management Action is needed. Refer to the <class> and <object> component for further information.
Reason:
Displayed during 'EMPOEMS Stat' or 'EMPOEMS Stop' command if the POEMS interface is not active.
Action:
This is an information message; no action is required.
Reason:
Displayed during Event Manager startup or during EMPOEMS Start and Stat commands if POEMS interface is active. <type> can be All or Selective.
Action:
This is an informational message; no action is required.
Reason:
Displayed as a result of ‘EMPOEMS Stat’ command. <SINCE> the locale-specific date and time the POEMS interface was started. It is the Event Manager Daemon start time or time the last ‘EMPOEMS Start’ was successfully executed. <#EVENTS> indicates the number of events forwarded to POEMS for processing since the interface was started.
Action:
This is an informational message; no action is required.
Reason:
Displayed as a result of ‘EMPOEMS Start’ command. <USERID> is the userid that tried to start the POEMS interface.
Action:
This is an informational message; no action is required.
Reason:
Displayed as a result of ‘EMPOEMS Stop’ command. <USERID> is the userid that tried to stop the POEMS interface.
Action:
This is an informational message; no action is required.
Reason:
This message may be logged when a held message is acknowledged or replied to AND the 'CAOP_I_ACKED' is trapped by one or more policy records.
Action:
To disable logging of this message, add a DISCARD Action to the policy record used to trap this message.
Reason:
The Burst Suppression feature has started for the collector xx.
Action:
This is an informational message; no action is required.
Reason:
This message displays after the completion of process initialization and indicates to the server that the process was initialized.
Action:
This is an informational message; no action is required.
Reason:
The Event Management process is shutting down in response to receiving a signal. This message may also be issued in response to a STOPUNI command.
Action:
This is an informational message; no action is required.
Reason:
The reloading of incore images of the Event Management policies defined in the CAIOPRDB database has completed successfully. The reload is typically performed during initialization of the Event Management process and in response to a opreload command being entered through the console dialog, or the OPRCMD command.
Action:
This is an informational message; no action is required.
Reason:
A console message that had a reply pending, or was sent to the console with a keep option, has been deleted or answered.
Action:
This is an informational message; no action is required.
Reason:
This message indicates that the Event Management process responsible for receiving console messages has completed initialization and is ready to process.
Action:
This is an informational message; no action is required.
Reason:
This message indicates that during startup, the Event Management message reader process found that a pid file existed for a previously active message reader process. Further analysis indicated, however, that the process identified through the pid (Process ID included in the message) is no longer active. This is usually caused by an untimely system shutdown that caused the prior message process pid file to be left intact (it is cleaned up during normal shutdown). The Event Management message reader process will continue initialization and correct the pid file automatically.
Action:
This is an informational message; no action is required.
Reason:
The Event Management message reader process is shutting down in response to receiving a soft kill (signal 15). This message may also be issued in response to a unishutdown command.
Action:
This is an informational message; no action is required.
Reason:
The prelog filtering feature has started against the collector xxx.
Action:
This is an informational message; no action is required.
Reason:
A message that had an outstanding reply pending has had that reply satisfied by the named user at the indicated time.
Action:
This is an informational message; no action is required.
Reason:
The console process was started with the NODB parameter, or the database is not started.
Action:
This is an informational message; no action is required.
Reason:
The Event Management service provider could not delete the specified console log file during clean-up processing. The log file name <file> can be defined as follows:
Common RC values are as follows:
Action:
Check the RC (return code) value for the Reason, and correct as necessary:
NET HELPMSG rc
/usr/include/errno.h
Reason:
The console log for the date requested does not exist.
Action:
Investigate CAI_CONLOG preference and existence of console log and index file.
Reason:
An attempt was made to perform an Action against an unknown message ID or message token.
Action:
Supply a valid message ID or message token and resubmit the command.
Reason:
An invalid sequence number was supplied.
Action:
Supply a valid sequence number and resubmit.
Reason:
A record has been selected, but no commands have been performed on this record.
Action:
Perform the appropriate action on the selected record.
Reason:
A command was issued without first selecting a target record.
Action:
Select a target record and resubmit this command.
Reason:
You tried a CAUTIL function (delete, list, or alter something) and it could not be found on the specified database.
Action:
Select another record and resubmit this command.
Reason:
The console process was not able to send a message to the daemon.
Action:
This message is followed by a more specific message (CAOP_W_108) indicating the cause of the problem. Refer to the action of message CAOP_W_108.
Reason:
The console process could not send a message to the process because an error was returned by the CAICCI. This typically results when there is “no receiver online.”
Action:
Issue the UNISTART OPR command.
Reason:
The console process received this return code from the Netware Client API function. This occurred while attempting to set extended attributes for Console Log files existing on a mapped Netware drive.
Action:
This is an informational message; no action is required.
Reason:
Event Management user exit <exit> had more program errors (exceptions) than allowed by setting "Number of errors allowed per exit."
Action:
Run Event Management in debug mode (set "OPR Trace" to 1) and debug the user exit in error.
Reason:
Invalid exit name was entered on 'EMEXIT <exit> {ON|OFF}' command.
Action:
Use one of the following for the exit name:
Reason:
Cannot use EMEXIT command because no user exit library was loaded.
Action:
Change "Name of user exits library" setting to the path of Event Management user exits library, and restart Event.
Reason:
OPRFIX utility truncated the corrupted log file <file> after last readable record, new size is <size>.
Action:
No action is required.
Reason:
The number of GOTO Actions executed exceeded <max> (setting 'Max # of GOTO Actions executed per match'), which can happen when GOTO Actions are used without stop condition. Example: '100 SENDOPER text', '200 GOTO 100'.
Action:
Remove the GOTO Action, or add condition (condop, condrc) to limit the number.
Reason:
The token value or token name entered into the message record is in the wrong format.
Action:
Check the message record and the format of the token to make sure it is correct. Reissue the message record and action.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |