Since the release of Mainframe Express version 2 - Micro Focus

Setting up Server to Server Connectivity Using Mainframe Express 2.5
Since the release of Mainframe Express version 2.5, there is a need to revise the procedure for
setting up Server-to-Server connectivity, when using XDB, as the navigation and some of the
settings have changed, to use a GUI windows interface. This document gives details of settings and
sequence of events to complete this task.
For ease of documentation, let's call the local server LOCSERV, and the local location LOCLOCN.
Let's also call the network (remote) server REMSERV, and the network (remote) location REMLOCN.
1. Start the LOCAL and REMOTE XDB servers, if they are not already started, by using.
TOOLS / SQL for DB2 / Start Server, in Mainframe Express, on both machines.
2. In Mainframe Express,
Use TOOLS / SQL for DB2 / XDB Server, to use the Server Configuration Utility,
On each tab the settings should be as follows:
ABOUT tab - Select XDB/DB2 version as required, Note that V6 now covers V5 and V6
GENERAL tab -
Protocols TCP/IP and LOCAL should be checked
Port should be set to 8898
Server Security should NOT be checked.
PATHS tab - Settings should be left to default
LIMITS tab - Settings should be left to default
CACHE tab - Settings should be left to default
TRACE tab - Settings should be left to default
LOGGING tab - RECOVERY option should NOT be checked.
Use APPLY, this will amend the settings and display an information window, notifying you
that the changes will not take effect until the XDB server is stopped and restarted.
Use OK, once again the display of the information window will occur, notifying you that the
changes will not take effect until the XDB server is stopped and restarted.
Stop and restart the XDB servers on both machines.
You will need to do this on both machines to match the values for both fields.
3. We need to make sure that security is either OFF on both machines or ON on both
machines.
In Mainframe Express,
Use TOOLS / SQL for DB2 / XDB Server, to use the Server Configuration Utility,
Examine ALL options on the GENERAL tab on both machines and compare the settings.
It may be easier to set security OFF for now, and then apply security later,
Steps 13 thru 15. If you choose this option, continue from step 6, otherwise….
In Mainframe Express,
Use OPTIONS / SQL for DB2 / Client, on the SECURITY tab, and check the client security.
If the security is ON, on both machines, make sure the client security enabled box is
checked, otherwise it should be unchecked.
Page 1 of 4

Setting up Server to Server Connectivity Using Mainframe Express 2.5
In Mainframe Express,
Use OPTIONS / SQL for DB2 / Client, on the MULTIUSER tab, and check the autocommit
setting.
The default will be checked on, this should be unchecked.
In Mainframe Express,
Use OPTIONS / SQL for DB2 / Client, on the SQL tab, to check the compatibility mode.
The default will be DB2, if it is not, then set it to DB2
4. In Mainframe Express, Create a user id in the SQL Wizard.
If you have security turned OFF, set the location and authid as follows:
Using OPTIONS / SQL for DB2 / Client, on the CONNECT tab,
Set LOCATION to SYSTEM, and set authid to INSTALL
If you have security turned ON, when the SQL wizard login window is displayed,
Set LOCATION to SYSTEM, and set authid to INSTALL
Use TOOLS / SQL for DB2 / SQL Wizard, to start the SQL Wizard.
Use ADMIN / USERS, on the task bar, to add the user id required.
Make sure that password required is unchecked.
Set user type to SUPER USER.
Click ADD, then close the SQL wizard.
This user id must be set up on both machines with the same settings
5. Stop and restart the XDB servers on both machines.
6. On the LOCAL machine, in Mainframe Express,
Use OPTIONS / SQL for DB2 / Client, on the CONNECT tab and check for the network
information for (remote) REMSERV.
If it exists, check that on the communication protocol is set to TCP/IP, that the TCP/IP
address is correct and the port is set to 8898.
If it does not exist, over type the currently displayed server name with the name of the
network (remote) server REMSERV.
Overtype the rest of the fields with the following vaues:
Communication protocol is set to TCP/IP.
TCP/IP address is set to the IP address of the network (remote) server.
Port is set to 8898.
To make sure that this has been successful, check the file MFUSER25\CONFIG\XDBNET.ini.
It should contain entries for the network (remote) server REMSERV as follows:
[SERVER REMSERV]
IPADDRESS=10.120.31.178 ==> TCP/IP address of the Remote Server
TCPPORT=8898 ==> Leave port 8898 as default
It will also contain an entry for your local server LOCSERV.
7. Stop and re-start the LOCAL XDB server.
8. On the LOCAL machine, in Mainframe Express.
Page 2 of 4

