17.08.2013 Views

System i: Programming Message Handling APIs - IBM

System i: Programming Message Handling APIs - IBM

System i: Programming Message Handling APIs - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Number of message queues used. The number of message queues listed. This is the number of elements<br />

in the message queue names used, starting message key used, and ending message key arrays.<br />

Number of receiving statement numbers or instruction numbers available followed by an array of the<br />

receiving statement numbers or instruction numbers. This field can be specified for the QMHLSTM API,<br />

but it never returns any data and the length of data field is 0.<br />

Number of sending statement numbers or instruction numbers available followed by an array of the<br />

sending statement numbers or instruction numbers. This field can be specified for the QMHLSTM API,<br />

but it never returns any data and the length of data field is 0.<br />

Offset to ending message key. The offset, in bytes, from the beginning of the user space to the beginning<br />

of the ending message key field.<br />

Offset to fields returned. The offset, in bytes, from the beginning of the user space to the beginning of<br />

the first repeating identified field of the LSTM0100 format.<br />

Offset to identifiers of fields to return. The offset, in bytes, from the beginning of the message selection<br />

information parameter to the beginning of the identifiers of fields to return field.<br />

Offset to identifiers of fields to return specified. The offset, in bytes, from the beginning of the user<br />

space to the beginning of the identifiers of fields to return specified field.<br />

Offset to message queue names specified. The offset, in bytes, from the beginning of the user space to<br />

the beginning of the message queue names specified field.<br />

Offset to message queue names used. The offset, in bytes, from the beginning of the user space to the<br />

beginning of the message queue names used field.<br />

Offset to qualified message queue names. The offset, in bytes, from the beginning of the message<br />

selection information parameter to the beginning of the qualified message queue names field.<br />

Offset to starting message keys. The offset, in bytes, from the beginning of the message selection<br />

information parameter to the beginning of the starting message key field.<br />

Offset to starting message key specified. The offset, in bytes, from the beginning of the user space to the<br />

beginning of the starting message key specified field.<br />

Offset to starting message key used. The offset, in bytes, from the beginning of the user space to the<br />

beginning of the starting message key used field.<br />

Offset to the next entry. The offset, in bytes, from the beginning of the user space to the beginning of the<br />

next message entry.<br />

Offset to the next field information returned. The offset, in bytes, from the beginning of the user space<br />

to the beginning of the next repeating identified field of the LSTM0100 format.<br />

Problem identification. The number the system generates to identify a problem if problem analysis can<br />

be run for the message being listed. The problem identification is in the following format:<br />

CHAR 1-10 Problem ID number. The number the system generates to identify the problem.<br />

CHAR 11-30 Origin system in the format network-ID.control-point-name.<br />

If problem analysis cannot be run, and this field is specified, the length of data field is 0.<br />

<strong>Message</strong> <strong>Handling</strong> <strong>APIs</strong> 43

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!