MQ Detailed Exam Objectives

IBM Cloud Professional
Certification Program
Study Guide Series
Exam C1000-002 - IBM MQ v9.0, Systems

Administration
Purpose of Exam Objectives .................................................................................................... 3
High-level Exam Objectives...................................................................................................... 3
Detailed Exam Objectives ......................................................................................................... 5
Section 1 - Planning, Installation, and Migration .................................................................. 5
Section 2 - Configuration ........................................................................................................11
Section 3 - Security .................................................................................................................19

Section 4 - Administration ......................................................................................................26
Section 5 - Availability .............................................................................................................31
Section 6 - Monitoring .............................................................................................................35
Section 7 - Performance Tuning ...........................................................................................37
Section 8 - Problem Determination .......................................................................................41
Next Steps ...................................................................................................................................44

Purpose of Exam Objectives
When an exam is being developed, the Subject Matter Experts work together to
define the role the certified individual will fill. They define all of the tasks and
knowledge that an individual would need to have in order to successfully
implement the product. This creates the foundation for the objectives and
measurement criteria, which are the basis for the certification exam.
The Middleware Certification item writers use these objectives to develop the
questions that they write and which will appear on the exam.
It is recommended that you review these objectives. Do you know how to

complete the task in the objective? Do you know why that task needs to be
done? Do you know what will happen if you do it incorrectly? If you are not
familiar with a task, then go through the objective and perform that task in your
own environment. Read more information on the task. If there is an objective on
a task there is about a 95% chance that you WILL see a question about it on the
actual exam.
After you have reviewed the objectives and completed your own research, then
take the assessment exam. While the assessment exam will not tell you which
question you answered incorrectly, it will tell you how you did by section. This will
give you a good indication as to whether you are ready to take the actual exam
or if you need to further review the materials.
Note: This is the high-level list of objectives. As you review these objectives, click
for a more detailed level of how to perform the task.
High-level Exam Objectives
Section 1 - Planning, Installation, and Migration
Describe the differences between Long Term Support (LTS) and

1.1
Continuous Delivery (CD)
1.2 Design an appropriate infrastructure to meet conflicting requirements
Identify the pre-requisites for installing and implementing an IBM MQ
1.3
configuration, including multi-instance queue managers
1.4 Plan the appropriate backup and recovery strategy
1.5 Describe the differences between MQ Advanced and MQ
1.6 Select the appropriate IBM MQ platform for a given workload
Outline migration considerations, including impact on existing applications
1.7
and multi-installation
Section 2 - Configuration
2.1 Create the necessary IBM MQ objects to support an application

2.2 Configure IBM MQ channels based on the network topology
2.3 Configure IBM MQ objects for triggered applications and channels
Create the objects required to enable queue manager clustering and
2.4
workload distribution
Predict the final destination of a message given a scenario containing alias
2.5
or remote definitions
2.6 Define the objects to support a publish/subscribe topology
2.7 Configure IBM MQ objects to support JMS
2.8 Configure channel exits
Section 3 - Security
3.1 Configure Channel Authentication (CHLAUTH)

3.2 Understand the purpose of Connection Authentication (CONNAUTH)
3.3 Control access to IBM MQ objects
3.4 Configure IBM MQ channels with SSL/TLS
3.5 Configure the IBM MQ client with SSL/TLS
3.6 Describe MQ features that provide intrusion detection
3.7 Distinguish between the available security choices
3.8 Configure end-to-end message security
Section 4 - Administration
4.1 Administer queue managers and their objects

4.2 Configure IBM MQ Explorer for remote administration
4.3 Monitor and alter IBM MQ using the different command tools
4.4 Define procedures to recover messages and objects in the event of failure
4.5 Implement dead-letter queue handling
4.6 Acquire and apply maintenance
Section 5 - Availability
5.1 Configure and manage a multi-instance queue manager

5.2 Configure IBM MQ for automatic client reconnection
5.3 Implement backup, restart and recovery procedures
5.4 Implement a Queue-Sharing Group for high availability
5.5 Manage an MQ cluster
5.6 Configure and manage HA/DR for MQ appliance
Section 6 - Monitoring
6.1 Explain the IBM MQ capabilities for monitoring
6.2 Enable and monitor IBM MQ events
6.3 Gather and analyze IBM MQ accounting and statistics data
Use IBM MQ administration tools or commands to monitor the status of a
6.4
queue manager, channel or queue
Section 7 - Performance Tuning
7.1 Identify the tools available to assist with IBM MQ performance
Use accounting and statistical data to identify and resolve performance
7.2
issues
7.3 Tune IBM MQ object definitions for performance
7.4 Tune client and server connection channel parameters
7.5 Describe how to use the performance monitoring API
Section 8 - Problem Determination
Locate problem information such as IBM MQ error logs, FFST files and IBM
8.1
MQ dumps
8.2 Produce an IBM MQ trace
Identify the steps to evaluate and recover a non-responsive queue manager
8.3
8.4 Identify and solve security issues with a user, application, or channel
Determine the route that a message took through a queue manager
8.5
network
8.6 Describe how to use the Enhanced Application Activity Trace
Detailed Exam Objectives
Section 1 - Planning, Installation, and Migration

1.1. Describe the differences between Long Term Support (LTS) and
Continuous Delivery (CD)
SUBTASK(S):
1.1.1. Describe Long Term Support (LTS)
1.1.2. Describe Continuous Delivery (CD)
1.1.3. Recognize release numbering of LTS versus CD
1.1.4. Understand differences in delivery for fixes
1.1.4.1. LTS (all), iFix and delivery in next Fixpack
1.1.4.2. CD in next CD release (urgent iFix only on latest 2 versions)
1.1.5. Understand differences in support window between LTS (max 5 years) and
CD (max 2 latest versions)
1.1.6. Understand new function can change with CD releases
1.1.7. Understand how to identify what is delivered in which version
1.1.8. Understand migration between LTS and CD
1.1.8.1. Migrate from an LTS release to a CD release at the same or
higher version or release number
1.1.8.2. Migrate from a CD release to an LTS release at a higher version
or release number.
References:
IBM MQ release types:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.pla.doc/q004
715_.htm#q004715_
IBM MQ FAQ for Long Term Support and Continuous Delivery releases:
http://www-01.ibm.com/support/docview.wss?uid=swg27047919 What's
new and changed in IBM MQ Version 9.0 (LTS)
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.pro.doc/q11
3110_.htm
What's new and changed in Version 9.0.x (CD):
8110_.htm
1.2. Design an appropriate infrastructure to meet conflicting requirements
SUBTASK(S):
1.2.1. Handle messages with different business value and time to live
1.2.1.1. Use different queue managers
1.2.1.2. Use different queues
1.2.2. Handle messages of different volume and/or size
1.2.2.3. Use different channels
1.2.3. Handle messages of different privacy and integrity
1.2.4. Demonstrate how to handle different requirements for persistence of
messages
Reference:
Mission: Messaging, Of mice and elephants:
https://www.ibm.com/developerworks/websphere/techjournal/0804_mismes/0804
_mismes-pdf.pdf Planning:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.pla.d
oc/q004690_.htm
IBM MQ distributed queuing techniques:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.d
oc/q015290_.htm
oc/q004730_.htm
1.3. Identify the pre-requisites for installing and implementing an IBM MQ

