Intercommunication

Defining an LU 6.2 connection

In WebSphere MQ for iSeries, a mode name, TP name, and connection name of a fully-qualified LU 6.2 connection can be used.

For other versions of WebSphere MQ for iSeries, a communications side information (CSI) object is required to define the LU 6.2 communications details for the sending end of a message channel. It is referred to in the CONNECTION NAME field of the Sender or Server channel definition for LU 6.2 connections. Further information on the communications side object is available in the AS/400 APPC Communications Programmer's Guide.

The initiated end of the link must have a routing entry definition to complement this CSI object. Further information on managing work requests from remote LU 6.2 systems is available in the AS/400 Programming: Work Management Guide.

See the Multiplatform APPC Configuration Guide and the following table for information.

Table 47. Settings on the local OS/400 system for a remote queue manager platform

Remote platform	TPNAME
z/OS, or OS/390 or MVS/ESA without CICS	The same as in the corresponding side information on the remote queue manager.
z/OS or OS/390 or MVS/ESA using CICS	CKRC relates to a sender channel on the OS/400 system. CKSV relates to a requester channel on the OS/400 system. CKRC relates to a server channel on the OS/400 system.
OS/400	The same as the compare value in the routing entry on the OS/400 system.
OS/2	As specified in the OS/2 Run Listener command, or defaulted from the OS/2 queue manager configuration file.
Compaq OpenVMS Alpha	As specified in the Digital OVMS Run Listener command.
Compaq NonStop Kernel	The same as the TPNAME specified in the receiver-channel definition.
Other UNIX systems	The invokable Transaction Program defined in the remote LU 6.2 configuration.
Windows	As specified in the Windows Run Listener command, or the invokable Transaction Program that was defined using TpSetup on Windows.

If you have more than one queue manager on the same machine, ensure that the TPnames in the channel definitions are unique.

Initiating end (Sending)

Use the CRTMQMCHL command to define a channel of transport type *LU62. For versions previous to WebSphere MQ for iSeries V5.3, define the name of the CSI object that this channel will use in the CONNECTION NAME field. (See Creating a channel for details of how to do this.) Use of the CSI object is optional in WebSphere MQ for iSeries V5.1 or later.

The initiating end panel is shown in Figure Figure 115. You press F10 from the first panel displayed to obtain the complete panel as shown.

Figure 115. LU 6.2 communication setup panel - initiating end

+--------------------------------------------------------------------------------+
|                      Create Comm Side Information (CRTCSI)                     |
|                                                                                |
| Type choices, press Enter.                                                     |
|                                                                                |
| Side information . . . . . . . . > WINSDOA1      Name                          |
|   Library  . . . . . . . . . . . >   QSYS        Name, *CURLIB                 |
| Remote location  . . . . . . . . > WINSDOA1      Name                          |
| Transaction program  . . . . . . > MQSERIES                                    |
|                                                                                |
| Text 'description' . . . . . . .   *BLANK                                      |
|                                                                                |
|                                                                                |
|                            Additional Parameters                               |
|                                                                                |
| Device . . . . . . . . . . . . .   *LOC          Name, *LOC                    |
| Local location . . . . . . . . .   *LOC          Name, *LOC, *NETATR           |
| Mode . . . . . . . . . . . . . .   JSTMOD92      Name, *NETATR                 |
| Remote network identifier  . . .   *LOC          Name, *LOC, *NETATR, *NONE    |
| Authority  . . . . . . . . . . .   *LIBCRTAUT    Name, *LIBCRTAUT, *CHANGE...  |
|                                                                                |
|                                                                         Bottom |
| F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display    |
| F24=More keys                                                                  |
+--------------------------------------------------------------------------------+

Complete the initiating end fields as follows:

Side information

Give this definition a name that will be used to store the side information object to be created, for example, WINSDOA1.

Note:: For LU 6.2, the link between the message channel definition and the communication connection is the Connection name field of the message channel definition at the sending end. This field contains the name of the CSI object.

Library

The name of the library where this definition will be stored.

The CSI object must be available in a library accessible to the program serving the message channel, for example, QSYS, QMQM, and QGPL.

If the name is incorrect, missing, or cannot be found then an error will occur on channel start up.

Remote location

Specifies the remote location name with which your program communicates.

In short, this required parameter contains the logical unit name of the partner at the remote system, as defined in the device description that is used for the communication link between the two systems.

The Remote location name can be found by issuing the command DSPNETA on the remote system and seeing the default local location name.

Transaction program

