Initiated end (Receiver)

Use the CRTMQMCHL command to define the receiving end of the message channel link with transport type *LU62.

Leave the CONNECTION NAME field blank and ensure that the corresponding details match the sending end of the channel. For details, see Create a channel.

To enable the initiating end to start the receiving channel, add a routing entry to a subsystem at the initiated end. The subsystem must be the one that allocates the APPC device used in the LU 6.2 sessions. Therefore, it must have a valid communications entry for that device. The routing entry calls the program that starts the receiving end of the message channel.

Use the IBM i commands (for example, ADDRTGE) to define the end of the link that is initiated by a communication session.

The initiated end panel is shown in LU 6.2 communication setup panel - add routing entry.
Figure 1. LU 6.2 communication setup panel - initiated end
Add Routing Entry (ADDRTGE)

Type choices, press Enter.

Subsystem description . . . . .  QCMN     Name
Library . . . . . . . . . . .   *LIBL    Name, *LIBL, *CURLIB
Routing entry sequence number .  1       1-9999
Comparison data:
Compare value . . . . . . . .  MQSERIES

Starting position . . . . . .  37      1-80
Program to call . . . . . . . .  AMQCRC6B   Name, *RTGDTA
Library . . . . . . . . . . .  QMAS400    Name, *LIBL, *CURLIB
Class . . . . . . . . . . . . .  *SBSD     Name, *SBSD
Library . . . . . . . . . . .  *LIBL     Name, *LIBL, *CURLIB
Maximum active routing steps . .  *NOMAX    0-1000, *NOMAX
Storage pool identifier . . . .  1       1-10



Bottom
F3=Exit  F4=Prompt  F5=Refresh  F12=Cancel  F13=How to use this display
F24=More keys

    Subsystem description
    The name of our subsystem where this definition resides. Use the IBM i WRKSBSD command to view and update the appropriate subsystem description for the routing entry.

    Routing entry sequence number
    A unique number in your subsystem to identify this communication definition. We can use values in the range 1 - 9999.

    Comparison data: Compare value
    A text string to compare with the string received when the session is started by a Transaction program parameter, as shown in Figure 1. The character string is derived from the Transaction program field of the sender CSI.

    Comparison data: Starting position
    The character position in the string where the comparison is to start. Note: The starting position field is the character position in the string for comparison, and this position is always 37.

    Program to call
    The name of the program that runs the inbound message program to be called to start the session.

    The program, AMQCRC6A, is called for the default queue manager. This program is supplied with IBM MQ for IBM i and sets up the environment and then calls AMQCRS6A.

    For additional queue managers:

    • Each queue manager has a specific LU 6.2 invokable program located in its library. This program is called AMQCRC6B and is automatically generated when the queue manager is created.
    • Each queue manager requires a specific routing entry with unique routing data to be added. This routing data must match the Transaction program name supplied by the requesting system (see Initiating end (Sender) ).

    An example is shown in LU 6.2 communication setup panel - display routing entries:

    Figure 2. LU 6.2 communication setup panel - initiated end
    Display Routing Entries
System:  MY400
Subsystem description:  QCMN      Status:  ACTIVE

Type options, press Enter.
5=Display details

Start
Opt  Seq Nbr  Program    Library    Compare Value   Pos
10   *RTGDTA           'QZSCSRVR'     37
20   *RTGDTA           'QZRCSRVR'     37
30   *RTGDTA           'QZHQTRG'     37
50   *RTGDTA           'QVPPRINT'     37
60   *RTGDTA           'QNPSERVR'     37
70   *RTGDTA           'QNMAPINGD'    37
80   QNMAREXECD  QSYS     'AREXECD'     37
90   AMQCRC6A   QMQMBW    'MQSERIES'     37
100   *RTGDTA           'QTFDWNLD'     37
150   *RTGDTA           'QMFRCVR'     37



F3=Exit  F9=Display all detailed descriptions  F12=Cancel

    In LU 6.2 communication setup panel - display routing entries, sequence number 90 represents the default queue manager and provides compatibility with configurations from previous releases (that is, V3R2, V3R6, V3R7, and V4R2) of IBM MQ for IBM i. These releases allow one queue manager only. Sequence numbers 92 and 94 represent two additional queue managers called ALPHA and BETA that are created with libraries QMALPHA and QMBETA.

    Note: We can have more than one routing entry for each queue manager by using different routing data. These entries give the option of different job priorities depending on the classes used.

    Class
    The name and library of the class used for the steps started through this routing entry. The class defines the attributes of the routing step's running environment and specifies the job priority. An appropriate class entry must be specified. Use, for example, the WRKCLS command to display existing classes or to create a class. Further information about managing work requests from remote LU 6.2 systems is available in the IBM i Programming: Work Management Guide.


Note on Work Management

The AMQCRS6A job is not able to take advantage of the normal IBM i work management features that are documented in Work management because it is not started in the same way as other IBM MQ jobs. To change the runtime properties of the LU62 receiver jobs, we can make one of the following changes:

  • Alter the class description that is specified on the routing entry for the AMQCRS6A job
  • Change the job description on the communications entry

See the IBM i Programming: Work Management Guide for more information about configuring Communication Jobs. Parent topic: Defining an LU 6.2 connection on IBM i