configuration, including multi-instance queue managers
SUBTASK(S):
1.3.1. Identify system requirements for IBM MQ software v9
1.3.1.1. Identify various OS levels for each supported platform (i.e., Linux,
AIX, Windows)
1.3.1.2. Use the Software Product Compatibility Reports (SPCR) tool to
determine supported operating systems, related software,
hypervisors and hardware requirements;
1.3.1.3. Determine space requirements for MQ software, logging and
message data.
1.3.2. Check file system compatibility for multi-instance queue managers. 1.3.2.1.
Run amqmfsck to determine if a shared file system meets the
requirements for storing the queue manager data of a multiinstance queue
manager.
1.3.2.2. Run the integrity checker application (AMQHAFST) to put and get
persistent messages under syncpoint while failing over the queue
manager and ensuring that no messages get lost or corrupted.
1.3.2.3. Check that error messages are correctly written to the error logs
during multi-instance queue manager failover test
1.3.3. Demonstrate how to verify tuning of operating system, including user limits
and kernel parameters for resources like shared memory and semaphores
1.3.3.1. mqconfig script output can be used to identify system settings that
need to be altered to prevent resource problem while running MQ
software
REFERENCES:
http://www-01.ibm.com/support/docview.wss?uid=swg27047751
oc/q018140_.htm https://www-
304.ibm.com/support/docview.wss?uid=swg21446194 https://www-
304.ibm.com/support/docview.wss?uid=swg21271236
1.4. Plan the appropriate backup and recovery strategy

SUBTASK(S):
1.4.1. Illustrate how logs can be used for recovery.
1.4.1.1. Restart recovery, when MQ is stopped in a planned way
1.4.1.2. Failure recovery, when a failure stops IBM MQ unexpectedly
1.4.1.3. Media recovery, to restore damaged objects
1.4.1.3.1. Linear logging required
1.4.1.3.2. Using rcdmqimg and rcrmqobj to record images and
recreate objects
1.4.2. Plan space required for logs and data
1.4.3. Plan for persistent messages as needed to ensure that critical data is not
lost, as non-persistent messages may be discarded upon queue manager
restart
1.4.4. Creating a backup
1.4.4.1. Ensure queue manager is stopped appropriately for backup
1.4.4.2. Backup entire queue manager with data
1.4.4.3. Backup queue manager configuration only – dmpmqcfg command
1.4.4.4. Using strmqm –r command to update backup queue manager by
reading qmgr log and replaying updates to the object file
1.4.5. Understand the implications of restoring a backup
1.4.5.1. Possible loss or duplication of data
REFERENCES:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.co
n.doc/q017790_.htm
n.doc/q018580_.htm
1.5. Describe the differences between MQ Advanced and MQ
SUBTASK(S):
1.5.1. Identify MQ Chargeable Components that are part of MQ Advanced
1.5.1.1. IBM MQ (Server)
1.5.1.2. Advanced Message Security
1.5.1.3. Managed File Transfer Service
1.5.1.4. Unlimited installs of MQ Telemetry
1.5.1.5. Unlimited installs of IBM MQ Client
1.5.1.6. *New* Unlimited installs of Managed File Transfer Agent,
providing the Queue Manager the Agent connects to is entitled
using IBM MQ Advanced capacity
Reference:
IBM MQ license information:
6140_.htm
1.6. Select the appropriate IBM MQ platform for a given workload
SUBTASK(S):
1.6.1. Determine if local or remote QM is required
1.6.2. Determine if requirements mandate specific platform
1.6.3. Determine if MQ can be virtualized/containerized
1.6.4. Determine required infrastructure for workload
Reference:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.pl
a.doc/q004690_.htm
1.7. Outline migration considerations, including impact on existing

applications and multi-installation
SUBTASK(S):
1.7.1. Upgrade Process
1.7.1.1. Check Pre-reqs
1.7.1.1.1. MQ pre-reqs
1.7.1.1.2. Other IBM pre-reqs
1.7.1.1.3. Other application pre-reqs
1.7.1.2. Determine migration path
1.7.1.3. Determine migration method
1.7.1.3.1. Rip-and-replace
1.7.1.3.2. Side-by-side
1.7.1.3.3. Multi-stage
1.7.1.4. Review interoperability considerations
1.7.1.5. Migrate
1.7.1.5.1. Special considerations for MIQM/Clusters (references 2
and 3)
1.7.2. Single instance to multi instance
1.7.2.1. Review requirements
1.7.2.2. Make infrastructure changes
1.7.2.3. Test infrastructure for support
1.7.2.4. Setup/configure users/groups as necessary
1.7.2.5. Move QM data/logs to share
1.7.2.6. Update QM configuration (if needed)
1.7.2.7. Add QM configuration to new server
1.7.2.8. Add new server to client/channels
1.7.2.9. Update other tools/applications/scripts for new server
Reference:
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/websph
ere_mq_ibm_mq_migration_guide?lang=en
a.doc/q004820_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.mi
g.doc/q008110_.htm
https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.mig.d
oc/q007620_.htm
Section 2 - Configuration
2.1. Create the necessary IBM MQ objects to support an application
SUBTASK(S):
2.1.1. Working with queue managers
2.1.1.1. Creating and managing queue managers on distributed platforms
2.1.1.2. Changing IBM MQ and queue manager configuration
2.1.1.3. Knowledge about mqs.ini and qm.ini configuration file
2.1.2. Working with queues
2.1.2.1. Creating MQ local and alias queues as per specification
2.1.2.2. Deleting local and alias queues
2.1.2.3. Clearing a local queue
2.1.2.4. Browsing a queue
2.1.2.5. Copying local and alias queue definitions
2.1.3. Configuring connections between the server and client
2.1.3.1. Using the IBM MQ listener
2.1.3.2. Creating the SVRCONN channel
Reference:
n.doc/q015210_.htm
n.doc/q018670_.htm
n.doc/q018700_.htm
n.doc/q018710_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.1.0/com.ibm.mq.d
oc/fa11220_.htm
n.doc/q016480_.htm
n.doc/q016090_.htm
2.2. Configure IBM MQ channels based on the network topology.
SUBTASK(S):
2.2.1. What are different channel types
2.2.1.1. Message channel
2.2.1.2. MQI channel
2.2.1.3. AMPQ channel
2.2.1.4. MQTT channel
2.2.2. Define the appropriate XMITQ queue to support channel
2.2.3. Define and modify various channels using MQSC commands
2.2.3.1. Sender channel
2.2.3.2. Server channel
2.2.3.3. Receiver channel
2.2.3.4. Requester channel
2.2.3.5. Client-connection channel
2.2.3.6. Server-connection channel
2.2.3.7. Cluster-sender channel
2.2.3.8. Cluster-receiver channel
2.2.3.9. MQTT channel
2.2.4. Define shared channels for IBM MQ for z/OS
2.2.5. Configure multiple IBM MQ channels in a non-clustered configuration
Reference:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.explo
rer.doc/e_channels.htm
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.ref.a
dm.doc/q085520_.htm
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.pro.d
oc/q003720_.htm
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.wmqfte.d
oc/configuring_channels_noncluster.htm
2.3. Configure IBM MQ objects for triggered applications and channels.
SUBTASK(S):
2.3.1. Triggering applications
2.3.1.1. Create application queue with name of the initiation queue in the
corresponding attribute
2.3.1.2. Define initiation queue
2.3.1.3. Create process definition for the triggering
2.3.1.4. Control trigger events with trigger conditions
2.3.1.5. Ensure the trigger monitoring is running for applications
2.3.2. Triggering channels
2.3.2.1. Create transmission queue with name of the initiation queue in the
corresponding attribute.
2.3.2.2. Define initiation queue
2.3.2.3. Control trigger events with trigger conditions
2.3.3. Properties of trigger messages
2.3.4. Troubleshoot triggering
Reference:
n.doc/q015730_.htm
ev.doc/q026920_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.a
dm.doc/q021080_.htm
https://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.csqz
ae.doc/ic10400_.htm
ev.doc/q026940_.htm
ev.doc/q026930_.htm
ev.doc/q027000_.htm
ev.doc/q027010_.htm
2.4. Create the objects required to enable queue manager clustering and
workload distribution
SUBTASK(S):
2.4.1. Describe how an MQ cluster works
2.4.2. Create the MQ cluster repository
2.4.2.1. Describe the ideal number of full repository queue managers
2.4.2.2. Configure a full repository queue manager
2.4.2.2.1. Modify queue-manager definitions to add repository
definitions
2.4.2.2.2. Create a suitable cluster receiver channel
2.4.2.2.3. Create a suitable cluster sender channel
2.4.3. Define the required cluster object
2.4.4. Define workload distribution in clusters
2.4.4.1. Add queue manager to an existing cluster
2.4.4.2. Add a queue to act as a backup
2.4.4.3. Add a queue manager to process more requests
2.4.4.4. Configure attributes associated with queue managers, queues,
and channels to manage message distribution
2.4.5. Clustering good practices
Reference:
a.doc/q004740_.htm
n.doc/q017470_.htm
n.doc/q017690_.htm
n.doc/q017760_.htm http://www-
01.ibm.com/support/docview.wss?uid=pub1sc34658900
2.5. Predict the final destination of a message given a scenario containing

