Openwings Home
Introduction
Search
In the News
Frequently Asked Questions
Registration
Open Forum
Openwings Tutorial
Bug Database
Openwings API
Download
Expert Teams
Process Management Office
Projects
Links
Terms of Use
Comment on this bug

04040:

InstallAnywhere: Unix Openwings installer doesn't set environment vars

Category: Integration
Status: Closed

Severity: MEDIUM
Reported against release: 0.8
Fixed in release: 0.9

PROBLEM:

On raven and on the AFATDS demo machine, after Openwings is installed, 
the environment variables are not set up as they should be.  As a 
workaround, wrapper scripts are being used on these systems to set the 
environment correctly and then call ow.csh or owsh.csh.

See "startcm" and "stopcm" for examples of wrapper scripts for starting 
and stopping the container manager.
See "startshell", "starteditcd", "startediticd" for examples of wrapper 
scripts for starting the shell and the component descriptor editors.  
These are the scripts currently being used on raven.

To resolve this defect, one of the following solutions should be 
implemented:

- InstallAnywhere should set the environment variables in the 
appropriate .cshrc file

or 

- Scripts such as "startcm" and "startshell" should be created on the 
user's system as part of the installation process.

ANALYSIS:

This problem was tested on a DII-COE based machine and was no longer an 
issue (i.e. environment vars were properly set).  Therefore, this 
defect should be closed as no change required.  DGP 4/17/2002

back to top

home | vision | search | in the news | faq | registration | open forum | tutorial | bug database
 API | download | expert teams | process management office | projects | links | terms of use

© Copyright 2001-2006 General Dynamics C4 Systems. All rights reserved.