Setting up Server to Server Connectivity Using Mainframe Express 2.5
If you have security turned OFF, set the location and authid as follows:
Using OPTIONS / SQL for DB2 / Client, on the CONNECT tab,
Set LOCATION to SYSTEM, and set authid to INSTALL
If you have security turned ON, when the SQL wizard login window is displayed,
Set LOCATION to SYSTEM, and set authid to INSTALL
Use TOOLS / SQL for DB2 / SQL Wizard, to start the SQL Wizard.
Create a row in table SYSTEM.SYSIBM.SYSLUNAMES using the following SQL statement.
INSERT INTO SYSIBM.SYSLUNAMES VALUES
("REMSERV"," "," "," "," "," ")
9. On the LOCAL machine, in Mainframe Express
If you have security turned OFF, set the location and authid as follows:
Using OPTIONS / SQL for DB2 / Client, on the CONNECT tab,
Set LOCATION to SYSTEM, and set authid to INSTALL
If you have security turned ON, when the SQL wizard login window is displayed,
Set LOCATION to SYSTEM, and set authid to INSTALL
Use TOOLS / SQL for DB2 / SQL Wizard, to start the SQL Wizard.
Create a row in table SYSTEM.SYSIBM.SYSLOCATIONS
The column values should be:
LOCATION should be set to the name of the remote location REMLOCN
(REMLOCN can not be the same name as a location existing locally)
LOCTYPE should be set to X , this means XDB location type LINKNAME should be set to the
name of the network (remote) server REMSERV
LINKATTR should be set to T , this means TCP/IP.
10. Close the SQL Wizard.
11. Stop and re-start the LOCAL XDB server.
12. On the LOCAL machine, in Mainframe Express
If you have security turned OFF, set the location and authid as follows:
Using OPTIONS / SQL for DB2 / Client, on the CONNECT tab,
Set LOCATION to REMLOCN, and set authid to the user created in step 11
If you have security turned ON, when the SQL wizard login window is displayed,
Set LOCATION to REMLOCN, and set authid to the user created in step 11
Use TOOLS / SQL for DB2 / SQL Wizard, to start the SQL Wizard.
The remote location, REMLOCN, should now appear in the Locations browser.
This now means that you can see the remote server on the local machine.
To set security on
13. In Mainframe Express, Create a user id in the SQL Wizard.
Page 3 of 4

Setting up Server to Server Connectivity Using Mainframe Express 2.5
If you have security turned OFF, set the location and authid as follows:
Using OPTIONS / SQL for DB2 / Client, on the CONNECT tab,
Set LOCATION to SYSTEM, and set authid to INSTALL
If you have security turned ON, when the SQL wizard login window is displayed,
Set LOCATION to SYSTEM, and set authid to INSTALL
Use TOOLS / SQL for DB2 / SQL Wizard, to start the SQL Wizard.
Use ADMIN / USERS, on the task bar, to add the user id required.
Make sure that password required is unchecked.
Set user type to SUPER USER.
Click ADD, then close the SQL wizard.
This user id must be set up on both machines with the same settings
14. Make sure that security is ON, on both machines.
In Mainframe Express,
Use TOOLS / SQL for DB2 / XDB Server, to use the Server Configuration Utility,
Examine ALL options on the GENERAL tab on both machines and compare the settings.
In Mainframe Express,
Use OPTIONS / SQL for DB2 / Client, on the SECURITY tab, and check the client security.
Make sure the client security enabled box is checked ON
In Mainframe Express,
Use OPTIONS / SQL for DB2 / Client, on the MULTIUSER tab, and check the autocommit
setting.
The default will be checked on, this should be unchecked.
In Mainframe Express,
Use TOOLS / SQL for DB2 / XDB Server, to use the Server Configuration Utility,
On the GENERAL tab, make sure the SERVER SECURITY option is checked.
Use APPLY, this will amend the settings and display an information window, notifying you
that the changes will not take effect until the XDB server is stopped and restarted.
Use OK, once again the display of the information window will occur, notifying you that the
changes will not take effect until the XDB server is stopped and restarted.
You must now Stop and restart the local XDB server to apply the changes you have just
made.
This must be done on both machines
15. Stop and restart the XDB servers on both machines.
16. To use the tables from the remote server REMLOCN, on the LOCAL machine,
Use OPTIONS / SQL for DB2 / Client, on the CONNECT tab
Set LOCATION to REMLOCN, and set authid to the user created in step 11
Page 4 of 4