home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
vabasi11.zip
/
IP21153O.ZIP
/
OS2
/
SERVER
/
INSTALL.TXT
< prev
next >
Wrap
Text File
|
1997-06-10
|
23KB
|
643 lines
============================================================
INSTALLING IBM VISUALAGE FOR BASIC VERSION 1.1
============================================================
IBM VisualAge for Basic includes the following components:
-- Clients for OS/2 and for Windows NT/Windows 95
-- Servers for OS/2, Windows NT, and AIX
-- Stored procedure VBX for Windows 3.1 (English only)
-- Stored procedure OCX for Windows NT/Windows 95
To install one or more of these components, see the
corresponding sections below
============================================================
CONTENTS OF THIS FILE
============================================================
Line
----
Copyright and Trademark Information For This File 30
Installing VisualAge for Basic on OS/2 60
Installing VisualAge for Basic on Win NT or Win 95 150
Creating SP catalog on OS/2, Win NT, or Win 95 200
Installing Stored Procedure VBX (English only) 230
Installing Stored Procedure OCX on Win NT or Win 95 260
Installing VisualAge for Basic on AIX 275
VisualAge for Basic Hardware and Software Requirements 450
============================================================
COPYRIGHT AND TRADEMARK INFORMATION FOR THIS FILE
============================================================
Licensed Materials -- Property of IBM.
(C) Copyright International Business Machines Corporation
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 Corporation.
AIX, AIX/6000, DB2, DB2/6000, IBM, OS/2, and VisualAge are
trademarks of International Business Machines Corporation.
Other company, product, and service names, which may be
denoted by a double asterisk (**), may be trademarks or
service marks of others.
Microsoft, Visual Basic, Windows, and Windows NT are
registered trademarks of Microsoft Corporation.
For license information, and copyright information related
to third-party code contained in IBM VisualAge for Basic,
please see the file NOTICES.TXT in the directory where you
installed VisualAge for Basic.
============================================================
INSTALLING VISUALAGE FOR BASIC ON OS/2
============================================================
Use this procedure to install VisualAge for Basic client or
server on OS/2.
IMPORTANT: On an OS/2 server machine, install DB2 for OS/2
before you install VisualAge for Basic server.
1. Put the VisualAge for Basic CD-ROM that contains the
language version you desire into your CD-ROM drive.
2. Open an OS/2 window and use the OS/2 command line for
steps 3-6.
3. Enter: e: (where e: is the drive letter for your
CD-ROM drive).
4. Change to the directory for the language you want to
install. For example, for the English version, enter:
cd \English
5. Select the component you want to install:
A. For VisualAge for Basic client enter: cd os2\client
B. For VisualAge for Basic server enter: cd os2\server
6. Enter: install and follow the instructions that
appear on your screen.
7. After installation is complete, shut down OS/2 and
reboot your machine.
8. Start VisualAge for Basic by opening the VisualAge for
Basic folder on your OS/2 desktop, then double-clicking
on the VisualAge for Basic icon. Or, you can go to an
OS/2 command line window and enter: vw
9. To view the VisualAge for Basic online help, select the
Help menu or press F1 in any product window.
10. To view the online books, open the VisualAge for
Basic folder, then open the Information folder, then
double- click on Getting Started, the Programming Guide,
or the Data Access Guide.
11. If you are installing VisualAge for Basic server on
OS/2, see the section below, "Creating Stored Procedure
Catalog on OS/2 or Windows NT."
============================================================
INSTALLING ODBC DRIVER MGR AND ODBC DATABASE DRIVERS ON OS/2
In the following instructions, D:\vabasic stands for the
drive and directory where you installed VisualAge for Basic.
1. Locate the following files in D:\vabasic\dll:
odbc.ini
odbcinst.ini
qeinst.ini
replace.exe
2. Run replace.exe against each of the three .ini files
above by entering the following three commands:
replace D:\vabasic\dll odbc.ini
replace D:\vabasic\dll odbcinst.ini
replace D:\vabasic\dll qeinst.ini
A file with an extension of .out is generated for each
of the three .ini files:
odbc.out
odbcinst.out
qeinst.out
3. Copy these three generated .out files to your C:\os2
system directory: copy *.out C:\os2
4. Change the file extension of each of the three .out
files to .ini:
ren odbc.out *.ini
ren odbcinst.out *.ini
ren qeinst.out *.ini
You should now be able to add new ODBC drivers by using the
odbcadm.exe command and clicking the Add button in the Data
Sources window.
Warning: In the list of installed ODBC drivers, some
databases may require that you install the database client
software first, before adding the ODBC driver in the Data
Sources window.
============================================================
INSTALLING VISUALAGE FOR BASIC ON WINDOWS NT OR WINDOWS 95
============================================================
Use this procedure to install VisualAge for Basic client on
Windows NT or Windows 95, or VisualAge for Basic server on
Windows NT.
1. Put the VisualAge for Basic CD-ROM that contains the
language version you desire into your CD-ROM drive.
2. On the Windows task bar, select Start --> Run.
3. Click on Browse and select the drive letter for your
CD-ROM drive.
4. Select the directory for the language you want to
install. For example, for the English version, select
the English directory.
5. Select the component you want to install:
A. For VisualAge for Basic client select \windows\client\disk1
B. For VisualAge for Basic server select \windows\server\disk1
6. In the directory you selected, double-click on setup.exe
7. Continue with the installation and follow the
instructions that appear on your screen.
8. After installation is complete, shut down Windows and
reboot your machine.
9. Start VisualAge for Basic by double-clicking on the
VisualAge for Basic icon on the Windows NT or Windows
95 desktop. Or, you can select: Start --> Programs -->
VisualAge for Basic --> VisualAge for Basic
10. To view the VisualAge for Basic online help, select the
Help menu or press F1 in any product window.
11. To view the online books, or the online help for the
stored procedure OLE custom control (SP OCX), open
the VisualAge for Basic folder, then click on Getting
Started, the Programming Guide, the Data Access Guide,
or SP OCX.
12. If you are installing VisualAge for Basic server on
Windows NT, see the section below, "Creating Stored
Procedure Catalog on OS/2 or Windows NT."
============================================================
CREATING STORED PROCEDURE CATALOG ON OS/2, WIN NT, OR WIN 95
============================================================
Use this procedure to create the catalog you will need to
keep track of your stored procedures.
1. On OS/2, open an OS/2 command line window. On Windows,
open a DB2 command line window.
2. Connect to the database. For example, enter:
db2 connect to sample
3. Change to the \sqllib\misc directory, where sqllib
is the root directory where DB2 is installed.
4. Run the script file to create the stored procedure
catalog by entering: db2 -vtf STORPROC.DDL
5. Grant users who can do remote build the authority to
update the catalog by entering one of the following
commands:
db2 GRANT ALL PRIVILEGES ON TABLE DB2CLI.PROCEDURES to PUBLIC
db2 GRANT ALL PRIVILEGES ON TABLE DB2CLI.PROCEDURES to userid
6. Disconnect from the database. For example, enter:
connect reset
============================================================
INSTALLING STORED PROCEDURE VBX ON WINDOWS 3.1
============================================================
The stored procedure VBX is supported only in the English
version of VisualAge for Basic. To install the stored
procedure VBX:
1. Put either one of the two VisualAge for Basic CD-ROMs
into your CD-ROM drive.
2. On Windows, select File --> Run --> Browse
3. Select the drive letter of your CD-ROM drive.
4. Select English\windows\vbx\install
5. After the installation screen appears, select VBX/OLE
support.
6. Continue with the installation and follow the
instructions that appear on your screen.
7. After installation is complete, shut down Windows and
reboot your machine.
8. To learn how to register and use the Stored Procedure
VBX/OLE control, read the SP VBX/OLE Help in the
VisualAge for Basic folder.
============================================================
INSTALLING STORED PROCEDURE OCX ON WINDOWS NT OR WINDOWS 95
============================================================
The Stored Procedure OCX is a selectable feature during the
installation of the VisualAge for Basic client on Windows NT
or Windows 95. See the section above, "Installing VisualAge
for Basic on Windows NT or Windows 95."
To learn how to register and use the OCX, see the "Stored
Procedure OCX Component" chapter in the "VisualAge for Basic
Programming Guide," and "SP/OCX Help" in the VisualAge for
Basic folder.
============================================================
INSTALLING VISUALAGE FOR BASIC ON AIX
============================================================
There are two phases to this installation:
1. Installing VisualAge for Basic as root.
2. Installing server as database instance owner.
============================================================
Installing VisualAge for Basic as Root on AIX
In this phase of the installation, you install the VisualAge
for Basic server code:
1. Log on to AIX as root.
2. Put the VisualAge for Basic CD-ROM that contains the
language version you desire into your CD-ROM drive.
3. Mount the CD-ROM to your CD-ROM mount directory.
4. Change to the desired language directory and then to
the AIX directory within your CD-ROM mount directory.
5. Copy vabasic.pkg to a temporary directory.
6. Change to the temporary directory and run the following
command: installp -ad vabasic.pkg all
7. Continue with the installation and follow the
instructions that appear on your screen.
8. After installation is complete, verify that VisualAge
for Basic is installed by running the following
command: lslpp -h vabasic.obj
9. Ensure your $PATH environment variable includes /usr/bin
10. If you need to remove VisualAge for Basic after
installation, log on as root and run the following
command:
installp -r vabasic.all (for AIX Version 3)
installp -u vabasic.all (for AIX Version 4)
============================================================
Installing Server as Database Instance Owner on AIX
Do this phase of the installation for each instance of
VisualAge for Basic that you want to operate on as a remote
or local server. In the steps below:
$HOME = home directory of the database instance
$SQLLIBDIR = sqllib/function directory
1. Log on to AIX as database instance owner.
2. Change to the $HOME/$SQLLIBDIR directory.
3. If you have already installed the server components,
remove them by executing the following command:
removeserver
4. To install the server components, execute the following
command: makeserver
5. The file $HOME/$SQLLIBDIR/CONFIG.VW has the single line:
VWDIR=/u/inst2/sqllib/function/vwdir
Change /u/inst2 to $HOME (your DB2 instance home
directory). For example, if your $HOME directory is
/u/inst, change the file to:
VWDIR=/u/inst/sqllib/function/vwdir
6. Update your LIBPATH by adding: $HOME/sqllib/function
7. To use the remote debug capabilities of VisualAge for
Basic Server on an AIX server that uses a DBCS locale,
enter the following settings in the .XDefaults file of
the userid that owns the DB2/6000 database instance(s):
*fontList: -dt-interface user-medium-r-normal-l*-*:
*XmText.fontList: -dt-interface
user-medium-r-normal-l*-*:
These settings are needed to correctly display error
messages containing double-byte characters.
============================================================
DB2-related tasks on AIX
1. Run db2profile for the appropriate database instance.
2. To run the VisualAge for Basic samples, create a
SAMPLE database by entering: $HOME/sqllib/misc/db2sampl
3. Do the steps below as database instance owner for
each database created:
A. Connect to the database. For example, enter:
db2 connect to sample
B. Change to the $HOME/sqllib/misc directory.
C. Run the script file to create the stored procedure
catalog by entering: db2 -vtf STORPROC.DDL
D. Grant users who can do remote build the authority to
update the catalog by entering one of the following
commands:
db2 GRANT ALL PRIVILEGES ON TABLE DB2CLI.PROCEDURES to PUBLIC
db2 GRANT ALL PRIVILEGES ON TABLE DB2CLI.PROCEDURES to userid
4. CLI applications cannot call to entry points in a
shared library on AIX if the library is in an archived
format, that is, if its name ends in "a". However,
VisualAge for Basic CAN call to entry points in a
non-archived library or in a .o file.
A. To extract the object file from a shared library,
create a file named shr.o by using the ar command:
ar vx libdb2.a
B. Then rename shr.o to libdb2.o by using the mv
command: mv shr.o libdb2.o
5. VisualAge for Basic makes the archived library for
DB2 for AIX Version 2.1.1 available as libdb2.o in
the $HOME/$SQLLIBDIR directory. If you are using a
different version of DB2 for AIX, create your own
libdb2.o by using the ar command and renaming
shr.o to libdb2.o
6. For DB2-related questions, see the DB2 for AIX
Installation Guide or the DB2 for AIX Reference.
============================================================
VisualAge for Basic Readme Files and Directories on AIX
During installation, VisualAge for Basic creates the
following readme files in /usr/lpp/vabasic:
INSTALL.TXT Installation information (the file you
are reading)
NOTICES.TXT Copyright information
README.1ST Readme file
During installation, VisualAge for Basic creates the
following files and directories under
/usr/lpp/vabasic/SERVER:
CONFIG.VW Root directory for config subdirectory
db2spla DLL provided by VisualAge for Basic
libdb2.o Unarchived libdb2.a
libgenAdapt.a Server remote build debug library
libgenAdapt2.a Server run-time library
stpsrv Server remote build file
spspstub Server stored procedure stub
udfxstub Server user-defined function stub
basI Command line Basic Interpreter for client
spbuild Command line stored procedure builder
for client
udfbuild Command line user-defined function
builder for client
vabasicx/include Server include files
vwdir/config Configuration files
vwdir/biudf Financial user-defined functions
makeserver Command to install VisualAge for Basic
removeserver Command to deinstall VisualAge for Basic
============================================================
VISUALAGE FOR BASIC HARDWARE AND SOFTWARE REQUIREMENTS
============================================================
============================================================
OS/2 Client Requirements
Hardware Requirements
-- 486 processor (or higher)
-- 24 MB of RAM
-- 49 MB of hard disk space
Software Requirements
-- OS/2 Version 3.0 or 4.0
-- If you are installing VisualAge for Basic with the
DB2 Support option, then you also need to install DB2
SDK for OS/2 Version 2.1 or later, using either NetBIOS
or TCP/IP communications. For information on DB2
communications requirements, see:
http://www.software.ibm.com/data/db2/db2v2.html
-- If your OS/2 client will connect to an AIX server, and
you plan to use the VisualAge for Basic Remote Debugger
to debug stored procedures and user-defined functions
on the AIX server from your client, then you need to
install the PMX X-Server component of TCP/IP on the
client.
============================================================
Windows NT or Windows 95 Client Requirements
Hardware Requirements
-- 486 processor (or higher)
-- 24 MB of RAM
-- 49 MB of hard disk space
Software Requirements
-- Microsoft Windows NT Version 3.51 or 4.0, or Windows 95.
-- If you are installing VisualAge for Basic with the
DB2 Support option, then you also need to install DB2
SDK for Windows Version 2.1 or later, using either
NetBIOS or TCP/IP communications. For information on
DB2 communications requirements, see:
http://www.software.ibm.com/data/db2/db2v2.html
-- If your Windows NT or Windows 95 client will connect to
an AIX server, and you plan to use the VisualAge for
Basic Remote Debugger to debug stored procedures and
user-defined functions on the AIX server from your
client, then you need to install a PC X-Server product.
============================================================
Stored Procedure VBX and OCX Requirements
Hardware Requirements
-- 486 processor (or higher)
-- 16 MB of RAM
-- 2 MB of hard disk space
Software Requirements
-- For VisualAge for Basic Stored Procedure VBX:
-- Microsoft Windows Version 3.1
-- Microsoft Visual Basic** Version 3.0
-- For VisualAge for Basic Stored Procedure OCX:
-- Microsoft Windows NT Version 3.51 or Windows 95
-- Microsoft Visual Basic Version 4.0
-- DB2 SDK for Windows Version 2.1 or later, using
either NetBIOS or TCP/IP communications. For
information on DB2 communications requirements, see:
http://www.software.ibm.com/data/db2/db2v2.html
-- If your Windows NT or Windows 95 client will connect to
an AIX server, and you plan to use the VisualAge for
Basic Remote Debugger to debug stored procedures and
user-defined functions on the AIX server from your
client, then you need to install a PC X-Server product.
============================================================
OS/2 Server Requirements
Hardware Requirements
-- 486 processor (or higher)
-- 24 MB of RAM
-- 12 MB of hard disk space
Software Requirements
-- OS/2 Version 2.0, 2.11, 3.0, or 4.0 (Version 2.0 must
include CSD 6055 or later)
-- DB2 for OS/2 Version 2.1 or later, using either NetBIOS
or TCP/IP communications. For information on DB2
communications requirements, see:
http://www.software.ibm.com/data/db2/db2v2.html
============================================================
Windows NT Server Requirements
Hardware Requirements
-- 486 processor (or higher)
-- 24 MB of RAM
-- 12 MB of hard disk space
Software Requirements
-- Microsoft Windows NT Version 3.51 or 4.0
-- DB2 for Windows NT Version 2.1 or later, using either
NetBIOS or TCP/IP communications. For information on
DB2 communications requirements, see:
http://www.software.ibm.com/data/db2/db2v2.html
============================================================
AIX Server Requirements
Hardware Requirements
-- 530 RISC processor (or higher)
-- 64 MB of RAM
-- 38 MB of hard disk space
Software Requirements
-- AIX Version 3.25 or 4.15
-- DB2 for AIX Version 2.1 or later, using TCP/IP
communications. For information on DB2 communications
requirements, see:
http://www.software.ibm.com/data/db2/db2v2.html
============================================================
Communication Controls Software Requirements
If you plan to use any the five VisualAge for Basic communi-
cation controls (APPC, Async, EHLLAPI, NetBIOS, or TCP/IP)
with VisualAge for Basic client, you need to install the
software listed below under the relevant communication
control and operating system. You also need to install the
SOM toolkit, which you can do by selecting the SOM toolkit
feature when you install VisualAge for Basic client.
APPC Communication Control Requirements
-- OS/2 Client: Communications Manager for OS/2
Version 1.1
-- Windows NT or Windows 95 Client: For SNA Server
Clients, connection to Windows NT Server Version 3.51
with Microsoft SNA Server Version 2.11
Async Communication Control Requirements
-- No additional software required
EHLLAPI Communication Control Requirements
-- OS/2 Client: Either Communications Manager/2 Version
1.1, or Personal Communications AS/400 and 3270
Version 4.0 for OS/2
-- Windows NT or Windows 95 Client: Personal Communica-
tions AS/400 and 3270 Version 4.1 for Windows 95
NetBIOS Communication Control Requirements
-- OS/2 Warp Client: NetBIOS, plus either OS/2 LAN
Server/Requester Version 4, or OS/2 Warp Server Version
4 Warp Connect
-- Windows NT or Windows 95 Client: No additional software
required
TCP/IP Communication Control Requirements
-- OS/2 Warp Client: TCP/IP Version 2.0 for OS/2
-- Warp Connect Client: TCP/IP Version 3.0 (shipped with
Warp Connect)
-- Windows NT or Windows 95 Client: No additional software
required