This section includes the initial step for installing each ADSM client program on UNIX workstations. This section is followed by installation information that applies to all UNIX clients and begins with "Setting Environment Variables (Optional)".
This section contains client environment information, including hardware and software requirements, for the AIX platform.
The following ADSM client components can be installed on an AIX workstation:
This includes any applications running on IBM's Scalable POWERparallel Systems 2 (SP2).
Figure 5. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| TCP/IP | Standard with AIX/6000 | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM, Windows NT |
| SNA LU6.2 (APPC) | AIX SNA Services/6000 | AIX, MVS, OS/2, OS/400, VSE, VM |
| Shared Memory | TCP/IP (Standard with AIX/6000) | AIX |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
To install ADSM on an AIX workstation, use the System Management Interface Tool (SMIT). For detailed information about using SMIT, see Getting Started: Managing IBM RISC System 6000 and read the SMIT windows during the installation process.
| Note: | The HSM client is a separately priced feature of ADSM. It is not functional on your system without a license. |
When you install ADSM on an AIX workstation, most of the ADSM files for the installed client components reside in /usr/lpp/adsm/bin.
On an AIX 4.1.4, 4.2.1, and 4.3 workstation, additional subdirectories and the files they contain are installed for only those language packages you select.
For example, if you select the French language package, the /usr/lpp/adsm/bin/fr_FR directory is installed. An additional symbolic link is also created. For example, for the French language package, the /usr/lib/nls/msg/fr_FR directory is created with a symbolic link to the dsmclient.cat file in /usr/lpp/adsm/bin/fr_FR. The dsmclient.cat file contains the message file for ADSM.
See "ADSM Files for AIX" for lists of files for each client component and information about where the files are stored.
| Attention |
|---|
|
If you are reinstalling HSM, be sure that all activity has stopped on all file systems to which you previously added space management, and that those file systems are not being accessed. Otherwise, the install process will fail. |
When you install the HSM client on an AIX workstation, the install process performs these steps:
File systems with a file system type of FSM:JFS exist only if the HSM client was previously installed. The file system type is FSM:JFS for any file system to which space management has been added.
For more information about HSM, see Using the UNIX HSM Clients, SH26-4030.
When HSM is installed on an AIX workstation, it must obtain a virtual file system (vfs) number. Because numbers 0 through 7 are reserved, it attempts to obtain a number in the range of 8 through 15, beginning with the number 15 and working down in the range to find an unused number.
If a number in that range is not available, HSM displays an error message. You must:
When HSM is installed on an AIX workstation, it must obtain group numbers for HSM execution modes. It picks an unused range of group numbers beginning with the largest possible group number and working down. The range is xxxxxx00 through xxxxxx7F.
The AIX system supports two versions of SMIT: ASCII and Motif. On the ASCII version, you select an item, and then press Enter. On the Motif version, you click on the item you want. The following procedure is written for the ASCII version.
If you are installing the ADSM base or admin client code on an AIX 4.1 or higher system, please note that the product will always be committed, even if the commit field is set to "no" in SMIT. This is due to AIX 4.1 allowing products to be uninstalled, therefore there is no difference between applied and committed products. Previous versions of AIX did not have this capability.
A WebShell client is available by selecting adsm.web.client while installing ADSM. The WebShell client runs on the same workstation as an ADSM command line Backup/Archive client. The WebShell client is accessable through a Web browser, from any workstation that has a Web browser installed. This allows the ADSM client machine with the WebShell client installed to be backed up remotely from any workstation running an appropriate Web browser. The readme file provides information on the setup and use of the WebShell client and is found in the /usr/lpp/adsm/bin/wsstuff directory. It is named wsreadme.html and should be viewed with a browser using a syntax similar to the following: file:/usr/lpp/adsm/bin/wsstuff/wsreadme.html
AFS/DFS backup functions are available by selecting adsm.afs.client while installing ADSM. The following filesets are available for AFS/DFS backup functions:
The AFS/DFS file backup clients also include new functions for excluding filespaces/directories, and using environment variables for virtualmountpoint/domain specification. The machine where you want to install the AFS volume backup agent or file backup client must have the AFS client installed. The machine where you want to install the DFS fileset backup agent must have DCE client installed. The DCE level should be current or the ADSM DFS client may have problems loading. The machine where you want to install the DFS file backup client must have the DFS client installed.
The AFS/DFS clients require the "Open Systems Environment" license on your ADSM server. For additional informaiton, refer to ADSTAR Distributed Storage Manager AFS/DFS Backup Clients, SH26-4048.
Attention: Do not put any user created files into /usr/lpp/adsm, the base directory into which the ADSM product is installed. The directory /usr/lpp/adsm is assumed to be owned by the installp process and any and all files in this directory are susceptible to deletion during installation processing. In particular, include/exclude files, dsm.opt, or dsm.sys files should not reside in this directory.
The SMIT install package allows several client pieces to be installed: Base Client, Admin Client, Space Management Client , API Client, and the different languages. Some client pieces have a dependency on a Common piece. To avoid installing all the client pieces (if space is a problem, for example), do the following in the SMITTY "Install Software Products" screen: Click on "List" at the "Software to Install" field. Choose the client piece you need.
If you are not installing from a CDROM, then from the AIX command line run /usr/sbin/inutoc in the directory where the ADSM image resides. A .toc file will be created in the directory.
For AIX 4.2.1 or later modification use the following installation steps:
For AIX 4.1.4 or later modification use the following installation steps:
A minimum installation requires ADSM Client - Common Files and at least one of the remaining client options.
Update the /usr/lpp/adsm/bin/dsm.sys file. This file is the same one used by ADSM Backup client. Update it to point to the latest ADSM server. Set the password option value to: GENERATE. Compression is supported, so you can specify "yes" or "no". Also, the include/exclude list is looked at to decide if a file should be allowed to migrate and for binding management classes. Either enable Open Registration on the server or register your node on the ADSM server. Then, if you have installed the hierarchical storage manager client, create a space managed file system by following he instructions in publication ADSTAR Distributed Storage Manager Using the UNIX Hierarchical Storage Management Clients, SH26-4030. Ater you have done that, copy a few files into the migrated filesystem and run the "dsmmigrate" command. The first time you run it it will ask for your node password (and contact information if you are running Open Registration).
After installation, if you decide to move the ADSM files from the installation directory to another directory, be sure to maintain the same directory structure for all directories and files below /usr/lpp/adsm/bin.
If you move the ADSM files from the installation directory (/usr/lpp/adsm/bin) to another directory, you must also complete the following steps:
The following tables list the ADSM files that are selectively installed for the backup-archive, administrative, and HSM clients on an AIX workstation. Files are selected for installation depending on the client components you choose to install.
For information about the files that are copied into the installation directory when you install the Application Programming Interface, see "Application Programming Interface (API)".
The files listed in Figure 6 are used by all AIX client components and are stored in
/usr/lpp/adsm/bin.
| File Name | Description |
|---|---|
| README | Last minute updates and other special information |
| dsm.sys.smp | Sample client system options file |
| dsm.opt.smp | Sample client user options file |
| dsmtca | Trusted Agent program |
| options.doc | Documentation for client options |
The files listed in Figure 7 are used by the backup-archive client and are stored in
/usr/lpp/adsm/bin.
Figure 7. ADSM Backup-Archive Client Files
| File Name | Description |
|---|---|
| dsm | Executable file for the backup-archive client graphical user interface |
| dsmadmc | Executable file for the administrative client command-line interface |
| dsmc | Executable file for the backup-archive command-line interface |
| dsmsna.drv | SNA driver program for APPC communications |
The files listed in Figure 8 are used by the backup-archive client and are stored in /usr/lpp/adsm/bin/en_US. That directory contains the files required for the American English version of the client.
When you install the backup-archive client on an AIX workstation, the files are also stored in only those directories that correspond to the language packages you select.
Figure 8. ADSM Backup-Archive Client Language Files
| File Name | Description |
|---|---|
| dsmc.hlp | Help file for the command-line interface |
The files listed in Figure 9 are used by the HSM client and are stored in
/usr/lpp/adsm/bin.
Figure 9. ADSM HSM Client Files
| File Name | Description |
|---|---|
| adsm.gif | Product graphic file |
| ddf | Symbolic link for dsmdf |
| ddu | Symbolic link for dsmdu |
| dls | Symbolic link for dsmls |
| dsmattr | Executable file for command-line interface |
| dsmautomig | Executable file for command-line interface |
| dsmdf | Executable file for command-line interface |
| dsmdu | Executable file for command-line interface |
| dsmls | Executable file for command-line interface |
| dsmmigfs | Executable file for command-line interface |
| dsmmigfstab.smp | Sample file system migrator file |
| dsmmighelp | Executable file for command-line interface |
| dsmmigquery | Executable file for command-line interface |
| dsmmigrate | Executable file for command-line interface |
| dsmmode | Executable file for command-line interface |
| dsmmonitord | Executable file to start the space monitor daemon |
| dsmq | Executable file for command-line interface |
| dsmrecall | Executable file for command-line interface |
| dsmrecalld | Executable file to start a recall daemon |
| dsmreconcile | Executable file for command-line interface |
| dsmrm | Executable file for command-line interface |
| dsmsetpw | Executable file for command-line interface |
| dsmhsm | Shell script-external command for HSM graphical user interface |
| dsmsm | Executable file for the HSM graphical user interface |
| installfsm | Executable file to load and unload kernel extension for HSM |
| kext | Kernel extension for HSM |
| manager.xbm | Bitmap for Space Management icon |
| fsmvfsmnthelp | Mount helper |
| migrate.xbm | Bitmap for Selective Migration icon |
| prod.xbm | Bitmap for Product icon |
| rc.adsmhsm | Shell script to mount fsm automatically |
| recall.xbm | Bitmap for Selective Recall icon |
The files listed in Figure 10 are used by the HSM client and are stored in /usr/lpp/adsm/bin/en_US. That directory contains the files required for the American English version of the client.
When you install the HSM client on an AIX workstation, the files are also stored in only those directories that correspond to the language packages you select.
Figure 10. ADSM HSM Client Files
| File Name | Description |
|---|---|
| Sm | X Window System resource file |
| dsmig.hlp | Help text file for command-line interface |
| hsmhelp.sdl | Help file for the HSM graphical user interface |
The files listed in Figure 11 are used by the AIX WebShell client and are stored in
/usr/lpp/adsm/bin.
Figure 11. ADSM WebShell Client Interface Files
| File Name | Description |
|---|---|
| adsmpswd | Used to create/update adsmpswd.ws (ADSM password file) |
| adsmpswd.ws | ADSM password file |
| adsmweb.ws | WebShell Web authentication file |
| mkwspswd | Used to create/update adsmweb.ws (WebShell Web authentication file) |
| webshell | WebShell client |
The files listed in Figure 12 are used by the AIX WebShell client and are stored in
/usr/lpp/adsm/bin/wsstuff.
Figure 12. ADSM WebShell Client Interface Files
| File Name | Description |
|---|---|
| adsmhbk.html | Backup help |
| adsmhbs.html | Backup selection help |
| adsmhead.gif | WebShell masthead |
| adsmhelp.gif | Graphic for the ADSM WebShell help banner |
| adsmhrs.html | Restore selection help |
| adsmhrst.html | Restore help |
| adsmresp.ws | File used by WebShell to end response prompting by the ADSM server |
| backgrou.gif | Graphic for the background |
| backup.gif | Graphic for the backup to safe image displayed on the backup form |
| blank.gif | Graphic for small space filler |
| info.gif | Graphic for the ADSM WebShell help icon |
| rbspace.gif | Graphic for larger space filler |
| restore.gif | Graphic for the safe to restore image displayed on the restore form |
| wsreadme.html | WebShell online documentation |
This section contains client environment information, including hardware and software requirements, for the Digital UNIX platform.
The following ADSM client components can be installed on a Digital UNIX workstation:
Digital UNIX V4.0C
Figure 13. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| TCP/IP | Standard with Digital UNIX | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM, Windows NT |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
To install ADSM Digital UNIX (DEC OSF/1) clients, use the setld -l command and follow the instructions. When you install ADSM on a Digital UNIX workstation, the ADSM files for the installed client components are copied into the /usr/opt/adsm directory, except as noted. The files associated with each client component are listed in "ADSM Files for UNIX Clients".
Use the following procedure to install ADSM Digital UNIX clients:
/usr/sbin/setld -d DSMBACxxx DSMAPIxxx
where xxx is the 210 if you had ADSM V2 packages installed or 310 if you had ADSM V3 packages installed.
/usr/sbin/setld -l `pwd` DSMBAC310 DSMAPI310
`pwd` can be replaced with the absolute name of the current directory. If you do not want to install the API then omit DSMAPI310.
If, after the installation, you move the ADSM files from the installation directory (/usr/opt/adsm) to another directory, you must also complete the following steps:
This section contains client environment information, including hardware and software requirements, for the HP-UX platform.
The following ADSM client components can be installed on an HP-UX workstation:
HP-UX 10.20
Figure 14. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| TCP/IP | Standard with HP-UX | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM, Windows NT |
| Shared Memory | TCP/IP (Standard with HP-UX) | HP-UX |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
When you install ADSM on an HP-UX workstation, the ADSM files for the installed client components are copied into the /usr/adsm directory, except as noted. The files associated with each client component are listed in "ADSM Files for UNIX Clients".
Login as root, root authority is required for the installation. Remove any previous versions of the ADSM backup-archive client and API that are installed on your system with the swremove command. To remove the entire client, issue the following command:
/usr/sbin/swremove -x mount_all_filesystems=false -v IBMADSM
ADSM Version 3 does not deliver an Administrative GUI, to preserve an installed copy of the ADSM Version 2 Administrative GUI client, issue the following command:
swremove -v IBMADSM.API swremove -v IBMADSM.CLIENT
To install ADSM on an HP-UX workstation, cd into the directory containing the image file, and issue the following command:
/usr/sbin/swinstall -x mount_all_filesystems=false -v -s `pwd`/adsm IBMADSM
`pwd` can be replaced with the absolute name of the current directory. If you do not want to install the API, omit IBMADM and mark the fileset IBMADM-CLIENT for installation in the swinstall user interface.
This installs the client in the /usr/adsm directory.
This section contains client environment information, including hardware and software requirements, for the NCR platform.
The following ADSM client components can be installed on an NCR workstation:
NCR Release 3.01, and 3.02
Figure 15. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| TCP/IP | Standard with NCR 3.01, and 3.02 | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM, Windows NT |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
Use the pkgadd utility to install the ADSM NCR clients. Two packages are available on the installation medium:
When you install the backup-archive client, the administrative client with command-line interface is also installed.
pkgadd -d location adsm
where location is the location on the CD-ROM, for example:
/CD-ROM/adsmcli/ncr/pkgadd/ncr.pkg
| Note: | Replace the word CD-ROM with the file system of the CD-ROM drive on your system. |
Then type go, and press Enter.
The system then displays many installation messages.
Installation of <adsm> was successful.
After you have installed ADSM for NCR, the files from this package reside in the directory /usr/adsm. The files associated with each client component are listed in "ADSM Files for UNIX Clients". If you want to move these files to another directory, do the following:
This section contains client environment information, including hardware and software requirements, for the NEC platform.
The following ADSM client components can be installed on an NEC workstation:
Figure 16. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| TCP/IP | Standard with all NEC UX/4800 Releases | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM, Windows NT |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
Use the pkgadd utility to install ADSM NEC EWS-UX/V clients. When you install the backup-archive client, the administrative client with command-line interface is also installed. Two packages are available on the installation medium:
Use the following procedure to install the packages of your choice.
pkgadd -d location <adsm>
where location is the location on the CD-ROM, for example:
/CD-ROM/adsmcli/nec/pkgadd/nec.pkg
| Note: | Replace the word CD-ROM with the file system of the CD-ROM drive on your system. |
Installation of <adsm> was successful.
After you have installed ADSM for NEC EWS-UX/V, the files from this package reside in the /usr/adsm directory. The files associated with each client component are listed in "ADSM Files for UNIX Clients". If you wish to move these files to another directory, do the following:
This section contains client environment information, including hardware and software requirements, for the SCO OpenServer platform.
The following ADSM client components can be installed on an SCO OpenServer workstation:
SCO OpenServer Version 5
Figure 17. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| TCP/IP | Standard with SCO OpenServer Version 5 | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
To install ADSM on an SCO OpenServer workstation, use the custom utility. For detailed information about using custom, see SCO UNIX Operating System: System Administrator's Reference, Document Version 3.2.4C When you install ADSM on an SCO OpenServer workstation, the ADSM files for the installed client components are copied into the /usr/adsm directory, except as noted. The files associated with each client component are listed in "ADSM Files for UNIX Clients".
Use the following procedure to install ADSM SCO Open Desktop clients. When you install the backup-archive client, the administrative client with command-line interface is also installed.
custom
If, after the installation, you move the ADSM files from the installation directory (/usr/adsm) to another directory, you must also complete the following steps:
This section contains client environment information, including hardware and software requirements, for the Sequent PTX platform.
The following ADSM client components can be installed on a Sequent PTX workstation:
Sequent PTX Release 4.2 or 4.4 starting with PTX 4.2.2
Figure 18. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| PTX TCP/IP | Standard with Sequent PTX UNIX | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
When you install ADSM on a Sequent PTX workstation, the ADSM files for the installed client components are copied into the /usr/adsm directory, except as noted. The files associated with each client component are listed in "ADSM Files for UNIX Clients".
Use the following procedure to install ADSM Sequent PTX. When you install the backup-archive client, the administrative client with command-line interface is also installed.
Enter the following command after the root> prompt:
/CD-ROM/adsmcli/sequent/pkgadd/sequent.pkg
| Note: | Replace the word CD-ROM with the file system of the CD-ROM drive on your system. |
Installation in progress. Do not remove the media.
Processing package instance <adsm> from </tmp/adsm.img>
ADSM Client for Sequent PTX 4.2 or 4.4
Version 3.1 Symmetry S5000, S2000
ADSTAR Distributed Storage Manager
Licensed Materials - Property of IBM
(C) Copyright IBM Corporation 1990, 1998. All rights reserved.
Refer to Copyright Instructions Form Number G120-2083
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
Installing ADSM Client for Sequent PTX 4.2 or 4.4 as <adsm>
## Installing part 1 of 1.
Installation of <adsm> was successful.
After you have installed ADSM for Sequent PTX, the files from this package reside in the /usr/adsm directory. If you want to move these files to another directory, do the following:
To indicate the amount of dynamic memory that a user-process is allowed to use, the Sequent PTX system provides the kernel parameter SHMGAP. The default value of SHMGAP is 2 MB. The value is less if Backup by directory tree is selected from the GUI menu.
If the value of SHMGAP has not already been increased, do the following:
This section contains client environment information, including hardware and software requirements, for the Silicon Graphics IRIX platform.
The following ADSM client components can be installed on a Silicon Graphics IRIX workstation:
IRIX UNIX Release 6.2 with efs- or xfs-Filesystem. The HSM client only supports xfs-Filesystem.
Figure 19. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| TCP/IP | Standard with IRIX UNIX | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
Use the following procedure to install the ADSM client for the Silicon Graphics IRIX 6.2 operating system. When you install the backup-archive client, the administrative client with command line interface is also installed.
The ADSM client components include the backup-archive client, administrative client, API, and HSM. The ADSM installation software includes the ADSM base software (ADSM.sw.base) the API (ADSM.sw.api) and the HSM client (ADSM.sw.hsm). These files are located in the /CDROM/adsmcli/sgi/ directory on the CDROM.
# swmgr
or start the interactive software installation tool (CLI) by entering the following command:
# inst
or start the software installation tool in batch mode by changing to the directory containing the ADSM client and API installation image and entering the following command:
# /usr/sbin/inst -a -f `pwd``pwd` can be replaced with the absolute name of the current directory.
Refer to the Silicon Graphics IRIX documentation for further software installation instructions using the swmgr or inst command.
This section contains client environment information, including hardware and software requirements, for the SINIX Reliant platform.
The following ADSM client components can be installed on a SINIX Reliant workstation:
SINIX Reliant 5.4.3
Figure 20. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| TCP/IP | Standard with the SINIX Reliant operating system | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
Use the pkgadd utility to install the ADSM for SINIX Reliant client. Two packages are available on the installation medium:
When you install the backup-archive client, the administrative client with command-line interface is also installed. Use the following procedure to install the packages of your choice.
pkgadd -d /CD-ROM/adsmcli/sinix/snr.pkg
| Note: | Replace the word CD-ROM with the file system of the CD-ROM drive on your system. |
After you have installed the ADSM client, the files from this package reside in the /usr/adsm directory. The files associated with each client component are listed in "ADSM Files for UNIX Clients". If you wish to move these files to another directory, do the following:
This section contains client environment information, including hardware and software requirements, for the Sun Solaris platform.
The following ADSM client components can be installed on a Sun Solaris workstation:
Figure 21. Communication Software
| To use this communication method: | Install this on the workstation | To connect to these ADSM servers: |
|---|---|---|
| TCP/IP | Standard with Solaris | AIX, HP-UX, MVS, OS/2, OS/400, Sun, VM |
| Shared Memory | TCP/IP (Standard with Solaris) | Sun |
| Attention |
|---|
|
For the latest information concerning the installation and configuration of the ADSM program product refer to the README file that is shipped on the product installation media. |
When you install ADSM on a Solaris workstation, the ADSM files for the installed client components are copied into the installation directory you choose. The files associated with each client component are listed in "ADSM Files for UNIX Clients".
This section contains information about the installation of the ADSM
backup-archive client and the administrative client command-line for the
Solaris platform. The installation package contains these two
components:
| Component | File |
|---|---|
Backup-archive (command-line and GUI) and administrative (command-line) | IBMadsm-c |
| API | IBMadsm-a |
You can install any of the two components separately (considering backup-archive and command-line administrative client as one installation component).
To install the ADSM Solaris clients, follow these steps:
# pkgrm IBMDSMba5 IBMDSMap5
# pkgrm IBMadsm-c IBMadsm-a
# pkgrm IBMDSMsa5
pkgadd -d `pwd` /sunadsm.pkg
`pwd` can be replaced with the absolute name of the current directory.
Select which package to install or just press enter to install both packages.
If you wish to override /opt as the base directory, use the -R option of the pkgadd command.
The post install program within pkgadd automatically creates symbolic links for the ADSM executables in /usr/bin and the ADSM libraries in /usr/lib.
For the client system options file, copy dsm.sys.smp to dsm.sys in the installation directory.
For the client user options file, copy dsm.opt.smp to dsm.opt in the installation directory.
You can then edit your dsm.sys and dsm.opt files as appropriate for your system.
If you later wish to remove the backup-archive client and administrative client, or the API from your system, issue the following command:
pkgrm <component-name>
The preremove part of pkgrm automatically removes any symbolic links created in /usr/sbin and /usr/lib.
The following tables list the ADSM files that are selectively installed for UNIX platforms. Files are selected for installation depending on the client components you choose to install.
| File Name | Description |
|---|---|
| README | Last minute updates and other special information |
| dsm.sys.smp | Sample client system options file |
| dsm.opt.smp | Sample client user options file |
| dscameng.txt | American English message text file, for non-MBCS clients |
| dsmtca | Trusted Agent program |
| options.doc | Documentation for client options |
| whatsnew.v3 | Documentation for new Version 3 client functions |
Figure 23. ADSM Backup-Archive Client Files
| File Name | Description |
|---|---|
| dsm | Executable file for the backup-archive client graphical user interface |
| dsmadmc | Executable file for the administrative client command-line interface |
| dsmc | Executable file for the backup-archive command-line interface |
| dsmc.hlp | Help file for the command-line interface |
| dsmstat | Executable file for NFS filesystem status timeout. Remove this file if you do not have any NFS mounted filesystems or you do not want to use the nfstimeout option. |
| dsmx.hlp | Windowed Interface help file |
If you install the Application Programming Interface, the
files in Figure 24 and Figure 25 are copied into the installation directory.
| File Name | Description | ||
|---|---|---|---|
| readme.api | Last minute updates and other special information for API | ||
| libApiDS.a 1 | API shared library for AIX | ||
| libApiDS.sl | API shared library for HP-UX | ||
| libApiDS.so | API shared library for Digital UNIX, NCR, NEC, SGI, SINIX, Solaris | ||
| liblpp.a | Required for SMIT, for AIX | ||
| |||
The files in Figure 25 are provided for developers who write applications that communicate with an
ADSM server.
Figure 25. ADSM API Files for Developers
| File Name | Description |
|---|---|
| dsmrc.h | Return codes header file |
| dsmapitd.h | Type definitions header file |
| dsmapifp.h | Function prototype header file |
dapibkup.c dapidata.h dapiinit.c dapint64.h dapint64.c dapipref.c dapiproc.c dapipw.c dapiqry.c dapirc.c dapismp.c dapitype.h dapiutil.h dapiutil.c | Modules for the command-line driven sample application |
| makeapi.aix | Makefile to build dapismp for AIX |
| makeapi.hp | Makefile to build dapismp for HP-UX |
| makeapi.sol | Makefile to build dapismp for Solaris |
| makeapi.ncr | Makefile to build dapismp for NCR |
| makeapi.sinix | Makefile to build dapismp for SINIX and Pyramid Nile |
| makeapi.nec | Makefile to build dapismp for NEC |
| makeapi.sgi | Makefile to build dapismp for SGI |
| makeapi.osf | Makefile to build dapismp for Digital UNIX |
caller1.c caller2.c | Simple example modules |
| register.frm | Registration form for developers to get support |
If you install the API on the AIX, Solaris, or HP-UX platforms, both the
base API and the X/Open API are installed. The files for the X/Open API
are listed in Figure 26.
| File Name | Description |
|---|---|
| libXApi.a | X/Open API shared library for AIX |
| libXApi.so | X/Open API shared library for Solaris and SGI |
| libXApi.sl | X/Open API shared library for HP-UX |
| custom.h | Platform custom integer definitions header file |
| xbsa.h | Header file containing constants, return codes, structure and type definitions, and function prototypes for the Data Movement function group |
| policy.h | Header file containing structure definitions relating to policy |
xapibkup.c xapidata.h xapiinit.c xapint64.h xapint64.c xapipref.c xapiproc.c xapipw.c xapiqry.c xapirc.c xapismp.c xapitype.h xapiutil.h xapiutil.c | Modules for the command line driven sample application |
| makexapi.aix | Makefile to build xapismp for AIX |
| makexapi.sol | Makefile to build xapismp for Solaris |
| makexapi.hp | Makefile to build xapismp for HP--UX |