Dump MQ Configuration (DMPMQMCFG)

Where allowed to run:	Threadsafe:
All environments (*ALL)	Yes

The Dump MQ Configuration (DMPMQMCFG) command is used to dump the configuration objects and authorities for a queue manager.

Parameters

Keyword	Description	Choices	Notes
MQMNAME	Message Queue Manager name	`Character value`, *ALL	Optional, Positional 1
OBJ	Object name	`Character value`, *ALL	Optional, Positional 2
OBJTYPE	Object type	ALL, AUTHINFO, CHL, CLTCN, COMMINFO, LSR, NMLIST, PRC, Q, MQM, SVC, SUB, *TOPIC	Optional, Positional 3
EXPTYPE	Export type	ALL, OBJECT, AUTHREC, CHLAUTH	Optional, Positional 4
EXPATTR	Export attributes	NONDEF, ALL	Optional, Positional 5
WARN	Warnings	NO, YES	Optional, Positional 6
OUTPUT	Output	MQSC, ONELINE, SETMQAUT, GRTMQMAUT	Optional, Positional 7
CLIENT	Client connection	NO, YES, *CHL	Optional, Positional 8
CLIENTCHL	MQSC Channel Definition	`Character value`, *NONE	Optional, Positional 9
MSGSEQNUM	Message sequence number	1-999999999, *NORESET	Optional, Positional 10
RPLYQ	Reply Queue	`Character value`, 'SYSTEM.DEFAULT.MODEL.QUEUE'	Optional, Positional 11
RMTMQMNAME	Remote Message Queue Manager	`Character value`, *NONE	Optional, Positional 12
TOFILE	File to receive output	`Qualified object name`	Optional, Positional 13
	Qualifier 1: File to receive output	`Name`
	Qualifier 2: Library	`Name`, *LIBL
TOMBR	Member to receive output	`Name`	Optional, Positional 14

Message Queue Manager name (MQMNAME)

Specifies the name of the IBM® MQ queue manager for which object information is to displayed.

The possible values are:

*DFT
queue-manager-name: The name of an existing message queue manager. The maximum string length is 48 characters.

Object name (OBJ)

Specifies the name of the objects to dump. It is a 48-character MQ object or generic object name.

The possible values are:

*ALL

All objects of the specified type (OBJTYPE) are dumped.

generic-object-name

Specify the generic name of the objects. A generic name is a character string followed by an asterisk (*). For example, ABC*. It selects all objects having names that start with the selected character string.

Specifying the required name within quotation marks ensures that your selection is precisely what you entered.

You cannot select all the uppercase and lowercase versions of a generic name on a single panel, without requesting all the names.

object-name

The name of an object for which the corresponding name and type is to be displayed.

Object type (OBJTYPE)

Specifies the type of the objects to be dumped.

The possible values are:

*ALL: All MQ Objects with names specified by OBJ.
*AUTHINFO: All MQ authentication information objects with names specified by OBJ.
*CHL: All MQ channel objects with names specified by OBJ.
*CLTCN: All MQ client connection objects with names specified by OBJ.
*COMMINFO: All MQ communication information objects with names specified by OBJ.
*LSR: All MQ listener objects with names specified by OBJ.
*NMLIST: All MQ namelist objects with names specified by OBJ.
*PRC: All MQ process objects with names specified by OBJ.
*Q: All MQ queue objects with names specified by OBJ.
*MQM: The queue manager object.
*SVC: All MQ service objects with names specified by OBJ.
*TOPIC: All MQ topic objects with names specified by OBJ.

Export type (EXPTYPE)

Specifies the type of the export.

The possible values are:

*ALL: All MQ object, authority and subscription configuration information is dumped.
*OBJECT: Only MQ object information is dumped.
*AUTHREC: Only MQ authority information is dumped.
*CHLAUTH: Only MQ channel authority records are dumped.
*SUB: Only MQ durable subscription information is dumped.

Export attributes (EXPATTR)

Specifies the attributes to export.

The possible values are:

*NONDEF: Only non-default attribute values are dumped.
*ALL: All attribute values are dumped.

Warnings (WARN)

Specifies whether warnings should be generated during the dump, for example if the command is issued against a newer queue manager or encounters a damaged object.

The possible values are:

*NO: No warnings messages will be issued during the dump.
*YES: Warning messages may be issued during the dump.