alias or remote definitions
SUBTASK(S):
2.5.1. Understand how queue manager performs queue name resolution
2.5.2. Understand queue names resolution when using MQOPEN
2.5.3. Understand how a message is routed through a distributed network
Reference:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.re
f.con.doc/q081570_.htm
ev.doc/q025990_.htm
n.doc/q015510_.htm
oc/q002660_.htm
2.6. Define the objects to support a publish/subscribe topology
SUBTASK(S):
2.6.1. Read about IBM WebSphere MQ publish/subscribe messaging
2.6.2. Describe the components of MQ publish/subscribe (PubSub) messaging
Publishers and publications
2.6.2.1. Describe Subscribers and subscriptions
2.6.2.2. Describe Topics
2.6.2.3. Describe Topic trees
2.6.3. Describe how single queue manager PubSub works
2.6.4. Describe how distributed PubSub work
2.6.5. Compare Publish/subscribe topologies
2.6.5.1. Define Publish/subscribe clusters
2.6.5.2. Define Publish/subscribe hierarchies
2.6.6. Configure and manage MQ PubSub with MQSC commands
2.6.6.1. Use DEFINE TOPIC (Use Topic Attributes PUBSCOPE,
SUBSCOPE, PROXYSUB)
2.6.6.2. Use DISPLAY TOPIC
2.6.6.3. Use DISPLAY TCLUSTER
2.6.6.4. Use DISPLAY TPSTATUS
2.6.6.5. Use USEDLQ attribute on topic
2.6.6.6. Use DISPLAY PUBSUB ALL
2.6.6.7. Setup subscription success or failure with PMSGDLV or
NPMSGDLV topic attributes
2.6.6.8. Use DEFINE SUB
2.6.6.9. Use DISPLAY SUB(*) TYPE(PROXY)
2.6.6.10. Use DISPLAY PUBSUB TYPE(local|child|parent|all)
Reference:
oc/q004870_.htm
a.doc/q004890_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.pr
o.doc/q004950_.htm
o.doc/q004990_.htm
a.doc/q004900_.htm
a.doc/q005120_.htm
a.doc/q005170_.htm
a.doc/q005200_.htm
o.doc/q005135_.htm
o.doc/q004920_.htm
o.doc/q004870_.htm
o.doc/q002960_.htm
2.7. Configure IBM MQ objects to support JMS
SUBTASK(S):
2.7.1. Configure connection factories and destinations in a JNDI namespace
2.7.1.1. Configure JMS objects using MQ Explorer
2.7.1.2. Configure JMS objects using the administration tool (jmsadmin)
2.7.1.3. Understand the use of the MQ Resource adapter
2.7.2. Tune channel MAXINST to guard against runaway client
2.7.3. Understand security implications for client connections
2.7.4. Use CCDT file to connect to queue manager from MQ clients
2.7.5. Use WebSphere MQ automatic client reconnection with the WebSphere
MQ classes for JMS
CLIENTRECONNECTOPTIONS
CONNECTIONNAMELIST
CCDTURL
2.7.6. Specify BOQNAME/BOQTHRESH so JMS avoids use of the DLQ
2.7.7. Ensure all permissions on all objects include +inq
2.7.8. DEFINE QMODEL, queues to be used by applications at runtime
Reference:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.explo
rer.doc/j_jmsadmin_intro.htm
oc/q123350_.htm
https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.sec.d
oc/q113250_.htm
https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/avoidin
g_runaway_numbers_of_mq_channels?lang=en
https://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.ref.c
on.doc/q081960_.htm
oc/q016730_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.se
c.doc/q118710_.htm
ev.doc/q032280_.htm
dm.doc/q020830_.htm
2.8. Configure channel exits
SUBTASK(S):
2.8.1. Describe the different MQ channel exits available and their uses
2.8.1.1. Enumerate the different MQ channel exit types
2.8.1.2. Describe the function of each of the different channel exit types
2.8.1.3. Describe the limitations of each of the different channel exit types
2.8.2. Describe the different channel exit calls and associated data structures
2.8.2.1. Describe the sequence of calls for each of the different channel
exit types
2.8.2.2. Describe the input information for each of the different channel
exit types
2.8.2.3. Describe the possible outputs from each of the different channel
exit types
2.8.3. Describe the programming languages and the associated requirements for
writing an MQ channel exit
2.8.3.1. Describe which programming languages may be used to write
channel exits for distributed platforms and z/OS
2.8.3.2. Describe the requirements and restrictions on the different
programming languages
2.8.4. Configure a channel auto-definition exit
2.8.4.1. Describe the parameters used to configure a channel
autodefinition exit
2.8.4.2. Describe the data which is applicable for each parameter used to
configure a channel auto-definition exit
2.8.4.3. Describe what types of channel may be configured with a channel
auto-definition exit
2.8.4.4. Modify an appropriate channel definition to configure a channel
auto-definition exit
2.8.5. Configure a channel message exit
2.8.5.1. Describe the parameters used to configure a channel message
exit
configure a channel message exit
message exit
message exit
2.8.6. Configure a channel security exit
2.8.6.1. Describe the parameters used to configure a channel security exit
configure a channel security exit
security exit
security exit
2.8.7. Configure a channel receive exit
2.8.7.1. Describe the parameters used to configure a channel receive exit
configure a channel receive exit
receive exit
receive exit
2.8.8. Configure a channel send exit
2.8.8.1. Describe the parameters used to configure a channel send exit
configure a channel send exit
send exit
send exit
2.8.9. Configure an MQI channel exit
2.8.9.1. Describe the type of MQI channel exit
2.8.9.2. Describe the parameters used to configure an MQI channel exit
configure an MQI channel exit
2.8.9.4. Modify the appropriate definition to configure an MQI channel exit
Reference:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q
027990_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.ref.dev.d
oc/q108170_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.ref.dev.d
oc/q108190_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.sec.doc/q
010660_.htm
https://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/cs12120
_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.1.0/com.ibm.mq.doc/ic174
70_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q
028100_.htm
Section 3 - Security
3.1. Configure Channel Authentication (CHLAUTH)
SUBTASK(S):
3.1.1. Describe the filtering and authentication functions of CHLAUTH
3.1.1.1. IP/Address filtering
3.1.1.2. User ID filtering
3.1.1.3. PEERNAME authentication
3.1.2. Identify the major functions performed by CHLAUTH rules
3.1.2.1. Deny access
3.1.2.2. Grant access
3.1.2.3. Grant access and map the user ID to a locally relevant value
3.1.3. Describe the behavior when CHLAUTH is enabled and a connection
request does not match any CHLAUTH rule
3.1.4. Determine which CHLAUTH rule takes precedence when more than one
rule matches a connection request
3.1.4.1. Multiple rules of the same rule type with different specificities
3.1.4.2. Multiple rules of different types
3.1.5. Describe interaction between CHLAUTH and other MQ security controls
3.1.5.1. CHLAUTH PEERMAP and CHANNEL SSLPEER
3.1.5.2. CHLAUTH rule and security exit
3.1.5.3. CHLAUTH and AUTHREC
3.1.6. Verify CHLAUTH configuration for specific connection criteria
3.1.6.1. Using CHLAUTH WARN
3.1.6.2. Using MQSC MATCH(RUNCHECK)
3.1.6.3. Using event messages
References:
Security concepts and mechanisms
c.doc/q009730_.htm
Channel authentication records
c.doc/q010250_.htm
MQSC DISPLAY CHLAUTH--for MATCH(RUNCHECK) in particular
f.adm.doc/q086070_.htm
MQSC SET CHLAUTH--for functions, precedence, usage in general
3.2. Understand the purpose of Connection Authentication (CONNAUTH)

