QIO Configuration and Management Manual

QIO SCF Error Messages
QIO Configuration and Management Manual—424717-008
A-4
00002 Object
previous-state
indicates the state that the QIOMON process was in before this event occurred.
current-state
indicates the state of the QIOMON process after the event occurred.
Cause. The cause for this event message can be one of the following:

The amount of memory QIO needs for use is too large or the MemoryPercent
parameter is too small. If one of these is the cause, the symptom string “T8671 -
QIOMON - Not Enough Unlocked Memory in CPU to Start” is displayed in the
event message.

The Priority parameter is not in the range 0 through 255. If this is the cause, the
symptom string “T8671 - QIOMON - Unable to Set Priority” is displayed in the
event message.

The PoolSize parameter is too large or too small. If this is the cause, the symptom
string “T8671 - QIOMON - Unable to Create Module ID” is displayed in the event
message.

An invalid value is configured in the QIO configuration file. If this is the case, the
event message contains the symptom string “T8671 - QIOMON - Invalid value
value for parameter name was detected in the configuration file. Valid values
are lower-limit to upper-limit.”

An unknown keyword is contained in the QIO configuration file. If this is the case,
the symptom string “T8671 - QIOMON - Unknown token token was detected in
the configuration file” is displayed in the event message.

The QIOMON process received a QIO event from another process and detected
that another process has corrupted the shared segment. The QIOMON process
wishes to stop the segment from being used. If this is the case, the symptom string
“T8671 - QIOMON - Bad Segment Event Received” is displayed in the event
message.
Effect. The QIO segment is unavailable for use by client applications, and the
QIOMON process sets the segment to the STOPPING state.
Recovery. If the symptom string is “Not Enough Unlocked Memory In CPU to Start,”
you can reduce memory by lowering the initial PoolSize or MemoryPercent values in
the QIO configuration file. You can use PEEK to see how much memory is available in
the processor. If the symptom string is “Unable to Set Priority,” retry the action that
caused the event message; if the error reoccurs, either change the priority value in the
QIO configuration file or call your support representative. If the symptom string is
“Unable to Create Module ID,” report the error to your support representative. If the
symptom string is “Invalid value,” correct the specified value in the QIO configuration
file. If the symptom string is “Unknown token,” check the QIO configuration file for
spelling or syntax errors. If the symptom string is “Bad Segment Event Received,” stop
the QIO client processes and restart them.