MQSeries for AT&T GIS UNIX configuration

Before beginning the installation process ensure that you have first created the mqm user and group, and set the password.

Start any channel using the command:

runmqchl -c channel.name

Notes:

1. Sample programs are installed in /opt/mqm/samp.

2. Error logs are stored in /var/mqm/qmgrs/qmgrname/errors.

3. When you are using the command interpreter runmqsc to enter administration commands, a + at the end of a line indicates that the next line is a continuation. Ensure that there is a space between the last parameter and the continuation character.

Basic configuration

1. Create the queue manager from the UNIX prompt using the command:

   crtmqm -u dlqname -q gis
   

   where:

   gis

   Is the name of the queue manager

   -q

   Indicates that this is to become the default queue manager

   -u dlqname

   Specifies the name of the undeliverable message queue

2. Start the queue manager from the UNIX prompt using the command:

   strmqm gis
   

   where gis is the name given to the queue manager when it was created.
3. Before creating your own objects you must first create the system default objects. These are a number of definitions for required objects and templates on which user definitions will be modelled.

   Create the default objects from the UNIX prompt using the command:

   runmqsc gis < /opt/mqm/samp/amqscoma.tst > defobj.out
   

   where gis is the name of the queue manager. Display the file defobj.out and ensure that all objects were created successfully. There is a report at the end of the file.

Channel configuration

The following section details the configuration to be performed on the AT&T GIS UNIX queue manager to implement the channel described in Figure 32.

In each case the MQSC command is shown. Either start runmqsc from a UNIX prompt and enter each command in turn, or build a command file of the same format as amqscoma.tst and use it as before to create the objects.

Examples are given for connecting MQSeries for AT&T GIS UNIX and MQSeries for OS/2 Warp. If you wish to connect to another WebSphere MQ product use the appropriate set of values from the table in place of those for OS/2.

Note:

The words in bold are user-specified and reflect the names of WebSphere MQ objects used throughout these examples. If you change the names used here, ensure that you also change the other references made to these objects throughout this book. All others are keywords and should be entered as shown.

Table 27. Configuration worksheet for MQSeries for AT&T GIS UNIX

MQSeries for AT&T GIS UNIX sender-channel definitions using SNA

def ql (OS2) +                                (F)
    usage(xmitq) +
    replace
 
def qr (OS2.REMOTEQ) +                        (D)
    rname(OS2.LOCALQ) +                       (E)
    rqmname(OS2) +                            (C)
    xmitq(OS2) +                              (F)
    replace
 
def chl (GIS.OS2.SNA) chltype(sdr) +          (G)
    trptype(lu62) +
    conname('OS2CPIC') +                      (14)
    xmitq(OS2) +                              (F)
    replace

MQSeries for AT&T GIS UNIX receiver-channel definitions using SNA

def ql (GIS.LOCALQ) replace                   (B)
 
def chl (OS2.GIS.SNA) chltype(rcvr) +         (I)
    trptype(lu62) +
    replace

MQSeries for AT&T GIS UNIX sender-channel definitions using TCP

def ql (OS2) +                                (F)
    usage(xmitq) +
    replace
 
def qr (OS2.REMOTEQ) +                        (D)
    rname(OS2.LOCALQ) +                       (E)
    rqmname(OS2) +                            (C)
    xmitq(OS2) +                              (F)
    replace
 
def chl (GIS.OS2.TCP) chltype(sdr) +          (H)
    trptype(tcp) +
    conname(remote_tcpip_hostname) +
    xmitq(OS2) +                              (F)
    replace

MQSeries for AT&T GIS UNIX receiver-channel definitions using TCP/IP

def ql (GIS.LOCALQ) replace                   (B)
 
def chl (OS2.GIS.TCP) chltype(rcvr) +         (J)
    trptype(tcp) +
    replace