SUBTASK(S):
3.2.1. Summarize the features of CONNAUTH
3.2.1.1. Authenticate local connections
3.2.1.2. Authenticate remote client connections
3.2.1.3. Distinguish between Admin and non-Admin connections
3.2.2. Describe the advantages of CONNAUTH over other types of
authentication in MQ
3.2.2.1. IP/DNS and user ID matching are filtering, not true authentication
3.2.2.2. Certificates (TLS) can be copied and are harder to revoke
3.2.2.3. Enterprise credentials used by CONNAUTH are subject to
password complexity, change frequency, and revocation standards
3.2.3. Choose the appropriate CONNAUTH setting
3.2.3.1. To authenticate Admin connections only
3.2.3.2. To authenticate remote connections only
3.2.4. Explain how CONNAUTH interacts with AUTHREC rules
Reference:
Connection authentication
c.doc/q113240_.htm
3.3. Control access to IBM MQ objects
SUBTASK(S):
3.3.1. Identify the different methods of setting access control rules on MQ objects
3.3.1.1. Use setmqaut CLI commands
3.3.1.2. Use SET AUTHREC commands within MQSC scripts
3.3.1.3. Use the SET AUTHORITY PCF command
3.3.2. Demonstrate specificity precedence of explicit and wild carded rules
3.3.2.1. Effect of * versus **
3.3.2.2. Governing rule when multiple rules match
3.3.3. Explain authorizations within topic hierarchies
3.3.3.1. When a rule matches multiple topic objects
3.3.3.2. When multiple rules match the same topic object
3.3.4. Name the authorizations that allow non-admin users and applications to
escalate to full admin privileges
3.3.4.1. Granting +chg on the queue manager
3.3.4.2. Granting +all on the Command Queue
3.3.4.3. Granting +crt on queues
3.3.5. Configure AUTHREC rules for the low-privileged MCAUSER in a RCVR
channel
3.3.5.1. +connect +inq +setid on the QMgr
3.3.5.2. +ctrlx on the channel
3.3.5.3. +open +put +setall on the DLQ and any application queues
3.3.6. Explain the security difference between setting the MCAUSER of a RCVR
channel versus setting AUTHREC rules on the XMITQ of the
corresponding SDR channel
3.3.7. Explain how to safely grant non-Admin users access to the Command
Queue to enable MQ Explorer
3.3.7.1. Grant +put and +inq but not +setid or +setall on the Command
Queue
3.3.7.2. Grant inquiry-only (+dsp/+inq) on other objects
3.3.7.3. Grant +browse on queues if message data is not restricted
3.3.8. Determine the object against which authorization will be checked
3.3.8.1. When opening an alias queue
3.3.8.2. When opening a non-local clustered queue
3.3.8.3. When opening a QRemote
3.3.9. Determine the authorization records that are in effect for a given object and
user
3.3.9.1. dspmqaut
3.3.9.2. dmpmqaut
Reference:
Planning authorization
c.doc/q010310_.htm
Authorizations for MQI calls
c.doc/q011170_.htm
Authorizations for PCF commands
c.doc/q011190_.htm?view=kc Name resolution
ev.doc/q025990_.htm
3.4. Configure IBM MQ channels with TLS/SSL
SUBTASK(S):
3.4.1. Identify the business requirements for which TLS is an appropriate solution
3.4.1.1. Encryption of data "on the wire"
3.4.1.2. Authentication of incoming connection requests
3.4.1.3. Integrity of data in transit
3.4.2. Generate a self-signed certificate for the queue manager and extract the
public portion
3.4.2.1. Use runmqakm -kdb -create
3.4.2.2. Use runmqakm -cert -create
3.4.2.3. Use runmqakm -cert -export
3.4.3. Generate a certificate signing request and install the signed certificate
3.4.3.1. Use runmqakm -csr -create
3.4.3.2. Submit the CSR for signing
3.4.3.3. Use runmqakm -cert -receive
3.4.4. Prepare the connection partner to trust the certificate
3.4.4.1. Install the cert signer chain for signed certificates
3.4.4.2. Install the public certificate for self-signed certs
3.4.5. Set queue manager’s CERTLABL and SSLKEYR
3.4.6. Describe what must be done after updating the queue manager's KDB
3.4.6.1. REFRESH SECURITY TYPE(SSL)
3.4.6.2. Or restart the queue manager
3.4.7. Configure SDR/RCVR channel pair
1.1. Without SSL
3.4.7.1. Using SSLCIPH and SSLCAUTH(OPTIONAL)
3.4.7.2. Using SSLCIPH and SSLCAUTH(REQUIRED)
3.4.7.3. Using SSLPEER
3.4.7.4. Using CHLAUTH PEERMAP
3.4.8. Debug the TLS connection
3.4.8.1. Queue manager error logs
3.4.8.2. Event messages
3.4.8.3. Client error logs
3.4.8.4. Traces
Reference:
Protecting channels with SSL/TLS
c.doc/q010750_.htm
Adding a CA certificate (or the public part of a self-signed certificate) into a key
repository, on UNIX, Linux or Windows systems
c.doc/q012830_.htm
SSLCAUTH, SSLCIPH, SSLPEER
dm.doc/q085520_.htm#q085520___sslcauth REFRESH
SECURITY
Renewing an existing personal certificate on UNIX, Linux, and Windows systems
c.doc/q012790_.htm
TLS Troubleshooting information
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.tr
o.doc/q123400_.htm runmqckm, and runmqakm commands
c.doc/q083820_.htm
3.5. Configure the IBM MQ client with TLS/SSL
SUBTASK(S):
3.5.1. Name some of the ways for an MQ client to locate the TLS keystore
3.5.1.1. The Client Channel Definition Table file
3.5.1.2. SSL stanza of the client configuration file
3.5.1.3. Environment variables
3.5.2. Determine the cause of TLS errors with MQ Client
3.5.2.1. Client error log
3.5.2.2. Client-side trace
3.5.2.3. Server-side error log
3.5.2.4. Event messages
3.5.3. Describe the configuration required for anonymous TLS connections
3.5.3.1. Channel set to SSLCAUTH(OPTIONAL)
3.5.3.2. The client must not have a personal certificate in its keystore
Reference:
SSL stanza of the client configuration file
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm
.mq.con.doc/q016900_.htm
3.6. Describe MQ features that provide intrusion detection
SUBTASK(S):
3.6.1. Outline the steps to design and implement intrusion detection
3.6.1.1. Understand the capabilities of the version of MQ
3.6.1.2. Describe the threats for which detection is desired
3.6.1.3. Enable the MQ features as required
3.6.1.4. Implement a program or monitor to collect the events and
instrumentation
3.6.1.5. Configure rules to alert based on events and state
3.6.1.6. Describe the effects of intrusion detection on the appliance
3.6.2. Name some of the event message types useful for intrusion detection
3.6.2.1. Authority events reveal failed connection attempts and failed object
access attempts
3.6.2.2. Configuration events reveal when system changes are made
3.6.2.3. Performance events reveal potential DOS attacks
3.6.2.4. Channel events provide evidence of unauthorized connection
attempts
3.6.2.5. Logger events can reveal unusual log usage patterns
3.6.2.6. Command events document all successful MQSC and PCF
commands
3.6.3. Describe how the Performance Monitoring API provides intrusion detection
capability
Reference:
Event monitoring
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.m
on.doc/q036150_.htm Event types
on.doc/q036170_.htm
System topics for monitoring and activity trace
on.doc/mo00040_.htm
Developing your own resource monitoring program
on.doc/mo00014_.htm
3.7. Distinguish between the available security choices
SUBTASK(S):
3.7.1. Name some of the MQ features that provide authentication
3.7.1.1. Security exit
3.7.1.2. CHANNEL SSLPEER,
3.7.1.3. CHLAUTH PEERMAP
3.7.1.4. CONNAUTH
3.7.1.5. AMS Signer policy
3.7.1.6. AMS Recipient policy
3.7.2. Name some of the MQ features that provide authorization
3.7.2.1. Message exit
3.7.2.2. API exit
3.7.2.3. CHLAUTH IP/DNS blocking
3.7.2.4. CHLAUTH User blocking
3.7.2.5. Object Authority Manager
3.7.2.6. AMS Signer policy
3.7.2.7. AMS Recipient policy
3.7.2.8. Custom authorization service
3.7.3. Name some MQ features that provide data confidentiality
3.7.3.1. CHANNEL non-null SSLCIPH
3.7.3.2. AMS encryption policy
3.7.4. Name some MQ features that provide data integrity
3.7.4.1. CHANNEL non-null SSLCIPH
3.7.4.2. AMS signing policy
3.8. Configure end-to-end message security

