home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
vabasi11.zip
/
IP21153O.DOC
< prev
next >
Wrap
Text File
|
1997-08-29
|
150KB
|
4,174 lines
========================================================================
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
README File
========================================================================
Licensed Materials -- Property of IBM.
IMPORTANT: The license for this version of IBM VisualAge for
Basic starts just after the table of contents below. If you are
installing this product, please page down and read the license. If you
agree to the terms of the license, signify your agreement by continuing
with the installation. If you do not agree to the terms of the license,
then you have to cancel the install. For other translations of this
license agreement, please look in the \VABASIC\LICENSE subdirectory.
For a description of known product defects and restrictions, please
read the VERSION1.TXT file located in the \VABASIC directory.
========================================================================
Table of Contents
1. License Agreement
2. About Product Support
3. Installation Information
4. Guide to VisualAge for Basic Documentation
5. Description of Functions Supported in this Version
6. Copyright Notice and Trademarks for this README File
========================================================================
1. INTERNATIONAL PROGRAM LICENSE AGREEMENT
__________________________________________
Part 1 - General Terms
______________________
PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM. IBM WILL
ONLY LICENSE THE PROGRAM TO YOU IF YOU FIRST ACCEPT THE TERMS OF THIS
AGREEMENT BY USING THE PROGRAM. IF YOU DO NOT AGREE TO THE TERMS OF
THIS AGREEMENT, PROMPTLY NOTIFY THE PROVIDER OF THE PROGRAM AND
REQUEST A REFUND OF THE AMOUNT YOU PAID.
The Program is owned by International Business Machines Corporation or
one of its subsidiaries (IBM) or an IBM supplier, and is copyrighted
and licensed, not sold.
IBM grants you a nonexclusive license for the Program. If IBM grants
you multiple licenses for the Program, the terms of this Agreement apply
to each license. The term "Program" means the original program and all
whole or partial copies of it, including portions merged into other
programs. A Program consists of machine-readable instructions,
audio/visual content (such as images, text, recordings, or pictures),
and related licensed materials. THIS AGREEMENT INCLUDES PART 1 -
GENERAL TERMS AND PART 2 - COUNTRY UNIQUE TERMS. THE TERMS OF PART 2
MAY REPLACE OR MODIFY THOSE OF PART 1. "LICENSE INFORMATION," WHICH IBM
PROVIDES FOR THE PROGRAM, MAY CONTAIN ADDITIONAL TERMS REGARDING THE
PROGRAM. ANY SUCH ADDITIONAL TERMS ARE PART OF THIS AGREEMENT.
1.License
_________
USE OF THE PROGRAM
You may use the Program on only one machine at any one time, except as
otherwise stated in this section. You agree to ensure that anyone who
uses the Program (accessed either locally or remotely) does so only for
your authorized use and complies with the terms of this Agreement.
A Program is considered to be in use when it resides in memory or is
otherwise stored on a machine. A Program stored on a network server
solely for the purpose of being distributed to other machines is not
considered to be in use.
IBM specifies charges for Programs based on how much you use a Program
(for example, the number of users), resources (for example, processor
size), or a combination of both.
For a Program managed by a license management tool, copies may be made
and stored on machines under control of that tool, but your use may not
exceed the total number of users or amount of resource authorized.
Certain Programs IBM designates for home or travel use may be stored on
the primary and another machine, provided the Program is not in active
use on both machines at the same time.
You may 1) copy the Program for backup and 2) merge the Program into
another program. You must reproduce the copyright notice and any other
legend of ownership on each copy, or partial copy, of the Program. You
may use any portion of the Program IBM marks restricted (for example,
"Restricted Materials of IBM") only to 1) resolve problems related to
the use of the Program and 2) modify the Program so that it will work
together with other products.
You may not: 1) use, copy, merge, or transfer the Program except as
provided in this Agreement; 2) reverse assemble, reverse compile, or
otherwise translate the Program except as specifically permitted by law
without the possibility of contractual waiver; or 3) sublicense, rent or
lease the Program.
TRANSFER OF RIGHTS AND OBLIGATIONS
You may transfer all your rights and obligations under a license for a
Program to another party, unless IBM specifies otherwise in its
License Information.
To transfer such rights and obligations, you must transfer a copy of
this Agreement, the License Information, all other documentation
(including proof of entitlement), and at least one complete, unaltered
copy of the Program to the other party. Your license is then
terminated.
A Program which IBM licenses in multiples of two or more (for example,
as a pack) may only be transferred in its entirety. In this case,
individual licenses may not be transferred.
2. CHARGES, PAYMENT, AND TAXES
______________________________
Payment must be made to the party (either IBM or its reseller) from whom
you acquired the Program. If you acquired the Program from IBM, you
agree to pay as IBM specifies. If any authority imposes a duty, tax,
levy or fee (excluding those based on IBM's net income) on the Program
supplied by IBM under this Agreement, you agree to pay that amount as
IBM specifies or supply appropriate exemption documentation.
You agree to notify IBM or its reseller and pay any applicable charges
if you change the number of users or amount of resource authorized. IBM
does not give refunds or credits for charges already due or paid.
3. LIMITED WARRANTY
___________________
For certain Programs IBM warrants that when they are used in the
specified operating environment they will conform to their spec-
ifications. IBM does not warrant uninterrupted or error-free
operation of a Program. The warranty period for a Program expires when
its Program services are no longer available. IBM will specify in its
License Information if a Program is warranted or not warranted.
During the warranty period warranty service is provided, without charge,
through defect-related Program services. Program services are
available for at least one year following a Program's general
availability. Therefore, the duration of warranty service depends on
when you obtain your license. If a Program does not function as
warranted during the first year after you obtain your license and IBM is
unable to make it do so, you may return the Program to the party (either
IBM or its reseller) from whom you acquired it and your money will be
refunded. To be eligible, you must have acquired the Program while
Program services (regardless of the remaining duration) were available
for it.
THESE WARRANTIES REPLACE ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR
CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
These warranties give you specific legal rights, and you may also have
other rights which vary from jurisdiction to jurisdiction. Some
jurisdictions do not allow the exclusion or limitation of implied
warranties, so the above exclusion or limitation may not apply to you.
In that event such warranties are limited in duration to the warranty
period. No warranties apply after that period.
4. PROGRAM SERVICES
___________________
Defect-related Program services are provided for warranted Programs and
for selected other Programs. If your reported problem can be reproduced
in the specified operating environment, defect correction information, a
restriction or a bypass will be issued. Program services are provided
only for the unmodified portion of a current release of a Program.
Information regarding how you may obtain Program services will be
provided by the party (either IBM or its reseller) from whom you
acquired the Program. The duration of Program services is specified in
the License Information.
5. PATENTS AND COPYRIGHTS
_________________________
If a third party claims that a Program IBM provides to you infringes
that party's patent or copyright, IBM will, at its expense, defend you
against that claim and pay all costs, damages, and attorney's fees that
a court finally awards, provided that you 1) promptly notify IBM in
writing of the claim and 2) allow IBM to control, and cooperate with
IBM in, the defense and any related settlement negotiations. If such a
claim is made or appears likely to be made, you agree to permit IBM to
enable you to continue to use the Program, or to modify it, or replace
it with one that is at least functionally equivalent. If IBM determines
that none of these alternatives is reasonably available, you agree to
return the Program to IBM on IBM's written request. IBM will then give
you a credit for a one-time charge Program, provided its total charges
have been fully paid. This is IBM's entire obligation to you regarding
any claim of infringement. IBM has no obligation regarding any claim
based on any of the following: 1) your modification of a Program; 2)
the combination, operation, or use of a Program with any programs, data,
or apparatus that IBM did not provide; or 3) infringement by a non-IBM
Program.
6. LIMITATION OF LIABILITY
__________________________
Regardless of the basis on which you may be entitled to recover damages
from IBM, for any claim (including fundamental breach, negligence,
misrepresentation or other tort), IBM's liability will only be for 1)
payments referred to in the patents and copyrights terms described
above; 2) bodily injury (including death), and damage to real property
and tangible personal property; and 3) the amount of any other actual
direct damages or loss, up to the greater of the equivalent of U.S.
$100,000 in your local currency or IBM's then generally available
license charge for the Program.
IBM WILL NOT BE LIABLE FOR ANY SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES
OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR
SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSI-
BILITY OF SUCH DAMAGES. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE
LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.
IBM will not be liable for 1) loss of, or damage to, your records or
data or 2) any damages claimed by you based on any third party claim.
This limitation of liability also applies to any developer of a Program
supplied to IBM. It is the maximum for which we are collectively
responsible.
7. GENERAL
__________
You may terminate your license at any time. If you do so, all your
license rights to the Program are terminated. You may keep a copy of
the Program in your archives. IBM may terminate your license if you
fail to comply with the terms of this Agreement. If IBM does so, all
your license rights to the Program are terminated and you must destroy
all your copies of it.
You agree to comply with all applicable export laws and regulations.
Neither party may bring a legal action under this Agreement more than
two years after the cause of action arose.
This Agreement is governed by the laws of the country in which you
acquired the Program.
This Agreement is governed by the laws of the State of New York.
After downloading the Software, you can view or print a copy of this
License, along with the complete Copyright Notices for IBM
VisualAge for Basic, in the file NOTICES.TXT in the directory where you
installed the Software.
END OF LICENSE AGREEMENT
========================================================================
2. ABOUT PRODUCT SUPPORT
For the latest information concerning IBM VisualAge for Basic, please
consult our Web Page:
http://www.software.ibm.com/ad/vabasic/vabasic.htm
========================================================================
3. INSTALLATION INFORMATION
For information on how to install VisualAge for Basic, including
prerequisite and configuration information, see the file INSTALL.TXT.
Installation information is also located in the "VisualAge for Basic
Getting Started" hardcopy and softcopy books.
INSTALLING VISUALAGE FOR BASIC CLIENT AND SERVER ON THE SAME MACHINE:
For users planning to install both the VisualAge for Basic Client and
the VisualAge for Basic Server on a single OS/2 machine, you must install
both programs in the same directory.
For users planning to install VisualAge for Basic Client or Server on
OS/2, and the machine has DB2/2 Server installed, stop the database
manager (type 'db2stop' at any OS/2 command prompt) before installing
VisualAge for Basic.
========================================================================
4. GUIDE TO VISUALAGE FOR BASIC DOCUMENTATION
------------------------------------------------------------------------
4.A. Summary of VisualAge for Basic Documentation
VisualAge for Basic documentation includes online help, online books,
and separately orderable hardcopy books. To order any of the hardcopy
publications listed below, call 1-800-879-2755 and select option 1.
VisualAge for Basic also ships printable PostScript files of some books,
which are located in the \BOOKS directory on the CD-ROM. These files
are not copied onto your machine during the installation.
VisualAge for Basic Online Help
-- Provides comprehensive, task-oriented information to help you use
the VisualAge for Basic graphical user interface to create GUI
applications, DB2 stored procedures, and DB2 user-defined functions.
-- Provides detailed descriptions of all VisualAge for Basic language
elements, including all components, events, functions, methods,
objects, properties, and statements.
Online Books:
VisualAge for Basic Getting Started
-- Tells you how to install and start using VisualAge for Basic.
Includes a quick tour and five tutorials.
Document number: GC26-8926-00
Softcopy format: \help\getstart.inf
Printable format:
\books\getstrt1.ps - Installation, Quick tour, First tutorial
\books\getstrt2.ps - Four tutorials, Glossary
VisualAge for Basic Programming Guide
-- Tells you how to use the VisualAge for Basic visual development
environment to develop GUI applications.
Document number: SC26-8833-00
Softcopy format: \help\proguide.inf
Printable format:
\books\proguid1.ps -
Part 1 Working with VisualAge for Basic Tools
\books\proguid2.ps -
Part 2 Writing Code
Part 3 Integrating with External Systems (thru Chapter 19)
\books\proguid3.ps -
Part 3 Integrating with External Systems (Chapters 20, 21)
Part 4 Advanced Techniques
Appendixes
Glossary
VisualAge for Basic Language Reference
-- Provides detailed descriptions of all VisualAge for Basic language
elements, including all components, events, functions, methods,
objects, properties, and statements, in A to Z order.
Document number: SC26-8693-00
Online help format: Select Help=>Language Reference
Printable format:
\books\lrfront.ps -
Front matter, Data Types, Operators,
Constructors, Reserved Words
\books\lrah.ps -
Language elements A thru H
\books\lrip.ps -
Language elements I thru P
\books\lrqz.ps -
Language elements Q thru Z
\books\lrerror.ps -
Error messages
\books\lrcomm.ps -
Communication components and related elements
\books\lrback.ps -
Glossary, Index
VisualAge for Basic Data Access Guide
-- Tells you how to access data from VisualAge for Basic applications
using embedded SQL and the DB2 CLI and ODBC function call
interfaces.
-- Tells you how to create, build, test, register, call, and manage
DB2 stored procedures and user-defined functions.
Document number: SC26-8692-00
Softcopy format: \help\dataaccg.inf
Printable format: \books\dataaccg.ps
------------------------------------------------------------------------
4.B. Accessing VisualAge for Basic Documentation
To view the VisualAge for Basic online help, install the product,
then from any product window, select the Help menu or press F1.
To view the online books, or the online help for the Stored Procedure OLE
custom control (SP OCX), install the product, then:
-- On OS/2, open the VisualAge for Basic folder, open the
VisualAge Information folder, and double click on
Getting Started, Programming Guide, or Data Access Guide.
-- On Windows NT and Windows 95**, open the VisualAge for Basic folder,
and click on Getting Started, Programming Guide, Data Access Guide,
or SP OCX.
To view the online help for the Stored Procedure VBX, install the
SP VBX component on Windows 3.1, open the VisualAge for Basic group,
and click on SP VBX/OLE.
------------------------------------------------------------------------
4.C. Suggestions for Using the VisualAge for Basic Documentation:
1. For installation information:
-- See the file INSTALL.TXT in the CD-ROM root directory
-- See Getting Started, chapter 1, but note that the install procedure
there for AIX server in the hardcopy version of the book
is incorrect. See the online book or the INSTALL.TXT file for
the correct procedure for AIX server.
2. For an overview and "quick tour" of VisualAge for Basic, see
Getting Started (hardcopy or softcopy), Chapter 2.
3. For step-by-step information for some common and some complex tasks,
see the tutorials in Getting Started.
4. For information on how to use the VisualAge for Basic visual
development environment to develop GUI applications, see
Getting Started, the online task help, or the Programming Guide,
Part 1.
5. For detailed information on VisualAge for Basic language elements, see
the Language Reference online help or the Language Reference book.
6. For information on VisualAge for Basic programming techniques,
see the Programming Guide, Part 2.
7. For information on integrating external object systems,
such as OpenDoc, SOM, and OLE, with your VisualAge for Basic
applications, see Part 3 of the Programming Guide.
8. For information on accessing databases, and on developing, building,
testing, registering, calling, and managing stored procedures
and user-defined functions, see the online task help
and the Data Access Guide.
9. For sample programs, see the \vabasic\samples directory.
README files in this directory and its subdirectories explain how to
use the sample programs.
10. For more information about SOMObjects programming, see the files
\vabasic\help\somguide.inf (SOMObjects User's Guide, document number
SC23-2680-01), and \vabasic\help\somref.inf (SOMObjects Program
Reference, document number SC23-2681-01).
11. For tutorials and samples on using the communication controls, see
the \vabasic\samples\comm subdirectory. Each subdirectory contains
a postscript file that explains the samples provided in that
subdirectory. The postscript files are:
- For APPC support: vabasic\samples\comm\appc\appsampl.ps
- For ASYNC support: vabasic\samples\comm\async\comsampl.ps
- For EHLLAPI support: vabasic\samples\comm\hllapi\hllsampl.ps
- For NETBIOS support: vabasic\samples\comm\netbios\netsampl.ps
- For TCP/IP support: vabasic\samples\comm\tcpip\tcpsampl.ps
========================================================================
5. DESCRIPTION OF FUNCTIONS SUPPORTED IN THIS VERSION
Version 1.1 of VisualAge for Basic contains a number of defect
fixes for errors in the product code, documentation, and samples.
Among the more significant fixes:
OS/2 users can now execute multiple instances of VisualAge for Basic
and/or multiple instances of executables generated by VisualAge for
Basic. This capability existed previously only for Windows users
of VisualAge for Basic.
VisualAge for Basic no longer crashes when double clicking the
System Menu of the Code Editor on OS/2.
Corrections to the "VisualAge for Basic Getting Started" book and
other books have been added.
Crashes when using an Editable Grid have been fixed.
Memory leaks in the string manipulation functions have been fixed.
Crashes building or running DB2 stored procedures have been fixed.
Errors displaying/processing special or DBCS characters have been
fixed.
------------------------------------------------------------------------
General Scenarios Supported:
-- Create client GUI applications that run on OS/2, Windows NT, and/or
Windows 95.
-- Integrate third-party visual and non-visual objects and controls
developed in C++, SOM, OLE, and OpenDoc into client applications.
-- Define, create, and manipulate objects in Basic using Object
Oriented extensions to the Basic language.
-- Migrate applications written in Microsoft Visual Basic 3.0 into
VisualAge for Basic.
-- Edit server procedures locally, and build and debug server
procedures locally and remotely.
-- Browse stored procedures in the DB2CLI.PROCEDURES catalog, and
browse user-defined functions in the DB2 catalog.
-- Invoke server procedures from a VisualAge for Basic client and
from other clients.
Definition: "server procedures" is used as a general term that includes
stored procedures and user-defined functions.
------------------------------------------------------------------------
Platforms Supported:
Client platforms: OS/2, Windows NT, Windows 95
Server platforms: AIX, OS/2, Windows NT
------------------------------------------------------------------------
Language Supported:
The complete VisualAge for Basic language is described in the VisualAge
for Basic online help. See the file \VABASIC\VERSION1.TXT for a
list of known defects and restrictions in this version.
------------------------------------------------------------------------
Functions Supported:
Project:
-- Creating a new project
-- Opening an existing project
-- Saving the project and changing the project name via Save as
-- Running the Project
-- Viewing the project: Forms, Modules, Build files, Components, etc.
-- Showing a file in full path or just the name
-- Loading projects written in Microsoft Visual Basic 3.0, modifying
them, and saving them in Visual Age for Basic format
-- Building server procedures (creation/deletion)
-- Generating an executable (.EXE) version of the project.
-- Accessing database information in ODBC data sources using a
Data component and/or Data Access classes.
-- Accessing database information in DB2 using Embedded SQL statements
or CLI calls.
Forms:
-- Selection and appropriate menu and icon state
-- Opening the Code Editor, Property Editor and Menu Editor
via menu item, mouse, keyboard
-- Showing or hiding design version of selected form
-- Saving in a file (.i), and changing name of file via Save As
Modules:
-- Selection and appropriate menu and icon state
-- Opening Code Editor on it via menu item, mouse, keyboard
-- Saving in a file (.bas), and changing name of file via Save As
-- Creating/removing a Module
Window Pulldown:
-- Property Editor
-- Toolbox
-- Menu Editor
-- Code Editor
-- Color selector
-- Component catalog
-- Stored procedure catalog
-- User-defined function catalog
Options Pulldown:
-- Interpreter
-- Project
-- Environment
-- Database
------------------------------------------------------------------------
Components shipped in this version:
Checkbox
Combo Box
Command Button
Common Dialog
Directory List Box
Drive List Box
File List Box
Frame
Grid
Horizontal Scrollbar
Image
Label
Line
Listbox
OLE Container (Windows NT and Windows 95 only)
OpenDoc Container (OS/2 only)
Option Button
Picture Box
Shape
Textbox
Timer
Vertical Scrollbar
========================================================================
6. COPYRIGHT NOTICE AND TRADEMARKS FOR THIS README FILE
(C) Copyright International Business Machines Corporation 1997.
All Rights Reserved.
AIX, DB2, DB2/2, DB2/6000, IBM, and OS/2 are trademarks of International
Business Machines Corporation.
Microsoft, Windows, and the Windows 95 logo are trademarks or registered
trademarks of Microsoft Corporation.
Other company, product, and service names, which may be denoted by a
double asterisk (**), may be trademarks or service marks of others.
========================================================================
##################################################========================================================================
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1 (June 1997)
========================================================================
DESCRIPTION OF KNOWN DEFECTS AND RESTRICTIONS IN THIS VERSION
The known defects and restrictions are grouped in the following
categories:
A. Building server procedures
B. Calling server procedures
C. Database access
D. Language elements
E. Miscellaneous
F. Run-time problems
G. User Interface
H. Communications Components
I. Country-specific information
------------------------------------------------------------------------
A. Building Server Procedures
------------------------------------------------------------------------
------------------------------------------------------------------------
A.1. Building Server Procedures: Replacing a server procedure on a DB2
server
During server procedure development, set the database manager
configuration using KEEPDARI=NO, so that DB2 will unload server
procedures after each call. (DB2 loads a server procedure into memory
when it runs, and may not unload it from memory to let you replace it.)
For execution, set KEEPDARI=YES to give better performance, so that the
server procedures do not need to be reloaded each time they are run.
With KEEPDARI=YES, the following message may appear: "Stored Procedure
DLL cannot be created because it is in use." This will happen if you
are trying to rebuild a server procedure which has already been run by
DB2. Stopping and restarting DB2 will free the server procedure from
memory, allowing you to rebuild it.
------------------------------------------------------------------------
A.2. Building Server Procedures: Running a server procedure on a DB2
server in UNFENCED mode
Do not run a server procedure built using VisualAge for Basic on DB2
in UNFENCED mode. For this version, run server procedures in FENCED
mode.
------------------------------------------------------------------------
A.3. Building Server Procedures: Building the UNITS UDF sample
Before building the UDF in vabasic\samples\udf\units\unitudf.prj,
edit the assignment statement of the global variable Path to use the
path (with a trailing "\" or "/") of the location of the UDF built on
the database server.
To run the units user-defined function on an AIX server, copy
only the units.dat file to the AIX server. Numbers in a
units.rec file generated on OS/2 or Windows will not be in the
correct binary format for AIX. The units.dat file, however, is
entirely in ASCII format.
For additional details about this and other UDF samples, browse the
README.UDF file in vabasic\samples\udf.
------------------------------------------------------------------------
B. Calling Server Procedures
------------------------------------------------------------------------
-------------------------------------------------------------------------
B.1. Calling Server Procedures: Calling more than 5 stored procedures
In DB2 for OS/2, Version 2.1.0, no more than 5 different stored
procedures can be invoked by one application. The sixth and subsequent
calls to different stored procedures receive SQL error code 1131. This
restriction is removed in DB2 for OS/2, Version 2.1.1 or later.
In DB2 for OS/2, Version 2.1.0 and later, an application can call the
same stored procedure as many times as system resources permit.
------------------------------------------------------------------------
B.2. Calling Server Procedures: Matching levels of CLI
When calling a stored procedure using CLI, make sure the levels of CLI
support on the client and server machines are the same, especially if the
client and server are on different operating systems.
------------------------------------------------------------------------
B.3. Calling Server Procedures: Calling from a generated executable
For OS/2, when a stored procedure is invoked from a generated executable,
Visual Age for Basic will display the following message when running
the executable:
"Priority cannot be set for the current thread".
This message can be suppressed by setting an environment variable
as follows:
set VWSPSETPRTY=NO
This environment setting should be made by each OS/2 client running the
generated executable.
------------------------------------------------------------------------
B.4. Calling Server Procedures: For UDFs with VARCHAR input or result
arguments
A DB2 UDF VARCHAR parameter should be declared as Basic data type
"string", not as a sqlvarchar structure. The result should be
NULL terminated ( & with chr$(0) before return). However, there have
been problems reported for VARCHAR result parameters when the client and
the server are on different platforms.
------------------------------------------------------------------------
B.5. Calling Server Procedures: Passing string arguments to a stored
procedure using SP OCX
The SP OCX pads a string argument with nulls to a length of 256,
whether the string is fixed or varying length. It also truncates
any input string at 255 (adding either a null or garbage to make
a length of 256), and any output string at 256. The stored
procedure, which declares the parameter as a varying-length
string, can test for the first null with the InStr function and
use the Left$ or Mid$ function to obtain the original string:
original_string = Left$(input_string, 1, InStr(input_string, Chr$(0)))
------------------------------------------------------------------------
B.6. Calling Server Procedures: Debugging server procedures when
client has an open cursor
If a client procedure has an open SQL cursor and calls a
server procedure which (a) contains embedded SQL and (b) has been
built with remote debug enabled, then subsequent processing with
the cursor fails since DB2 will have closed the cursor. To bypass
the problem, debug the procedures locally before making them server
procedures, and then build them with remote debug disabled.
------------------------------------------------------------------------
B.7. Calling Server Procedures: Bad characters in AIX server messages
When doing a remote debug of a server procedure running on an AIX server,
there may be times when messages in the debugger contain bad characters.
If messages contain bad characters, then the AIX server may be using
a different language locale than the X Windows system displaying the
debugger. Make sure the locale setting of the debugger client and
server are the same language.
If a user wants to check the contents of the message in English, then
change the LANG setting in the file CONFIG.VW located on the AIX server
in $HOME/$SQLLIBDIR:
LANG=En_US
------------------------------------------------------------------------
C. Database Access
------------------------------------------------------------------------
------------------------------------------------------------------------
C.1. Database Access: CLI SQLProcedures function
The CLI SQLProcedures function cannot be used to access information from
the DB2CLI.PROCEDURES table that VisualAge for Basic has inserted.
Attempting this results in a CLI0166E PARMLIST syntax error, because
the VisualAge for Basic parameter descriptions currently use Basic
datatypes, which are not supported by CLI. You can use the CLI procs
sample to access only information that respects the restrictions
documented in the DB2 for OS/2 CLI Guide and Reference, Appendix G.
See the vabasic\samples\cli\procx.prj sample for how to bypass this
restriction.
------------------------------------------------------------------------
C.2. Database Access: DB2 not started or CONNECT RESET missing
If a message appears in the Code Window saying "DB2 is not started or a
CONNECT RESET statement is missing," and you have verified that DB2 is
started and you have appropriate CONNECT RESET statements in place, exit
VisualAge for Basic and then start it again.
If the problem persists, then one reason may be that the DB2 server
being accessed has the configuration setting AUTHENTICATION set to
SERVER. To determine this setting, issue the command
db2 get dbm cfg | more
from a DB2 Command Line window on the DB2 Server.
To avoid such connection errors, use the Options -> Database -> Set
database logon information menuitem in the Project Window of VisualAge
for Basic with DB2 Support to enter an userid and password that is
authorized to the DB2 server.
------------------------------------------------------------------------
C.3. Database Access: DB2 Patches and the Data Component
If you are planning to develop and/or run a VisualAge for Basic
application that uses the Data Component and/or Data Access classes to
access a DB2 database, then each client needs to have several DB2 patches
configured. These patches need to be configured on every client
workstation, and for each DB2 database alias defined on a client
workstation. NOTE: these steps are necessary for Windows 95 and
Windows NT users of VisualAge for Basic who accessing a DB2 Version 2.x
Server or users on Windows 95 and Windows NT who have a DB2 Version 2.x
Software Developer's Kit installed. Users with DB2 Version 5 Server
and/or Software Developer's Kit installed are not affected.
1. In the "DB2 for Windows 95" or "DB2 for Windows NT" menu/folder,
locate the "DB2 CLI/ODBC Administrator" and run it. If you do not
have this item, then your level of the DB2 SDK may not contain these
patches.
2. Select a DB2 Alias and, if not done already, click the "Add as ODBC"
button.
3. The selected alias should now also appear in the "ODBC Data Source
Name" column.
4. Click the "Configure" button.
5. A message may appear asking whether to connect to the DB2 Alias.
click the "Yes" button.
6. A logon screen may appear. Enter a userid and password authorized
to the database and click "Ok".
7. A message "Connect completed successfully" may appear. Click "Ok".
8. A "ODBC Data Source Configuration" notebook appears. In the lower
right portion of this notebook, Click the tab labeled with two
downward pointing arrows. This scrolls the visible notebook tabs
down by one tab.
9. The tab "Patches" should now appear along the right side of the
notebook. Click this tab.
10. The "PATCH1:" notebook page appears, listing a number of available
patches provided by DB2. See section 9.2.2 of the DB2 SDK
README.TXT file for detailed descriptions of these patches.
11. Select the following patches. The cumulative total displayed for
PATCH1 should be 1485:
- Map COUNT(colname) to COUNT(*)
- Map timestamp values to date values
- Map timestamp values to time values
- Null terminate DBCS strings
- Permit MS Access, Visual Basic handshake
- Return primary key ahead of unique index
- MS Visual Basic fix for empty searched update/delete
12. Click "OK".
13. Message "Save changes to the DB2CLI.INI file?" appears. Click "OK".
14. Double click in upper left corner of notebook to close the notebook.
15. Click the "Exit" button to end the DB2 CLI/ODBC Administrator.
------------------------------------------------------------------------
C.4. Database Access: Can't Load xxODBCxx.DLL Error Message
On Windows NT and Windows 95, if you get the error message "Can't load
xxODBCxx.DLL" whenever starting VisualAge for Basic, then this indicates
that you do not have an ODBC driver installed. If you are planning on
using the Data Component and/or Data Access classes, then you need to
install the ODBC driver shipped with the database management system you
will be accessing. If you are not planning to do database access using
ODBC, then you can suppress this error message by renaming the file
\VABASIC\BIN\VWODBC.DLL (Ex., VWODBC.BLL).
------------------------------------------------------------------------
C.5. Database Access: Starting ODBCADM.EXE on OS/2
When running the ODBC driver manager (ODBCADM.EXE) from an OS/2 command
window, use the start command (i.e., 'start odbcadm'). This will create
a separate session that may be closed after exiting the driver manager.
------------------------------------------------------------------------
C.6. Database Access: Resizing sample dialogs
In many Embedded SQL and CLI samples in the \VABASIC\SAMPLES\EMBED and
\VABASIC\SAMPLES\CLI subdirectories, there are small secondary dialogs
that appear asking for input like the database alias, logon userid, or
logon password. The dialogs have OK and Cancel buttons, but they do not
appear until one has resized the dialog. Resizing in any direction will
display the buttons.
------------------------------------------------------------------------
C.7. Database Access: The Data Component and DB2 Support
The Data Component is not working on the Windows version of VisualAge
for Basic with DB2 Support. The component works correctly on VisualAge
for Basic (i.e., without DB2 Support). To access DB2 databases, an
application can use the Data Component and Data Access classes in
VisualAge for Basic, or the application can use embedded SQL and/or CLI
in VisualAge for Basic with DB2 Support.
------------------------------------------------------------------------
D. Language Elements
------------------------------------------------------------------------
------------------------------------------------------------------------
D.1. Language Elements: PrintForm method
The PrintForm method on a form is not implemented.
Details: The printer does not behave as expected when the following code
is entered in the Form_Click method:
printer.print "This may never print"
printer.enddoc
In addition, there should be an implicit Printer.EndDoc when the
application has finished executing (providing it has printed something).
Workaround: save the form to a file and print it from there.
------------------------------------------------------------------------
D.2. Language Elements: Title Property - not working in a generated
executable.
On all platforms the Title property does not work properly when
set in a generated executable.
------------------------------------------------------------------------
D.3. Language Elements: String DataType byte size
The description of the Byte Size for a String datatype. as described in
the DataType appendix of the Language Reference, is incorrect. The
correct description is below:
Byte Size
English International(Multibyte)
Win32 VariantString Unicode Unicode
2 bytes/char. 2bytes/character
String Type 1 byte/char. Multibyte per character
OS/2, AIX 1 byte/char. Multibyte per character
to a max of 2 billion.
------------------------------------------------------------------------
E. Miscellaneous
------------------------------------------------------------------------
------------------------------------------------------------------------
E.1. Miscellaneous: Creating a SOM object on a form
When you create a SOM object on a form, VisualAge for Basic may crash.
Details: when you select a SOM class from the Component Catalog, and use the
Toolbox to create a SOM object on a form, VisualAge for Basic may crash.
SOM objects that may cause this error include: AttributeDef, ConstantDef,
Contained, ExceptionDef, InterfaceDef, ModuleDef, OperationDef,
ParameterDef, SOMDClientProxy, SOMMSingleInstance, and TypeDef.
Actions that may cause this error include:
-- Selecting the object on the form and clicking on the Delete key.
-- Going to the File menu and selecting New Project
-- Going to Project Window Run Menu and clicking on Run, then on End
------------------------------------------------------------------------
E.2. Miscellaneous: Renaming DLLs for Microsoft Visual Basic 4.0
If you plan to use both Microsoft Visual Basic 4.0 and IBM VisualAge for
Basic client, you will need to rename the following DLLs located in the
vabasic\bin directory to a backup name (for example, by replacing the
DLL extension with BLL):
CTL3D32.DLL MSVCR40.DLL
MFC40.DLL MSVCRT40.DLL
MFCO40.DLL OLEPRO32.DLL
------------------------------------------------------------------------
E.3. Miscellaneous: The Two-Dimensional Graphics Part
The Two-Dimensional Graphics Part (shipped with the OpenDoc
runtime), will crash VisualAge for Basic if the "link" pages
are selected from the OpenDoc Properties notebook. The link
pages are not active, so this is not a functional problem.
------------------------------------------------------------------------
E.4. Miscellaneous: The OpenDoc Cookbook part
The OpenDoc Cookbook part is not recommended for use in
VisualAge for Basic at this time.
------------------------------------------------------------------------
E.5. Miscellaneous: The OpenDoc MultiMedia parts
The OpenDoc MultiMedia parts (shipped with the Developer's
Connection) work best if they are first contained within
other container parts. For example, instead of using the
Video Part as the root part of an OpenDoc document, use a
container part as the root and embed the Video Part in it
(example container parts include the Page Layout and Text
Parts shipped with the OpenDoc runtime or the Container Part
shipped with the Warp Toolkit). This is also a useful tip for
other OpenDoc parts that do not behave as expected.
------------------------------------------------------------------------
E.6. Miscellaneous: Generating executables from projects building
Stored Procedures and/or User-Defined Functions
If a project that calls a stored procedure or user-defined function is
also the project that builds them, then there will be error messages
when building and/or executing the project as a generated executable.
The following workaround can be used to build an executable client
application:
1) Start VisualAge for Basic and load the project.
2) Run the application.
3) Stop the application.
4) In the project window, remove any files in the Stored Procedure
or User-Defined Function categories (do NOT save the project).
5) Build an executable file.
6) Exit VisualAge for Basic (do NOT save the project), and run the
generated executable.
------------------------------------------------------------------------
E.7. Miscellaneous: Font Migration
If a font name specified in a VisualAge for Basic application is not
installed on the machine loading or running the application, then the
font will be changed to the default font of the operating system (for
example, System font for Windows NT, System Proportional font for OS/2).
One side effect of this behavior is that invalid font names are not
flagged as errors in the Property Editor or the Code Editor.
------------------------------------------------------------------------
E.8. Miscellaneous: VBX/OCX Migration
Users of Microsoft Visual Basic 3.0 and VBX controls may be able to
migrate their applications into VisualAge for Basic and use the
equivalent OCX. Follow these steps:
1. Save any .FRM files as text files (not binary files) in Microsoft
Visual Basic 3.0.
2. Start VisualAge for Basic for Windows NT
3. In the Project window, select Window ==> Component Catalog.
4. Select the OLE components to be used in the application. As a
component is selected, any applicable icons will be placed in the
ToolBox window.
5. Using a text editor (NotePad, for example), inspect the .FRM files
for the Begin... End sections describing VBX instances. Remove this
section from the form (Save a backup of this form prior to such an
operation). Do NOT remove event logic (ex., vbxname1_click()) from
the form.
6. Save any modified files.
7. Remove the Form1 loaded by VisualAge for Basic from the untitled
project choosing Selected ==> Remove in the Project Window.
8. In the Project Window, select File ==> Add File to load individually
each file of the application, including the modified forms.
9. Choose Selected ==> Show Form to view each form in Design Mode.
Using the ToolBox, add in an OCX instance for each VBX instance
removed from the form(s), giving each the same Name as each VBX
instance had in Visual Basic 3.0. This will preserve the event
logic.
10. Choose File ==> Save Project As to create a .PRJ file that can be
used to load the converted project into VisualAge for Basic. Save
each modified form as a .I formatted file.
------------------------------------------------------------------------
E.9. Miscellaneous: TrueType Fonts
If you are finding text displayed in VisualAge for Basic is just some
garbled graphic characters, then your computer may have a setting
restricting fonts to only TrueType fonts. In the Fonts control panel,
there is a setting determining whether to show only TrueType fonts.
To show non-TrueType fonts on Windows 95:
1) Open the My Computer folder.
2) Open the Control Panel folder.
3) Open the Fonts folder.
4) In the menu of the Fonts folder, select the View -> Options menuitem.
5) In the Fonts Notebook, select the TrueType notebook tab.
6) Uncheck the option Show only TrueType fonts in programs on my
computer.
7) Restart the computer.
To show non-TrueType fonts on Windows NT:
1) Open the Main folder.
2) Open the Control Panel folder.
3) Open the Fonts dialog.
4) In the Fonts dialog, click the TrueType button.
5) Uncheck the option Show only TrueType fonts in applications.
6) Close the Fonts dialog
7) You do not need to restart the computer.
------------------------------------------------------------------------
E.10. Miscellaneous: Passing strings from SOM to VisualAge for Basic
Consider the following C function:
static char myStr[] = "hello world";
SOM_Scope string SOMLINK _my_sub()
{
return(myStr);
}
As per the SOM rules, to allow the memory management of SOM and
VisualAge for Basic to work correctly you must copy all return string
parameters as follows:
static char myStr[] = "hello world";
static char *SOMstrdup(const char *str)
{
char *rtrn = SOMMalloc(strlen(str)+1);
strcpy(rtrn, str);
return str;
}
SOM_Scope string SOMLINK _my_sub()
{
return SOMstrdup(myStr);
}
------------------------------------------------------------------------
E.11. Miscellaneous: Running Tutorial #2
To run tutorial #2, start VisualAge for Basic in a command prompt window
from the \vabasic\samples\tutorial\tutor2 subdirectory. This will
allow VisualAge for Basic to find the SOM.IR file containing the
SOMCalculator class.
------------------------------------------------------------------------
E.12. Miscellaneous: SOM object access and SOMBASE environment variable
When using a SOM object with VisualAge for Basic, the SOMBASE environment
variable must be set. Usually, SOMBASE environment variable is set
automatically by installing a product like VisualAge for C++ or SOM
Toolkit. In some cases, the SOM support of VisualAge for Basic is not
setting SOMBASE. If the level of SOM installed by VisualAge for Basic
is your preferred level, make sure SOMBASE is set to the \VABASIC\SOM
directory.
------------------------------------------------------------------------
E.13. Miscellaneous: Product Descriptions During Install on OS/2
When using the Installation program for VisualAge for Basic on OS/2 from
the CD-ROM, there may be an error message after displaying a product
description. There is a restriction in the installation program that
limits one to browsing only one product description in each invocation
of the install program. This error condition does not occur when
copying the install directory onto a hard disk.
The product descriptions are displayed using the Details -> Product
Description menuitem of the Installation and Maintenance window of
the OS/2 VisualAge for Basic installation program. If the message
"EPFIE112: Unable to transfer C:\OS2\SYSTEM\$EPFINST\EPFIDESC.TMP -
the file is in use or locked" appears, exit and restart the install
program.
------------------------------------------------------------------------
E.14. Miscellaneous: Dialog title of OCX "(Custom)" Properties
The Dialog Window title of any OCX "(Custom)" Property is incorrect.
It is always "Editor's Property".
------------------------------------------------------------------------
E.15. Miscellaneous: Drop down list of SP.OCX on Property Editor
The following properties of SP.OCX do not show a "Dropdown list"
on the Property Editor in VisualAge for Basic:
- DatabaseAlias
- DatabasePassword
- DatabaseSPInfo
Workaround: These values must be typed in, or entered using the (Custom)
property dialog.
------------------------------------------------------------------------
E.16 Miscellaneous: Using the Online Books in NT 4.0
Browsing the Online Books (Ex., Getting Started, Programmer's Guide) on
NT 4.0 may result in crashes in the XVIEW utility. One workaround for
use in the English, Italian, or Brazilian translations of these books
is to change the ShortCut for these books to use the IVIEW utility
instead. IVIEW.EXE is found in the \VABASIC\BIN directory. The XVIEW
utility works well on NT 3.5.1 and Windows 95.
------------------------------------------------------------------------
F. Run-Time Problems
------------------------------------------------------------------------
------------------------------------------------------------------------
F.1. Run-Time Problems: Restriction on dynamic array passing
Because DB2 cannot determine the size of a ReDim-ed array during run
time, it can only handle the default value of MAXARRAYSIZE.
On OS/2 and Windows NT clients, if the array being ReDim-ed is larger
than the default value of MAXARRAYSIZE, it will cause a SQL0822N error
("The SQLDA contains a data address or indicator variable address which
is not valid.").
Solution: VisualAge for Basic provides an environment variable called
MAXARRAYSIZE. Its default values are 64KB on AIX, 10KB on OS/2, and
SQLMAXBLOB on Windows. Set this environment variable to be the same or
larger than the array's ReDim-ed size. For example:
/* OS/2 clients: foo.bas module */
subroutine foo()
Dim array1() as integer
Redim array1(10, 2000);
/* End of subroutine foo() */
In this example, the array's ReDim-ed size (10 x 2000 or 20,000) is
larger than the default value of MAXARRAYSIZE on OS/2 (10KB), so you need
to set the MAXARRAYSIZE environment variable to 20,000 or greater.
To improve performance, you can set MAXARRAYSIZE less than the default
value, as long as it is as large or larger than any ReDim-ed arrays in
your program. Here are the maximum sizes for any ReDim-ed arrays in your
program: OS/2 = 27 KB (27,648 bytes), Windows NT and Windows 95 = 32KB
(32,768 bytes).
------------------------------------------------------------------------
F.2. Run-Time Problems: ScaleWidth/ScaleHeight properties
If a program performs a resize in its code (in other words, changes the
value of the Width and/or Height property), VisualAge for Basic does not
update the ScaleWidth and ScaleHeight properties.
If a user manually resizes a form, VisualAge for Basic updates the
ScaleWidth and ScaleHeight properties correctly.
If the ScaleMode is set to a value different than 1 (Twips), then the
ScaleHeight and ScaleWidth values may be incorrect at runtime.
------------------------------------------------------------------------
F.3. Run-Time Problems: Calling external functions
On OS/2, all function calls made to external functions must be made to
DLLs which use the _system linkage convention. DLLs which use the
_optlink system linkage convention are not supported in this version.
------------------------------------------------------------------------
F.4. Run-Time Problems: SOM Interface Repository Performance Enhancement
The SOM toolkit shipped in VisualAge for Basic is Version 2.1.2. If you
have installed SOM 2.1.4 or later, it includes the ability to add
an index to a SOM Interface Repository (SOMIR). Users of SOMIR files
that don't have an index will notice VisualAge for Basic runs an
application slower the first time than in subsequent runs of the
application. Users of SOMIR files that predate Version 2.1.4 can add
indexes to these files by using the IRINDEX utility
(irindex <SOMIR name>). For additional details, please read the README
file for SOM 2.1.4 or later.
For users planning to install SOM 2.1.4 or later, please note that if you
have a previous version installed that does not include the sample
directories, then you will need to create these directories in order
to complete the installation. The 2.1.4 install program will indicate
which directories are needed.
--------------------------------------------------------------------
F.5. Run-Time Problems: Note for String and Variant usage on Windows
NT and Windows 95
The following issues concern the usage of String and Variant datatypes
in VisualAge for Basic for Windows NT and Windows 95:
(1) Difference of internal code
In VisualAge for Basic, the internal code of a String variable
is the PC code (DBCS PC code in DBCS PC environments). On the other
hand, the internal code of Variant variable type is Unicode to
exploit performance advantages in the interaction with 32bit OLE
automation.
This internal code difference typically appears in the result of
byte operational string functions (such as LenB($), LeftB($),
MidB($), RightB($), etc...).
(2) File & display I/O, interaction with DB2 and CLI/ODBC drivers
Regardless the above internal code difference,
both String type and Variant type variables can be used in the
VisualAge for Basic APIs for file I/O, display I/O, and interaction
with database systems where PC code is expected implicitly.
In case of Variant variables, the output data (from VisualAge for
Basic program) is automatically converted to the String type
representation (PC code), and input data is automatically converted
to a receiving Variant data type representation (Unicode).
Programmers just need to care about putting valid data which is not
corrupted in the variables.
(3) String and Variant variables in OLE automation server/container
Regardless the internal code difference, both String and Variant
variables can be used in OLE automation containers and can call both
16bit and 32bit versions of OLE automation servers. VisualAge for
Basic can convert data types to the one expected by an OLE server
automatically (i.e. if a 32bit OLE server expects BSTR,
VisualAge for Basic converts a String type variable to Variant
representation and then passes it to the OLE server. An OLE server
also performs automatic conversion if necessary according to the OLE
server's responsibility.
(4) String/Variant data conversion by VisualAge for Basic
On the Windows NT and Windows 95 platforms, VisualAge for Basic
automatically performs necessary conversions for String and Variant
types. In this conversion process, if there is invalid data in the
source variable, VisualAge for Basic just removes it and the result
may include no data after the conversion.
------------------------------------------------------------------------
G. User Interface
------------------------------------------------------------------------
------------------------------------------------------------------------
G.1. User Interface: Mnemonic characters not working on OS/2
On OS/2, if Fixpack 17 or later has not been applied, the mnemonic
character (i.e., the accelerator key) in the caption of labels and
buttons (check box, option, and command buttons) does not appear
underlined when using certain fonts. This applies to the VisualAge
for Basic user interface as well as applications written in VisualAge
for Basic.
------------------------------------------------------------------------
G.2. User Interface: OS/2 Support
In some areas where system requirements are mentioned, OS/2 support is
described as OS/2 3.0 (Warp). The correct statement for OS/2 support is
OS/2 3.0 (Warp) or later.
------------------------------------------------------------------------
G.3. User Interface: Editing captions in the Menu Editor
The Edit "textbox" that appears in the menu editor over a menuitem when
changing its caption does not move with the menuitem when the menu
editor scrollbar is used. Clicking on another menuitem will reposition
the edit textbox.
------------------------------------------------------------------------
G.4. User Interface: Screen Resolution Migration
If a form in an application written on a machine with one screen
resolution is migrated to a machine with less screen resolution, and
the form's width and/or height now exceeds the screen size, then an error
occurs when displaying the form in design and run modes.
------------------------------------------------------------------------
G.5. User Interface: Alignment Property on OS/2
OS/2 does not support allow text alignment (i.e., right justify, center,
etc.) of its checkbox, option button, and textbox controls. In
VisualAge for Basic for OS/2, the alignment property of these
components is ignored.
------------------------------------------------------------------------
G.6. User Interface: FontSize Property
When browsing the FontSize property in the Property Editor, the same list
of font sizes is displayed for every font, regardless of whether each
size is supported on the current machine. If an unsupported FontSize
is selected, VisualAge for Basic will use the closest supported FontSize.
------------------------------------------------------------------------
G.7. User Interface: Long File Names in the FileListBox component
On Windows95, the FileListBox component does not display any long file
names. Also, it does not display any file names in a long subdirectory
name. This problem does not occur on OS/2 and Windows NT.
------------------------------------------------------------------------
H. Communication Components
------------------------------------------------------------------------
------------------------------------------------------------------------
H.1.1. Communication Components: SOM requirement
All the Communication Components (APPC, ASYNC, HLLAPI, NetBIOS, TCP/IP)
are created with SOM classes, so you need to set up your environment
to make SOM available on OS/2, Windows NT, and Windows 95.
------------------------------------------------------------------------
H.2.1. NetBIOS: No-Wait functions
In this version, NetBIOS does not support No-Wait functions even if you
can find the API names in the ccnetapi.idl.
------------------------------------------------------------------------
H.2.2. NetBIOS: Sequence octet data type
Some APIs use SOM's sequence octet data type, so when you invoke a
method of NetBIOS or NetBiosAPI class you are required to convert the
received/sent data to an appropriate data type.
e.g.,
If the received data can be processed as a string, first you need
to receive the data in a data type that can handle binary data,
then convert to string data type, or something appropriate.
When sending data, you may code as follows:
Dim IntArrayBuf(50) As Integer
Dim testdata As String
Dim netbios As NetBiosAPI
Set netbios = New NetBiosAPI
testdata = "(Client) SEND-Data from SendWait."
For i = 1 to 32
IntArrayBuf(i-1) = Asc(Mid$(testdata, i, 1))
Next i
rc = netbios.SendWait(0, ncb_lsn, IntArrayBuf, 33)
When receiving data, you may code as follows:
Dim receivebuf As String * 512
Dim IntArrayBuf(50) As Integer
Dim netbios As NetBiosAPI
Set netbios = New NetBiosAPI
rc = netbios.ReceiveWait(0, ncb_lsn, IntArrayBuf, ncb_length)
If rc <> 0 Then
'MsgBox "ReceiveWait error RC = " & rc
GoTo EndProcess
Else
For i = 0 to 511
Mid(receivebuf, i+1, 1) = Chr$( IntArrayBuf(i) )
Next i
'MsgBox "ReceiveWait succeeded!"
End If
To know which API uses SOM sequence octet data type, please refer to
ccnetapi.idl or ccnetapv.idl.
------------------------------------------------------------------------
H.3.1. TCP/IP: Sock_init method
For Windows, Sock_init method issues WSAStartup() system call that
assumes the WinSock version is 1.1 on the Windows environments.
------------------------------------------------------------------------
H.3.2. TCP/IP: Sock_errno method
The Sock_errno method returns the error code set by the last issued
socket call. When a socket call has an error, the return value of
the sock_errno() (OS/2) or WSAGetLastError()(Windows) system calls are
stored in an internal variable, and the value is returned when this
method is called. On OS/2, the Sock_errno method also returns the value
of h_errno for gethostbyaddr() and gethostbyname() calls.
------------------------------------------------------------------------
H.3.3. TCP/IP: ConnectTimeOut property
For OS/2, the ConnectTimeOut property does not affect the ConnectStart
method. This means no timeout occurs and the control immediately returns
an error when connection is not established.
------------------------------------------------------------------------
H.3.4. TCP/IP: Naming convention
The method names of TCPIPSockAPI are almost based on the Socket API
function names. But there are some differences between them because
of the differences across operating systems.
OS/2 Windows Method Name
-------------------------------------------------------
ioctl() ioctosocket() Ioctlsocket()
soclose() closesocket() Soclose()
sock_init() WSAStartup()(*1) Sock_Init()
sock_errno()(*2) WSAGetLastError()(*2) Sock_errno()
(*1) Please refer the "Sock_init method" in this file.
(*2) Please refer the "Sock_errno method" in this file.
------------------------------------------------------------------------
H.4.1. ASYNC: Event driven programming (OnComm/SThreshold/RThreshold)
The OnComm event does not work on all platforms. So, even if you
changed the value of SThreshold/RThreshold value, you will not trigger
events. This means that you cannot write an "Event driven"
asynchronous program using CCCOM. Instead, use the polling mechanism
program described in the example/tutorial.
For an error during a binary file transfer, you can get the error status
by getting the value of FxStatus Property.
------------------------------------------------------------------------
H.4.2. ASYNC: AutoPortOpen
If you set the AutoPortOpen property to False and start the project,
CCCOM automatically searches and opens an available serial port, if
possible. After that, if you set the AutoPortOpen to False, the port is
not open when you set the CommPort property. If you set AutoPortOpen
to True, the port will be opened automatically when you change or
set the CommPort property.
------------------------------------------------------------------------
H.4.3. ASYNC: Sample program
In the ASYNC sample program in ...\samples\comm\async, when you
push the "File Receive" or "File Send" buttons, a file transferred
message appears immediately on the TextBox1. But the actual file
transfer is going in a separate thread. You can confirm real transfer
completion by getting the value of FxStatus. If the file transfer is
on going, FxStatus is 4. If it completed, it will be 0.
------------------------------------------------------------------------
H.4.4. ASYNC: Binary file transfer
When using the Binary file transfer functions of CCCOM component:
- In YMODEM and ZMODEM, you can not download more than 1 file at
one time. If you set the Download property to "", only 1 file
will be stored.
- In the ZMODEM protocol, XferFileSize sometimes indicate a size
twice as much as the original size.
- XMODEM is more stable than YMODEM and ZMODEM. ZMODEM also is slower.
The use of XMODEM is strongly recommended.
------------------------------------------------------------------------
H.5.1. HLLAPI: Multiple instances of Esession component
When you create more than 2 Esession components in a project, you cannot
assign separate SessionID property values for each component. Once you
change the SessionID of one component, the other component's SessionID
will be changed to the same ID.
------------------------------------------------------------------------
H.5.2. HLLAPI: String return data
Some methods of Ehllapi SOM class returns a string data (e.g.
QuerySessions, QuerySessionStatus, etc.). You can not get the entire
value as in REXX-HLLAPI because the data after NULL will be lost and
is not seen in Basic. "Lost" information includes Host Row/Column and
Codepage information. To see these values, read the corresponding
properties of the Esession component.
------------------------------------------------------------------------
I. Country-specific information
------------------------------------------------------------------------
------------------------------------------------------------------------
I.1. Country: DBCS Font Name
Statements in the Sub main in samples\db2api\util.bas and in
samples\cli\samputil.bas set the font name for the iOutput form
to "Courier" so that output can be displayed in aligned columns.
In a DBCS environment, the Courier font cannot display double-byte
characters; therefore, DBCS users should change the font name to
MINCHO or some other DBCS font.
------------------------------------------------------------------------
I.2. Country: DBCS Data in CLI calls
When passing arguments that contain DBCS characters in CLI calls, be
sure to use byte counting, not character counting, functions like LenB,
InStrB, MidB.
------------------------------------------------------------------------
I.3. Country: Distribution of INTSTRNG.DLL
All the country dependent functions, such as IME (Input Method Editor)
related functions and DBCS character comparison functions, are stored in
the DLL named INTSTRNG.DLL. If you distribute an executable file which
calls INTSTRNG.DLL, in Japan, make the directory named "081" (for OS/2)
or "JPN" (for Windows) under the subdirectory that stores other DLL
files, then put the INTSTRNG.DLL there.
------------------------------------------------------------------------
I.4. Country: Italian Codepage for AIX
When using the remote debugging feature of the VisualAge for Basic
Server on AIX on an Italian RS/6000, some characters may not display
correctly using the default locale installed on the server. The locale
IBM 850 will display characters correctly. Characters affected are ones
with accents and other features.
------------------------------------------------------------------------
I.5. Country: Entering special characters in the Property Editor
When using the Alt + <ASCII code> sequence to enter a character, some
sequence numbers will not work correctly in the Property Editor (ex.,
Alt + 163 will tab into another property). To get around this problem,
set the Num Lock key on. Some numbers may appear along with the desired
character, but these can be removed using the Delete or Backspace keys.
------------------------------------------------------------------------
I.6. Country: Displaying DBCS errors message on AIX server
When using the Remote Debug capabilities of VisualAge for Basic Server
on an AIX server using 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*-*:
This setting is needed to display correctly error messages containing
double-byte characters.
------------------------------------------------------------------------
I.7. Country: Displaying Simplified Chinese characters in the Code
Editor
The default System font on the Simplified Chinese version of Windows NT
and Windows 95 is a True Type font. The code editor of VisualAge for
Basic does not display Simplified Chinese characters correctly when
using this font. To correct the problem, select a non-True Type font,
such as MINCHO or the "Ming" font, and enable this font in the Code
Editor. Example:
1) Edit the file \VABASIC\CONFIG\INSTPREF.INI
2) In the [Application] stanza, add the following lines:
EditComponents.Font.FontName=MINCHO
EditComponents.Font.Size=12
3) Save this file, and restart VisualAge for Basic
------------------------------------------------------------------------
I.8. Country: Cursor position on a character in the Code Editor.
For SBCS characters, the cursor should appear along the front edge of the
current character. For DBCS characters, the cursor may appear further
within the current character.
------------------------------------------------------------------------
I.9. Country: KeyAscii value of KeyPress event
In any DBCS environment, KeyAscii value of KeyPress event does not
carry the correct double byte character code.
On OS/2, the bytes are returned in the reverse order.
On Windows, only the first byte of the DBCS character is returned.
This function works correctly for the SBCS input.
##################################################============================================================
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
################################################## LICENSE INFORMATION
LICENSINFORMATION
LICENTIE-INFORMATIE
KAEYTTOEOIKEUSTIEDOT
INFORMATIONS SUR LES LICENCES
LIZENZ-INFORMATION
INFORMAZIONI RELATIVE ALLA LICENZA
LISENS INFORMASJON
INFORMACOES SOBRE A LICENCA
INFORMACION SOBRE LA LICENCIA
LICENSINFORMATION
PROGRAM NAME
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
SPECIFIED OPERATING ENVIRONMENT
The Program Specifications and Specified
Operating Environment information may be found
in the Installation/Users Guide provided with
this program.
ADDITIONAL TERMS AND CONDITIONS
Authorization for Copy and Use on Home/Portable
Computer
Yes; under the terms stated in the IPLA.
Transfer of Program
Program is fully transferable.
Proof of Entitlement
The Proof of Entitlement for this program
should be retained in order to support
eligibility provided by IBM or its authorized
reseller for warranty services, future upgrade
program prices (if announced), potential
special or promotional opportunities (if any),
and as evidence of the end user's authorized
use of this IBM licensed program.
Redistribution Information
The files/modules listed below may be copied
onto your application diskette in object code
only when your application is dependent upon
them:
o Copies of these modules are provided 'AS
IS'. You are responsible for all technical
assistance for your application.
o You agree to indemnify IBM from and against
any third party claim arising out of the
use or distribution of your application.
o You agree not to use IBM's name or
trademarks in connection with the marketing
of your applications without IBM's prior
written consent.
o You agree to prohibit the recipient from
copying (except for backup purposes),
transferring, reverse assembling, reverse
compiling, or otherwise translating the
application except as specifically
permitted by law without the possibility of
contractual waiver.
o You agree not to use the same path name as
the original files/modules.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDBF08.DLL
IBINF508.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
Your application containing a copy of the
above files/modules must be labeled as follows:
CONTAINS
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Runtime Modules
(c) Copyright IBM Corporation 1996, 1997
All Rights Reserved
(c) Copyright Visual Edge Software, LTD. 1996, 1997
All Rights Reserved
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
All Rights Reserved
Program Services
AVAILABILITY/DURATION OF PROGRAM SERVICES:
Program services will be available until
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Statement of Service
IBM provides defect support through Program
Services. A defect related problem means the
program does not conform to specifications and
could be either a code or documentation error.
For information on how you may access Program
Services, or other fee-based support services,
please contact IBM or its reseller from whom
you acquired this program.
Warranty
Yes.
U.S. Government Users Restricted Rights
U.S. Government Users Restricted Rights -
Use, duplication, or disclosure restricted by
the GSA ADP Schedule Contract with the IBM
Corporation.
Any other documentation with respect to this
licensed program, including any such
documentation referenced herein, is provided
for information purposes only and does not
extend or modify the material contained in the
License Information.
PROGRAMNAVN
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
OVRIGE VILKAR
Autorisation til kopiering/brug pa
hjemmecomputer/baerbar computer
Ja, under de vilkar, der er anfort i IPLA.
Programoverdragelse
Programmet kan overdrages.
Licensbevis
Programmets licensbevis skal gemmes som bevis
pa, at De er berettiget til eventuel
Programservice, eventuelle specielle
opgraderingspriser eller saerlige tilbud fra
IBM eller IBM's autoriserede forhandler og som
bevis pa, at De er autoriseret til at anvende
Programmet.
Information om redistribution
De nedenfor anforte filer og moduler ma kun
kopieres i objektkode til Deres
programdiskette, hvis de er nodvendige for
Deres program.
o Kopier af disse moduler leveres "i den
stand, de forefindes". De er selv ansvarlig
for afhjaelpning af eventuelle fejl i
forbindelse med denne anvendelse af
Programmet.
o De er indforstaet med at holde IBM
skadeslos for tredjemands krav, der
eventuelt rejses i forbindelse med brug
eller distribuering af Deres program.
o De er indforstaet med ikke at bruge IBM's
navn eller varemaerker i forbindelse med
markedsforingen af Deres programmer uden
IBM's skriftlige tilladelse.
o De vil forhindre, at modtageren kopierer
(undtagen til backup-formal), overforer,
tilbageoversaetter (reverse assembling/-
compiling) eller pa anden made oversaetter
Programmet, medmindre andet gaelder ifolge
ufravigelig lovbestemmelse.
o De ma ikke bruge samme stinavn som
originalfilerne/modulerne.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
Programmer, der indeholder en kopi af en af
de ovennaevnte filer/moduler, skal maerkes
saledes:
INDEHOLDER
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Programmoduler
(c) Copyright IBM Corporation 1996, 1997
IBM forbeholder sig alle rettigheder
(c) Copyright Visual Edge Software, LTD. 1996, 1997
IBM forbeholder sig alle rettigheder
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
IBM forbeholder sig alle rettigheder
Programservice
VARIGHED: Programservice er til radighed
indtil
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Serviceomfang
IBM yder fejlafhjaelpning via Programservice.
Ved fejl forstas, at Programmet ikke overholder
de angivne specifikationer og kan besta af fejl
i enten Programmet eller i dokumentationen.
Hvis De har brug for oplysninger om, hvordan
De far adgang til Programservice eller andre
betalbare serviceydelser, bedes De kontakte IBM
eller den IBM-forhandler, der har leveret
Programmet.
Garanti
Programmmet er omfattet af begraenset
garanti.
Enhver anden dokumentation i forbindelse med
dette licensprogram, herunder den dokumentation
der er omtalt her, leveres udelukkende til
oplysning og skal ikke udvide eller aendre de
betingelser, som er anfort i
licensinformationen.
PROGRAMMA-NAAM
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
AANVULLENDE VOORWAARDEN EN BEPALINGEN
Toestemming tot kopieeren en gebruik op
thuiscomputer of draagbare computer
Ja; onder de voorwaarden zoals in de
overeenkomst vermeld.
Overdracht van programma
Het programma is volledig overdraagbaar.
Bewijs van gebruiksrecht
Het bewijs van gebruiksrecht voor dit
programma dient te worden bewaard om aan te
tonen dat de gebruiker recht heeft op de door
IBM of haar geautoriseerde wederverkoper
aangeboden garantieservice, toekomstige
upgrade-prijzen (voorzover aangekondigd),
deelname aan speciale of promotionele
aanbiedingen (indien van toepassing), en als
bewijs dat de gebruiker geautoriseerd is dit
IBM programma te gebruiken.
Informatie over verdere distributie
De onderstaande bestanden/modules mogen
alleen in objectcode op uw applicatiediskette
worden gekopieerd als uw applicatie daarvan
afhankelijk is:
o Kopieeen van deze modules worden op "AS IS"
basis verstrekt. U bent zelf
verantwoordelijk voor alle technische
assistentie voor uw toepassing.
o U verklaart IBM te vrijwaren tegen elke
vordering van een derde partij die
voortvloeit uit het gebruik of de
distributie van uw toepassing.
o U verklaart geen gebruik te maken van de
naam of handelsmerken van IBM in samenhang
met de marketing van uw toepassingen zonder
voorafgaande schriftelijke toestemming van
IBM.
o U verklaart de ontvanger te verbieden de
applicatie te kopieeren (anders dan voor
het maken van een "back-up" kopie), over te
dragen, omgekeerd te assembleren ("reverse
assemble"), omgekeerd te compileren
("reverse compile") of anderszins te
vertalen, uitgezonderd wanneer dit
expliciet bij wet is toegestaan zonder de
mogelijkheid hiervan bij contract af te
wijken.
o U verklaart niet dezelfde padnaam te
gebruiken als die van de originele
bestanden/modules.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
Als uw applicatie een kopie van een van de
bovenstaande bestanden/modules bevat, moet de
applicatie de volgende vermelding bevatten:
BEVAT
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Runtime Modules
(c) Copyright IBM Corporation 1996, 1997
alle rechten voorbehouden
(c) Copyright Visual Edge Software, LTD. 1996, 1997
alle rechten voorbehouden
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
alle rechten voorbehouden
Programmaservice
BESCHIKBAARHEID/DUUR VAN PROGRAMMASERVICE:
Programmaservice zal beschikbaar zijn tot
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Serviceverklaring
IBM biedt defect-ondersteuning via
programmaservice. Een probleem met betrekking
tot een defect houdt in dat het programma niet
voldoet aan de specificaties, hetgeen een fout
in de code of in de documentatie kan betekenen.
Voor informatie over toegang tot
programmaservice of andere
ondersteuningsservices op tariefbasis kunt u
contact opnemen met IBM of de door IBM
geautoriseerde wederverkoper van wie u het
programma heeft afgenomen.
Garantie
Ja.
Iedere andere documentatie met betrekking tot
dit programma, met inbegrip van de documentatie
waarnaar hier wordt verwezen, wordt uitsluitend
verstrekt ter informatie. De inhoud van de
Licentie-Informatie wordt door dergelijke
documentatie niet uitgebreid of aangepast.
OHJELMAN NIMI
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
LISAEEHDOT
Kopiointi- ja kaeyttoeoikeus kotitietokonetta
ja kannettavaa tietokonetta varten
Sallittu Kansainvaelisen lisenssisopimuksen
(IPLA) ehtojen mukaisesti.
Ohjelman siirto
Ohjelman saa siirtaeae.
Kaeyttoelupatodistus
Ohjelman kaeyttoelupatodistus tulee
saeilyttaeae IBM:n tai sen jaelleenmyyjaen
myoentaemaen kaeyttoeoikeuden todistamiseksi
takuuta, tulevien ohjelmapaeivitysten hintoja
(jos niitae julkistetaan) ja mahdollisia
erikois- tai esittelytarjouksia (jos niitae
tarjotaan) varten sekae todisteena kaeyttaejaen
oikeudesta kaeyttaeae taetae lisensoitua
IBM-ohjelmaa.
Jakelutiedot
Asiakas saa kopioida seuraavan luettelon
sisaeltaemaet tiedostot tai moduulit
sovelluslevykkeelleen konekoodina vain, kun
sovelluksen kaeyttoe sitae edellyttaeae:
o Moduulien kopiot ovat kaeytettaevissae
"sellaisinaan". Asiakas on itse vastuussa
sovelluksen kaikesta teknisestae tuesta.
o Asiakas sitoutuu korvaamaan IBM:lle kaikki
sovelluksen kaeyttoeoen tai jakeluun
liittyvaestae kolmannen osapuolen vaateesta
aiheutuvat vahingot.
o Asiakas sitoutuu olemaan kaeyttaemaettae
IBM:n nimeae ja tavaramerkkejae
sovellustensa markkinoinnissa, ellei IBM
anna siihen etukaeteen kirjallista
suostumusta.
o Asiakas sitoutuu kieltaemaeaen
vastaanottajalta ohjelman kopioinnin
(varmistuskopiointia lukuun ottamatta),
siirron, kaeaentaemisen takaisin
alkuperaeiskielelle ja kaiken muun
kaeaentaemisen, ellei pakottavasta
lainsaeaedaennoestae nimenomaan muuta
johdu.
o Asiakas sitoutuu olemaan kaeyttaemaettae
samaa polun nimeae kuin alkuperaeisten
tiedostojen tai moduulien polun nimi.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
Sovellukseen, joka sisaeltaeae jonkin edellae
mainitun tiedoston tai moduulin kopion, on
merkittaevae seuraavat tiedot:
SISAeLTAeAe
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
ajossa tarvittavia moduuleja
(c) Copyright IBM Corporation 1996, 1997
All Rights Reserved
(c) Copyright Visual Edge Software, LTD. 1996, 1997
All Rights Reserved
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
All Rights Reserved
Ohjelmapalvelut
OHJELMAPALVELUJEN SAATAVUUS JA
VOIMASSAOLOAIKA: Ohjelmapalveluja on
saatavissa seuraavaan paeivaemaeaeraeaen
saakka:
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Palveluehto
IBM antaa ohjelmapalveluja ohjelmavirheisiin
liittyvissae ongelmissa. Ohjelmavirhe
tarkoittaa ongelmaa, joka johtuu siitae, ettae
ohjelma ei toimi maeaeritystensae mukaisesti.
Kyseessae voi olla joko ohjelman koodin tai
julkaisun virhe.
Lisaetietoja ohjelmapalvelujen tai muiden
maksullisten tukipalvelujen kaeytoestae saa
IBM:ltae tai IBM:n jaelleenmyyjaeltae, jolta
ohjelma on hankittu.
Takuu
On.
Muut taehaen lisensoituun ohjelmaan
liittyvaet julkaisut, mukaan lukien ne
julkaisut, joihin taessae julkaisussa
viitataan, eivaet ole lisaeyksiae tai muutoksia
Kaeyttoeoikeustietojen sisaeltoeoen.
DESIGNATION DU LOGICIEL
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
DISPOSITIONS SUPPLEMENTAIRES
Autorisation de reproduction et d'utilisation
sur un ordinateur familial ou portable
Oui, selon les Conditions internationales
d'utilisation des logiciels IBM.
Cession du logiciel
Ce logiciel est pleinement cessible.
Autorisation
L'Autorisation d'utilisation de ce logiciel
doit etre conservee comme preuve
d'admissibilite aux services prevus par la
garantie et assures par IBM ou son revendeur,
aux prix consentis pour des mises a niveau
ulterieures du logiciel (si IBM en annonce), ou
a des offres speciales ou promotionnelles (s'il
en est) et comme preuve de l'autorisation dont
l'utilisateur final jouit relativement a
l'utilisation de ce logiciel IBM.
Renseignements sur la redistribution
Les fichiers ou modules ci-apres peuvent etre
copies sur votre disquette d'application en
format code objet exclusivement, lorsque votre
application en est tributaire.
o Les copies de ces modules sont fournies EN
L'ETAT. Vous etes seul responsable de
l'assistance technique relative a votre
application.
o Vous vous engagez a indemniser IBM de toute
reclamation d'un tiers liee a l'utilisation
ou a la distribution de votre application.
o Vous vous engagez a ne pas utiliser, sans
autorisation ecrite prealable de sa part,
le nom d'IBM ou les marques lui appartenant
lors de la commercialisation de vos
applications.
o Vous vous engagez a interdire a
l'utilisateur de copier votre application
(sauf a des fins de sauvegarde), de la
ceder, de la desassembler, la decompiler ou
la traduire de quelque facon que ce soit,
sauf si la loi vous y autorise expressement
nonobstant toute interdiction
contractuelle.
o Vous vous engagez a ne pas utiliser le meme
chemin d'acces que celui des fichiers ou
modules d'origine.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
L'etiquette de la disquette d'application
contenant une copie de l'un des fichiers ou
modules susmentionnes doit porter la mention
suivante :
CONTIENT
des modules d'execution
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
(c) Copyright IBM Corporation 1996, 1997
Tous droits reserves
(c) Copyright Visual Edge Software, LTD. 1996, 1997
Tous droits reserves
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
Tous droits reserves
Service de logiciel
DISPONIBILITE ET DUREE DU SERVICE DE LOGICIEL:
Le service de logiciel est offert jusqu'au
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Service de logiciel
L'assistance en cas de defaut est assuree
dans le cadre du service de logiciel. Par
"defaut," on entend tout cas ou le logiciel ne
fonctionne pas conformement aux specifications
qui y sont associees, en raison d'une erreur
que comporte le code ou la documentation.
Pour savoir comment obtenir le service de
logiciel, ou tout autre service d'assistance
facturable, prenez contact avec IBM ou avec le
revendeur aupres duquel vous avez acquis ce
logiciel.
Garantie
Oui.
Toute autre documentation concernant ce
logiciel autorise, y compris toute
documentation mentionnee aux presentes, n'est
fournie qu'a titre d'information et n'etend pas
ni ne modifie la portee des Informations sur
les Licences.
PROGRAMMNAME
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
ZUSAETZLICHE VERTRAGSBEDINGUNGEN
Kopierberechtigung und Nutzung auf
Heimcomputern und tragbaren Computern
Ja; unter den in den Internationalen
Nutzungsbedingungen angegebenen Bedingungen.
Programmuebertragung
Das Programm ist vollstaendig uebertragbar.
Berechtigungsnachweis
Der Berechtigungsnachweis fuer dieses
Programm ist als Nachweis des Anspruchs auf
Garantieleistungen, zukuenftige
Programmaufruestungen (bei Ankuendigung) oder
ggf. Sonderangebote sowie als Nachweis des
Endbenutzers fuer die berechtigte Nutzung
dieses IBM Lizenzprogramms aufzubewahren.
Information zur Kopierberechtigung
Nur die folgenden Dateien/Module duerfen im
Objektcode auf eine Anwendungsdiskette kopiert
werden, wenn die Anwendung von diesen Modulen
abhaengig ist:
o Kopien dieser Module werden 'AS IS' zur
Verfuegung gestellt. Die gesamte
Verantwortung fuer technische
Unterstuetzung liegt bei Ihnen.
o Sie werden IBM fuer Ansprueche Dritter
entschaedigen, die durch die Nutzung und
Verteilung Ihrer Anwendung begruendet sind.
o Sie werden nicht den Namen der IBM oder
deren Warenzeichen ohne vorherige
schriftliche Zustimmung der IBM in
Verbindung mit der Vermarktung Ihrer
Anwendung verwenden.
o Sie werden den Empfaenger am Kopieren
(auBer zu Sicherungszwecken), am
Uebertragen, an der Desassemblierung, an
der Dekompilierung oder einer sonstigen
Umsetzung der Anwendung hindern, soweit
dies nicht ausdr}cklich gesetzlich und ohne
die Moeglichkeit des vertraglichen
Ausschlusses erlaubt ist.
o Sie werden nicht die gleichen Pfadnamen
verwenden, wie sie fuer die
Originaldateien/-module verwendet werden.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
Enthaelt Ihre Anwendung eine Kopie der oben
aufgefuehrten Dateien/Module, muB sie wie folgt
gekennzeichnet sein:
ENTHAeLT
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Runtime-Module
(c) Copyright IBM Corporation 1996, 1997
Alle Rechte vorbehalten
(c) Copyright Visual Edge Software, LTD. 1996, 1997
Alle Rechte vorbehalten
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
Alle Rechte vorbehalten
Programmservice
VERFUEGBARKEIT/DAUER DES PROGRAMMSERVICE:
Programmservice ist verfuegbar bis
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Service
Im Falle eines Programmfehlers erfolgt die
Unterstuetzung durch die IBM im Rahmen des
Programmservice, sofern fuer die
Lizenzprogramme Programmservice vereinbart
wurde. "Programmfehler" sind alle Abweichungen
von den veroeffentlichten
Programmspezifikationen des Codes oder der
Dokumentation.
Die Adresse der Servicestelle, die den
Programmservice erbringt, kann beim IBM
Vertriebsbeauftragten oder beim
Wiederverkaeufer - abhaengig davon, bei wem das
Programm erworben wurde - erfragt werden.
Gewaehrleistung
Ja.
Jede andere Dokumentation, die einen Bezug zu
diesem Lizenzprogramm herstellt, einschlieBlich
jeglicher Dokumentation, die darin referenziert
ist, dient nur zur Information und erweitert
oder modifiziert diese Lizenz-Information
nicht.
PROGRAMMA
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
CONDIZIONI AGGIUNTIVE
Autorizzazione alla copia e all'utilizzo su
Computer Portatile
Si; in base alle condizioni contenute
nell'IPLA.
Trasferimento del Programma
Il programma e interamente trasferibile.
Prova di Titolarita
La Prova di Titolarita per questo programma
deve essere conservata per poter usufruire dei
servizi di garanzia, dei benefici previsti per
i futuri Programmi di aggiornamento (se
annunciati), delle eventuali opportunita
promozionali fornite dalla IBM o suoi
rivenditori autorizzati, e come prova
dell'autorizzazione all'uso del Programma da
parte dell'utente finale.
Informazioni sulla ridistribuzione
I file/moduli qui elencati possono essere
ridistribuiti, in formato codice-oggetto,
unitamente alla vostra applicazione quando la
stessa ne richiede l'utilizzo:
o Le copie di questi moduli vengono fornite
"As is" (Nello stato in cui si trovano).
Voi siete responsabili dell'assistenza
tecnica alla vostra applicazione.
o Accettate di risarcire l'IBM da e contro
qualsiasi rivendicazione di terzi che
risultino danneggiati dall'uso o dalla
distribuzione della vostra applicazione.
o Accettate di non utilizzare il nome o il
marchio IBM per commercializzare le vostre
applicazioni senza autorizzazione scritta
da parte dell'IBM.
o Accettate di impedire al destinatario di
copiare (se non allo scopo di copia di
back-up), trasferire, disassemblare,
decompilare o convertire l'applicazione.
o Accettate di non utilizzare il nome dei
file/moduli originali.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
L'applicazione contenente una copia dei
file/moduli deve essere etichettata nel modo
seguente:
CONTAINS
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Moduli runtime
(c) Copyright IBM Corporation 1996, 1997
Tutti i diritti riservati
(c) Copyright Visual Edge Software, LTD. 1996, 1997
Tutti i diritti riservati
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
Tutti i diritti riservati
Servizi al Programma
DISPONIBILITA/DURATA: I servizi al programma
saranno forniti fino al:
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Informazioni sul Servizio
L'IBM fornisce l'assistenza per la
risoluzione dei problemi dovuti a difetti,
tramite i Servizi al Programma. Un problema e
relativo a un difetto quando il programma non e
conforme alle specifiche e puo derivare da un
errore di codice o da un errore nella
documentazione.
Per le informazioni relative a come ottenere
i Servizi al Programma o altri servizi di
supporto a pagamento, contattare l'IBM o suo
rivenditore autorizzato presso il quale e stato
acquistato questo programma.
Garanzia
Si.
Qualunque altra documentazione relativa a
questo programma, richiamata in questo
documento, viene fornita solo per informazione
e non amplia o modifica il contenuto delle
"Informazioni relative alla Licenza".
PROGRAM NAVN
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
TILLEGGSBETINGELSER
Tillatelse til a kopiere og bruke pa
hjemme-/baerbar datamaskin.
Ja, pa vilkarene nevnt i de internasjonale
bruksbetingelsene.
Overdragelse av programmet
Programmet kan overdras i sin helhet.
Kjopsbevis
Kjopsbeviset for dette programmet ma
oppbevares som dokumentasjon overf IBM eller en
autorisert IBM-forhandler for retten til
garantiservice, fremtidige
programoppgraderingstilbud (hvis annonsert),
eventuelle spesial- eller markedsforingstilbud
og som bevis for at brukeren har rett til a
bruke dette IBM-lisensierte programmet.
Informasjon om redistribuering
Filene og modulene nedenfor kan bare kopieres
til applikasjonsdisketten i objektkode nar
applikasjonen er avhengig av dem:
o Kopier av disse modulene leveres som 'SOM
DE ER'. Du er selv ansvarlig for all
teknisk assistanse for din applikasjon.
o Du samtykker i a holde IBM skadeslos
overfor ethvert krav fra tredje p for bruk
eller distribusjon av din applikasjon.
o Du samtykker i a ikke bruke IBMs navn eller
varemerker i forbindelse med markedsforing
av dine applikasjoner uten pa forhand a ha
innhentet I skriftlige samtykke.
o Du samtykker i a forby mottakeren a kopiere
(bortsett fra reservekopiering), overfore,
utfore reversert kompilering eller pa anne
oversette eller omgjore applikasjonen
unntatt slik det er uttrykkelig tillatt ved
lov, uten mulighet til kontraktsmessige
unntak.
o Du samtykker i a ikke bruke de samme
navnene pa tilgangsbanene som i
originalfilene og originalmodulene.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
Applikasjonen som inneholder en kopi av
hvilke som helst av filene/modulene ovenfor, ma
merkes slik:
INNEHOLDER
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Runtime Modules
(c) Copyright IBM Corporation 1996, 1997
All Rights Reserved
(c) Copyright Visual Edge Software, LTD. 1996, 1997
All Rights Reserved
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
All Rights Reserved
Programservice
TILGJENGELIGHET/VARIGHET AV PROGRAMSERVICE:
Programservice er tilgjengelig frem til
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Programservice
IBM leverer stotte gjennom Programservice.
Et defekt-relatert problem betyr at programmet
ikke er i samsvar med spesifikasjonene. Dette
kan vaere enten kode- eller dokumentasjonsfeil.
For naermere opplysninger om a bruke
Programservice eller andre avgiftsbelagte
stottetjenester, kontakt IBM eller en
autorisert IBM-forhandle
Garanti
Ja.
Enhver annen dokumentasjon knyttet til dette
Lisensierte Program, inkludert enhver
dokumentasjon det refereres til, er fremlagt
kun for informasjonsformal, og hverken utvider
eller endrer materialet som ligger
lisensinformasjonen.
NOME DO PROGRAMA
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
TERMOS E CONDICOES ADICIONAIS
Autorizacao Para Copia e Utilizacao em
Computador Domestico/Portatil
Sim; de acordo com os termos e condicoes
determinados no CIPISL (Contrato Internacional
de Programas IBM Sob Licenca).
Transferencia da Licenca
A Licenca pode ser transferida na sua
totalidade.
Prova de Licenciamento
A Prova de Licenciamento deste Programa deve
ser conservada a fim de comprovar a
elegibilidade do Cliente aos servicos de
garantia, a futuros precos para atualizacoes do
Programa (se anunciadas), a promocoes especiais
(se existirem) e, ainda, como prova de que o
Cliente esta autorizado a usar este Programa
IBM sob licenca.
Informacoes Sobre Redistribuicao
Os arquivos/modulos apresentados a seguir so
poderao ser copiados para o disquete de
aplicacao do Cliente quando a aplicacao
depender dos mesmos:
o As copias destes modulos sao fornecidas 'NO
ESTADO'. O Cliente e responsavel por toda a
assistencia tecnica relacionada com a
respectiva aplicacao
o O Cliente concorda em indenizar a IBM por
reclamacoes efetuadas por e contra
terceiros, resultantes da utilizacao ou
distribuicao da aplicacao feitas ou
permitidas pelo mesmo.
o O Cliente concorda em nao utilizar o nome
IBM ou marcas comerciais da IBM, em conexao
com a comercializacao de suas aplicacoes,
sem autorizacao pre escrito da IBM.
o O Cliente concorda em proibir o
destinatario de copiar (exceto para fins de
copia de seguranca), transferir, fazer a
engenharia reversa, descompilar ou, de
outro modo, converter a aplicacao exceto
como especificamente permitido por lei sem
a possibilidade de excecao contratual
especifica.
o O Cliente concorda em nao utilizar o mesmo
nome de caminho dos arquivos/modulos
originais.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
Cada disquete da aplicacao do Cliente que
contenha uma copia de qualquer um dos
arquivos/modulos acima relacionados devera ter
um rotulo com o seguinte formato:
CONTEM
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Runtime Modules
(c) Copyright IBM Corporation 1996, 1997
Todos os Direitos Reservados
(c) Copyright Visual Edge Software, LTD. 1996, 1997
Todos os Direitos Reservados
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
Todos os Direitos Reservados
Servicos a Programa
DISPONIBILIDADE E DURACAO DOS SERVICOS A
PROGRAMA: Servicos a programa estarao
disponiveis ate
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Declaracao de Servicos de Suporte
A IBM fornece suporte a defeitos atraves dos
Servicos de Suporte a Programa. Um problema
relacionado com um defeito implica que o
Programa nao esta em conformidade com as
especificacoes, podendo consistir em um erro de
codigo ou em um erro de documentacao.
Para obter informacoes sobre o acesso aos
Servicos de Suporte a Programa ou a outros
servicos de suporte com cobranca de encargos, o
Cliente deve entrar em contato com a IBM ou o
Representante Autorizado IBM de quem adquiriu
este Programa.
Garantia
Sim.
Qualquer outra documentacao relativa a este
programa licenciado incluindo qualquer
documentacao mencionada neste documento, e
oferecida unicamente com proposito informativo
e nao modifica ou amplia o material contido
nestas Informacoes sobre a Licenca.
NOMBRE DEL PROGRAMA
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
TERMINOS Y CONDICIONES ADICIONALES
Autorizaci∞n para copia y uso en ordenador
dom⌐stico o portÉtil
SÑ; en las condiciones especificadas en el
IPLA.
Transferencia del Programa
Este Programa es totalmente transferible.
Documento de titularidad
El Documento de titularidad de este programa
debe guardarse para que IBM, o el concesionario
autorizado, pueda dar cobertura a los servicios
de la garantÑa, a los precios de futuros
programas de actualizaci∞n (si se anuncian), a
las posibles oportunidades especiales o de
promoci∞n (si las hay), y como prueba del uso
autorizado de este programa bajo licencia IBM
por parte del usuario final.
Informacion sobre redistribucion
unicamente se podran copiar los siguientes
modulos o archivos en el disquete de aplicacion
en codigo de objetos si su aplicacion depende
de ellos:
o Las copias de estos modulos se proporcionan
'TAL CUAL'. Es responsabilidad del usuario
la asistencia tecnica de la aplicacion.
o Debera indemnizar a IBM como resultado de
las reclamaciones de terceros que se
deriven del uso o la distribucion de la
aplicacion.
o No podra utilizar el nombre o las marcas
registradas de IBM con la comercializacion
de sus aplicaciones sin el consentimiento
previo por escrito de IBM.
o Queda terminantemente prohibido copiar
(salvo a efectos de copia de seguridad),
transferir, descomponer, descompilar o
traducir la aplicacion de un modo distinto
que no sea el permitido especificamente por
ley sin posibilidad de renuncia
contractual.
o No podra utilizar el mismo nombre de via de
acceso que los archivos o modulos
originales.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
La aplicacion que contenga una copia de uno
de los archivos o modulos mencionados debe
etiquetarse de este modo:
CONTIENE
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Modulos en tiempo de ejecucion
(c) Copyright IBM Corporation 1996, 1997
Reservados todos los derechos
(c) Copyright Visual Edge Software, LTD. 1996, 1997
Reservados todos los derechos
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
Reservados todos los derechos
Servicios del programa
DISPONIBILIDAD/DURACION DE LOS SERVICIOS DEL
PROGRAMA: Los servicios para el programa
estaran disponibles hasta
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Declaracion de Servicio
IBM proporciona soporte t⌐cnico de los
defectos a trav⌐s de los Servicios de Programa.
Un problema relacionado con un defecto implica
que el programa no se ajusta a las
especificaciones pudiendo tratarse de un error
de documentacion o de codigo.
Para obtener informacion sobre el acceso a
los Servicios de Programa o a otros servicios
facturables de soporte t⌐cnico, p∞ngase en
contacto con IBM o con el concesionario en el
que haya adquirido el programa.
GarantÑa
SÑ.
Cualquier otra documentacion relacionada con
este programa bajo licencia, incluyendo
cualquier documentacion a la que se hace
referencia ac , es suministrada solamente con
car cter informativo y no aumenta, ni modifica,
el material que constituye la Informacion bajo
Licencia.
PROGRAMBETECKNING
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
YTTERLIGARE VILLKOR
Raett till kopiering och anvaendning pa
hemdator/baerbar dator
Ja, enligt villkoren i IPLA.
Oeverlatelse av Program
Programmet far till fullo oeverlatas.
Licensbevis
Licensbeviset (Proof of Entitlement) till
detta program skall sparas som bevis pa raetten
till garantiservice, eventuella framtida
priserbjudanden pa uppgraderingar och
specialerbjudanden fran IBM eller dess
auktoriserade aterfoersaeljare samt som bevis
pa slutanvaendarens raett att anvaenda detta
IBM-licencerade program.
Information om vidaredistribution
De filer/moduler som raeknas upp nedan far
kopieras till er applikationsdiskett i
objektkodsform endast naer er applikation aer
beroende av dem:
o Modulerna tillhandahalls "i befintligt
skick". Ni aer ansvarig foer all teknisk
assistans foer er applikation.
o Ni atar er att halla IBM skadesloest foer
varje form av ansprak fran tredje part som
kan uppsta som foeljd av anvaendning eller
distribution av er applikation.
o Ni atar er att inte anvaenda IBMs namn
eller varumaerken i samband med
marknadsfoeringen av era applikationer utan
att i foervaeg inhaemta IBMs skriftliga
medgivande.
o Ni atar er att foerhindra mottagaren att
kopiera (utom foer backup-aendamal)
applikationen, att oeverlata applikationen
eller att disassemblera, dekompilera eller
pa annat saett oeversaetta (savida inte
sadan raett medges i tvingande lag)
applikationen.
o Ni atar er att inte anvaenda samma
soekvaegsnamn som
originalfilerna/modulerna.
BINTER.DLL
BRTL.DLL
CATALOG.DLL
SOMOSA.DLL
RTINT.DLL
RTKERN.DLL
VWCOMP.DLL
VWEUC.DLL
VWFCALL.DLL
VWGEN.DLL
VWUTIL.DLL
VVWVCR.DLL
OLE2UI.DLL
OLEOSA.DLL
OLEPRO32.DLL
MSVCRT20.DLL
MSVCRT40.DLL
RTOCX.DLL
VWCAUTIL.DLL
ODBUDDY.EXE
ODBC.DLL
IBSS08.DLL
IBDCF08.DLL
IBSYB08.DLL
IBOR708.DLL
IBMDI08.DLL
IBGUP08.DLL
IBTXT08.DLL
IBING408.DLL
DB2CLI.DLL
QEIB.LIC
LICOS2.DLL
SOM.DLL
SOMD.DLL
SOMIR.DLL
SOMTC.DLL
CCAPPAPV.DLL
CCAPPAPI.DLL
CCAPPPRT.DLL
CCTCPAPV.DLL
CCTCPAPI.DLL
CCTCPPRT.DLL
CCNETAPV.DLL
CCNETAPI.DDL
CCNETPRT.DLL
CCHLLSE.DLL
CCHLLAPI.DLL
CCHLLRE.DLL
CCCOM.DLL
CCCOMRT.DLL
SP.OCX
SPCLI.DLL
libgenAdapt2.a
GENADPT2.dll
De av era applikationer som innehaller en
kopia av nagon av ovan naemnda filer/moduler
maste maerkas pa foeljande saett:
INNEHALLER
IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Runtime-moduler
(c) Copyright IBM Corporation 1996, 1997
All Rights Reserved
(c) Copyright Visual Edge Software, LTD. 1996, 1997
All Rights Reserved
(c) Copyright Intersolv, Inc. 1994, 1996, 1997
All Rights Reserved
Programservice
TILLGANG/VARAKTIGHET - PROGRAMSERVICE:
Programservice aer tillgaenglig t o m
1997/12/31 IBM VisualAge for Basic for OS/2 and for Windows Version 1.1
Servicemeddelande
IBM tillhandahaller stoed vid fel genom
programservice. Med ett felrelaterat problem
avses att programmet inte oeverensstaemmer med
specifikationerna, och det kan vara antingen
ett fel i koden eller i dokumentationen.
Foer information om hur ni far tillgang till
programservice och avgiftsbelagda andra
supporttjaenster, kontakta IBM eller den
aterfoersaeljare till IBM fran vilken ni
anskaffat detta program.
Garanti
Ja.
All annan dokumentation avseende detta
licensierade program, inklusive sadan haer
refererad dokumentation, tillhandahalls endast
i informationssyfte och utvidgar eller aendrar
inte det material som finns i
licensinformationen.
IBM
Part Number: 84H6465