Kbase 18694: Major Release Minor Release connection from client to server
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/07/2000 |
|
Major Release Minor Release connection from client to server
INTRODUCTION:
=============
This document has been made to clarify some possible questions
that might exist for those people making Progress client connections
to Progress database servers.
This document is specifically aimed at anser what Major and Minor
release numbers signify and what client version should be able to
connect to what server version.
WHY YOU NEED TO KNOW THIS:
===========================
This is a general guideline if you need to determine if a client
should be able to connect to a specific server version and whether
the connection may be shared memory, direct or client-server or if
it must be client-server.
VERSION NUMBERING
=================
When discussing Progress versions, you will usually see at least
2 numbers and a letter.
Examples:
7.2D
7.3E
8.3A
If you see more than this 2 number and a letter pattern it usually
indicates a patch level applied to a version.
Examples:
7.2D08
7.3C18
7.3E04
8.3C09
(Only in extremely rare cases will a Commercial release have more
than just the 2 numbers and a letter version number.)
MAJOR RELEASE AND MINOR RELEASE
===============================
In discussing Progress versioning, we refer to the first number in
the version as the Major release number.
The second number is referred to as the Minor release (aka point
release number).
The letter usually designates a specific main release or maintenance
release within that version level.
The addition numbers after the letter are used typically to denote
a patch number.
Examples:
Version 8.2A
is Major release 8 Minor release 2 main release A
Version 8.2B
is Major release 8 Minor release 2 maintenance release B
Version 8.2C04
is Major release 8 Minor release 2 maintenance release C with patch 04
CLIENT CONNECTIONS: WHAT TYPE OF CONNECTION IS POSSIBLE
========================================================
A client may connect to a database in Self-Service mode using shared
memory only when the clients version exactly matches the database
servers version.
Example:
Client is version 8.2C04
Server is version 8.2C04
If the client and server do not have the exact same version
and they try and connect in Self-Service mode using shared memory
then the client will likely receive an 1178 error
The shared memory is version <num>; expected <num> (1178)
If the client and server do not have the same Major and Minor release
numbers and they try and perform a direct single-user connection
then the client will likely receive a 44 error
** Database has the wrong version number. (db: <value>, pro: <value>).
(44)
If the Major and Minor release numbers are the same for the database
then a client may make a single user direct connect to the database.
(i.e. no server is running for the database).
If the client and server have different version numbers (including
Major, Minor, Maintenance, and Patch) and a server is running on
the database, then the client *must* connect client/server.
That is, the server must be started with -H -S -N parameters and
the client must use the exact same parameters as part of its connect
statement.
Example:
mpro <dbname> -N tcp -S <servicename> -H <hostname>
Clients are able to connect to database servers using client/server
within the same Major release and 1 Major release prior.
Example 1:
A version 8.3A client can connect to:
A version 8.3x database server (same major release)
A version 8.2x database server (same major release)
A version 7.3x database server (1 major release prior)
Example 2:
A version 8.1C client can connect to:
A version 8.3x database server (same major release)
A version 8.2x database server (same major release)
A version 7.3x database server (1 major release prior)
A version 8.3A client CAN NOT connect to a version 9 database server.
A version 7.3E client CAN NOT connect to a version 8 database server.
WEBSPEED Connectivity
=====================
Webspeed has similar rules to the rest of Progress. The important
thing to be aware of with Webspeed is that Webspeed is a modified
Progress client.
Webspeed Versions
Webspeed 2.1 is a specially architected 8.1A client.
Webspeed 3.0 is a specially architected 9.0A client.
Example:
Following the Client connection rules listed in the earlier part of
this Knowledge Base, Webspeed 2.1 can only make a single-user or
self-serv connection to an 8.1A database or database server. All
other connections must be made using the remote client connection
parameters and follow the same restrictions of an 8.1A client.
(RAS 03/26/99)