Output (OUTPUT)

Specifies the output format from the dump.

The possible values are:

*MQSC: The output format is in the form of MQSC commands that could be used as input to the RUNMQSC or STRMQMMQSC commands.
*ONELINE: The output format is in the form of MQSC commands formatted into single line records, suitable for use with line comparison tools.
*SETMQAUT: The output format is in the form of setmqaut commands, suitable for use with Windows or UNIX.
*GRTMQMAUT: The output format is in the form of GRTMQMAUT commands, suitable for use generating a CL program on the IBM i platform.

Client connection (CLIENT)

Specifies whether to use a client connection to the queue manager.

The possible values are:

*NO: The command will first attempt a server bindings connection, if this connection fails a client connection will be attempted.
*YES: The command will attempt to connect via a client connection using the default client connection process. If the MQSERVER environment variable is set it will override use of a client connection channel table.
*CHL: The command will attempt to connect to the queue manager using a temporary channel definition defined by the MQSC string specified in the CLIENTCHL parameter.

MQSC Channel Definition (CLIENTCHL)

Specifies, via MQSC syntax, a temporary client channel definition to use in connecting to the queue manager.

The possible values are:

*NONE: Do not use a temporary client channel definition when connecting to the queue manager.
mqsc-define-channel-string: The command will attempt to construct a temporary client channel definition from the using the MQSC command supplied on this parameter. The MQSC command must define all required attributes for a client connection channel, for example:
"DEFINE CHANNEL(MY.CHL) CHLTYPE(CLNTCONN) CONNAME(MYHOST.MYCORP.COM(1414))"

Message sequence number (MSGSEQNUM)

Specifies whether to generate reset channel commands for sender, server and cluster sender channel types when dumping channel objects.

The possible values are:

*NORESET: Do not include any reset channel commands in the dumped output.
1 - 999999999: Specify a message sequence number for the reset channel commands included in the dump.

Reply Queue (RPLYQ)

Specifies the name of the queue to use for receiving PCF replies when inquiring configuration information.

The possible values are:

SYSTEM.DEFAULT.MODEL.QUEUE: The default model queue, a dynamic queue will be generated to receive replies.
reply-to-queue-name: Specify the name of the reply to queue.

Remote Message Queue Manager (RMTMQMNAME)

Specifies the name of a remote MQ queue manager for which object information is to displayed.

The possible values are:

*NONE: The configuration information is collected from the queue manager specified in the MQMNAME parameter.
remote-queue-manager-name: Specify the name of the remote queue manager. PCF inquiry commands are issued to the queue manager specified in RMTMQMNAME via the queue manager specified in MQMNAME, this is known as queued mode. \

File to receive output (TOFILE)

Specifies the qualified name of the file, in the form LIBRARY/FILE, that will be used to store the dumped configuration data. The FILE should have been created with a record length of 240, otherwise the configuration information might be truncated.

The possible values are:

*LIBL: The library list is searched for the file name.
*CURLIB: The current library is used.
to-library-name: Specify the name of the library to be used.
to-file-name: Specify the name of the file to contain the configuration data.

Member to receive output (TOMBR)

Specifies the name of the member to store the dumped configuration data.

The possible values are:

to-member-name: Specify the name of the member to contain the configuration data.

Examples

To make these examples work you need to ensure that your system is set up for remote MQSC operation. See Preparing queue managers for remote administration and Preparing channels and transmission queues for remote administration.

DMPMQMCFG MQMNAME('MYQMGR') CLIENT(*YES) CLIENTCHL('''DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN)
                   CHLTYPE(CLNTCONN) CONNAME(''myhost.mycorp.com(1414)'')''')

dumps all the configuration information from remote queue manager MYQMGR in MQSC format and creates an ad-hoc client connection to the queue manager using a client channel called SYSTEM.ADMIN.SVRCONN.

Note: You need to ensure that a server-connection channel with the same name exists.

DMPMQMCFG MQMNAME('LOCALQM') RMTMQMNAME('MYQMGR')

dumps all configuration information from remote queue manager MYQMGR, in MQSC format, connects initially to local queue manager LOCALQM, and sends inquiry messages through this local queue manager.

Note: You need to ensure that the local queue manager has a transmission queue named MYQMGR, with channel pairings defined in both directions, to send and receive replies between queue managers.