[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference star::wizards

Title:	"ASK THE WIZARDS"

Moderator:	QUARK::LIONEL

Created:	Mon Oct 30 1995
Last Modified:	Mon May 12 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1857
Total number of notes:	3728

1604.0. "Closed: is 6.2 fully backward compatible?" by STAR::JKEENAN () Fri Feb 14 1997 12:31

Date: Fri, 14 Feb 1997 11:59:24 -0500
Message-Id: <[email protected]>
From: "VMS001::WWW"@vms001.das-x.dec.com (14-Feb-1997 1159)
To: [email protected], [email protected], [email protected]
Subject: Ask the Wizard: '[email protected]'

Remote Host: (null)
Browser Type: Mozilla/2.0 (compatible; MSIE 3.01; Windows NT)
Remote Info: <null>
Name: Andrew marshall
Email Address: [email protected]
CPU Architecture: Alpha
Version: v 6.2
Questions: 

Is version 6.2 fully backward  compatibilty with version 6.1.

We are a software company that has many customers on version 6.1 and one customer on 6.2. If we install V6.2 can we still compile and send out software to our V6.1 customers. Is there any problems.

Please this is a urgent request for information.

T.R Title User Personal
Name Date Lines

1604.1 QUARK::LIONEL Free advice is worth every cent Fri Feb 14 1997 12:44 13

T.R	Title	User	Personal Name	Date	Lines
1604.1		QUARK::LIONEL	Free advice is worth every cent	`Fri Feb 14 1997 12:44`	13
	OpenVMS does not promise backward compatibility, only forward compatibility. To link applications on a V6.2 system that will run on a V6.1 system, create a directory with a copy of all of the .OLB and .EXE files from SYS$LIBRARY of a V6.1 system. Then, when you link, define the following logical name first: $ DEFINE SYS$LIBRARY disk:[dir] ! where the V6.1 files are You can use DEFINE/USER if the LINK command follows directly afterward. Don't forget to DEASSIGN the logical after if /USER is not used. You should read the release notes of the programming language(s) you are using to see if there are other issues.

OpenVMS does not promise backward compatibility, only forward compatibility.
To link applications on a V6.2 system that will run on a V6.1 system, create
a directory with a copy of all of the .OLB and .EXE files from 
SYS$LIBRARY of a V6.1 system.  Then, when you link, define the following
logical name first:

	$ DEFINE SYS$LIBRARY disk:[dir] ! where the V6.1 files are

You can use DEFINE/USER if the LINK command follows directly afterward.  Don't
forget to DEASSIGN the logical after if /USER is not used.

You should read the release notes of the programming language(s) you are using
to see if there are other issues.