SUBTASK(S):
3.8.1. Create a keystore
3.8.2. Edit the keystore.conf file
3.8.3. Populate the keystore with at least one personal certificate
3.8.4. If message signer or recipient policies will be used, populate the keystore
with the certificates of the authorized signers and recipients
3.8.5. Set one or more AMS policies
Reference:
Advanced Message Security
c.doc/q014580_.htm
Section 4 - Administration
4.1. Administer queue managers and their objects
SUBTASK(S):
4.1.1. Administer queue managers and associated resources using local
administration or remote administration
4.1.1.1. Perform local administration tasks on queue managers that are
defined on local system
4.1.1.2. Perform remote administration of queue managers and their
objects from local system
4.1.2. Administer MQ Objects using the IBM MQ control commands issued at
system command line
4.1.3. Administer MQ Objects using the MQSC commands
4.1.4. Use Programmable Command Formats (PCFs) to perform administration
of queue managers (that supports PCFs) in a network
4.1.5. Administer MQ network of queue managers using MQ Explorer from a
computer running Windows, or Linux
4.1.6. Administer the MQ appliance using the web-based MQ Console (MQ
Appliance)
4.1.7. Administer MQ objects on z/OS using ISPF
Reference:
dm.doc/q019950_.htm
dm.doc/q019960_.htm
dm.doc/q021090_.htm
dm.doc/q019970_.htm
dm.doc/q020620_.htm
dm.doc/q019990_.htm
dm.doc/q020330_.htm
dm.doc/q020330_.htm
dm.doc/q127570_.htm
https://www.ibm.com/support/knowledgecenter/en/SS5K6E_9.0.0/com.ibm.mqa.
doc/administering/ad00010_.htm
4.2. Configure IBM MQ Explorer for remote administration

SUBTASK(S):
4.2.1. Identify the prerequisite software and definitions to use MQ Explorer
4.2.2. Identify the security requirements for using MQ Explorer
4.2.2.1. Identify the authorization requirements to use the MQ Explorer
4.2.2.2. Secure the channel between MQ Explorer and each remote queue
manager
4.2.2.3. Secure the MQI Channel between MQ Explorer and the remote
queue manager using TLS security
4.2.3. Use MQ Explorer to connect to a queue manager directly or use an
intermediary queue manager
4.2.4. Configure queue manager to allow read-only access for MQ Explorer
Reference:
dm.doc/q020380_.htm
dm.doc/q020390_.htm
dm.doc/q020400_.htm
dm.doc/q020480_.htm
dm.doc/q020410_.htm
dm.doc/q020430_.htm
dm.doc/q020440_.htm
dm.doc/q020450_.htm
https://hursleyonwmq.wordpress.com/2007/02/08/using-websphere-mq-
exploreras-a-read-only-viewer/
4.3. Monitor and alter IBM MQ using the different command tools
SUBTASK(S):
4.3.1. Perform administration using MQSC commands
4.3.1.1. Display/Modify queue manager parameters
4.3.1.2. Display/Define/Modify/Delete queue manager objects like queues,
channels, listeners, topics, subscriptions, services, process
definitions, etc.
4.3.1.3. Start/Stop/Refresh/Resolve queue manager objects
4.3.2. Use PCF to perform administration tasks
4.3.2.1. Identify the format of PCF command message
4.3.2.2. Send and Receive PCF messages in specified queue
4.3.2.3. Identify the PCF commands for specific actions
4.3.3. Identify and use CL commands for MQ Administration.
4.3.4. Perform administration using Command Line Interface.
4.3.4.1. Perform queue manager administration using control commands
4.3.4.2. Use utility control commands to perform administration
4.3.5. Perform administration tasks using administrative tools.
4.3.5.1. Use IBM MQ Explorer to monitor and alter IBM MQ
4.3.5.2. Configure and use MQ Console to monitor and alter IBM MQ (MQ
Appliance)
Reference:
dm.doc/q020620_.htm
dm.doc/q020010_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.ex
plorer.doc/e_configuring.htm
n.doc/q128300_.htm
dm.doc/q127570_.htm
4.4. Define procedures to recover messages and objects in the event of

