Air Cleaner User Manual

Status for all channels that meet the selection criteria is given, whether the
channels were defined manually or automatically.
Before explaining the syntax and options for this command, it is necessary to
describe the format of the status data that is available for channels and the states
that channels can have.
There are three classes of data available for channel status. These are saved,
current, and (on OS/390 only) short.
The status fields available for saved data are a subset of the fields available for
current data and are called common status fields. Note that although the common
data fields are the same, the data values might be different for saved and current
status. The rest of the fields available for current data are called current-only status
fields.
v Saved data consists of the common status fields noted in the syntax diagram.
This data is reset at the following times:
– For all channels:
- When the channel enters or leaves STOPPED or RETRY state
- On AIX, HP-UX, OS/2 Warp, OS/400, Sun Solaris, and Windows NT, when
the queue manager is ended
– For a sending channel:
- Before requesting confirmation that a batch of messages has been received
- When confirmation has been received
– For a receiving channel:
- Just before confirming that a batch of messages has been received
– For a server connection channel:
- No data is saved
Therefore, a channel that has never been current cannot have any saved status.
Note: Status is not saved until a persistent message is transmitted across a
channel, or a nonpersistent message is transmitted with a NPMSPEED of
NORMAL. Because status is saved at the end of each batch, a channel will
not have any saved status until at least one batch has been transmitted.
v Current data consists of the common status fields and current-only status fields
as noted in the syntax diagram. The data fields are continually updated as
messages are sent/received.
v Short data consists of the STATUS current data item and the short status field as
noted in the syntax diagram.
This method of operation has the following consequences:
v An inactive channel might not have any saved status – if it has never been
current or has not yet reached a point where saved status is reset.
v The “common” data fields might have different values for saved and current
status.
v A current channel always has current status and might have saved status.
Channels can be current or inactive:
Current channels
These are channels that have been started, or on which a client has
connected, and that have not finished or disconnected normally. They
might not yet have reached the point of transferring messages, or data, or
DISPLAY CHSTATUS
Chapter 2. The MQSeries commands 159
|
|
|
|