Chapter 79 QIO (QIO Monitor) Messages

The messages in this chapter are sent by the QIO Monitor subsystem. The subsystem ID displayed by these messages includes ZQIO as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

Object available Segment - segment-name:sequence-no, event number:1, reason: event-reason,previous state: previous-state,current state: current-state, user content:

`segment-name`	is the name of the memory segment for which the QIO Monitor generated this error.
`sequence-no`	is the sequence number from the Phandle. This number increments each time the QIO Monitor is started.
`event-reason`	describes the reason for the error. This field displays “internal failed” or “operator initiated.”
`previous-state`	indicates the state of the QIO Monitor before this error occurred.
`current-state`	indicates the state of the QIO Monitor after this error occurred.
content	May or may not be undefined.

Cause The system has initialized the QIO segment, and the Monitor object is ready. The QIO Monitor also generates this message when it receives a Configuration Utility Program (COUP) STOP command, and the QIO Monitor finds active client processes using the shared segment.

Effect The symptom string “T8671 - QIOMON - Unable to Stop Because of Active Client Processes” is displayed if a COUP STOP command was received; otherwise, no symptom string is displayed and no corrective action is needed.

Recovery If the symptom string is displayed, use the NAMES command to show current APPLs and then stop them. Once no APPLs are displayed, the QIO Monitor accepts a COUP STOP command. Use the COUP STOP! command to force the Monitor to stop.

Object unavailable Segment - segment-name:sequence-no, event number:2, cause: event-reason,previous state: previous-state,current state: current-state, user content: undefined

`segment-name`	is the name of the memory segment for which the QIO Monitor generated this error.
`sequence-no`	is the sequence number from the Phandle. This number increments each time the QIO Monitor is started.
`event-reason`	describes the reason for the error. This field displays “internal failed” or “operator initiated.”
`previous-state`	indicates the state that the QIO Monitor was in before this error occurred.
`current-state`	indicates the state of the QIO Monitor after the error occurred.

Cause The cause for this error message is operator-initiated by a Configuration Utility Program (COUP) STOP command. The event-reason can be one of the following:

Cause	Meaning
The amount of memory QIO needed is too large or the memory MemoryPercent parameter is too small.	The symptom string “T8671 - QIOMON - Not Enough Unlocked Memory in CPU to Start” is displayed in the error message.
The Priority parameter is not in the range of 0 through 255.	The symptom string “T8671 - QIOMON - Unable to Set Priority” is displayed in the error message.
The PoolSize parameter is wrong.	The symptom string “T8671 - QIOMON - Unable to Create Module ID” is displayed in the error message.
The MDCount parameter is wrong.	The symptom string “T8671 - QIOMON - Unable to Create MD List” is displayed in the error message.
The MessageSizes or MessageCounts parameters are wrong.	The symptom string “T8671 - QIOMON - Unable to Create Message Lists” is displayed in the error message.
The QIO Monitor received a QIO error from another process and detected that another process has corrupted the shared segment. The QIO Monitor wishes to stop the segment from being used.	The symptom string “T8671 - QIOMON - Bad Segment Event Received” is displayed in the error message.

Effect The QIO segment is unavailable for use by client applications and the QIO Monitor sets the segment to the STOPPING state.

Recovery Edit the ZMxxxx file used for QIOMON’s InFile or specify another InFile. See the causes described above for the InFile parameters that need to change. If the symptom string is “Not Enough Unlocked Memory In CPU to Start,” reduce memory by lowering the PoolSize, MDCount, and MessageCounts in the InFile. Use the PEEK utility to see how much memory is available in the processor. If you receive the symptom string “Bad Segment Event Receive,” restart QIO.

Buffer shortage occurred nn times in last 3 minutes.

nn	is the number of times that the error occurred.

Cause The QIO Library decremented a buffer count to 0. This condition may occur often, so errors after the initial error are accumulated and reported approximately every 3 minutes.

Effect None.

Recovery Reconfigure the QIO Monitor with larger values for the MessageNCount parameters.

MD shortage shortage occurred nn times in last 3 minutes.

nn	is the number of times that the error occurred.

Cause The QIO Library decremented the MD count to 0. This condition may occur often, so errors after the initial error are accumulated and reported approximately every 3 minutes.

Effect None.

Recovery Reconfigure the QIO Monitor with a larger value for the MDCount parameter.

Pool shortage occurred nn times in last 3 minutes.

nn	is the number of times that the error occurred.

Cause The QIO Library has declined a pool request. This condition may occur often, so errors after the initial error are accumulated and reported approximately every 3 minutes.

Effect None.

Recovery Reconfigure the QIO Monitor with a larger value for the PoolSize parameter.