failure
SUBTASK(S):
4.4.1. Identify the recovery steps in the case of disk drive failures
4.4.1.1. Identify the recovery steps that can be performed in the case of
linear logging.
4.4.1.2. Identify the recovery steps that can be performed in the case of
circular logging.
4.4.2. Identify the recovery steps in the case of damaged queue manager objects
4.4.3. Recover damaged object in IBM MQ
4.4.4. Identify the recovery procedures for IBM MQ on z/OS
4.4.5. Identify the recovery procedures for IBM MQ Appliance
Reference:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.tro.d
oc/q040550_.htm
oc/q040560_.htm
n.doc/q018550_.htm
oc/q040590_.htm
https://www.ibm.com/support/knowledgecenter/SS5K6E_9.0.0/com.ibm.mqa.doc/
troubleshooting/tr00030_.htm
4.5. Implement dead-letter queue handling
SUBTASK(S):
4.5.1. Configure dead letter queue for queue managers
4.5.2. Process messages from dead letter queue using DLQ handler
4.5.3. Use DLQ Handler rules table to process messages that arrive on the DLQ
Reference:
dm.doc/q020730_.htm
dm.doc/q005540_.htm
dm.doc/q005640_.htm
dm.doc/q005660_.htm
4.6. Acquire and apply maintenance
SUBTASK(S):
4.6.1. Query the maintenance level of the IBM MQ
4.6.2. Acquire fix packs from Fix Central
4.6.3. Apply and remove fix packs on platforms
4.6.4. Apply upgrade on an MQ platform
Reference:
g.doc/q006180_.htm
g.doc/q008130_.htm
g.doc/q007990_.htm
g.doc/q006260_.htm
Section 5 - Availability
5.1. Configure and manage a multi-instance queue manager
SUBTASK(S):
5.1.1. Describe the storage requirements for a multi-instance queue manager
5.1.1.1. Describe the restrictions on shared storage for a multi-instance
queue manager
5.1.1.2. Describe what shared storage must be defined for a multi-instance
queue manager
5.1.2. Create a multi-instance queue manager
5.1.2.1. Create a primary multi-instance queue manager
5.1.2.2. Create a standby multi-instance queue manager
5.1.2.3. Describe the process for converting a single instance queue
manager to a multi-instance queue manager
5.1.3. Start and stop a primary multi-instance queue manager
5.1.3.1. Start a queue manager allowing it to be multi-instance primary
5.1.3.2. Start a queue manager preventing it from being multi-instance
5.1.3.3. Start a queue manager allowing it to be multi-instance standby
5.1.3.4. Stop both the primary and standby instances of a multi-instance
queue manager in a single command execution
5.1.3.5. Stop the primary instance and switch to using the standby
instance
5.1.3.6. Stop the standby instance
5.1.4. Display the status of the instance(s) of a multi-instance queue manager
and show where they are executing
5.1.5. Apply maintenance to a multi-instance queue manager
5.1.5.1. Understand the process that must be followed to apply
maintenance to a multi-instance queue manager
5.1.6. Describe the implications for MQ Clustering if a multi-instance queue
manager is included in the cluster
5.1.6.1. Describe the restrictions placed on an MQ cluster when a
multiinstance queue manager is a member of the cluster
5.1.6.2. Describe the implications of using a multi-instance queue
manager as a cluster repository Reference:
oc/q018140_.htm
oc/q018330_.htm
g.doc/q008110_.htm
n.doc/q018160_.htm
n.doc/q018300_.htm
a.doc/q004830_.htm
a.doc/q004830_.htm
5.2. Configure IBM MQ for automatic client reconnection
SUBTASK(S):
5.2.1. Describe how automatic client reconnection may be configured
5.2.1.1. Programmatically on the MQCONN or MQCONNX invocation
5.2.1.2. Using a Client Connection Definition Table (CCDT)
5.2.1.3. Using a client.ini file
5.2.2. Describe the automatic client connection requirements
5.2.2.1. Describe the version level restrictions for automatic client
reconnection
5.2.2.2. Describe the requirements for automatic client reconnection
5.2.3. Describe the parameters that may affect automatic client reconnection and
how their settings have an effect
Reference:
oc/q017800_.htm
dm.doc/q085570_.htm
5.3. Implement backup, restart and recovery procedures
SUBTASK(S):
5.3.1. Implement procedure for graceful shutdown and restart when downtime is
required
5.3.1.1. Use endmqm –w command (a wait shutdown), only if that fails,
use the endmqm -i
5.3.2. Create and use a backup queue manager
5.3.2.1. Use crtmqm to create qmgr, needs to be same MQ level or higher,
same attributes, same platform
5.3.2.2. Overwrite backup qmgr data and log files with copies of existing
qmgr data and log files
5.3.2.3. Use strmqm –r command to designate backup qmgr and replay
copies log extents
5.3.3. Backup queue manager data
5.3.3.1. Requires queue manager to be stopped
5.3.3.2. Make copies of all queue manager data and log file directories,
including subdirectories and .ini file
5.3.3.3. Backup mqs.ini file
5.3.3.4. Backup contents of exit directories and exit parameter files
5.3.3.5. Preserve ownership of the files
5.3.4. Recovering from media image
5.3.4.1. Recovering damaged objects
5.3.4.2. rcdmqimg command
5.3.4.3. rcrmqobj command
5.3.5. Backup queue manager configuration only – dmpmqcfg command
REFERENCES:
oc/q018550_.htm
oc/q018620_.htm
5.4. Implement a Queue-Sharing Group for high availability
SUBTASK(S):
5.4.1. Determine pre-reqs
5.4.2. Determining naming convention
5.4.3. Make necessary infrastructure changes for shared objects
5.4.4. Setup access controls
5.4.5. Create shared queues
5.4.6. Create Queue Sharing Group
5.4.7. Perform performance tuning (i.e. workload balancing)
Reference:
oc/q003630_.htm (and children links)
5.5. Manage an MQ cluster
SUBTASK(S):
5.5.1. Use multiple cluster transmit queues to isolate traffic between clusters
5.5.2. Remove a queue manager from an MQ cluster
5.5.3. Suspend and resume a queue manager from an MQ cluster
5.5.4. Describe the uses and effects of the REFRESH CLUSTER command
5.5.5. Display the contents of the MQ cluster repository
5.5.6. Move a full repository to another queue manager
5.5.7. Convert a distributed MQ network to an MQ cluster and vice versa
5.5.8. Interconnect two clusters
5.5.8.1. Using a gateway queue manager
5.5.8.2. Overlapping two or more clusters so that they share one or more
queue managers
5.5.9. Create and remove queues advertised to an MQ cluster
Reference:
o.doc/q002750_.htm
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v
2r2.isfa500/mqclust.htm
n.doc/q017160_.htm
n.doc/q017360_.htm
n.doc/q017350_.htm
5.6. Configure and manage HA/DR for MQ appliance
SUBTASK(S):
5.6.1. Physically connect ports as described (either direct or switched) 5.6.2.
Define HA/DR requirements
5.6.3. For HA:
5.6.3.1. Create HA group for appliances
5.6.3.2. Create HA QMs
5.6.3.3. Perform any necessary HA configuration items to meet the
defined requirements(i.e. Floating IP)
5.6.4. For DR:
5.6.4.1. Ensure connectivity
5.6.4.2. Configure QMs for DR
5.6.4.3. Perform any necessary DR configuration items to meet the
defined requirements (i.e. Floating IP)
5.6.5. Managing
5.6.5.1. Remove a member from the group
5.6.5.2. Failover/fail back
5.6.5.3. Modify QMs – Add/Delete/running preference/etc.
Reference:
1) https://www.ibm.com/support/knowledgecenter/SS5K6E_9.0.0/com.ibm.m
qa.doc/configuring/co00230_.htm
qa.doc/configuring/co00400_.htm
qa.doc/administering/ad00160_.htm - HA Managing (and children)
qa.doc/administering/ad00180_.htm - DR Managing (and children)
Section 6 - Monitoring
6.1. Explain the IBM MQ capabilities for monitoring
SUBTASK(S):
6.1.1. Describe the attributes that control monitoring
6.1.1.1. Describe the use and effect of the MONQ parameter on queue
definitions
6.1.1.2. Describe the use and effect of the MONCHL parameter on
channel definitions
6.1.2. Display monitoring data
6.1.2.1. Describe how the appropriate MQSC commands can be used to
display queue and/or channel status
6.1.2.2. Describe how to use the MQ explorer to display queue and/or
channel status
6.1.3. Monitor queues
6.1.3.1. Determine if an application has a queue open
6.1.3.2. Checking if messages on a queue are available to an application
6.1.3.3. Checking if an application is getting messages off a queue
6.1.3.4. Checking if an application can process messages fast enough
6.1.3.5. Routine monitoring of a queue
6.1.4. Monitor channels
6.1.4.1. Determine if a channel is running
6.1.4.2. Checking that a channel is processing messages
6.1.4.3. Checking why a batch takes a long time to process
Reference:
on.doc/q037980_.htm
6.2. Enable and monitor IBM MQ events
SUBTASK(S):
6.2.1. Describe the different types of instrumentation events that are available for
use and the type of information contained in the event message
6.2.2. Describe the queue from which a particular event type may be read
6.2.3. Configure the production of particular events and disable their production
6.2.3.1. Instrumentation events
6.2.3.2. Performance event
6.2.3.3. Configuration events
6.2.3.4. Command events
6.2.3.5. Logger events
6.2.3.6. Authority configuration events
6.2.4. Describe the format and structure of an event message
6.2.5. Describe the use of the sample program amqsevt as an example of
processing event messages
Reference:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.mon.
doc/q036150_.htm
6.3. Gather and analyze IBM MQ accounting and statistics data
SUBTASK(S):
6.3.1. Describe the differences between accounting and statistics messages, the
format of the data and the different collection methods that exist for
different platforms
6.3.1.1. For z/OS data is collected as part of the System Management
Facility (SMF) data collection
6.3.1.2. For distributed platforms, the data is collected via queues
6.3.2. Configure the collection of accounting and/or statistics data for queues
6.3.2.1. Collect the data based on control at a queue manager level
6.3.2.2. Collect the data based on control at a queue level
6.3.3. Configure the collection of accounting and/or statistics data for channels
6.3.3.1. Collect the data based on control at a queue manager level
6.3.3.2. Collect the data based on control at a channel level
6.3.3.3. Describe the potential effects of the different level of statistics
collection
6.3.4. Describe how to display the data that has been collected using the
amqsmon sample program or the MQ Console
Reference:
on.doc/q037240_.htm
on.doc/q037390_.htm
on.doc/q037420_.htm
6.4. Use IBM MQ administration tools or commands to monitor the status of