Specifies the name (up to 64 characters) of the transaction program on the remote system to be started. It may be a transaction process name, a program name, the channel name, or a character string that matches the Compare value in the routing entry.

This is a required parameter.

Note:: To specify SNA service transaction program names, enter the hexadecimal representation of the service transaction program name. For example, to specify a service transaction program name whose hexadecimal representation is 21F0F0F1, you would enter X'21F0F0F1'.

More information on SNA service transaction program names is in the SNA Transaction Programmer's Reference manual for LU Type 6.2.

If the receiving end is another iSeries system, the Transaction program name is used to match the CSI object at the sending end with the routing entry at the receiving end. This should be unique for each queue manager on the target iSeries system. (See the Program to call parameter under Initiated end (Receiver).) See also the Comparison data: compare value parameter in the Add Routing Entry panel.

Text description

A description (up to 50 characters) to remind you of the intended use of this connection.

Device

Specifies the name of the device description used for the remote system. The possible values are:

*LOC: The device is determined by the system.
Device-name: Specify the name of the device that is associated with the remote location.

Local location

Specifies the local location name. The possible values are:

*LOC: The local location name is determined by the system.
*NETATR: The LCLLOCNAME value specified in the system network attributes is used.
Local-location-name: Specify the name of your location. Specify the local location if you want to indicate a specific location name for the remote location. The location name can be found by using the DSPNETA command.

Mode

Specifies the mode used to control the session. This name is the same as the Common Programming Interface (CPI)- Communications Mode_Name. The possible values are:

*NETATR: The mode in the network attributes is used.
BLANK: Eight blank characters are used.
Mode-name: Specify a mode name for the remote location.

Note:

Because the mode determines the transmission priority of the communications session, it may be useful to define different modes depending on the priority of the messages being sent; for example MQMODE_HI, MQMODE_MED, and MQMODE_LOW. (You can have more than one CSI pointing to the same location.)

Remote network identifier

Specifies the remote network identifier used with the remote location. The possible values are:

*LOC: The remote network ID for the remote location is used.
*NETATR: The remote network identifier specified in the network attributes is used.
*NONE: The remote network has no name.
Remote-network-id: Specify a remote network ID. Use the DSPNETA command at the remote location to find the name of this network ID. It is the 'local network ID' at the remote location.

Authority

Specifies the authority you are giving to users who do not have specific authority to the object, who are not on an authorization list, and whose group profile has no specific authority to the object. The possible values are:

*LIBCRTAUT: Public authority for the object is taken from the CRTAUT parameter of the specified library. This value is determined at create time. If the CRTAUT value for the library changes after the object is created, the new value does not affect existing objects.
*CHANGE: Change authority allows the user to perform basic functions on the object, however, the user cannot change the object. Change authority provides object operational authority and all data authority.
*ALL: The user can perform all operations except those limited to the owner or controlled by authorization list management authority. The user can control the object's existence and specify the security for the object, change the object, and perform basic functions on the object. The user can change ownership of the object.
*USE: Use authority provides object operational authority and read authority.
*EXCLUDE: Exclude authority prevents the user from accessing the object.
Authorization-list: Specify the name of the authorization list whose authority is used for the side information.

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. (See Creating a channel for details of how to do this.)

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 and, 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 OS/400 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 Figure Figure 116.

Figure 116. 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 your subsystem where this definition resides. Use the OS/400 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. You can use values in the range 1 to 9999.

Comparison data: Compare value

A text string to compare with that received when the session is started by a Transaction program parameter, as shown in Figure 115. 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 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 is a program supplied with WebSphere MQ for iSeries that 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 should match the Transaction program name supplied by the requesting system (see Initiating end (Sending)).

An example of this is shown in Figure Figure 117:

Figure 117. 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 Figure Figure 117 sequence number 90 represents the default queue manager and provides compatibility with configurations from previous releases (that is, V3R2, V3R6, V3R7, and V4R2) of WebSphere MQ for iSeries. 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:: You can have more than one routing entry for each queue manager by using different routing data. This gives 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 new class. Further information on managing work requests from remote LU 6.2 systems is available in the AS/400 Programming: Work Management Guide.

Note on Work Management

The AMQCRS6A job will not be able to take advantage of the normal iSeries work management features that are documented in the WebSphere MQ for iSeries V5.3 System Administration book because it is not started in the same way as other WebSphere MQ jobs. To change the run-time properties of the LU62 receiver jobs, you can do one of the following:

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 AS/400 Programming: Work Management Guide for more information about configuring Communication Jobs.