Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Clustering and Shared queues with the queue-sharing group as the resource owner.

IP.com Disclosure Number: IPCOM000013261D
Original Publication Date: 2001-Dec-16
Included in the Prior Art Database: 2003-Jun-18
Document File: 1 page(s) / 28K

Publishing Venue

IBM

Abstract

Clustering is a technology which allows resources owned by queue managers to be discovered on a 'need to know' basis. These resources are queues and channels and are grouped in clusters. Problem Solved In a shared queue environment, a way is needed of allowing users to make shared queues available to the cluster and seen to an external queue manager as being hosted by a single entity, the queue-sharing group, rather than by each queue manager within the queue-sharing group. Application Message Flow

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 86% of the total text.

Page 1 of 1

  Clustering and Shared queues with the queue-sharing group as the resource owner.

Clustering is a technology which allows resources owned by queue
managers to be discovered on a 'need to know' basis. These
resources are queues and channels and are grouped in clusters.
Problem Solved

     In a shared queue environment, a way is needed of allowing
users to make shared queues available to the cluster and seen to
an external queue manager as being hosted by a single entity, the
queue-sharing group, rather than by each queue manager within the
queue-sharing group.

Application Message Flow

     Shared queues can be defined as being owned by either the
queue manager or the queue-sharing group. This would be done
using the following commands:
DEF QLOCAL(SQ1) QSGDISP(SHARED) CLUSDISP(QMGR) CLUSTER(DEMO)
or DEF QLOCAL(SQ2) QSGDISP(SHARED) CLUSDISP(QSG) CLUSTER(DEMO)

     Cluster-receiver channels can be defined as being owned by
either the queue manager or the queue-sharing group. When a
cluster-receiver channel uses the generic queue-sharing group
address, this advertises a path to the whole queue-sharing group
rather than an individual queue manager within the queue-sharing
group. This would be done using the following commands:
DEF CHL(TO.QM1) CHLTYPE(CLUSRCVR) CLUSTER(DEMO) CLUSDISP(QMGR)
CONNAME(<local portal to queue manager>)
or
DEF CHL(TO.QSG) CHLTYPE(CLUSRCVR) CLUSTER(DEMO) CLUSDISP(QSG)
CONNAME(<generic address of QSG>)

     There is a shared SYSTEM.QSG.CLUSTER.TRANSMIT.QUEUE which
supports channel retry...