Establishing a connection using SunLink Version 9.1

---

This section describes how to establish a connection using SunLink Version 9.1 The topics discussed are:

• SunLink 9.0 base configuration

• Invokable TPs

• CPI-C side information

 

SunLink 9.1 base configuration

To start the SunLink 9.1 graphical interface:

1. Enter sungmi at the command line.

   It is assumed that the domain, manager systems, and default system were defined during installation.

2. On the main screen, highlight Config1 in the resource tree and select File and Open. A window entitled Connect to domain appears:

3. Enter required details to connect to the required domain.

 

Configuring a PU 2.1 server

1. Double click on Systems in the resource tree to display a list of systems.

2. Double click on System name in the resource tree to open its subordinate entries.

3. Using the right mouse button, highlight PU2.1 Servers in the resource tree and select New and PU2.1 Server from the pop-up menu. A window entitled Create PU2.1 Server appears:

   
   

4. Enter the PU2.1 Name ((1)).

5. Enter the CP Name. This consists of the Network Name ((2))and the CP Name ((3)).

6. Click on Advanced >>. The advanced window appears:

   
   

7. Enter the SunOp Service and LU6.2 Service

8. Click on OK when you are happy with the settings.

 

Adding a LAN connection

1. Double click on PU2.1 Servers in the resource tree to display the name of the PU2.1 server.

2. Using the right mouse button, highlight the server name in the resource tree and select New and LAN Connection from the pop-up menu. A window entitled Create LAN Connection appears:

   
   

3. Enter a Line Name ((4)) and Local MAC Address ((5)).

4. Click on Advanced>> The advanced window appears:

   
   

5. Check the LAN Speed is correct.

6. Click on OK when you are happy with the settings.

 

Configuring a connection to a remote PU

1. Double click the PU2.1 server name in the resource tree to open its suborditnate entries.

2. Double click on LAN Connections.

3. Using the right mouse button, highlight the LAN connection name in the resource tree and select New and DLC from the pop-up menu. A window entitled Create DLC appears:

   
   

4. Enter the DLC Name ((12)) and Remote MAC Address ((19)).

5. Click on Advanced>>. A window entitled Create DLC (advanced) appears:

   
   

6. Enter the Local LSAP for this DLC ((14)), Local Terminal ID ((6)), and Remote CP Name ((13)).

7. When you are happy with the settings, click on OK.

 

Configuring an independent LU

1. Double click on Systems in the resource tree to display a list of systems.

2. Double click on the system name to open its subordinate entries.

3. Double click on PU2.1 Servers to display a list of servers.

4. Double click on the PU2.1 server name to open its subordinate entries.

5. From the main window, select Edit, New, and Independent LU to display the Create Independent LU window:

   
   

6. Enter the Local LU Name ((7)).

7. Click on Advanced>>. An advanced Create Independent LU window appears:

   
   

8. Enter the Network Qual Name. This consists of the Network Name ((2)) and the Local LU ((7)).

9. Click on OK

 

Configuring a partner LU

1. Double click on the PU2.1 server name in the resource tree to open its subordinate entries.

2. From the main window, select Edit, New, and Partner LU to display the Create Partner LU window:

   
   

3. Enter the Partner LU ((15)) and the Local LU Name ((7)).

4. Click on Advanced>>. The advanced Create Partner LU window appears:

   
   

5. Choose a Local LU from the drop-down list.

6. Click on OK.

 

Configuring the session mode

1. Double click on the PU2.1 server name to open its subordinate entries.

2. Double click on Partner LU in the resource tree to display a list of partner LUs.

3. Click on the partner LU to select it.

4. From the main window, select Edit, New, and Mode to display the Create Mode window:

   
   

5. Enter the Mode Name ((17)) and DLC Name ((12)).

6. Click on Advanced>>. The advanced Create Mode window appears:

   
   

7. Enter the Unique Session Name ((10)).

8. When you are happy with the settings, click on OK.

 

Configuring a transaction program

1. Double click on the PU2.1 server name to open its subordinate entries.

2. Click on Transaction Programs in the resource tree to select it.

3. From the main window, select Edit, New, and Transaction Program to display the Create Transaction Program window:

   
   

4. Enter the TP Name ((8)) and Local LU ((7)).

5. Enter a path to the invokable TP in the Command Path ((9)) field:

6. Click on Advanced>>. The advanced Create Transaction Program window appears:

   
   

7. When you are happy with the settings, click on OK.

 

Invokable TP path

In order to set required environment variables a script file should be defined for each invokable TP containing the following:

#!/bin/ksh
export APPC_GATEWAY=zinfandel
export APPC_LOCAL_LU=SOLARLU
/opt/mqm/bin/amqcrs6a -m SOLARIS -n MQSERIES

 

CPI-C side information

In common with most other platforms, WebSphere MQ for Solaris uses CPI-C side information files ((18)) to hold information about its partner systems. In SunLink 9.1, these are ASCII files (one per partner).

The location of the file must be specified either explicitly in the conname parameter of the sender channel definition or in the search path. It is better to specify it fully in the conname parameter because the value of the PATH environment variable can vary from user to user.

 

What next?

The connection is now established. You are ready to complete the configuration. Go to WebSphere MQ for Solaris 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.