Skip to main content

New objects and new attributes for objects in WebSphere MQ 7.1, 7.5 and 8.0 - Middleware News

These are shown as new folders in the MQ Explorer 7.1 and later versions

CHLAUTH => New in 7.1

WebSphere MQ > Reference > Administration reference > MQSC reference > The MQSC commands
SET CHLAUTH
Use the MQSC command SET CHLAUTH to create or modify a channel authentication record.

COMMINFO => New in 7.1
WebSphere MQ > Reference > Administration reference > MQSC reference > The MQSC commands
DEFINE COMMINFO
Use the MQSC command DEFINE COMMINFO to define a new communication information object. These objects contain the definitions required for Multicast messaging.



Object: Local Queue (QLOCAL)
New attribute: CUSTOM => New in 7.1
WebSphere MQ > Reference > Administration reference > MQSC reference > The MQSC commands
ALTER queues
CUSTOM(string)
The custom attribute for new features.
This attribute is reserved for the configuration of new features before separate attributes are introduced.

Object: Transmission Queues:
New attribute: CLCHNAME => New in 7.5
WebSphere MQ > Reference > Administration reference > MQSC reference > The MQSC commands
ALTER queues
CLCHNAME(channel name)
CLCHNAME is the generic name of the cluster-sender channels that use this queue as a transmission queue. The attribute specifies which cluster-sender channels send messages to a cluster-receiver channel from this cluster transmission queue.

Object: Topic
New attributes:
COMMINFO => New in 7.1

CUSTOM => New in 7.1

MCAST => New in 7.1

WebSphere MQ > Reference > Administration reference > MQSC reference > The MQSC commands
DEFINE TOPIC
MCAST: Specifies whether multicast is allowable in the topic tree.

USEDLQ => New in 7.1

WebSphere MQ > Reference > Administration reference > MQSC reference > The MQSC commands
DEFINE TOPIC
USDELQ: Determines whether the dead-letter queue is used when publication messages cannot be delivered to their correct subscriber queue.

CLROUTE => New in 8.0

WebSphere MQ 8.0.0>WebSphere MQ>Reference>Administration reference>MQSC reference>The MQSC commands>
DEFINE TOPIC
CLROUTE - The routing behavior to use for topics in the cluster defined by the CLUSTER parameter.
DIRECT - When you configure a direct routed clustered topic on a queue manager, all queue managers in the cluster become aware of all other queue managers in the cluster. When performing publish and subscribe operations, each queue manager can connect direct to any other queue manager in the cluster.
TOPICHOST - When you use topic host routing, all queue managers in the cluster become aware of the cluster queue managers that host the routed topic definition (that is, the queue managers on which you have defined the topic object). When performing publish and subscribe operations, queue managers in the cluster connect only to these topic host queue managers, and not directly to each other. The topic host queue managers are responsible for routing publications from queue managers on which publications are published to queue managers with matching subscriptions.


+ Channels


WebSphere MQ > Reference > Administration reference > MQSC reference > The MQSC commands
DEFINE CHANNEL

Object: Server-Connection Channel (SVRCONN)
New attribute: DISCINT => New in 7.1 for Distributed (Unix, Windows)
The minimum time in seconds for which the channel waits for a message to arrive on the transmission queue, after a batch ends, before terminating the channel. A value of zero causes the message channel agent to wait indefinitely.
The value must be in the range zero through 999 999.
In MQ 7.0: This parameter is valid only for SVRCONN on z/OS and for SDR, SVR, CLUSSDR, CLUSRCVR.
In MQ 7.1 it is available now in Unix and Windows for SVRCONN, and continues to be available for SDR, SVR, CLUSSDR, CLUSRCVR.

Object: Client-Connection Channel (CLNTCONN)
New attribute: DEFRECON => New in 7.1
Specifies whether a client connection automatically reconnects a client application if its connection breaks.

Object: Cluster Receiver Channel (CLUSRCVR)
New attributes:
BATCHLIM => New in 7.1
The limit, in kilobytes, of the amount of data that can be sent through a channel before taking a sync point.

RESETSEQ => New in 7.1
Pending reset sequence number.
This is the sequence number from an outstanding request and it indicates a user RESET CHANNEL command request is outstanding.

USEDLQ => New in 7.1
Determines whether the dead-letter queue is used when messages cannot be delivered by channels.


Object: Cluster Sender Channel (CLUSSDR)
New attributes:
BATCHLIM => New in 7.1
RESETSEQ => New in 7.1
USEDLQ => New in 7.1

Object: Receiver Channel (RCVR)
New attributes:
RESETSEQ => New in 7.1
USEDLQ => New in 7.1

Object: Requester Channel (RQSTR)
New attributes:
RESETSEQ => New in 7.1
USEDLQ => New in 7.1

Object: Sender Channel (SDR)
New attributes:
BATCHLIM => New in 7.1
USEDLQ => New in 7.1

Object: Server Channel (SVR)
New attributes:
BATCHLIM => New in 7.1
RESETSEQ => New in 7.1
USEDLQ => New in 7.1

Object: Channels in general
New attribute in 8.0:
CERTLABL(' ') => Only for certain types: not for CHLTYPE(CLUSSDR)

WebSphere MQ 8.0.0 > WebSphere MQ > Reference > Configuration reference > Channel attributes > Channel attributes in alphabetical order >
Certificate label (CERTLABL)
This attribute specifies the certificate label of the channel definition.
The label identifies which personal certificate in the key repository is sent to the remote peer. The certificate is defined as described in Digital certificate labels.

+ New types for AUTHINFO (New in 8.0)
SYSTEM.DEFAULT.AUTHINFO.IDPWLDAP - AUTHTYPE(IDPWLDAP)
SYSTEM.DEFAULT.AUTHINFO.IDPWOS - AUTHTYPE(IDPWOS)
DEFINE AUTHINFO

AUTHTYPE - The type of authentication information.
CRLLDAP - Certificate Revocation List checking is done using LDAP servers.
IDPWLDAP - Connection authentication user ID and password checking is done using an LDAP server.
IDPWOS - Connection authentication user ID and password checking is done using the operating system.
OCSP - Certificate revocation checking is done using OCSP.


+ Adding attribute CHCKCLNT to CHLAUTH
Example:
SET CHLAUTH('SYSTEM.ADMIN.SVRCONN') +
CHCKCLNT(ASQMGR) +

WebSphere MQ 8.0.0 > WebSphere MQ > Reference > Administration reference > MQSC reference > The MQSC commands >
SET CHLAUTH
CHCKCLNT - Specifies whether the connection that matches this rule and is being allowed in with USERSRC(CHANNEL) or USERSRC(MAP), must also specify a valid user ID and password. REQDADM

MQ 7.1: How to remove a CHLAUTH record

WMQ 7.1 / 7.5 / 8.0 queue manager RC 2035 MQRC_NOT_AUTHORIZED or AMQ4036 when using client connection as an MQ Administrator

See the related presentation for a tutorial on how to use the COMMINFO object:
Multicast in WebSphere MQ V7.1


New SYSTEM queues added in WebSphere MQ 7.1, 7.5 and 8.0

New MQ 7.1, 7.5 and 8.0 attributes in DISPLAY QMGR for new or migrated queue managers

Comments

adsrerrapop

Popular posts from this blog

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...