Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Browse MQ Queue Message (5.6.2)

Related Tpoics

Quick-Reference

Customizing-after-installation

The Browse MQ Queue Message screen (5.6.2) allows access to a message in an MQ queue. Data can be displayed in character, vertical hexadecimal, or dump format. File mapping is available on this screen. For more information on file mapping, see USING.

Access this screen by typing the number 2 on the MQ-Menu-5-6, typing 6.2 on the File-Utility-Menu-5, by typing the B line command on the MQ-Queue-List-5-6-1 screen, or as described in Transferring Between Screens.

Important

Browsing a message from an initiation queue may cause a trigger event to occur, which may result in a trigger message being generated in the initiation queue. For details about trigger events and trigger messages, see section entitled “Starting IBM MQ applications using triggers” in the IBM documentation site.

Browse MQ Queue Message Screen (5.6.2)

 ------------------------- BROWSE MQ QUEUE MESSAGE (5.6.2) ----------------C024
COMMAND ===>                                                   SCROLL ===> CSR
MODULE:          CSECT:
VALID COMMANDS: FIRST  NEXT
                                                              TYPE : QLOCAL
QUEUE NAME : XD06.DEFXMIT.QUEUE                               DEPTH: 000000002
REPLYTOQ . : CSQ4SAMP.MAILMGR.ACMEJET0
REPLYTOQMGR: XD06
PUTAPPLNAME: XD06                        PUTDATE: 20011101 PUTTIME: 17194454

TRIGGER TYPE: NONE    TRIGGER PRIORITY: 000000000   TRIGGER DEPTH: 000000001
TRIGGER DATA:

DEC-OFFSET: 000000 ADD-OFFSET: ______   REC-LENGTH: 001168
----+---10----+---20----+---30----+---40----+---50----+---60----+---70----+--->
XQH ....CSQ4SAMP.MAILMGR.ACMEJET0                       XD40
----+---10----+---20----+---30----+---40----+---50----+---60----+---70----+--->

Input Fields

QUEUE NAME

Name of the queue that is accessed. Queues can be aliases, that is, point to another queue. In this case, Code Debug CICS displays the entered alias queue name above the name of the queue that is accessed.

HEX/DEC-OFFSET

Displays the current offset within the column's data. This value is always relative to 0. The data display begins at this offset. This field may be modified. The value entered must be in the range of 0 to the decimal displayed in the RECLN field. When DEC-OFFSET is displayed, a hexadecimal value with a leading positive (+) sign may be entered instead, e.g. 80 or +50 are equivalent.

Important

The HEX/DEC-OFFSET field is protected (non-modifiable) when the USING command is in effect.

ADD-OFFSET

Use with the HEX/DEC-OFFSET field to provide a new starting offset into the I/O area. The entered value is added to the value in the HEX/DEC-OFFSET field to yield a new starting offset value. If the entered value has a leading minus sign (-), the entered value is subtracted from the value in the HEX/DEC-OFFSET field.

If the display mode is HEX DUMP mode, only hexadecimal values can be entered. If the display mode is character (HEX OFF) or vertical hexadecimal (HEX ON), the value can be entered either in decimal or hexadecimal. This can be done by preceding the value with a plus sign (+). To add a negative offset, precede the value by a minus sign (-). A value preceded by a minus sign is treated as decimal when in HEX ON or HEX OFF mode and as hexadecimal when in HEX DUMP mode.

Important

The ADD-OFFSET field is protected (non-modifiable) when the USING command is in effect.

Output Fields

VALID COMMANDS

List of primary commands available for use against this queue.

ALIAS NAME

Name of the entered alias queue. Queues can be aliases, that is, point to another queue. In this case, when a message is displayed, Code Debug CICS displays the entered alias queue name above the name of the queue that is accessed. Otherwise, the ALIAS NAME field will not be displayed.

TYPE

Type of MQ queue. Valid entries are:

  • QALIAS: The queue name is an alias for another queue defined to the local queue manager. When an alias queue is selected, the alias is resolved and messages from the associated base queue will be displayed on the Browse MQ Queue Message screen (5.6.2).
  • QLOCAL: The queue belongs to the local queue manager. The local queue manager is the MQ queue manager connected to the CICS system.
  • QMODEL: The queue is a model for use when creating a dynamic queue. Model queues are not selectable.
  • QREMOTE: The queue belongs to an MQ queue manager other than the local queue manager. Remote queues are not selectable.

DEPTH

The current depth (number of messages) of the queue that is accessed.

REPLYTOQ

The name of the queue to which the program that put this message on the queue wants a reply sent.

REPLYTOQMGR

The name of the queue manager to which the queue specified in REPLYTOQ belongs.

PUTAPPLNAME

The name of the application which put the message on the queue.

PUTDATE

Date the message was put on the queue.

PUTTIME

Time the message was put on the queue.

TRIGGER TYPE

One of the following values:

  • NONE - no trigger message
  • FIRST - trigger message when queue depth goes from 0 to 1
  • EVERY - trigger message for every addition to the queue
  • DEPTH - trigger message when depth threshold exceeded.

TRIGGER PRIORITY

Messages below this priority do not contribute to the trigger depth.

TRIGGER DEPTH

The number of messages that must be on the queue before a trigger message is written.

TRIGGER DATA

Free-format data that the queue manager inserts into the trigger message.

REC-LENGTH

The length of the message currently displayed.

I/O area

Data from the Code Debug CICS I/O area that can be displayed in four modes. Each mode supports different scrolling commands, as shown in File Utility Scrolling Commands. For more information, see Using the Code Debug CICS I/O Area.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*