Establishing a session using Communications Server for Linux

Note:
The information in this section applies only to WebSphere MQ for Linux for Intel. It does not apply to WebSphere MQ for Linux for zSeries.

The following information guides you through the tasks perform to create the SNA infrastructure that WebSphere MQ requires. This example creates the definitions for a partner node and LU on HP-UX.

Use sna start followed by xsnaadmin to access the Communications Server for Linux main window. You need root authority to use xsnaadmin.

 

Communications Server for Linux configuration

Communications Server for Linux configuration involves the following steps:

  1. Defining a local node

  2. Adding a Token-Ring port

  3. Defining a local LU

The Communications Server for Linux main window, from which you start, is shown here:



The Communications Server for Linux main window. It contains the menu items and options that you need to select to establish the session. The main menu at the top of the window contains the following items: Selection, Services, Diagnostics, and Windows. The main window also contains three areas, which display details of the current configuration. These areas are labelled: Connectivity and dependent LUs, Independent local LUs, and Remote systems. The instructions and windows following this figure guide you through the configuration process.

 

Defining a local node

  1. From the Communications Server for Linux main menu, click Services --> Configure node parameters. The "Node parameters" window opens.



    The <a href=Node parameters window. The instructions that follow guide you through the next step of the process.">

  2. Set APPN support to End node.

  3. In the Control point name fields, specify the network qualified name of the control point at the local node. In the first field, type the network name ((4)). In the second field, type the control point name ((2)).

  4. In the Control point alias field, type the control point name ((2)) again.

  5. In the Node ID fields, type the two components of the node ID ((3)).

  6. Click OK. A message is displayed informing you that a default LU has been defined automatically for the local node.

  7. Click OK.

 

Adding a Token-Ring port

  1. From the Communications Server for Linux main menu, click Services --> Connectivity --> New port. The following window opens.



    The window to add a new port and specify the network adapter card with which it is associated. The instructions that follow guide you through the next step of the process.

  2. Set Port using to Token Ring Card, or to the type of network adapter card you are using.

  3. Click OK. The "Token-Ring SAP" window opens.



    Adding a Token-Ring port. The instructions that follow guide you through the next step of the process.

  4. In the SNA port name field, type the port name ((9)).

  5. Click OK.

 

Defining a local LU

  1. From the Communications Server for Linux main menu, click Services --> APPC --> New independent local LU. The "Local LU" window opens.



    Adding an independent local LU. You use this panel to specify the LU name, LU alias, and a description. The instructions that follow guide you through the next step of the process.

  2. In the LU name field, type the name of the local LU ((5)).

  3. Click the LU alias field. Communications Server for Linux suggests an LU alias that is the same as the name of the local LU ((5)).

  4. Click OK.

 

APPC configuration

APPC configuration involves the following steps:

  1. Defining a remote node

  2. Defining a partner LU

  3. Defining a link station

  4. Defining a mode

  5. Adding CPI-C information

  6. Adding a TP definition

 

Defining a remote node

  1. From the Communications Server for Linux main menu, click Services --> APPC --> New remote node. The "Remote node" window opens.



    The Remote node window. The instructions that follow explain how to use this window.

  2. In the Node's SNA network name fields, specify the network qualified name of the control point at the remote node. Communications Server for Linux completes the first field for you by setting it to the network name ((4) and (13)) you entered earlier. In the second field, type the control point name ((14)).

  3. Click OK. A message is displayed informing you that a default LU has been defined automatically for the remote node.

  4. Click OK.

 

Defining a partner LU

  1. From the Communications Server for Linux main menu, click Services --> APPC --> New partner LUs --> Partner LU on remote node. The "Partner LU" window opens.



    The Partner LU window. The instructions that follow explain how to use this window.

  2. In the Partner LU name fields, specify the network qualified name of the partner LU at the remote node. Communications Server for Linux completes the first field for you by setting it to the network name ((4) and (13)) you entered earlier. In the second field, type the name of the partner LU ((15)).

  3. In the Alias and Uninterpreted name fields, type the name of the partner LU ((15)) again.

  4. Click Location, select the network qualified name of the control point at the remote node ((13).(14)) from the list that is displayed, and click OK.

  5. Click OK.

 