a queue manager, channel or queue
SUBTASK(S):
6.4.1. Check the status of a queue manager
6.4.1.1. Use control command dspmq
6.4.1.2. Use MQ Explorer and lookup the queue manager in the list under
queue managers
6.4.2. Check the status of a channel
6.4.2.1. Use MQSC command: DISPLAY CHSTATUS(Channelname) ALL
6.4.2.2. Use MQ Explorer and lookup the channel in the Channels tab
under the queue manager, select the channel and right-click and
select Status…
6.4.2.3. If additional information is needed turn MONCHL to
LOW,MEDIUM or HIGH on the channel or qmgr
6.4.3. Check the status of a queue
6.4.3.1. Use MQSC command: DISPLAY QSTATUS(Queuename) ALL
6.4.3.2. Use MQSC command: DISPLAY QSTATUS(Queuename)
TYPE(HANDLE) to see which application is accessing the queue
6.4.3.3. Use MQ Explorer and lookup the queuename under the queue tab
and right-click select Status…
6.4.3.4. If additional information is needed turn MONQ to LOW,MEDIUM
or HIGH on the queue or qmgr
Note: DISPLAY can be shortened to DIS but not DISP

CHSTATUS can be shortened to CHS but not CHST
QSTATUS can be shortened to QS but not QST
Reference:
Control command dspmq:
dm.doc/q083180_.htm Administration using MQSC:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.adm.
doc/q020620_.htm
Administration using the MQ Explorer:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.adm.
doc/q020620_.htm
Section 7 - Performance Tuning

7.1. Identify the tools available to assist with IBM MQ performance
SUBTASK(S):
7.1.1. Utilize accounting and statistics to determine how the MQ is performing
7.1.2. Describe how to capture Events, including performance events
7.1.3. Understand how to gather traces
Reference:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.m
q.mon.doc/q037240_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.m
q.mon.doc/q036320_.htm http://www-
01.ibm.com/support/docview.wss?uid=swg21291189
http://www.ibm.com/support/docview.wss?uid=swg21624944
http://www.ibm.com/support/docview.wss?uid=swg21271236
7.2. Use accounting and statistical data to identify and resolve performance
issues.
SUBTASK(S):
7.2.1. Describe the different data fields that are collected in statistics messages
for the MQI, for queues and for channels
7.2.1.1. There are three different statistics messages for the three types of
statistic message, each containing different data
7.2.2. Analyze the MQI statistics to determine if the incorrect use of an API is
causing an issue
An example of this would be the MQI statistics from a test run showing
that the number of MQOPEN, MQGET and MQCLOSE calls equaled the
number of messages read. This suggests that there is a loop in the
application performing MQOPEN-MQGET-MQCLOSE rather than
MQOPEN-Sequence of MQGETs-MQCLOSE
7.2.3. Analyze the queue statistics to determine the cause of a performance
issue with a queue
An example would be the use of the ExpiredMsgCount having a high
value, suggesting that there was insufficient resource getting the
messages
7.2.4. Analyze the MQI statistics to determine the cause of a performance issue
with a channel
An example would be using the complete, incomplete and average batch
size values to optimize the BATCHSZ parameter setting for a channel
Reference:
on.doc/q037420_.htm
7.3. Tune IBM MQ object definitions for performance
SUBTASK(S):
7.3.1. Understand the effects of different log properties
7.3.2. Understand configuration changes that should be made with large, small,
persistent, or non-persistent messages
7.3.3. Describe the performance implications and changes required to add TLS
7.3.4. Describe the conditions in which parameters would be set near their
extremes
7.3.5. Describe the tradeoffs between configuring for reliability vs performance
Reference:
https://www.ibm.com/developerworks/websphere/library/techarticles/0712_dunn/
0712_dunn.html
ftp://public.dhe.ibm.com/software/integration/support/supportpacs/individual/mp0
1.pdf
oc/q004090_.htm
7.4. Tune client and server connection channel parameters
SUBTASK(S):
7.4.1. Describe the interaction between DISCINT, HBINT and KAINT
7.4.2. Explain the performance considerations around TLS/SSL
7.4.3. Understand the effects of changing the channel properties
7.4.4. Understand the performance impact of COMPHDR and COMPMSG
7.4.5. Understand the performance impact of CLNTWGHT and AFFINITY
Reference:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.ex
plorer.doc/e_properties_channels.htm
7.5. Describe how to use the performance monitoring API
SUBTASK(S):
7.5.1. Use the amqsrua command to query metadata related to the system
resource usage of a queue manager.
7.5.2. Develop a program to monitor system resources using publish/subscribe
7.5.3. Parse the PCF messages that are returned
7.5.4. Authorize the user or service account to $SYS/MQ or lower
7.5.5. Decide which of the topics at or under $SYS/MQ/# meet the monitoring
requirement
7.5.6. Subscribe to the topics of interest
Reference:
on.doc/mo00040_.htm
on.doc/mo00013_.htm
on.doc/mo00014_.htm
Section 8 - Problem Determination
8.1. Locate problem information such as IBM MQ error logs, FFST files and
IBM MQ dumps
SUBTASK(S):
8.1.1. Locate specific queue manager Error logs
8.1.1.1. MQ error logs are named AMQERR01.LOG, AMQERR02.LOG
and AMQERR03.LOG
8.1.1.1.1. AMQERR01.LOG has the most recent info
8.1.1.2. By default QMGR error logs on UNIX are located in directory
/var/mqm/qmgrs/<queueManagerName>/errors
8.1.1.3. Windows default directory for queue manager logs
c:\Program Files\IBM\WebSphere
MQ\qmgrs\<queueManagerName>\errors
8.1.1.4. To find error logs location for qmgrs check qm.ini file for directory
8.1.1.4.1. The mqs.ini file specifies the qm.ini file location
8.1.1.5. Admins have ability to suppress or exclude messages that are not
indicating errors
8.1.2. Locate FFST files that contain information about errors
8.1.2.1. Files located in the /var/mqm/errors for UNIX and Linux systems
8.1.2.2. Files located in the C:\Program Files\IBM\MQ\errors directory for
windows
8.1.2.3. Files may be referred to as FDC files
8.1.2.4. Files are named AMQnnnnn.mm.FDC on Windows and UNIX
8.1.2.5. When using IBM MQ classes for JMS, FFST files are named
JMSC0001.FDC and found in subdirectory FFDC, of the current
working directory for the JMS application
8.1.3. Describe how to view logs and dumps on z/OS
8.1.3.1. SYSUDUMPS
8.1.3.2. SNAP DUMPS
8.1.3.3. Job logs are located in Syslog, MSTR job log, CHIN job log
REFERENCES:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg21173468#z
oc/q032310_.htm
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.5.0/com.ibm.mq.tr
o.doc/q039550_.htm
8.2. Produce an IBM MQ trace.
SUBTASK(S):
8.2.1. Identify what to trace
8.2.1.1. All processes of a queue manager
8.2.1.2. Api usage on a queue manager
8.2.1.3. Communication (comms) between queue managers
8.2.1.4. Whole applications (apps) using a queue manager
8.2.2. Start the trace (Use the strmqtrc command)
8.2.2.1. Depending on selected traces use appropriate options, like –t all
for all processes
8.2.2.2. -t api for api usage
8.2.2.3. -t comms for communications
8.2.2.4. -p Applname (if multiple names use , to separate) for
applications
8.2.3. End the trace (Use the endmqtrc command)
8.2.3.1. Use the same options you used to start to end the trace when -p
was used, otherwise use –a for all or -m for specified queue
manager
8.2.4. Locate the trace output files
8.2.5. Review the trace output (Use the dspmqtrc command)
8.2.6. Check if all tracing is off when done using strmqtrc -s
Reference:
Troubleshooting and support:
oc/q038530_.htm Using trace:
oc/q039590_.htm strmqtrc command:
8.3. Identify the steps to evaluate and recover a non-responsive queue

