The client can be a IBM Storage Protect backup-archive client or a
IBM Storage Protect Data Protection application client.
Before you begin
Before you begin this procedure, you must complete the following steps:
- Verify that the client system meets the prerequisites for client software. To ensure software
compatibility, review the website for IBM Storage Protect storage agent and
backup-archive client compatibility. You can download the latest software levels from the
IBM Storage Protect product support website.
- Ensure that you completed the configuration worksheets.
- Ensure that client nodes are registered and configured on the server. To register client nodes,
use the REGISTER NODE or UPDATE NODE command.
Note: If multiple clients are moving data from a storage agent to a z/OS media
server, install or upgrade the client software on each client system.
Procedure
Complete the following steps to install and configure the client:
-
Using the LAN-free communications protocol and LAN-free port information that you collected in
the configuration worksheets, modify the following file:

dsm.sys client system-options file
dsm.opt client options file
Tip: The file can be in one of several places, such as the installation directory, or in
a location pointed to by an environment variable.
Select a communication method that you want the client and server to use. The methods are
described in Table 1, Table 2, and Table 3.
Table 1. Communications methods for a IBM Storage Protect server connecting to a
z/OS media server
| To use this communication method |
Configuration requirements |
To connect to these IBM Storage Protect servers |
| TCP/IP |
Install TCP/IP (standard with supported operating systems) |
AIX, Linux on System z |
| HiperSockets |
For details about configuring HiperSocket connectivity between Linux on System z and z/OS,
see the IBM Redbooks publication IBM HiperSockets Implementation Guide. This document is
available online at http://www.redbooks.ibm.com/abstracts/sg246816.html |
Linux on System z |
Table 2. Communications methods from a storage agent to a z/OS media
server
| To use this communication method |
Configuration requirements |
To connect to these IBM Storage Protect servers |
| TCP/IP |
Install TCP/IP (standard with supported operating systems) |
AIX, Linux x86_64, Linux on System z, Linux on Power Systems, Solaris, Windows Server |
| HiperSockets |
For details about configuring HiperSocket connectivity between Linux on System z and z/OS,
see the IBM Redbooks publication IBM HiperSockets Implementation Guide. This document is
available online at http://www.redbooks.ibm.com/abstracts/sg246816.html |
Linux on System z |
Table 3. Communications methods for the IBM Storage Protect
client
| To use this communication method |
Install this software |
To connect to these IBM Storage Protect servers |
| TCP/IP |
TCP/IP (standard with supported operating systems) |
AIX, Linux x86_64, Linux on System z, Linux on Power Systems, Solaris, Windows Server |
| Shared memory |
TCP/IP (standard with platforms) |
AIX
Linux x86_64, Linux on System z, Linux on Power Systems
Windows Server
|
|
Named pipes
|
Named pipes (standard with Windows platforms)
|
Windows Server
|
For example:


commmethod tcpip
tcpserveraddress server_c.example.com
tcpport 1502

commmethod tcpip
tcpserveraddress tsmsrver.example.com
tcpport 1502
The preceding example uses a TCPPORT of 1502. However, the default TCPPORT is 1500.

Restriction: The backup-archive client
servername option is not related to the storage agent
SERVERNAME
option.
-
Install or upgrade the backup-archive client software or Data Protection application-client
software.
-
Add the following options to the same stanza in the same file that you edited in step #zsrv_inst_client/step1. These options specify that the client
uses SAN-attached devices, when the path is available, during backup, restore, archive, and retrieve
processing.
TCP/IP Communications:
enablelanfree yes
lanfreecommmethod tcpip
lanfreetcpserveraddress agent.example.com
lanfreetcpport 1500
Shared memory:
enablelanfree yes
lanfreecommmethod SharedMem
lanfreeshmport 1510
Named pipes:

lanfreecommmethod namedpipes
lanfreeport \\hostname\\pipename