DX beta 21 - 10 Oct 1997 - 13:25:57
IBM Visualization Data Explorer
Installation and Configuration Guide
Version 3 Release 1 Modification 4
USEM-EM42-C8
| Note! |
|---|
|
Before using this information and the product it supports, be sure to read the general information under "Notices". |
Second Edition (10 Oct 1997)
This edition applies to IBM Visualization Data Explorer Version 3.1.4, to IBM Visualization Data Explorer SMP Version 3.1.4, and to all subsequent releases and modifications thereof until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the product. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below.
A form for readers' comments appears at the back of this publication. If the form has been removed, address your comments to:
If you send information to IBM, you grant IBM a nonexclusive right to use or distribute that information, in any way it believes appropriate, without incurring any obligation to you.
© Copyright International Business Machines Corporation 1991-1997.
All rights reserved.
Note to U.S. Government Users -- Documentation
related to restricted rights -- Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule contract with IBM Corp.
IBM may have patents or pending patent applications covering subject
matter in this document.
The furnishing of this document does not give the user any license to
those patents.
License inquiries should be sent, in writing, to:
International Business Machines Corporation
IBM Director of Licensing
500 Columbus Avenue
Thornwood, New York 10594
USA
The following terms, marked by an asterisk (*) at their first
occurrence in this publication, are trademarks or registered
trademarks of the IBM Corporation in the United States
and/or other countries.
AIX
IBM
IBM Power Visualization System
RISC System/6000
Visualization Data Explorer
The following terms, marked by a double asterisk (**) at their first occurrence in this publication, are trademarks of other companies.
| AViiON | Data General Corporation |
| DEC | Digital Equipment Corporation |
| DGC | Data General Corporation |
| Graphics Interchange Format (GIF) | CompuServe, Inc. |
| Hewlett-Packard | Hewlett-Packard Company |
| HP | Hewlett-Packard Company |
| iFOR/LS | Apollo Computer, Inc. |
| Motif | Open Software Foundation |
| NetLS | Apollo Computer, Inc. |
| Network Licensing Software | Apollo Computer, Inc. |
| OpenWindows | Sun Microsystems, Inc. |
| OSF | Open Software Foundation, Inc. |
| PostScript | Adobe Systems, Inc. |
| X Window System | Massachusetts Institute of Technology |
IBM Visualization Data Explorer contains software copyrighted as follows:
Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of E. I. du Pont de Nemours and Company not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. E. I. du Pont de Nemours and Company makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
E. I. du Pont de Nemours and Company disclaims all warranties with regard to this software, including all implied warranties of merchantability and fitness, in no event shall E. I. du Pont de Nemours and Company be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of this software.
National Space Science Data Center
NASA/Goddard Space Flight Center
Greenbelt, Maryland 20771 USA
(NSI/DECnet -- NSSDCA::CDFSUPPORT)
(Internet -- CDFSUPPORT@NSSDCA.GSFC.NASA.GOV)
Permission to use, copy, modify, and distribute this software and its documentation for any purpose without fee is hereby granted, provided that the above copyright notice appear in all copies, that both that copyright notice and this permission notice appear in supporting documentation, and that the name of UCAR/Unidata not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UCAR makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. It is provided with no support and without obligation on the part of UCAR Unidata, to assist in its use, correction, modification, or enhancement.
NCSA HDF Version 3.2 source code and documentation are in the public domain. Specifically, we give to the public domain all rights for future licensing of the source code, all resale rights, and all publishing rights.
We ask, but do not require, that the following message be included in all derived works:
Portions developed at the National Center for Supercomputing Applications at the University of Illinois at Urbana-Champaign, in collaboration with the Information Technology Institute of Singapore.
THE UNIVERSITY OF ILLINOIS GIVES NO WARRANTY, EXPRESSED OR IMPLIED, FOR THE SOFTWARE AND/OR DOCUMENTATION PROVIDED, INCLUDING, WITHOUT LIMITATION, WARRANTY OF MERCHANTABILITY AND WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE
June, 1993
UNIX is a registered trademark of UNIX Systems Laboratories, Inc.
Gradient is a registered trademark of Gradient Technologies, Inc.
NetLS and Network Licensing System are trademarks of Apollo Computer, Inc., a subsidiary of Hewlett-Packard Co.
Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
The Graphics Interchange Format © is the copyright property of Compuserve Incorporated. GIF(SM) is a Service Mark property of Compuserve Incorporated.
Motif Shrinkwrap License
READ THIS LICENSE AGREEMENT CAREFULLY BEFORE USING THE PROGRAM TAPE, THE SOFTWARE (THE "PROGRAM"), OR THE ACCOMPANYING USER DOCUMENTATION (THE "DOCUMENTATION"). THIS AGREEMENT REPRESENTS THE ENTIRE AGREEMENT CONCERNING THE PROGRAM AND DOCUMENTATION POSAL, REPRESENTATION, OR UNDERSTANDING BETWEEN THE PARTIES WITH RESPECT TO ITS SUBJECT MATTER. BY BREAKING THE SEAL ON THE TAPE, YOU ARE ACCEPTING AND AGREEING TO THE TERMS OF THIS AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND NY THE TERMS OF THIS AGREEMENT, YOU SHOULD PROMPTLY RETURN THE CONTENTS, WITH THE TAPE SEAL UNBROKEN; YOUR MONEY WILL BE REFUNDED.
1. License: ISC remains the exclusive owner of the Program and the Documentation. ICS grant to Customer a nonexclusive, nontransferable (except as provided herein) license to use, modify, have modified, and prepare and have prepared derivative works of the Program as necessary to use it.
2. Customer Rights: Customer may use, modify and have modified and prepare and have prepared derivative works of the Program in object code form as is necessary to use the Program. Customer may make copies of the Program up to the number authorized by ICS in writing, in advance. There shall be no fee for Statically linked copies of the Motif libraries. Statically linked copies are object code copies integrated within a single application program and executable only with that single application. Run Time copies require payment of ICS' then applicable fee. Run Time copies are copies which include any portion of a linkable object file (".o" file), library file (".a" file), the window manager (mwm manager), the U.I.L. compiler, a shared library, or any tool or mechanism that enables generation of any portion of such components; other copies will require payment of ICS' applicable fees. TRANSFERS TO THIRD PARTIES OF COPIES OF THE LICENSED PROGRAMS, OR OF APPLICATIONS PROGRAMS INCORPORATING THE PROGRAM (OR ANY PORTION THEREOF), REQUIRE ICS' RESELLER AGREEMENT. Customer may not lease or lend the Program to any party. Customer shall not attempt to reverse engineer, disassemble or decompile the program.
3. Limited Warranty: (a) ICS warrants that for thirty (30) days from the delivery to Customer, each copy of the Program, when installed and used in accordance with the Documentation, will conform in all material respects to the description of the Program's operations in the Documentation. (b) Customer's exclusive remedy and ICS' sole liability under this warranty shall be for ICS to attempt, through reasonable efforts, to correct any material failure of the Program to perform as warranted, if such failure is reported to ICS within the warranty period and Customer, at ICS' request, provides ICS with sufficient information (which may include access to Customer's computer system for use of Customer's copies of the Program by ICS personnel) to reproduce the defect in question; provided, that if ICS is unable to correct any such failure within a reasonable time, ICS may, at its sole option, refund to the Customer the license fee paid for the Product. (c) ICS need not treat minor discrepancies in the Documentation as errors in the Program, and may instead furnish correction to the Program. (d) ICS does not warrant that the operation of the Program will be uninterrupted or error-free, or that all errors will be corrected. (e) THE FOREGOING WARRANTY IS IN LIEU OF, AND ICS DISCLAIMS, ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL ICS BE LIABLE FOR ANY INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION LOST PROFITS, ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM OR DOCUMENTATION.
4. Term and Termination: The term of this agreement shall be indefinite; however, this Agreement may be terminated by ICS in the event of a material default by Customer which is not cured within thirty (30) days after the receipt of notice of such breech by ICS. Customer may terminate this Agreement at any time by destruction of the Program, the Documentation, and all other copies of either of them. Upon termination, Customer shall immediately cease use of, and return immediately to ICS, all existing copies of the Program and Documentation, and cease all use thereof. All provisions hereof regarding liability and limits thereon shall survive the termination of this the Agreement.
5. U.S. GOVERNMENT LICENSES. If the Product is provided to the U.S. Government, the Government acknowledges receipt of notice that the Product and Documentation were developed at private expense and that no part of either of them is in the public domain. The Government acknowledges ICS' representation that the Product is "Restricted Computer Software" as defined in clause 52.227-19 of the Federal Acquisition Regulations (the "FAR" and is "Commercial Computer Software" as defined in Subpart 227.471 of the Department of Defense Federal Acquisition Regulation Supplement (the "DFARS"). The Government agrees that (i) if the software is supplied to the Department of Defense, the software is classified as "Commercial Computer Software" . and that the Government is acquiring only "Restricted Rights" in the software and its documentation as that term is defined in Clause 252.227-7013(c)(1) of the DFARS and (ii) if the software is supplied to any unit or agency of the Government other than the Department of Defense, then notwithstanding any other lease or license agreement that may pertain to, or accompany the delivery of, the computer software and accompanying documentation, the rights of the Government regarding its use, reproduction and disclosure are as set forth in Clause 52.227-19(c)(2) of the FAR. All copies of the software and the documentation sold to or for use by the Government shall contain any and all notices and legends necessary or appropriate to assure that the Government acquires only limited right in any such documentation and restricted rights in any such software.
6. Governing Law: This license shall be governed by and construed in accordance with the laws of the Commonwealth of Massachusetts as a contract made and performed therein.
Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the names of OMRON, NTT Software, NTT, and M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. OMRON, NTT Software, NTT, and M.I.T. make no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
OMRON, NTT SOFTWARE, NTT, AND M.I.T. DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL OMRON, NTT SOFTWARE, NTT, OR M.I.T. BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
The following terms are trademarks or registered trademarks of the IBM Corporation in the United States and/or other countries:
RISC System/6000
IBM Visualization Data Explorer
The following terms are trademarks of other companies as follows:
AViiON | Data General Corporation |
AXP | Digital Equipment Corporation |
Data General | Data General Corporation |
DEC | Digital Equipment Corporation |
Digital Equipment | Digital Equipment Corporation |
Hewlett-Packard | Hewlett-Packard Company |
Iris Crimson | Silicon Graphics, Inc. |
Iris Indigo | Silicon Graphics, Inc. |
IRIX | Silicon Graphics, Inc. |
Silicon Graphics | Silicon Graphics, Inc. |
SPARCstation | Sun Microsystems |
Sun | Sun Microsystems |
This document describes how to install and configure IBM Visualization Data Explorer for any of the following platforms (the installation procedure for Data Explorer SMP is the same as that for Data Explorer):
This document tells you how to install Data Explorer on your system. To install Data Explorer, you need to do the following:
If you want to use a floating, or concurrent, license of Data Explorer, and you are not currently running a NetLS license server somewhere in your network, then you also need to read Chapter 15. "Installing a NetLS License Server".
To check that the installation has completed successfully, type the following:
cd /usr/lpp/dx/samples/programs dx -image -execute MappedIso.netAn Image window will then open and an image of a colored cloud will appear.
If you have trouble, see Chapter 14. "Troubleshooting the Data Explorer Installation".
If at any time you have problems installing or using Data Explorer, please send electronic mail to dxsupp@watson.ibm.com or call IBM Data Explorer Support at (800) 435-6813 (from the US and Canada) or (914) 784-5142 (from elsewhere).
There are a number of resources that can be used to get support, information and publicly available software related to Data Explorer from other Data Explorer users. These include the following:
Data Explorer is comprised of five subsystems as follows:
Base executables | contains all files needed to run Data Explorer. |
Development environment | contains libraries, header files and other tools needed to build a custom executive. |
Samples | example programs, scripts, tutorial, and makefiles. |
Online help and HTML | online help available from the Data Explorer User Interface, and documentation in HTML format. |
PostScript and ASCII documentation | Documentation in PostScript format and for printing and in flat ASCII format for basic minimal viewing. |
If you are installing Data Explorer from tape:
Disk space requirements for each subsystem are shown in Table 1.
Table 1. Disk space requirements in
megabytes
| Subsystem/Platform | Base executables | Development | Samples | Online help / HTML | PostScript / ASCII | Total |
|---|---|---|---|---|---|---|
| IBM | 17 | 16 | 17 | 16 | 12 | 78 |
| HP | 15 | 14 | 17 | 16 | 12 | 74 |
| Sun 4 | 24 | 16 | 17 | 16 | 12 | 85 |
| Sun Solaris | 24 | 17 | 17 | 16 | 12 | 86 |
| SGI | 18 | 23 | 17 | 16 | 12 | 86 |
| Data General | 22 | 13 | 17 | 16 | 12 | 80 |
| Digital Equip. | 33 | 40 | 17 | 16 | 12 | 118 |
If you are installing an upgrade version of Data Explorer, you should not install the new version over your current version. You should either remove the previous version of Data Explorer, or install the new version in a different directory. If you would like to install a new version of Data Explorer, but want the prior version to remain the default, then you can use the -noconfig option to the installdx script. This will install the new version, but will not set up the links which cause it to be the default installation. Note that you can use the DXROOT environment variable to specify which version of Data Explorer you want to use if you have multiple versions. DXROOT should point to the top level installation directory.
Data Explorer is comprised of five subsystems as follows:
Base executables | contains all files needed to run Data Explorer. |
Development environment | contains libraries, header files and other tools needed to build a custom executive. |
Samples | example programs, scripts, tutorial, and makefiles. |
Online help and HTML | online help available from the Data Explorer User Interface, and documentation in HTML format. |
PostScript and ASCII documentation | Documentation in PostScript format and for printing and in flat ASCII format for basic minimal viewing. |
All subsystems are placed under a common directory (e.g. /usr/lpp/dx) which is referred to as the root of the Data Explorer installation tree. Architecture-specific executable and library files are placed in the directories bin_ARCH and lib_ARCH under the Data Explorer root, where ARCH is one of the supported architectures (alphax, aviion, hp700, ibm6000, sgi, solaris, sun4). As part of configuring Data Explorer, links and small files are placed in the public file system that reference files within the Data Explorer root directory. The default Data Explorer root directory is /usr/lpp/dx. In a networked environment, it is most convenient for users if all workstations have Data Explorer available through the same root directory. This makes it easier to run the User Interface on one machine and the server on another.
Data Explorer is a licensed software product and uses the NetLS licensing system to manage its licensing. Two types of licenses are supported: node-locked and floating (or concurrent-use). Node-locked licenses require a single configuration file containing an enabling password, while the floating license requires that a NetLS license server configured with at least one Data Explorer license is running somewhere within your network. If you expect to use a floating license and you do not have a NetLS license server running in your network you will need to install one (see Chapter 15. "Installing a NetLS License Server"). Please note that node-locked licenses do not require the use or installation of a NetLS license server.
Data Explorer running under AIX requires that the following software products be installed before attempting to install Data Explorer:
If you want to use hardware rendering you will need to have the following installed:
If you want create a customized executive, you will need the following development products:
You can use AIX's lslpp tool to determine whether or not a software product has been installed. For example, to determine if the the X11 run-time environment for AIX 4.x has been installed enter the following:
lslpp -h X11.base.rte
Note: Data Explorer does not use installp format.
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting Network Computing System (NCS) issues (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for each of the supported architectures. The third file contains NetLS license server installation kits for each supported architecture. The NetLS license server is used to support the standard licensing mechanism for Data Explorer.
To install Data Explorer, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> installdx ./installdx <platform>
<device> is the appropriate tape device for the operating system from which you run installdx. Example tape devices for AIX are:
/dev/rmt0, /dev/rmt1, ...<platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (ibm6000).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
Please follow the instructions presented by installdx carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 7.3 , "Configuring a Data Explorer License for IBM RISC System/6000" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
Note: On AIX systems, the block size of the tape device must be set to 512 bytes. Use "smit" to determine and change the device block size if necessary.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation. The NetLS license server is used to support the standard licensing mechanism used for Data Explorer.
To install Data Explorer, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom by entering the following command:
mount -r -v cdrfs <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/cd0.
Type:
cd /cdrom ./installdx.sh <platform><platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (ibm6000).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 7.3 , "Configuring a Data Explorer License for IBM RISC System/6000" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
Data Explorer uses the NetLS licensing system from Gradient Technologies, Inc., to manage the two types of licenses available with Data Explorer:
Node-locked license | This license program is restricted to the machine matching the node identifier for which a license was acquired. All version 1 basic one-time charge licenses are considered node-locked licenses. Please note that this type of license does NOT require the installation of the NetLS license server software included with Data Explorer. |
Floating (or concurrent use) license | This license can be used by any supported workstation on the network as long as the maximum number of concurrent Data Explorer users does not exceed the number of purchased floating licenses. Floating (or concurrent use) license installations require that a NetLS license server run somewhere in the network. If your network does not currently run a license server, see Chapter 15. "Installing a NetLS License Server". Under a floating license, IBM waives the requirement that customers notify IBM of change in designated machine. When this program does not operate under the control of NetLS, normal customer notification of change in designated machine rules apply. For more information on the licensing software, please refer to the Gradient documentation that is provided with the Data Explorer installation kit. |
Both node-locked and floating licenses require that IBM be provided with a unique workstation identifier. Identifiers are generated by the NodeID script located in the bin directory of the Data Explorer installation directory tree (e.g. /usr/lpp/dx/bin/NodeID). This identifier is provided at the end of a successful installation. License type specifics are covered in the following sections.
When ordering license keys for Data Explorer SMP (Symmetric Multi-Processing), the product ID which you should provide to IBM software registration is 5765-587. Providing this product number will result in two keys being issued for each 5765-587 license request: one key for product ID 5765-586, which enables uniprocessor operation, and a second key for ID 5765-587, which enables SMP functionality. Both of these keys must be installed before Data Explorer SMP will be fully functional.
To enable Data Explorer with a node-locked license:
For the AIX operating system both the Vendor ID and the Product Password must be placed in the file:
/usr/lib/netls/conf/nodelock
The Vendor ID and the Product Password must appear on the same line with the Vendor ID placed first and a space between them. For example,
543b0f87c093.02.81.87.92.34.00.00.00 gganccupqb5d8auxabdws2a
Additional information on editing the nodelock file can be found on page 31 of Gradient's Managing Software Products with the Network License System included with your Data Explorer package.
To set up a floating (or concurrent use) license, you must have a license server running within your network. If you do not have a license server running, see Chapter 15. "Installing a NetLS License Server".
Once you have a NetLS license server running within your network, you should:
Data Explorer is comprised of five subsystems as follows:
Base executables | contains all files needed to run Data Explorer. |
Development environment | contains libraries, header files and other tools needed to build a custom executive. |
Samples | example programs, scripts, tutorial, and makefiles. |
Online help and HTML | online help available from the Data Explorer User Interface, and documentation in HTML format. |
PostScript and ASCII documentation | Documentation in PostScript format and for printing and in flat ASCII format for basic minimal viewing. |
All subsystems are placed under a common directory (e.g. /usr/lpp/dx) which is referred to as the root of the Data Explorer installation tree. Architecture-specific executable and library files are placed in the directories bin_ARCH and lib_ARCH under the Data Explorer root, where ARCH is one of the supported architectures (alphax, aviion, hp700, ibm6000, sgi, solaris, sun4). As part of configuring Data Explorer, links and small files are placed in the public file system that reference files within the Data Explorer root directory. The default Data Explorer root directory is /usr/lpp/dx. In a networked environment, it is most convenient for users if all workstations have Data Explorer available through the same root directory. This makes it easier to run the User Interface on one machine and the server on another.
Data Explorer is a licensed software product and uses the NetLS licensing system to manage its licensing. Two types of licenses are supported: node-locked and floating (or concurrent-use). Node-locked licenses require a single configuration file containing an enabling password, while the floating license requires that a NetLS license server configured with at least one Data Explorer license is running somewhere within your network. If you expect to use a floating license and you do not have a NetLS license server running in your network you will need to install one (see Chapter 15. "Installing a NetLS License Server"). Please note that node-locked licenses do not require the use or installation of a NetLS license server.
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting Network Computing System (NCS) issues (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for each of the supported architectures. The third file contains NetLS license server installation kits for each supported architecture. The NetLS license server is used to support the standard licensing mechanism for Data Explorer.
To install Data Explorer, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> installdx ./installdx <platform>
<device> is the appropriate tape device for the operating system from which you run installdx. Example tape devices for HP-UX are:
/dev/rmt/0<platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (hp700).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
Please follow the instructions presented by installdx carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 8.3 , "Configuring a Data Explorer License for an HP Workstation" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation. The NetLS license server is used to support the standard licensing mechanism used for Data Explorer.
To install Data Explorer, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom by entering the following command:
mount -r -t cdfs <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/dsk/2s0.
Type:
cd /cdrom ./installdx.sh <platform><platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (hp700).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 8.3 , "Configuring a Data Explorer License for an HP Workstation" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
Note: On HP-UX systems, the file names will appear capitalized and include a version number (e.g. INSTALLDX.SH;1). If this is the case, then you must enter:
'./INSTALLDX.SH;1'(including the single quotes) instead of ./installdx.
Data Explorer uses the NetLS licensing system from Gradient Technologies, Inc., to manage the two types of licenses available with Data Explorer:
Node-locked license | This license program is restricted to the machine matching the node identifier for which a license was acquired. All version 1 basic one-time charge licenses are considered node-locked licenses. Please note that this type of license does NOT require the installation of the NetLS license server software included with Data Explorer. |
Floating (or concurrent use) license | This license can be used by any supported workstation on the network as long as the maximum number of concurrent Data Explorer users does not exceed the number of purchased floating licenses. Floating (or concurrent use) license installations require that a NetLS license server run somewhere in the network. If your network does not currently run a license server, see Chapter 15. "Installing a NetLS License Server". Under a floating license, IBM waives the requirement that customers notify IBM of change in designated machine. When this program does not operate under the control of NetLS, normal customer notification of change in designated machine rules apply. For more information on the licensing software, please refer to the Gradient documentation that is provided with the Data Explorer installation kit. |
Both node-locked and floating licenses require that IBM be provided with a unique workstation identifier. Identifiers are generated by the NodeID script located in the bin directory of the Data Explorer installation directory tree (e.g. /usr/lpp/dx/bin/NodeID). This identifier is provided at the end of a successful installation. License type specifics are covered in the following sections.
To enable Data Explorer with a node-locked license:
For the HP-UX operating system both the Vendor ID and the Product Password must be placed in the file:
/usr/netls/nodelock
The Vendor ID and the Product Password must appear on the same line with the Vendor ID placed first and a space between them. For example,
543b0f87c093.02.81.87.92.34.00.00.00 gganccupqb5d8auxabdws2a
Additional information on editing the nodelock file can be found on page 31 of Gradient's Managing Software Products with the Network License System included with your Data Explorer package.
Note: You should refer to the section "Floating License Issues on an HP Workstation" before continuing with this section.
To set up a floating (or concurrent use) license, you must have a license server running within your network. If you do not have a license server running, see Chapter 15. "Installing a NetLS License Server".
Once you have a NetLS license server running within your network, you should:
Data Explorer is comprised of five subsystems as follows:
Base executables | contains all files needed to run Data Explorer. |
Development environment | contains libraries, header files and other tools needed to build a custom executive. |
Samples | example programs, scripts, tutorial, and makefiles. |
Online help and HTML | online help available from the Data Explorer User Interface, and documentation in HTML format. |
PostScript and ASCII documentation | Documentation in PostScript format and for printing and in flat ASCII format for basic minimal viewing. |
All subsystems are placed under a common directory (e.g. /usr/lpp/dx) which is referred to as the root of the Data Explorer installation tree. Architecture-specific executable and library files are placed in the directories bin_ARCH and lib_ARCH under the Data Explorer root, where ARCH is one of the supported architectures (alphax, aviion, hp700, ibm6000, sgi, solaris, sun4). As part of configuring Data Explorer, links and small files are placed in the public file system that reference files within the Data Explorer root directory. The default Data Explorer root directory is /usr/lpp/dx. In a networked environment, it is most convenient for users if all workstations have Data Explorer available through the same root directory. This makes it easier to run the User Interface on one machine and the server on another.
Data Explorer is a licensed software product and uses the NetLS licensing system to manage its licensing. Two types of licenses are supported: node-locked and floating (or concurrent-use). Node-locked licenses require a single configuration file containing an enabling password, while the floating license requires that a NetLS license server configured with at least one Data Explorer license is running somewhere within your network. If you expect to use a floating license and you do not have a NetLS license server running in your network you will need to install one (see Chapter 15. "Installing a NetLS License Server"). Please note that node-locked licenses do not require the use or installation of a NetLS license server.
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting Network Computing System (NCS) issues (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for each of the supported architectures. The third file contains NetLS license server installation kits for each supported architecture. The NetLS license server is used to support the standard licensing mechanism for Data Explorer.
To install Data Explorer, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> installdx ./installdx <platform>
<device> is the appropriate tape device for the operating system from which you run installdx. Example tape devices for SunOS and Solaris are:
Sun4: /dev/rst0, /dev/rst1, ... Solaris: /dev/rmt0<platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (sun4 or solaris).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
Please follow the instructions presented by installdx carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 9.3 , "Configuring a Data Explorer License for a Sun SPARCstation" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation. The NetLS license server is used to support the standard licensing mechanism used for Data Explorer.
To install Data Explorer, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom by entering the following command:
SunOS: mount -r -t hsfs <CD-ROM-Device> /cdrom Solaris: mount -r -f hsfs <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/sr0.
Type:
cd /cdrom ./installdx.sh <platform><platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (sun4 or solaris).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 9.3 , "Configuring a Data Explorer License for a Sun SPARCstation" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
Note: For Solaris, once your installation is complete, unmount and eject the disk by entering:
eject <CD-ROM-device>
Data Explorer uses the NetLS licensing system from Gradient Technologies, Inc., to manage the two types of licenses available with Data Explorer:
Node-locked license | This license program is restricted to the machine matching the node identifier for which a license was acquired. All version 1 basic one-time charge licenses are considered node-locked licenses. Please note that this type of license does NOT require the installation of the NetLS license server software included with Data Explorer. |
Floating (or concurrent use) license | This license can be used by any supported workstation on the network as long as the maximum number of concurrent Data Explorer users does not exceed the number of purchased floating licenses. Floating (or concurrent use) license installations require that a NetLS license server run somewhere in the network. If your network does not currently run a license server, see Chapter 15. "Installing a NetLS License Server". Under a floating license, IBM waives the requirement that customers notify IBM of change in designated machine. When this program does not operate under the control of NetLS, normal customer notification of change in designated machine rules apply. For more information on the licensing software, please refer to the Gradient documentation that is provided with the Data Explorer installation kit. |
Both node-locked and floating licenses require that IBM be provided with a unique workstation identifier. Identifiers are generated by the NodeID script located in the bin directory of the Data Explorer installation directory tree (e.g. /usr/lpp/dx/bin/NodeID). This identifier is provided at the end of a successful installation. License type specifics are covered in the following sections.
When ordering license keys for Data Explorer SMP (Symmetric Multi-Processing), the product ID which you should provide to IBM software registration is 5765-587. Providing this product number will result in two keys being issued for each 5765-587 license request: one key for product ID 5765-586, which enables uniprocessor operation, and a second key for ID 5765-587, which enables SMP functionality. Both of these keys must be installed before Data Explorer SMP will be fully functional.
To enable Data Explorer with a node-locked license:
For the SunOS and Solaris operating system both the Vendor ID and the Product Password must be placed in the file:
/var/netls/nodelock
The Vendor ID and the Product Password must appear on the same line with the Vendor ID placed first and a space between them. For example,
543b0f87c093.02.81.87.92.34.00.00.00 gganccupqb5d8auxabdws2a
Additional information on editing the nodelock file can be found on page 31 of Gradient's Managing Software Products with the Network License System included with your Data Explorer package.
To set up a floating (or concurrent use) license, you must have a license server running within your network. If you do not have a license server running, see Chapter 15. "Installing a NetLS License Server".
Once you have a NetLS license server running within your network, you should:
Data Explorer is comprised of five subsystems as follows:
Base executables | contains all files needed to run Data Explorer. |
Development environment | contains libraries, header files and other tools needed to build a custom executive. |
Samples | example programs, scripts, tutorial, and makefiles. |
Online help and HTML | online help available from the Data Explorer User Interface, and documentation in HTML format. |
PostScript and ASCII documentation | Documentation in PostScript format and for printing and in flat ASCII format for basic minimal viewing. |
All subsystems are placed under a common directory (e.g. /usr/lpp/dx) which is referred to as the root of the Data Explorer installation tree. Architecture-specific executable and library files are placed in the directories bin_ARCH and lib_ARCH under the Data Explorer root, where ARCH is one of the supported architectures (alphax, aviion, hp700, ibm6000, sgi, solaris, sun4). As part of configuring Data Explorer, links and small files are placed in the public file system that reference files within the Data Explorer root directory. The default Data Explorer root directory is /usr/lpp/dx. In a networked environment, it is most convenient for users if all workstations have Data Explorer available through the same root directory. This makes it easier to run the User Interface on one machine and the server on another.
Data Explorer is a licensed software product and uses the NetLS licensing system to manage its licensing. Two types of licenses are supported: node-locked and floating (or concurrent-use). Node-locked licenses require a single configuration file containing an enabling password, while the floating license requires that a NetLS license server configured with at least one Data Explorer license is running somewhere within your network. If you expect to use a floating license and you do not have a NetLS license server running in your network you will need to install one (see Chapter 15. "Installing a NetLS License Server"). Please note that node-locked licenses do not require the use or installation of a NetLS license server.
Note: The block size of the tape device must be set to 512 bytes. Use the following command to determine the current block size:
mt -t <device> blksize<device> is the appropriate tape device for the operating system from which you run installdx. Example IRIX tape devices are:
/dev/rmt/tps0d4ns, /dev/rmt/tps0d5ns, ...
On IRIX be sure to use the no-swap tape drives which have the characters "ns" in the device name.
Use the following command to set the correct block size if necessary:
mt -t <device> setblksz 512
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting Network Computing System (NCS) issues (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for each of the supported architectures. The third file contains NetLS license server installation kits for each supported architecture. The NetLS license server is used to support the standard licensing mechanism for Data Explorer.
To install Data Explorer, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> installdx ./installdx <platform>
<device> is the appropriate tape device for the operating system from which you run installdx. Example tape devices for IRIX are:
/dev/rmt/tps0d4ns, /dev/rmt/tps0d5ns, ...<platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (sgi).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
Please follow the instructions presented by installdx carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 10.3 , "Configuring a Data Explorer License for an SGI Workstation" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation. The NetLS license server is used to support the standard licensing mechanism used for Data Explorer.
To install Data Explorer, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom by entering the following command:
mount -r -t iso9660 <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/scsi/sc0d0l0.
Type:
cd /cdrom ./installdx.sh <platform><platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (sgi).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 10.3 , "Configuring a Data Explorer License for an SGI Workstation" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
Data Explorer uses the NetLS licensing system from Gradient Technologies, Inc., to manage the two types of licenses available with Data Explorer:
Node-locked license | This license program is restricted to the machine matching the node identifier for which a license was acquired. All version 1 basic one-time charge licenses are considered node-locked licenses. Please note that this type of license does NOT require the installation of the NetLS license server software included with Data Explorer. |
Floating (or concurrent use) license | This license can be used by any supported workstation on the network as long as the maximum number of concurrent Data Explorer users does not exceed the number of purchased floating licenses. Floating (or concurrent use) license installations require that a NetLS license server run somewhere in the network. If your network does not currently run a license server, see Chapter 15. "Installing a NetLS License Server". Under a floating license, IBM waives the requirement that customers notify IBM of change in designated machine. When this program does not operate under the control of NetLS, normal customer notification of change in designated machine rules apply. For more information on the licensing software, please refer to the Gradient documentation that is provided with the Data Explorer installation kit. |
Both node-locked and floating licenses require that IBM be provided with a unique workstation identifier. Identifiers are generated by the NodeID script located in the bin directory of the Data Explorer installation directory tree (e.g. /usr/lpp/dx/bin/NodeID). This identifier is provided at the end of a successful installation. License type specifics are covered in the following sections.
When ordering license keys for Data Explorer SMP (Symmetric Multi-Processing), the product ID which you should provide to IBM software registration is 5765-587. Providing this product number will result in two keys being issued for each 5765-587 license request: one key for product ID 5765-586, which enables uniprocessor operation, and a second key for ID 5765-587, which enables SMP functionality. Both of these keys must be installed before Data Explorer SMP will be fully functional.
To enable Data Explorer with a node-locked license:
For the IRIX operating system both the Vendor ID and the Product Password must be placed in the file:
/usr/netls/nodelock
The Vendor ID and the Product Password must appear on the same line with the Vendor ID placed first and a space between them. For example,
543b0f87c093.02.81.87.92.34.00.00.00 gganccupqb5d8auxabdws2a
Additional information on editing the nodelock file can be found on page 31 of Gradient's Managing Software Products with the Network License System included with your Data Explorer package.
To set up a floating (or concurrent use) license, you must have a license server running within your network. If you do not have a license server running, see Chapter 15. "Installing a NetLS License Server".
Once you have a NetLS license server running within your network, you should:
Data Explorer is comprised of five subsystems as follows:
Base executables | contains all files needed to run Data Explorer. |
Development environment | contains libraries, header files and other tools needed to build a custom executive. |
Samples | example programs, scripts, tutorial, and makefiles. |
Online help and HTML | online help available from the Data Explorer User Interface, and documentation in HTML format. |
PostScript and ASCII documentation | Documentation in PostScript format and for printing and in flat ASCII format for basic minimal viewing. |
All subsystems are placed under a common directory (e.g. /usr/lpp/dx) which is referred to as the root of the Data Explorer installation tree. Architecture-specific executable and library files are placed in the directories bin_ARCH and lib_ARCH under the Data Explorer root, where ARCH is one of the supported architectures (alphax, aviion, hp700, ibm6000, sgi, solaris, sun4). As part of configuring Data Explorer, links and small files are placed in the public file system that reference files within the Data Explorer root directory. The default Data Explorer root directory is /usr/lpp/dx. In a networked environment, it is most convenient for users if all workstations have Data Explorer available through the same root directory. This makes it easier to run the User Interface on one machine and the server on another.
Data Explorer is a licensed software product and uses the NetLS licensing system to manage its licensing. Two types of licenses are supported: node-locked and floating (or concurrent-use). Node-locked licenses require a single configuration file containing an enabling password, while the floating license requires that a NetLS license server configured with at least one Data Explorer license is running somewhere within your network. If you expect to use a floating license and you do not have a NetLS license server running in your network you will need to install one (see Chapter 15. "Installing a NetLS License Server"). Please note that node-locked licenses do not require the use or installation of a NetLS license server.
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting Network Computing System (NCS) issues (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for each of the supported architectures. The third file contains NetLS license server installation kits for each supported architecture. The NetLS license server is used to support the standard licensing mechanism for Data Explorer.
To install Data Explorer, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> installdx ./installdx <platform>
<device> is the appropriate tape device for the operating system from which you run installdx. Example tape devices for DG/UX are:
/dev/rmt/0, ...<platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (aviion).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
Please follow the instructions presented by installdx carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 11.3 , "Configuring a Data Explorer License for a Data General AViiON" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation. The NetLS license server is used to support the standard licensing mechanism used for Data Explorer.
To install Data Explorer, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom by entering the following command:
mount -r -t cdrom -o noversion <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/pdsk/1.
Type:
cd /cdrom ./installdx.sh <platform><platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (aviion).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 11.3 , "Configuring a Data Explorer License for a Data General AViiON" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
Data Explorer uses the NetLS licensing system from Gradient Technologies, Inc., to manage the two types of licenses available with Data Explorer:
Node-locked license | This license program is restricted to the machine matching the node identifier for which a license was acquired. All version 1 basic one-time charge licenses are considered node-locked licenses. Please note that this type of license does NOT require the installation of the NetLS license server software included with Data Explorer. |
Floating (or concurrent use) license | This license can be used by any supported workstation on the network as long as the maximum number of concurrent Data Explorer users does not exceed the number of purchased floating licenses. Floating (or concurrent use) license installations require that a NetLS license server run somewhere in the network. If your network does not currently run a license server, see Chapter 15. "Installing a NetLS License Server". Under a floating license, IBM waives the requirement that customers notify IBM of change in designated machine. When this program does not operate under the control of NetLS, normal customer notification of change in designated machine rules apply. For more information on the licensing software, please refer to the Gradient documentation that is provided with the Data Explorer installation kit. |
Both node-locked and floating licenses require that IBM be provided with a unique workstation identifier. Identifiers are generated by the NodeID script located in the bin directory of the Data Explorer installation directory tree (e.g. /usr/lpp/dx/bin/NodeID). This identifier is provided at the end of a successful installation. License type specifics are covered in the following sections.
To enable Data Explorer with a node-locked license:
For the DG/UX operating system both the Vendor ID and the Product Password must be placed in the file:
/var/netls/nodelock
The Vendor ID and the Product Password must appear on the same line with the Vendor ID placed first and a space between them. For example,
543b0f87c093.02.81.87.92.34.00.00.00 gganccupqb5d8auxabdws2a
Additional information on editing the nodelock file can be found on page 31 of Gradient's Managing Software Products with the Network License System included with your Data Explorer package.
To set up a floating (or concurrent use) license, you must have a license server running within your network. If you do not have a license server running, see Chapter 15. "Installing a NetLS License Server".
Once you have a NetLS license server running within your network, you should:
Data Explorer is comprised of five subsystems as follows:
Base executables | contains all files needed to run Data Explorer. |
Development environment | contains libraries, header files and other tools needed to build a custom executive. |
Samples | example programs, scripts, tutorial, and makefiles. |
Online help and HTML | online help available from the Data Explorer User Interface, and documentation in HTML format. |
PostScript and ASCII documentation | Documentation in PostScript format and for printing and in flat ASCII format for basic minimal viewing. |
All subsystems are placed under a common directory (e.g. /usr/lpp/dx) which is referred to as the root of the Data Explorer installation tree. Architecture-specific executable and library files are placed in the directories bin_ARCH and lib_ARCH under the Data Explorer root, where ARCH is one of the supported architectures (alphax, aviion, hp700, ibm6000, sgi, solaris, sun4). As part of configuring Data Explorer, links and small files are placed in the public file system that reference files within the Data Explorer root directory. The default Data Explorer root directory is /usr/lpp/dx. In a networked environment, it is most convenient for users if all workstations have Data Explorer available through the same root directory. This makes it easier to run the User Interface on one machine and the server on another.
Data Explorer is a licensed software product and uses the NetLS licensing system to manage its licensing. Two types of licenses are supported: node-locked and floating (or concurrent-use). Node-locked licenses require a single configuration file containing an enabling password, while the floating license requires that a NetLS license server configured with at least one Data Explorer license is running somewhere within your network. If you expect to use a floating license and you do not have a NetLS license server running in your network you will need to install one (see Chapter 15. "Installing a NetLS License Server"). Please note that node-locked licenses do not require the use or installation of a NetLS license server.
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting Network Computing System (NCS) issues (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for each of the supported architectures. The third file contains NetLS license server installation kits for each supported architecture. The NetLS license server is used to support the standard licensing mechanism for Data Explorer.
To install Data Explorer, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> installdx ./installdx <platform>
<device> is the appropriate tape device for the operating system from which you run installdx. Example tape devices for OSF/1 are:
/dev/rmt01, /dev/rmt0h, ...<platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (alphax).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
Please follow the instructions presented by installdx carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 12.3 , "Configuring a Data Explorer License for a DEC 3000 AXP" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation. The NetLS license server is used to support the standard licensing mechanism used for Data Explorer.
To install Data Explorer, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom by entering the following command:
mount -r -t cdfs <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/rz4c.
Type:
cd /cdrom ./installdx.sh <platform><platform> is used to indicate the platform for which the Data Explorer files will be extracted. The supported platforms are:
alphax, aviion, hp700, ibm6000, sgi, solaris, sun4
This argument is optional and the default is the host platform (alphax).
The installation script will ask if you want to install or deinstall Data Explorer and then a series of questions related to the installation. You will be given the opportunity to set the installation directory and to select the Data Explorer subsystems to install.
When doing an installation for an architecture other than the current host, you may need to run the Configure script provided with Data Explorer on the workstations to which you expect to export the Data Explorer installation tree. See Chapter 13. "The Configure Script".
After installation and configuration is complete, which may take as much as 30 minutes, you will be provided with a unique workstation (node) identifier that must be provided to IBM to acquire the enabling license information. See 12.3 , "Configuring a Data Explorer License for a DEC 3000 AXP" for information on how to reacquire the identifier (if you lose it) and on how to use the node identifier to enable Data Explorer.
Note: On OSF/1 systems, the file names will appear capitalized and include a version number (e.g. INSTALLDX.SH;1). If this is the case, then you must enter:
'./INSTALLDX.SH;1'(including the single quotes) instead of ./installdx.
Data Explorer uses the NetLS licensing system from Gradient Technologies, Inc., to manage the two types of licenses available with Data Explorer:
Node-locked license | This license program is restricted to the machine matching the node identifier for which a license was acquired. All version 1 basic one-time charge licenses are considered node-locked licenses. Please note that this type of license does NOT require the installation of the NetLS license server software included with Data Explorer. |
Floating (or concurrent use) license | This license can be used by any supported workstation on the network as long as the maximum number of concurrent Data Explorer users does not exceed the number of purchased floating licenses. Floating (or concurrent use) license installations require that a NetLS license server run somewhere in the network. If your network does not currently run a license server, see Chapter 15. "Installing a NetLS License Server". Under a floating license, IBM waives the requirement that customers notify IBM of change in designated machine. When this program does not operate under the control of NetLS, normal customer notification of change in designated machine rules apply. For more information on the licensing software, please refer to the Gradient documentation that is provided with the Data Explorer installation kit. |
Both node-locked and floating licenses require that IBM be provided with a unique workstation identifier. Identifiers are generated by the NodeID script located in the bin directory of the Data Explorer installation directory tree (e.g. /usr/lpp/dx/bin/NodeID). This identifier is provided at the end of a successful installation. License type specifics are covered in the following sections.
To enable Data Explorer with a node-locked license:
For the OSF/1 operating system both the Vendor ID and the Product Password must be placed in the file:
/var/netls/nodelock
The Vendor ID and the Product Password must appear on the same line with the Vendor ID placed first and a space between them. For example,
543b0f87c093.02.81.87.92.34.00.00.00 gganccupqb5d8auxabdws2a
Additional information on editing the nodelock file can be found on page 31 of Gradient's Managing Software Products with the Network License System included with your Data Explorer package.
To set up a floating (or concurrent use) license, you must have a license server running within your network. If you do not have a license server running, see Chapter 15. "Installing a NetLS License Server".
Once you have a NetLS license server running within your network, you should:
The Configure script, located in the bin directory of the Data Explorer installation tree, is used to install or deinstall soft links and small files in standard places (e.g.. /usr/local/bin, /usr/local/lib, ...) that reference the Data Explorer installation tree.
Configure is run automatically from the installation script, so generally one does not need to run it directly. However, if for example, Data Explorer for architecture A (e.g. ibm6000) is installed on a machine with architecture B (e.g. hp700), then Configure may need to be run on the machine with architecture A that expects to use Data Explorer.
Configure provides the ability to configure individual subsystems of Data Explorer, but by default will attempt to configure all of them.
The run-time subsystem uses either /usr/local/bin or /usr/bin (in that order) as the directory to install executables (e.g. the dx driver script). If neither of these directories is writable an error will occur. A Data Explorer manual page is also installed in the appropriate manual page directory tree if that directory is writable. Note, that in a networked environment in which /usr/local/bin and the manual page directory are shared among many hosts, Configure need only be run once to configure all such machines to use the run-time subsystem of Data Explorer.
The development subsystem uses the same executable directories as the run-time subsystem to install its development related executables (e.g. mdf-c). This subsystem also uses either /usr/local/lib or /usr/lib (in that order) as the directory to install links to libraries (i.e. libDX.a, libDXlite.a). In addition, a link is made from /usr/include/dx to the include directory of the Data Explorer installation directory. Note, that in a networked environment in which /usr/local/lib and /usr/local/bin directory are shared among many hosts, Configure need only be run once to configure all such machines to use the development subsystem of Data Explorer with the exception of the /usr/include/dx directory which is generally not shared.
The samples subsystem and the online help subsystem do not require configuring.
To perform the standard configuration after installation, enter the following:
Configure
To perform the standard deconfiguration prior to removing Data Explorer from your system or to reconfigure Data Explorer, enter the following:
Configure deinstall
If the root directory is moved after installation, Data Explorer can (and should) be reconfigured to use the new root directory with the following:
Configure deinstall Configure -dxroot <new directory>
A complete description of the usage and options for Configure are found in 13.1 , "Command Line Options for Configure".
Usage is as follows:
Configure [ -<option> ... ] [ <platform> ] [ <operation> ]Where <operation> is one of install or deinstall and <platform> is one of the supported architectures (alphax, aviion, hp700, ibm6000, sgi, solaris, sun4). The default action is to configure all Data Explorer subsystems for the architecture that is running Configure.
The options are as follows:
-bindir <bindir> | indicates the name of the directory where executable shell scripts should be placed. The given directory must exist. The default is /usr/local/bin and if this is not writable, then /usr/bin. |
-libdir <libdir> | indicates the name of the directory where Data Explorer libraries should be placed. The given directory must exist. The default is /usr/local/lib and if this is not writable, then /usr/lib. |
-check | lists the actions that will be taken without actually performing them. |
-dxroot | indicates the root of the Data Explorer installation directory. The default is /usr/lpp/dx. |
-echo | the same as -check, above. |
-help | gives a listing of supported options. |
-online-help | perform the given operation for the online help subsystem. |
-html | perform the given operation for the HTML subsystem. |
-samples | perform the given operation for the samples subsystem. |
-runtime | perform the given operation for the run-time subsystem. |
-develop | perform the given operation for the develop subsystem. |
If you would like to use a configuration other than the one provided by the default installation you can deinstall the configuration and reconfigure Data Explorer with the configuration you prefer. You can use the options as discussed in 13.1 , "Command Line Options for Configure" to customize your installation. To remove the default configuration, execute the following:
Configure deinstall
So, for example, to change the configuration of the run-time subsystem to use a different library and executable directory, execute the following:
Configure deinstall Configure -runtime -libdir /my/lib/dir -bindir /my/bin/dir
To change the configuration of all subsystems to use the default executable directory and a different library directory, execute the following:
Configure deinstall Configure -libdir /my/lib/dir
If the error message "./Configure: not found" occurs during a tape installation, it is likely that the autorewinding tape drive was given as the name of the tape device during installation. To fix this, rerun the installation script and be sure to give the non-autorewinding device as listed by the installation script.
If a tape installation seems to take longer than 30-40 minutes on AIX, it may be that the block size of the tape size is set to 0. If this is the case, use "smit", AIX's System Management Interface Tool, to change the block size of the device to 512 bytes.
It is necessary for you to read this section only if you expect to use a floating (or concurrent use) license and you are NOT presently running a NetLS license server somewhere in your network. (Please note that node-locked licenses do NOT require the installation of a NetLS license server). The job of selecting and configuring a license server is best performed by someone knowledgeable in system administration tasks. The remainder of this section is designed to assist a system/network administrator in configuring a license server.
This section describes a basic installation in which the license server and all client nodes reside on the same network segment. It also assumes that you are not currently using the Network Computing System (NCS) local or global location broker daemons llbd and glbd. For more complex NetLS configurations it is recommended that you consult both Gradient's Managing Software Products with the Network License System and Managing NCS Software which is provided in PostScript format on the distribution media in the compressed file ncs_ps.Z. You need to decompress this file using the UNIX uncompress command before viewing or printing it..
NetLS uses NCS to provide location services through the use of global and local location broker daemons (glbd and llbd). Therefore you must install and configure a NCS "cell" before you can run the NetLS license server daemon (netlsd).
The basic setup described here will configure a default cell and install and start all three daemons on a single "License Server" machine and configure them to start automatically when the machine is re-booted. If you decide on a different setup for your network please keep in mind that you must:
Run a glbd on at least one node in your network
Run llbd's on the node running the netlsd and the node running the glbd.
To configure a basic license server installation you must first identify
the node best suited to be your license server. This should be a node
which is very stable (i.e. rarely goes down) as floating licenses will
be unavailable when this machine is down. A file server machine would be
a good choice. Once a machine has been selected you can proceed with the
installation of the license server software.
We provide license server software on our installation media primarily
to support downlevel operating systems and to resolve compatibility
issues for certain platforms. With this in mind, PLEASE adhere to the
following:
15.2 IMPORTANT License Server
information for concurrent licensees.
| Important |
|---|
| This section is only applicable if you are running AIX 3.2.5. For AIX 4.x, NetLS and NCS are provided as part of the operating system distribution. Users should insure that both the NCS and NetLS components of their operating system have been installed. If not they should be installed and started from your O/S vendor's distribution media. |
Note: On AIX systems, the block size of the tape device must be set to 512 bytes. Use smit to determine and change the device block size if necessary.
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting the Network Computing System (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for all supported architectures. The third file contains NetLS license server installation kits for each supported architecture.
To install the license server, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> install_lsk ./install_lsk
<device> is the appropriate tape device for the operating system from which you run install_lsk. Example AIX tape devices are:
/dev/rmt0, /dev/rmt1, ...
Please follow the instructions presented by install_lsk carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation.
To install the license server, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom. Mount the disk by entering the following command:
mount -r -v cdrfs <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/cd0.
Type:
cd /cdrom ./install_lsk.sh
NetLS and NCS are provided as part of the operating system distribution for HP-UX. HP-UX users should insure that both the NCS and NetLS components of their operating system have been installed. If not they should be installed and started from your O/S vendor's distribution media.
The HP-UX 8.0x operating system contains an older and incompatible version of the network license server daemon (netlsd). Users of this operating system must run the install_lsk or install_lsk.sh script from the Data Explorer distribution media (see "Installing a License Server for HP Workstation from Tape" or "Installing a License Server for HP Workstation from CD-ROM"). This script will detect the older version and replace it with a current version of netlsd which is delivered on the Data Explorer distribution media.
HP-UX 9.0x users do not need to run the NetLS installation script and may proceed with the section 8.3 , "Configuring a Data Explorer License for an HP Workstation" once the NetLS software is up and running.
HP users can refer to the following documents for assistance in installing and configuring NetLS and NCS:
11895-A02 | Managing NCS Software 11272-A01 Managing Software Products with the Network License System |
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting the Network Computing System (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for all supported architectures. The third file contains NetLS license server installation kits for each supported architecture.
To install the license server, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> install_lsk ./install_lsk
<device> is the appropriate tape device for the operating system from which you run install_lsk. Example HP-UX tape devices are:
/dev/rmt/0
Please follow the instructions presented by install_lsk carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation.
To install the license server, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom. Mount the disk by entering the following command:
mount -r -t cdfs <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/dsk/2s0.
Type:
cd /cdrom ./install_lsk.sh
Note: On HP-UX systems, the file names will appear capitalized and include a version number (e.g. INSTALL_LSK.SH;1). If this is the case, then you must enter:
'./INSTALL_LSK.SH;1'(including the single quotes) instead of ./install_lsk.
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting the Network Computing System (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for all supported architectures. The third file contains NetLS license server installation kits for each supported architecture.
To install the license server, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> install_lsk ./install_lsk
<device> is the appropriate tape device for the operating system from which you run install_lsk. Example SunOS and Solaris tape devices are:
Sun4: /dev/rst0, /dev/rst1, ... Solaris: /dev/rmt0
Please follow the instructions presented by install_lsk carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation.
To install the license server, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom. Mount the disk by entering the following command:
SunOS: mount -r -t hsfs <CD-ROM-Device> /cdrom Solaris: mount -r -f hsfs <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/sr0.
Type:
cd /cdrom ./install_lsk.sh
Note: For Solaris, once your installation is complete, unmount and eject the disk by entering:
eject <CD-ROM-device>
Note: The block size of the tape device must be set to 512 bytes. Use the following command to determine the current block size:
mt -t <device> blksize<device> is the appropriate tape device for the operating system from which you run installdx. Example IRIX tape devices are:
/dev/rmt/tps0d4ns, /dev/rmt/tps0d5ns, ...
On IRIX be sure to use the no-swap tape drives which have the characters "ns" in the device name.
Use the following command to set the correct block size if necessary:
mt -t <device> setblksz 512
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting the Network Computing System (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for all supported architectures. The third file contains NetLS license server installation kits for each supported architecture.
To install the license server, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> install_lsk ./install_lsk
<device> is the appropriate tape device for the operating system from which you run install_lsk. Example IRIX tape devices are:
/dev/rmt/tps0d4ns, /dev/rmt/tps0d5ns, ...
Please follow the instructions presented by install_lsk carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation.
To install the license server, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom. Mount the disk by entering the following command:
mount -r -t iso9660 <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/scsi/sc0d0l0.
Type:
cd /cdrom ./install_lsk.sh
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting the Network Computing System (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for all supported architectures. The third file contains NetLS license server installation kits for each supported architecture.
To install the license server, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> install_lsk ./install_lsk
<device> is the appropriate tape device for the operating system from which you run install_lsk. Example DG/UX tape devices are:
/dev/rmt/0, ...
Please follow the instructions presented by install_lsk carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation.
To install the license server, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom. Mount the disk by entering the following command:
mount -r -t cdrom -o noversion <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/pdsk/1.
Type:
cd /cdrom ./install_lsk.sh
Tape distributions of Data Explorer contain three tar format files. The first contains two install scripts (installdx, install_lsk) and a PostScript file documenting the Network Computing System (ncs_ps.Z). The second contains the Data Explorer installation tree which contains Data Explorer for all supported architectures. The third file contains NetLS license server installation kits for each supported architecture.
To install the license server, log in as root, insert the tape in the drive, and type:
cd /tmp tar xvf <device> install_lsk ./install_lsk
<device> is the appropriate tape device for the operating system from which you run install_lsk. Example OSF/1 tape devices are:
/dev/rmt01, /dev/rmt0h, ...
Please follow the instructions presented by install_lsk carefully. In particular, when asked to give the name of the tape device, be sure to give the name of the non-autorewinding tape drive, examples of which are provided by the script. Also, if at anytime during the tape installation you are asked to mount the next tape, just press the <ENTER> key to have the installation continue normally.
CD-ROM distributions of Data Explorer contain a mountable file system that includes the installation scripts (installdx.sh for Data Explorer and install_lsk.sh for the NetLS license server software), the software itself (in tar format) and documentation.
To install the license server, log in as root, insert the distribution media in the drive, and type:
mkdir /cdrom
Mount the CD on /cdrom. Mount the disk by entering the following command:
mount -r -t cdfs <CD-ROM-Device> /cdromwhere <CD-ROM-device> is the actual name of the CD-ROM drive on your system. A typical name is /dev/rz4c.
Type:
cd /cdrom ./install_lsk.sh
Note: On OSF/1 systems, the file names will appear capitalized and include a version number (e.g. INSTALL_LSK.SH;1). If this is the case, then you must enter:
'./INSTALL_LSK.SH;1'(including the single quotes) instead of ./install_lsk.