From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,99cf26e179e838e0
X-Google-Attributes: gid103376,public
From: Joseph P Vlietstra <joevl@concentric.net>
Subject: Re: Conversion from Verdix VADS to Rational APEX
Date: 2000/04/27
Message-ID: <3907D847.707E8BEA@concentric.net>#1/1
X-Deja-AN: 616225841
Content-Transfer-Encoding: 7bit
References: <8e8ga0$qvb$1@nnrp1.deja.com>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854";
 x-mac-creator="4D4F5353"
Organization: Mojave Systems Corporation
Mime-Version: 1.0
Reply-To: joevl@concentric.net
Newsgroups: comp.lang.ada
Date: 2000-04-27T00:00:00+00:00
List-Id: <comp.lang.ada>

Chris Miller wrote:

> I have been given the task of evaluating a proposal to convert a
> large project from a Verdix VADS platform to Rational APEX. The code is
> cross compiled from Sun Solaris ==> 68K VME Embedded.
>
> The main issues are what to do about the Vads runtime and exec, and how
> long it will all take.

Rational supplies a VADS compatibility library with Apex.
You'll need to explicity add this library to the import list of your view
since it's not
normally imported when you create the view.  If you have a LOT of VADS
code,
you can customize Apex to automatically import the VADS compatibility
library
during view creation.

BTW: Rational provides fairly good technical support in this area.
Ask your Rational sales rep for help.  There's usually a technical support
person
backing up your sales rep.