Defining a link station

  1. From the Communications Server for Linux main menu, click Services --> Connectivity --> New link station. The following window opens.



    The window to add a new link station and specify the port with which it is associated. The instructions that follow explain how to use this window.

  2. Set Link station to to MQPORT.

  3. Click OK. The "Token ring link station" window opens.



    The Token ring link station window. The instructions that follow explain how to use this window.

  4. In the Name field, type the name of the link station ((12)).

  5. Set Activation to On demand.

  6. Select the Independent only check box.

  7. Click Remote node, select the network qualified name of the control point at the remote node ((13).(14)) from the list that is displayed, and click OK.

  8. Set Remote node type to End or LEN node.

  9. In the MAC address field, type the MAC address ((19)) of the network adapter card at the remote node.

  10. Click Advanced. The "Token ring link station parameters" window opens.



    The Token ring link station parameters window. The instructions that follow explain how to use this window.

  11. Select the Request CP-CP sessions check box.

  12. Select the Reactivate link station after failure check box.

  13. Click OK to exit the "Token ring link station parameters" window.

  14. Click OK to exit the "Token ring link station" window.

 

Defining a mode

This purpose of the section is to explain how to define a new mode with the name LU62PS. The example continues subsequently, however, by using the mode #INTER ((17)), which is a standard mode supplied by Communications Server for Linux.

  1. From the Communications Server for Linux main menu, click Services --> APPC --> Modes. The "Modes" window opens.



    This windows displays the modes that are already defined. The instructions that follow guide you through the next step in the process.

  2. Click New. The "Mode" window opens.



    The window to add a new mode. The instructions that follow guide you through the next step in the process.

  3. In the Name field, type the name of the new mode, LU62PS.

  4. Click COS Name, select the class of service #INTER from the list that is displayed, and click OK.

  5. For the Session limits:

    • Type 8 in the Initial field.

    • Type 8 in the Maximum field.

    • Type 4 in the Min con. winner sessions field.

  6. Click OK to exit the "Mode" window.

  7. Click Close to exit the "Modes" window.

 

Adding CPI-C information

  1. From the Communications Server for Linux main menu, click Services --> APPC --> CPI-C. The "CPI-C destination names" window opens.



    This windows displays the CPI-C destination names that are already defined. The instructions that follow guide you through the next step in the process.

  2. Click New. The "CPI-C destination" window opens.



    The window to add a new CPI-C destination. The instructions that follow guide you through the next step in the process.

  3. In the Name field, type the CPI-C symbolic destination name ((18)).

  4. Select the Use PLU alias check box, and type the name of the partner LU ((15)), which you specified earlier as the partner LU alias.

  5. In the Mode field, type the mode name ((17)).

  6. Select the Application TP check box, and type the TP name ((16)).

  7. Click OK to exit the "CPI-C destination" window.

  8. Click Close to exit the "CPI-C destination names" window.

 

Adding a TP definition

  1. From the Communications Server for Linux main menu, click Services --> APPC --> Transaction programs. The "Transaction Programs" window opens.



    The Transaction programs window. The instructions that follow guide you through the next step in the process.

  2. Click New. The "TP invocation" window opens.



    The TP invocation window. The instructions that follow guide you through the next step in the process.

  3. Select the Application TP check box, and type the TP name ((7)).

  4. Clear the Queue incoming Allocates check box.

  5. In the Full path to TP executable field, type the full path to the executable program ((10)).

  6. In the Arguments field, type -m local queue manager ((11)).

  7. In the User ID and Group ID fields, type mqm.

  8. In the Environment field, type APPCLLU=local LU name ((5)) and APPCTPN=TP name ((7)) separated by the pipe character.

  9. Click OK to exit the "TP invocation" window.

  10. Click Selection --> Close TP window to exit the "Transaction Programs" window.

 

Communications Server for Linux operation

The Communications Server for Linux control daemon is started with the sna start command. Depending on the options selected at installation, it may already be running.

The xsnaadmin utility controls Communications Server for Linux resources.

Logging and tracing are controlled from here. Log and trace files can be found in the /var/opt/sna directory. The logging files sna.aud and sna.err can be read using a standard editor such as vi.

In order to read the sna1.trc trace file, first format it by running the command: 

snatrcfmt -f sna1.trc -o sna1

This produces an sna1.dmp file, which can be read using a normal editor. The sna2.trc trace file can be processed in the same way.

It is possible to edit the configuration file, but this is not a recommended method of configuring Communications Server for Linux.

The APPCLLU environment variable must be set before starting a sender channel from the Linux system. The command can be either entered interactively or added to the logon profile. Depending on the level of Bourne shell or Korn shell program being used, the command is: 

export APPCLLU=Local LU name    (5)   newer level

or 

APPCLLU=Local LU name           (5)   older level
export

 

What next?

The connection is now established. You are ready to complete the configuration. Go to WebSphere MQ for Linux configuration.

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.