A queue manager QM1 on UNIX has an unrecoverable problem. The IBM Support Center has asked the administrator to send any FFST reports.
Which directory can an administrator get these FFST files from?

An administrator has set up sender receiver channels between QMGR1 running on AIX and QMGR2 running on i5/OS. During verification testing, the administrator noticed that messages being sent from one queue manager are not visible on the other queue manager.
Which of the following files should the administrator look at to find the cause of the problem?

Queue managers QMGR1, QMGR2 and QMGR3 are members of cluster QC. An administrator created the following queues for an application:
On QMGR1: DEFINEQALIAS(TEST.ALIAS) + TARGET(TEST.LOCAL) + DEFBIND(OPEN) + DEFPSIST(NO)
On QMGR2 and QMGR3: DEFINE QLOCAL(TEST.LOCAL) + CLUSTER(QC) + DEFBIND(OPEN) + CLWLPRTY(0) + CLWLRANK(0) +DEFPSIST(NO)

The administrator verifies the setup by putting messages on TEST.ALIAS using the sample amqsput program but notices that all messages end up on the same queue manager (either QMGR2 or QMGR3).

What could be the likely cause?

It is important to the IBM WebSphere MQ operations team that none of their application queues exceed seventy percent of the maximum number of messages the queues can hold. By default, application queues are created with a maximum depth of one thousand messages.
What commands can the operations team use to monitor ROUTE_DATA_Q?

An IBM WebSphere MQ client application puts messages onto remote queue RQ on queue manager QM1, which resolves to the local queue LQ on queue manager QM2. A new version of the application has been deployed that has the capability to put messages greater than 4MB. The administrator changed the max message length attributes for the queue managers, transmission queue, sender-receiver channels and LQ to handle the larger messages. The administrator was later notified that messages greater than 4MB are still not reaching LQ.
The most likely cause of the problem is the max message length attribute:

Two queue managers, QMGR1 and QMGR2, are running on Windows connected by sender receiver channels. An application connected to QMGR1 puts persistent messages on a remote queue of QMGR1 destined for a local queue of QMGR2. The administrator is notified that the messages have not reached QMGR2. On investigation the administrator notices that the server on which QMGR2 runs has crashed and rebooted automatically. The administrator also notices that the sender channel on QMGR1 is in an indoubt state.
What action can the administrator take to recover the messages?

An administrator deployed an IBM WebSphere MQ application on an AIX server which is causing a lot of errors to be generated in the WebSphere MQ error logs.
Which option should be used by the administrator to increase the size of the IBM WebSphere MQ error logs?

An administrator created a queue manager for an application using the command: crtmqm TESTQMGR The application is started by triggering, and puts forty 3.5MB persistent messages onto a remote queue. The administrator is notified that the IBM WebSphere MQ error logs are getting populated with errors whenever the application is started.
What could be the likely cause?

Queue managers QMGR1 and QMGR2 are members of cluster QMCLUS.
An application connected to QMGR1 needs to send messages to a local queue APP.LOCAL of QMGR2.
The administrator creates the following definitions:
On QMGR1: DEFINE QALIAS(APP.ALIAS) + TARGET(APP.LOCAL) + CLUSTER(QMCLUS) On QMGR2: DEFINE QLOCAL(APP.LOCAL) + MAXDEPTH(50000)
The administrator is notified that the application is unable to send messages to APP.LOCAL.

What is the most likely cause?

An administrator was asked to restrict the IBM WebSphere MQ trace file size on AIX to 10 MB.
How can the administrator do this?