MQ/204 monitoring and troubleshooting - Revision history

ELowell at 20:33, 27 October 2017

2017-10-27T20:33:39Z

← Older revision		Revision as of 20:33, 27 October 2017
Line 80:		Line 80:
	<tr>		<tr>
	<td>5</td>		<td>5</td>
	<td>WebSphere MQ ~~A PI~~ level MQCONN failed. $STATUSD is set to the WebSphere MQ reason code.		<td>WebSphere MQ API level MQCONN failed. $STATUSD is set to the WebSphere MQ reason code.
	</td>		</td>
	<td>		<td>
Line 133:		Line 133:
	<tr>		<tr>
	<td>9</td>		<td>9</td>
	<td>WebSphere MQ ~~A PI~~ level MQOPEN failed. $STATUSD is set to the WebSphere MQ reason code.		<td>WebSphere MQ API level MQOPEN failed. $STATUSD is set to the WebSphere MQ reason code.
	</td>		</td>
	<td>OPEN QUEUE</td>		<td>OPEN QUEUE</td>
Line 171:		Line 171:
	<tr>		<tr>
	<td>12</td>		<td>12</td>
	<td>WebSphere MQ ~~A PI~~ level MQGET failed. $STATUSD is set to the WebSphere MQ reason code.</td>		<td>WebSphere MQ API level MQGET failed. $STATUSD is set to the WebSphere MQ reason code.</td>
	<td>		<td>
	MQGET</td>		MQGET</td>
Line 187:		Line 187:
	<tr>		<tr>
	<td>15</td>		<td>15</td>
	<td>WebSphere MQ ~~A PI~~ level MQPUT failed. $STATUSD is set to the WebSphere MQ reason code.</td>		<td>WebSphere MQ API level MQPUT failed. $STATUSD is set to the WebSphere MQ reason code.</td>
	<td>MQPUT</td>		<td>MQPUT</td>
	</tr>		</tr>
	<tr>		<tr>
	<td>16</td>		<td>16</td>
	<td>WebSphere MQ ~~A PI~~ level MQPUT1 failed. $STATUSD is set to the WebSphere MQ reason code.		<td>WebSphere MQ API level MQPUT1 failed. $STATUSD is set to the WebSphere MQ reason code.
	</td>		</td>
	<td>MQPUT1</td>		<td>MQPUT1</td>
Line 203:		Line 203:
	<tr>		<tr>
	<td>18</td>		<td>18</td>
	<td>WebSphere MQ ~~A PI~~ level MQCMIT failed. $STATUSD is set to the WebSphere MQ reason code.		<td>WebSphere MQ API level MQCMIT failed. $STATUSD is set to the WebSphere MQ reason code.
	</td>		</td>
	<td>MQCMIT</td>		<td>MQCMIT</td>

ELowell: /* Measuring MQGET calls with the WAIT options */

2015-12-17T16:57:56Z

Measuring MQGET calls with the WAIT options

← Older revision		Revision as of 16:57, 17 December 2015
Line 877:		Line 877:
	</tr>		</tr>
	</table>		</table>

			==See also==
			{{Template: MQ/204 topic list}}

	[[Category:MQ/204]]		[[Category:MQ/204]]

ELowell at 20:46, 11 November 2015

2015-11-11T20:46:21Z