manager
SUBTASK(S):
8.3.1. Identify non-responsive queue manager
8.3.1.1. runmqsc command does not return information
8.3.1.2. Message processing is halted
8.3.2. Evaluate hung queue manager
8.3.2.1. Check for FFST files
8.3.2.2. Check error logs for messages
8.3.2.3. Check system file space
8.3.3. End and restart queue manager manually
8.3.3.1. Queue manager that will not end with endmqm –w wait option
may need to be ended immediately with endmqm –i option
8.3.3.2. Queue manager that will not end with endmqm –i option may
need to be ended immediately with endmqm –p option
8.3.3.3. Very rare occasions may require mq processes to be killed in
particular order
8.3.4. Describe steps to recover from unexpected failures
8.3.4.1. Disk drive failures
8.3.4.2. Damaged objects
8.3.5. Restore queue manager from point-in-time backups
REFERENCES:
mqzag.doc/fa22290_.htm
8.4. Identify and solve security issues with a user, application, or channel
SUBTASK(S):
8.4.1. Prevent intrusions
8.4.1.1. Test for positive and negative results to ensure users are not
overauthorized
8.4.2. Detect intrusions
8.4.2.1. Monitor logs for security errors
8.4.2.2. Check for intrusions by using event messaging
8.4.3. Respond and recover from a security incident
REFERENCES:
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.sec.d
oc/q014350_.htm
8.5. Determine the route that a message took through a queue manager
network
SUBTASK(S):
8.5.1. Monitoring messages
8.5.1.1. Display route (dspmqrte)
8.5.1.2. Activity recording
8.5.1.3. Trace-route messaging
8.5.2. Check for undelivered messages
8.5.2.1. Message on dead letter queue
8.5.2.2. Messages on transmission queues.
8.5.3. Manually investigate message route
8.5.3.1. Determine message route through a cluster
8.5.3.2. Determine point-to-point message routing including queue alias
and channels
REFERENCES:
https://www.slideshare.net/MattLeming/where-is-my-
message?cm_mc_uid=13747546678514912266867&cm_mc_sid_50200000=14
91394968
on.doc/q036600_.htm
8.6. Describe how to use the Application Activity Trace
SUBTASK(S):
8.6.1. Identify what to trace
8.6.2. Decide how to trace
8.6.2.1. Use mqat.ini and turn on and off ACTVTRC on queue manager
8.6.2.2. Use alternate method by subscribing to $SYS … ActivityTrace
topics
8.6.3. Start tracing
8.6.3.1. When using mqat.ini turn on ACTVTRC on queue manager
8.6.3.2. When using alternate method subscribe to
$SYS/MQ/INFO/QMGR/qmgr_name/ActivityTrace/resource_type/r
esource_identifier
8.6.4. Review the trace output (Use the amqsact program)
8.6.5. End tracing
8.6.5.1. When using mqat.ini turn off ACTVTRC on queue manager
8.6.5.2. When using alternate method remove subscription to
$SYS/MQ/INFO/QMGR/qmgr_name/ActivityTrace/resource_type/r
esource_identifier
Reference:
Application activity trace:
doc/q037520_.htm
Application activity trace - alternate method:
doc/mo00020_.htm
Next Steps
1. Take the IBM MQ v9.0, Systems Administrator assessment test. Use the
promotion code 2018StudyAssess20 for $20 off each assessment.
2. If you pass the assessment exam, visit pearsonvue.com/ibm to schedule
your testing sessions. Use the promotion code 2018StudyCert20 to
receive 20% off the exam.
3. If you failed the assessment exam, review how you did by section. Focus
attention on the sections where you need improvement. Keep in mind that
you can take the assessment exam as many times as you would like ($10
per exam), however, you will still receive the same questions only in a
different order.

MQ Detailed Exam Objectives

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MQ Detailed Exam Objectives

Uploaded by

Copyright:

Available Formats

IBM Cloud Professional

Study Guide Series

Exam C1000-002 - IBM MQ v9.0, Systems

High-level Exam Objectives...................................................................................................... 3

Detailed Exam Objectives ......................................................................................................... 5

Section 1 - Planning, Installation, and Migration .................................................................. 5

Section 2 - Configuration ........................................................................................................11

Section 3 - Security .................................................................................................................19

Section 5 - Availability .............................................................................................................31

Section 6 - Monitoring .............................................................................................................35

Section 7 - Performance Tuning ...........................................................................................37

Section 8 - Problem Determination .......................................................................................41

Next Steps ...................................................................................................................................44

It is recommended that you review these objectives. Do you know how to

Describe the differences between Long Term Support (LTS) and

2.1 Create the necessary IBM MQ objects to support an application

3.1 Configure Channel Authentication (CHLAUTH)

4.1 Administer queue managers and their objects

5.1 Configure and manage a multi-instance queue manager

Section 1 - Planning, Installation, and Migration

1.2. Design an appropriate infrastructure to meet conflicting requirements

1.3. Identify the pre-requisites for installing and implementing an IBM MQ

1.4. Plan the appropriate backup and recovery strategy

1.5. Describe the differences between MQ Advanced and MQ

1.6. Select the appropriate IBM MQ platform for a given workload

1.7. Outline migration considerations, including impact on existing

2.2. Configure IBM MQ channels based on the network topology.

2.3. Configure IBM MQ objects for triggered applications and channels.

2.5. Predict the final destination of a message given a scenario containing

2.6. Define the objects to support a publish/subscribe topology

2.7. Configure IBM MQ objects to support JMS

2.8. Configure channel exits

3.2. Understand the purpose of Connection Authentication (CONNAUTH)

3.3. Control access to IBM MQ objects

3.4. Configure IBM MQ channels with TLS/SSL

3.6. Describe MQ features that provide intrusion detection

3.7. Distinguish between the available security choices

3.8. Configure end-to-end message security

4.2. Configure IBM MQ Explorer for remote administration

4.4. Define procedures to recover messages and objects in the event of

4.5. Implement dead-letter queue handling

4.6. Acquire and apply maintenance

5.2. Configure IBM MQ for automatic client reconnection

5.3. Implement backup, restart and recovery procedures

5.4. Implement a Queue-Sharing Group for high availability

5.5. Manage an MQ cluster

5.6. Configure and manage HA/DR for MQ appliance

6.2. Enable and monitor IBM MQ events

6.4. Use IBM MQ administration tools or commands to monitor the status of

Note: DISPLAY can be shortened to DIS but not DISP

Section 7 - Performance Tuning

7.3. Tune IBM MQ object definitions for performance

7.4. Tune client and server connection channel parameters

7.5. Describe how to use the performance monitoring API

8.2. Produce an IBM MQ trace.

8.3. Identify the steps to evaluate and recover a non-responsive queue

8.6. Describe how to use the Application Activity Trace

You might also like