These are error messages that may be generated by the jobs running on the Ironstream Agent for IBM i:
|
Message ID |
EVM0001 |
|
Text |
Invalid Reply. Please contact your System Administrator |
|
Description |
A reply was sent for a message that is not on the queue, perhaps because the message had already been answered |
|
Inserts |
None |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
Processing continues |
|
User Action |
Contact your system administrator to reply to the message on the agent |
|
Message ID |
EVM0007 |
|
Text |
queue limit reached, queue cleared |
|
Description |
Maximum number of records were written to the queue. This is most likely due to the Management Server not being connected to the agent |
|
Inserts |
queue Name of queue |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
Queue is cleared. Processing continues |
|
User Action |
If this appears repeatedly, contact Precisely support |
|
Message ID |
EVM0015 |
|
Text |
***WARNING*** Processing has ended due to the possible loss of connectivity |
|
Description |
This message is generated when a data queue requires clearing. The message gives the option of (A) clearing the data queue, or (B) ending the EVSBS subsystem entirely |
|
Inserts |
None |
|
Severity |
99 |
|
Type |
Inq |
|
System Action |
Clearing the queue or ending the subsystem |
|
User Action |
Respond "A" or "B" to the message |
|
Message ID |
EVM0017 |
|
Text |
Message queue queue was not cleared |
|
Description |
The request to clear the message queue failed |
|
Inserts |
queue Name of queue |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
Processing continues |
|
User Action |
Run the CLRMSGQ command manually to find the error explaining why the clear attempt failed |
|
Message ID |
EVM0100 |
|
Text |
EVCMSG: Error converting version message, return code- code |
|
Description |
An error occurred when executing character set conversion functions |
|
Inserts |
code Return code from EVTCTLPROC job |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
The EVTCTLPROC job terminates |
|
User Action |
Look for an error message in the EVIEW/EVTRACE output queue from the EVTCTLPROC job. Contact Precisely support |
|
Message ID |
EVM0101 |
|
Text |
port : Invalid or missing value in parameter |
|
Description |
The port parameter does not exist in the EVPARMS file or the value is not a valid numeric value |
|
Inserts |
port Port value read from the EVPARMS file |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
The EVTCTLPROC job terminates |
|
User Action |
Correct the parameter and restart the agent |
|
Message ID |
EVM0160 |
|
Text |
EVCQSCAN: Invalid scan interval specified - setting to 5 seconds |
|
Description |
The scan interval specified for the EV400_QSCAN_INTERVAL is not a valid numeric value |
|
Inserts |
None |
|
Severity |
20 |
|
Type |
Info |
|
System Action |
Default value is used and processing continues |
|
User Action |
Correct the parameter and restart the subsystem |
|
Message ID |
EVM0161 |
|
Text |
EVCQSCAN: Failed creating message queue configuration user space, exception code msg |
|
Description |
The creation of a user space for the EVMSGQMON job failed |
|
Inserts |
msg Error message ID of the creation attempt |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
The EVMSGQMON job terminates |
|
User Action |
Consult IBM documentation for explanation of the msg |
|
Message ID |
EVM0162 |
|
Text |
EVCQSCAN: Unable to open EVMSGQCFG file |
|
Description |
The message queue configuration file EVMSGQCFG could not be opened |
|
Inserts |
None |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
The EVCQSCAN job terminates |
|
User Action |
Verify that the EVMSGQCFG file exists in the EVIEW library. Redistribute message queue configuration from the server if necessary |
|
Message ID |
EVM0163 |
|
Text |
EVCQSCAN: Message queue table exceeds maximum size |
|
Description |
The internal table for holding message queues has exceed the maximum allocated size (100 queue names) |
|
Inserts |
None |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
Processing continues. No further queue names are added |
|
User Action |
Contact Precisely support |
|
Message ID |
EVM0164 |
|
Text |
EVCQSCAN: Failed creating message filter user space, exception code - msg |
|
Description |
The creation of a user space for the EVMSGQMON job's message filter table failed. |
|
Inserts |
msg Error message ID of the creation attempt |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
The EVCQSCAN job terminates |
|
User Action |
Consult IBM documentation for explanation of the msg |
|
Message ID |
EVM0165 |
|
Text |
EVCQSCAN: Message filter table exceeds maximum size |
|
Description |
The message filter table exceeds the allocated maximum size (2000 message IDs) |
|
Inserts |
None |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
Processing continues. No further message IDs are added |
|
User Action |
Contact Precisely support |
|
Message ID |
EVM0166 |
|
Text |
EVCQSCAN: Invalid line in EVMSGQSCF - value |
|
Description |
An invalid line was read from the EVMSGQCFG file |
|
Inserts |
value The keyword containing the erroneous value |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
The EVMSGQMON job terminates |
|
User Action |
Verify the value conforms to syntax rules. Re-distribute the configuration from the server if necessary |
|
Message ID |
EVM0167 |
|
Text |
EVCQSCAN: Message queue name not found |
|
Description |
EVCQSCAN could not find the message queue on this system |
|
Inserts |
name The library/queue name |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
The EVMSGQMON job terminates |
|
User Action |
Either create the message queue, or correct and re-distribute the list of message queues from the server |
|
Message ID |
EVM0170 |
|
Text |
EVC070: Error creating status poll user space - Exception ID: msg |
|
Description |
The creation of a user space for the EVSRSCPROC job's message filter table failed |
|
Inserts |
msg Error message ID of the creation attempt |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
The EVSRSCPROC job terminates |
|
User Action |
Consult IBM documentation for explanation of the msg |
|
Message ID |
EVM0400 |
|
Text |
EView/400 Health Check Message |
|
Description |
This message is generated when the EVHEALTHCK program is called to generate a heartbeat message |
|
Inserts |
None |
|
Severity |
0 |
|
Type |
Info |
|
System Action |
Processing continues |
|
User Action |
None |
|
Message ID |
EVM4444 |
|
Text |
Cannot allocate file file |
|
Description |
Restoration of default configuration file failed |
|
Inserts |
file File name |
|
Severity |
99 |
|
Type |
Info |
|
System Action |
Processing continues |
|
User Action |
Release the lock on file and try your operation again |
|
Message ID |
EVM5555 |
|
Text |
There is a lock on the EVIEW library. Verify that the EVSBS subsystem is ended |
|
Description |
This message is generated if there is a failure in the conversion of older versions of the configuration files to the current version |
|
Inserts |
None |
|
Severity |
99 |
|
Type |
Inq |
|
System Action |
The conversion process terminates |
|
User Action |
Enter "I" to continue or "C" to cancel |
|
Message ID |
EVM7060 |
|
Text |
Invalid object olib / oname / omem removed from monitoring in journal jlib / jname . |
|
Description |
Either the object oname with member omem does not exist on this system, or it does exist and is not being journaled to jname |
|
Inserts |
olib Object library oname Object Name omem Object member jlib Journal library jname Journal name |
|
Severity |
40 |
|
Type |
Info |
|
System Action |
The object is removed from monitoring in this journal |
|
User Action |
Either remove the olib/ oname (omem) object from the monitor configuration, or start journaling the object to journal jname. Then, re-distribute the journal configuration(s) using the Ironstream IBM i Configuration Tool, or restart the subsystem to restore the monitoring of this object |