← Older revision		Revision as of 20:46, 11 November 2015
Line 844:		Line 844:
	<tr>		<tr>
	<td>MQAPICNT </td>		<td>MQAPICNT </td>
	<td>Number of MQAPI waits performed. See [[#WebSphere MQ API wait types access control\|WebSphere MQ API wait types access control]].		<td>Number of MQAPI waits performed. See [[MQ/204 queue management#WebSphere MQ API wait types access control\|WebSphere MQ API wait types access control]].
	</td>		</td>
	</tr>		</tr>
	<tr>		<tr>
	<td>MQAPITIM</td>		<td>MQAPITIM</td>
	<td>Elapsed time spent in MQAPI waits. See [[#WebSphere MQ API wait types access control\|WebSphere MQ API wait types access control]].</td>		<td>Elapsed time spent in MQAPI waits. See [[MQ/204 queue management#WebSphere MQ API wait types access control\|WebSphere MQ API wait types access control]].</td>
	</tr>		</tr>
	</table>		</table>
Line 862:		Line 862:
	<tr>		<tr>
	<td>MQGWTCNT</td>		<td>MQGWTCNT</td>
	<td>Number of MQGWT waits performed for MQGET calls with the WAIT option and a finite WAIT_TIME value specified. See [[#WebSphere MQ API wait types access control\|WebSphere MQ API wait types access control]].</td>		<td>Number of MQGWT waits performed for MQGET calls with the WAIT option and a finite WAIT_TIME value specified. See [[MQ/204 queue management#WebSphere MQ API wait types access control\|WebSphere MQ API wait types access control]].</td>
	</tr>		</tr>
	<tr>		<tr>
Line 870:		Line 870:
	<tr>		<tr>
	<td>MQGWTTIM</td>		<td>MQGWTTIM</td>
	<td>Elapsed time spent in MQGWT waits done for MQGET calls with the WAIT option and a finite WAIT_TIME value specified. See [[#WebSphere MQ API wait types access control\|WebSphere MQ API wait types access control]].</td>		<td>Elapsed time spent in MQGWT waits done for MQGET calls with the WAIT option and a finite WAIT_TIME value specified. See [[MQ/204 queue management#WebSphere MQ API wait types access control\|WebSphere MQ API wait types access control]].</td>
	</tr>		</tr>
	<tr>		<tr>

ELowell: /* $STATUS return codes */

2015-11-11T20:41:07Z

$STATUS return codes

← Older revision		Revision as of 20:41, 11 November 2015
Line 12:		Line 12:
	===$STATUS return codes===		===$STATUS return codes===
	<p>		<p>
	The following table lists the $STATUS return code values and text that is used for all MQ/204 SOUL statements. See [[SOUL ~~statement reference~~]] for a detailed description of each statement.</p>		The following table lists the $STATUS return code values and text that is used for all MQ/204 SOUL statements. See [[MQ/204 and SOUL statements]] for a detailed description of each statement.</p>
	<p>		<p>
	When an error can be returned by more than one statement, it has the same $STATUS value for all statements that can raise that error. This practice allows you to write a generic SOUL routine that is an error handler for all MQ/204 statements.</p>		When an error can be returned by more than one statement, it has the same $STATUS value for all statements that can raise that error. This practice allows you to write a generic SOUL routine that is an error handler for all MQ/204 statements.</p>

ELowell: Created page with "==Overview== This topic discusses:

Installation considerations particular to MQ/204

Tools available within Model 204 to develop and debug MQ/204 applications..."

2015-11-11T16:07:11Z

Created page with "==Overview== This topic discusses: <ul> <li>Installation considerations particular to MQ/204</li> <li>Tools available within Model 204 to develop and debug MQ/204 applications..."

New page

==Overview==
This topic discusses:
<ul>
<li>Installation considerations particular to MQ/204</li>
<li>Tools available within Model 204 to develop and debug MQ/204 applications</li>
</ul>

==Error handling with $STATUS and $STATUSD==

$STATUS is the primary return code and $STATUSD is an ancillary or secondary return code. Certain $STATUS return codes automatically generate a $STATUSD return code. For other $STATUS return codes, the value of $STATUSD is 0.

===$STATUS return codes===

The following table lists the $STATUS return code values and text that is used for all MQ/204 SOUL statements. See [[SOUL statement reference]] for a detailed description of each statement.

When an error can be returned by more than one statement, it has the same $STATUS value for all statements that can raise that error. This practice allows you to write a generic SOUL routine that is an error handler for all MQ/204 statements.
<table>
<caption>$STATUS values for MQ/204 errors</caption>
<tr class="head">
<th>$STATUS value</th>
<th>Meaning</th>
<th>Statement</th>
</tr>
<tr>
<td>1</td>
<td>Queue or queue manager was not found.</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQBACK

MQCMIT

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>2</td>
<td>Reply queue not found.</td>
<td>

MODIFY QUEUE

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>3</td>
<td>Queue manager is not started.</td>
<td>

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>4</td>
<td>No WebSphere MQ interface subtasks are available.</td>
<td>

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>5</td>
<td>WebSphere MQ A PI level MQCONN failed. $STATUSD is set to the WebSphere MQ reason code.
</td>
<td>

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>6</td>
<td>Queue manager has been stopped.</td>
<td>

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>7</td>
<td>Queue is already open.</td>
<td>OPEN QUEUE</td>
</tr>
<tr>
<td>8</td>
<td>

Storage allocation error.
</td>
<td>

MODIFY MQ_BUFFER

MQBACK

MQCMIT

MQGET

MQPUT

MQPUT1

OPEN QUEUE

READ IMAGE

WRITE IMAGE
</td>
</tr>
<tr>
<td>9</td>
<td>WebSphere MQ A PI level MQOPEN failed. $STATUSD is set to the WebSphere MQ reason code.
</td>
<td>OPEN QUEUE</td>
</tr>
<tr>
<td>10</td>
<td>%Variable substitution error, consult $STATUSD for more details. (See "Identifying invalid options by $STATUSD value.")</td>
<td>

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>11</td>
<td>Specified queue is not open.</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1
</td>
</tr>
<tr>
<td>12</td>
<td>WebSphere MQ A PI level MQGET failed. $STATUSD is set to the WebSphere MQ reason code.</td>
<td>
MQGET</td>
</tr>
<tr>
<td>13</td>
<td>Browse was attempted on MQGET, but the queue was not open for browsing.</td>
<td>MQGET</td>
</tr>
<tr>
<td>14</td>
<td>Data truncation occurred on an MQGET. The target image or variable for the data area is too small.</td>
<td>MQGET</td>
</tr>
<tr>
<td>15</td>
<td>WebSphere MQ A PI level MQPUT failed. $STATUSD is set to the WebSphere MQ reason code.</td>
<td>MQPUT</td>
</tr>
<tr>
<td>16</td>
<td>WebSphere MQ A PI level MQPUT1 failed. $STATUSD is set to the WebSphere MQ reason code.
</td>
<td>MQPUT1</td>
</tr>
<tr>
<td>17</td>
<td>MQPUT was attempted, and the queue was not open for output.</td>
<td>MQPUT</td>
</tr>
<tr>
<td>18</td>
<td>WebSphere MQ A PI level MQCMIT failed. $STATUSD is set to the WebSphere MQ reason code.
</td>
<td>MQCMIT</td>
</tr>
<tr>
<td>19</td>
<td>WebSphere MQ API level MQBACK failed. $STATUSD is set to the WebSphere MQ reason code.
</td>
<td>MQBACK</td>
</tr>
<tr>
<td>20</td>
<td>WebSphere MQ API level MQCLOSE failed. $STATUSD is set to the WebSphere MQ reason code.</td>
<td>CLOSE QUEUE</td>
</tr>
<tr>
<td>21</td>
<td>User is not connected to the queue manager specified.</td>
<td>

MQBACK

MQCMIT
</td>
</tr>
<tr>
<td>22</td>
<td>Destructive get operation attempted, but the queue was not open for input.</td>
<td>MQGET</td>
</tr>
<tr>
<td>23</td>
<td>MQGET was issued, but no message was available.</td>
<td>MQGET</td>
</tr>
<tr>
<td>24</td>
<td>MQGET was issued with MSG_UNDER_CURSOR option, but the queue was not open for both input and browse.</td>
<td>MQGET</td>
</tr>
<tr>
<td>25</td>
<td>Data does not fit in the buffer and has been truncated.</td>
<td>

MQPUT

MQPUT1

WRITE
</td>
</tr>
<tr>
<td>26</td>
<td>No message is in the message buffer, so no message was put.</td>
<td>

MQPUT

MQPUT1
</td>
</tr>
<tr>
<td>27</td>
<td>Statement tried to reference a remote queue, but MQDEQMAN was not set.</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>28</td>
<td>An OPEN QUEUE statement was issued for a remote queue, but the mode option specified was not OUTPUT.</td>
<td>OPEN QUEUE</td>
</tr>
<tr>
<td>30</td>
<td>Context queue entity was not found.</td>
<td>

MODIFY QUEUE

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>31</td>
<td>Context queue not specified or inherited when it was needed, because a PASS option was specified.</td>
<td>

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>32</td>
<td>Context queue not open for INPUT and SAVE_ALL_CONTEXT.</td>
<td>

MQPUT

MQPUT1
</td>
</tr>
<tr>
<td>33</td>
<td>On PASS_USER_CONTEXT there was no user ID to pass.</td>
<td>

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>34</td>
<td>Invalid value of SIZE on MODIFY MQ_BUFFER.</td>
<td>

MODIFY MQ_BUFFER
</td>
</tr>
<tr>
<td>35</td>
<td>LIBUFF too small while parsing runtime options.</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>36</td>
<td>Invalid or unrecognized option found while parsing runtime options.</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>37</td>
<td>Unexpected end of option string while parsing runtime options.</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>38</td>
<td>Duplicate options found while parsing runtime options.</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>39</td>
<td>While parsing runtime options, keyword=%variable found, but %variable is undefined, $STATUSD set. (See "Identifying invalid options by $STATUSD value.")</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>40</td>
<td>While parsing runtime options, keyword=value found, but value invalid, $STATUSD set. (See "Identifying invalid options by $STATUSD value.")</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>41</td>
<td>While parsing runtime options, mutually exclusive options found.</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>42</td>
<td>While parsing runtime options, invalid combination of options found, $STATUSD set.</td>
<td>

CLOSE QUEUE

MODIFY QUEUE

MQGET

MQPUT

MQPUT1

OPEN QUEUE
</td>
</tr>
<tr>
<td>43</td>
<td>Local dynamic queue, but null dynamic queue name.</td>
<td>

OPEN QUEUE
</td>
</tr>
<tr>
<td>44</td>
<td>Local dynamic queue, but null model queue name.</td>
<td>

OPEN QUEUE
</td>
</tr>
<tr>
<td>45</td>
<td>Local dynamic queue, but no model queue entity.</td>
<td>OPEN QUEUE</td>
</tr>
<tr>
<td>46</td>
<td>Local dynamic queue, but dynamic queue already exists.</td>
<td>OPEN QUEUE</td>
</tr>
<tr>
<td>47</td>
<td>RFH2 expected but not received.</td>
<td> </td>
</tr>
<tr>
<td>48</td>
<td>RFH2 imaged specified, but too small</td>
<td> </td>
</tr>
<tr>
<td>49</td>
<td>Error moving data to image</td>
<td> </td>
</tr>
<tr>
<td>50</td>
<td>Size error with multiple images on PUT(1)</td>
<td> </td>
</tr>
<tr>
<td>51</td>
<td>GCORE error saving data with PUT(1) and RFH2</td>
<td> </td>
</tr>
<tr>
<td>52</td>
<td>BUFLEN specified too small for RFH2 header</td>
<td>
 </td>
</tr>
</table>

====%Variable substitution errors====

The following table lists $STATUS values that indicate a %variable substitution error, when the option was evaluated, and how the option was initially specified. You specified the value of an option as a %variable. When the statement was executed, the %variable contained an invalid value for the option in question. 
<table>
<caption>$STATUS values that indicate a %variable substitution error</caption>
<tr class="head">
<th>$STATUS value</th>
<th>Evaluated at...</th>
<th>Option initially specified as...</th>
</tr>
<tr>
<td>

10 
</td>
<td>

Compile time, as a %variable 
</td>
<td>

%Variable
</td>
</tr>
<tr>
<td>

39 
</td>
<td>

Runtime, as a ?%variable 
</td>
<td>

%Variable
</td>
</tr>
<tr>
<td>

40 
</td>
<td>

Runtime, as a ?%variable 
</td>
<td>

Literal
</td>
</tr>
</table>

To find out which $STATUS option had a problem, check the $STATUSD values, as listed in the following table.

===$STATUSD return codes===

On all $STATUS return codes that indicate a failure of a WebSphere MQ API level call, the value of $STATUSD is set to the WebSphere MQ reason code. The values and meanings of the reason codes are described in applicable IBM WebSphere MQ documents. 
For reason codes, see <var class="book">WebSphere MQ for z/OS Messages and Codes V5.3.1</var>, Appendix A.

To find out which option had a problem, check $STATUSD to determine which option, as listed in the following table.
<table>
<caption>Identifying invalid options by $STATUSD value</caption>
<tr class="head">
<th>$STATUSD 
value</th>
<th>Indicates invalid value for...</th>
</tr>
<tr>
<td>1</td>
<td>MSGTYPE</td>
</tr>
<tr>
<td>2</td>
<td>PRIORITY</td>
</tr>
<tr>
<td>3</td>
<td>REPLY_QUEUE</td>
</tr>
<tr>
<td>4</td>
<td>MSGID</td>
</tr>
<tr>
<td>5</td>
<td>CORRELID</td>
</tr>
<tr>
<td>6</td>
<td>EXPIRY</td>
</tr>
<tr>
<td>7</td>
<td>FEEDBACK</td>
</tr>
<tr>
<td>8</td>
<td>FORMAT</td>
</tr>
<tr>
<td>9</td>
<td>WAIT_TIME</td>
</tr>
<tr>
<td>10</td>
<td>CONTEXT</td>
</tr>
<tr>
<td>11</td>
<td>PUTAPPLTYPE</td>
</tr>
<tr>
<td>12</td>
<td>USERIDENTIFIER</td>
</tr>
<tr>
<td>13</td>
<td>ACCOUNTINGTOKEN</td>
</tr>
<tr>
<td>14</td>
<td>APPLIDENTITYDATA</td>
</tr>
<tr>
<td>15</td>
<td>PUTAPPLNAME</td>
</tr>
<tr>
<td>16</td>
<td>PUTDATE</td>
</tr>
<tr>
<td>17</td>
<td>PUTTIME</td>
</tr>
<tr>
<td>18</td>
<td>APPLORIGINDATA</td>
</tr>
<tr>
<td>19</td>
<td>MAXLEN</td>
</tr>
<tr>
<td>20</td>
<td>POSITION</td>
</tr>
<tr>
<td>21</td>
<td>BUFLEN</td>
</tr>
<tr>
<td>22</td>
<td>DESCRIPTOR</td>
</tr>
<tr>
<td>23</td>
<td>REPORT</td>
</tr>
<tr>
<td>24</td>
<td>MSGLEN</td>
</tr>
<tr>
<td>25</td>
<td>REPLY_QMGR</td>
</tr>
<tr>
<td>26</td>
<td>DYNAMICQNAME</td>
</tr>
<tr>
<td>27</td>
<td>MODEL</td>
</tr>
<tr>
<td>28</td>
<td>GROUPID</td>
</tr>
<tr>
<td>29</td>
<td>GSTATUS</td>
</tr>
<tr>
<td>30</td>
<td>Options that save context require queue to be open with an input option</td>
</tr>
<tr>
<td>31</td>
<td>Options that allow and pass context require queue to be open for output</td>
</tr>
<tr>
<td>32</td>
<td>APPLORIGINDATA, PUTAPPLNAME, PUTAPPLTYPE, PUTDATE, and PUTTIME options that require the SET_ALL_CONTEXT option</td>
</tr>
<tr>
<td>33</td>
<td>USERIDENTIFIER, ACCOUNTINGTOKEN, and APPLIDENTITYDATA options that require SET_IDENTITY_CONTEXT or SET_ALL_CONTEXT</td>
</tr>
<tr>
<td>34</td>
<td>DYNAMICQNAME and MODEL options that must be specified together</td>
</tr>
<tr>
<td>35</td>
<td>MSGTOKEN</td>
</tr>
<tr>
<td>36</td>
<td>SEQUENCE</td>
</tr>
</table>

For all other values of $STATUS, $STATUSD is set to 0.

==Debugging aid==

Information recorded in the audit trail aids in debugging MQ/204 applications.

===Audit trail===

Each MQ/204 statement executed is logged to the audit trail as RK lines. Each RK line contains the following information:
<ul>
<li>
Current user ID</li>
<li>
Statement being executed, for example, OPEN QUEUE, MQGET, and so on.</li>
<li>
Queue manager name</li>
<li>
If the call is queue specific, the queue name</li>
<li>
Completion code and reason code returned by the WebSphere MQ API call</li>
</ul>

For OPEN QUEUE statements, an additional RK line is logged including:
<ul>
<li>
External queue manager name</li>
<li>
External queue name</li>
</ul>

For MQCONN and MQDISC calls, which are made on behalf of the user but are not strictly under the control of the SOUL program, a different RK line is logged containing the following information:
<ul>
<li>
Current user ID</li>
<li>
Function being performed, MQCONN or MQDISC</li>
<li>
Queue manager name</li>
<li>
External queue manager name</li>
<li>
Completion code and reason code returned by the WebSphere MQ API call</li>
<li>
Address of the associated subtask control block</li>
</ul>

Each of the RK lines has its own message number, so that each can be controlled independently with Model 204 MSGCTL parameter.

==Wait types and statistics==

To ensure that the system manager has full information, wait types identify waits that a user thread might perform when using MQ/204. 
<table>
<tr class="head">
<th>Wait type</th>
<th>Value</th>
<th>Used when a thread is waiting for ...</th>
</tr>
<tr>
<td>MQAPI</td>
<td>41</td>
<td>WebSphere MQ operation to complete. The one exception is for the MQGWT wait type.</td>
</tr>
<tr>
<td>MQGWT</td>
<td>42</td>
<td>WebSphere MQ MQGET operations, where the WAIT option has been specified.</td>
</tr>
<tr>
<td>MQTSK</td>
<td>40</td>
<td>Subtask to become available (the MQWAIT parameter must be nonzero to have this type of wait).</td>
</tr>
</table>

===Measuring the throughput of the WebSphere MQ API===

The following statistics attempt to measure the throughput of the WebSphere MQ API itself. To separate API execution time from time spent waiting within the API, MQGET calls with the WAIT option specified are measured separately. The following statistics measure all WebSphere MQ API calls except MQGET with the WAIT option.
<table>
<tr class="head">
<th>Statistic name</th>
<th>Tracks...</th>
</tr>
<tr>
<td>MQAPICNT </td>
<td>Number of MQAPI waits performed. See [[#WebSphere MQ API wait types access control|WebSphere MQ API wait types access control]].
</td>
</tr>
<tr>
<td>MQAPITIM</td>
<td>Elapsed time spent in MQAPI waits. See [[#WebSphere MQ API wait types access control|WebSphere MQ API wait types access control]].</td>
</tr>
</table>
===Measuring MQGET calls with the WAIT options===

The following statistics measure MQGET calls performed with the WAIT option and a finite WAIT_TIME value specified. MQGET calls with the WAIT option and WAIT_TIME=UNLIMITED specified are intentionally excluded from these measurements.
<table>
<tr class="head">
<th>Statistic name</th>
<th>Tracks...</th>
</tr>
<tr>
<td>MQGWTCNT</td>
<td>Number of MQGWT waits performed for MQGET calls with the WAIT option and a finite WAIT_TIME value specified. See [[#WebSphere MQ API wait types access control|WebSphere MQ API wait types access control]].</td>
</tr>
<tr>
<td>MQGWTSUC</td>
<td>Number of MQGET calls performed with the WAIT option and a finite WAIT_TIME specified that succeeded; for example, where a message was actually returned.</td>
</tr>
<tr>
<td>MQGWTTIM</td>
<td>Elapsed time spent in MQGWT waits done for MQGET calls with the WAIT option and a finite WAIT_TIME value specified. See [[#WebSphere MQ API wait types access control|WebSphere MQ API wait types access control]].</td>
</tr>
<tr>
<td>MQGWTTSP</td>
<td>Total WAIT_TIME specified on all MQGET calls performed with the WAIT option and a finite WAIT_TIME value specified.</td>
</tr>
</table>
[[Category:MQ/204]]

MQ/204 monitoring and troubleshooting - Revision history

ELowell at 20:33, 27 October 2017

ELowell: /* Measuring MQGET calls with the WAIT options */

ELowell at 20:46, 11 November 2015

ELowell: /* $STATUS return codes */

ELowell: Created page with "==Overview== This topic discusses: Installation considerations particular to MQ/204 Tools available within Model 204 to develop and debug MQ/204 applications..."

ELowell: Created page with "==Overview== This topic discusses:

Installation considerations particular to MQ/204

Tools available within Model 204 to develop and debug MQ/204 applications..."