Release Notes

Landmark Desktop-VIP
Desktop-VIP 2003.4 Release Notes Page 1

Desktop-VIP 2003.4
Release Notes
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Setting the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Running DESKTOP-VIP for the First Time. . . . . . . . . . . . 25
Enhancements and New Features. . . . . . . . . . . . . . . . . . . . 27
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Landmark/Asia Pacific
11th Floor Menara Tan & Tan
207 Jalan Tun Razak
50400 Kuala Lumpur
Malaysia
Tel: 011-60-3-2164-1121
Fax: 011-60-3-2164-1135
Help Desk: 011-61-8-9481-4488
Email: [email protected]
Landmark/EAME
Hill Park South
Springfield Drive
Leatherhead, Surrey GU22 7NL
England
Tel: 011-44 (0) 1372 868-600
Fax: 011-44 (0) 1372 868-601
Help Desk: 011-44 (0) 1372-868-
686
Landmark/The Americas
Building 1, Suite 200, 2101 CityWest
Houston, TX 77042
P.O. Box 42806, Houston, TX 77242
U.S.A.
Tel: 713-839-2000
Help Desk: 713-839-2200
Fax: 713-839-2169
Table of Contents
Introduction
Whats New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Restatement of VIP NT to Windows 2000 Considerations . . . . . . . . . . . . . . . . . . . . . . . . 8
VIP NT Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
VIP Unix/Linux Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
New Windows 2000 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
System Requirements
Windows 2000 Workstations and Windows 2000 Operating Systems . . . . . . . . . . . . . . 11
Graphics Cards and Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
X Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Adobe Acrobat Reader Version 5.05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
FLEXlm Version 7.2e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
FLEXlm Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
FLEXlm Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Unique Parallel Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Software Requirements -- Critical MPI Software . . . . . . . . . . . . . . . . . . 15
Hardware Requirements -- Critical MPI Software . . . . . . . . . . . . . . . . . 15
Include File Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Other Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Known System Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
General Known Issue -- pcAnywhere/Exceed Conflict . . . . . . . . . . . . . . 16
VIP Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Integration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installation
Setup Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Decide Where to Install the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Uninstallation of Older DESKTOP VIP Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Install Acrobat Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
DESKTOP-VIP R2003.4 Installation on Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . 22
Setting the Environment
Windows 2000 Systems Setting the Users Environment . . . . . . . . . . . . . . . . . . . . . 25
Setting User Privilege . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting up the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Before Installing VIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
ENVIROMENTAL VARIABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
System Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
XENVIRONMENT Resource File Definition . . . . . . . . . . . . . . . . . . . 27
Simulator Selection Environment Variables Default Executables . . . . 28
VIP VDB Directory Structure and VDB Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Running DESKTOP-VIP for the First Time
Windows 2000 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Enhancements and New Features
Version R2003.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
VIP-Executive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Modified Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
VDB Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
DeskTop-VIP User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
VIP Job Submittal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
SimResults / SimResults+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
VIP Convert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
VIP Data Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
VDS-CORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
VDS-EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Known Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Grid Calculator (GridCalc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Known Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Region Calculator (RegCalc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
E2V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
GridGenr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Appendix A: Installing PaTENT for Parallel Computing
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Location of Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
On-Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Assumptions About the Customer's Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuring the Client Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Restarting MPI Service for TMP/TMPDIR Changes on Remote Nodes . . . . . . . . . . . . 46
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Appendix B: Setup Instructions to Submit Jobs via Remote Shell
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Assumptions: About the Users Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Key Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Key Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Job Submission Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Appendix C: VIPrshServer & VIPrshClient Utilities
VIPrshServer: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
VIPrshClient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Appendix D: FLEXlm Licensing
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Version Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Understanding the License Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Using the License System with Third-Party Software . . . . . . . . . . . . . . . . . . . . . 66
LAM 2003.0 Guide Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
LAM System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Obtaining a Server License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Installing LAM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
License Server Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
LAM Technical Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Using LAM Server Without NT Service . . . . . . . . . . . . . . . . . . . . . . . . . 73
LAM Server Installation Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
If Applications Cannot Find License File . . . . . . . . . . . . . . . . . . . . . . . . 73
Overriding LM_LICENSE_FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
LAM Server Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Stop and Remove the License Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Uninstall Previous Versions of LAM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Uninstalling LAM 2000 Server Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Appendix E: Installing Hummingbird Exceed 7.1 on Windows 2000
Exceed-X Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Exceed 3D Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Optimizing the Hummingbird Exceed 7.1 X-server for Desktop-VIP . . . . . . . . . . . . . . 81
Optimize the X Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Appendix F: Installing Adobe Acrobat
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Printing Books from Adobe Acrobat Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Appendix G: OpenWorks Install after VIP
Setting up VIP in a New OpenWorks Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Appendix H: Uninstall Older Versions
Uninstall LAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Uninstall Critical MPI Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Uninstall Nutcracker Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Uninstall Older Versions of Desktop-VIP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Appendix I: Uninstall Desktop-VIP R2003.4
Desktop-VIP 2003.4 Release Notes Page 7 Introduction
Introduction
These Release Notes provide the necessary information to correctly install
DESKTOP-VIP Release 2003.4 on Windows 2000 machines. They also contain
operating system support levels and required third party software, as well as
instructions for setting up parallel configurations, network dependencies and
tested hardware configurations. Instructions for uninstalling older versions of
DESKTOP-VIP and related third party software are also included in these
Release Notes.
Whats New
DESKTOP-VIP R2003.4 provides a graphical user interface that is certified on
Windows 2000 Service Pack 1 and 2. It has also been tested on Windows XP
Professional, with no problems detected. VIP simulators are certified on
Windows 2000 SP1 and 2, as well as Solaris 8, IRIX 6.5.11m, and AIX 4.3.3,
and Linux Red Hat 7.2. VIP simulators have also been tested on Windows XP
Professional with no problems detected.
This release provides a wide range of enhancements, including the following
major changes to Windows-based user interface applications:
Desktop. The new JAVA-based Desktop has a Windows look-and-feel, with
features like docking/floating toolbars and mouse-over tooltips. Study/
Case management and network access from the Desktop has been
improved.
Job Submittal. The new JAVA-based Job Submittal application with
emphasis placed on ease-of-use, job queueing, remote job submittal,
and input/output/include file management.
SimResults and SimResults+. The SimResults plotting application takes
advantage of Windows-based features such as drag-and-drop to let you more
efficiently use those plotting capabilities that were available in PlotView.
SimResults+ (license required) also lets you create RTF plots, allows for
batch plotting, and provides a seamless interchange between Eclipse and VIP
data and .grf templates.
Enhancements to VIP Data Studio. This efficient, wizard-driven application
has been expanded to let you create VIP-CORE as well as VIP-EXEC data
files.
VIP Convert. This powerful conversion application now lets you export and
import Rescue geocellular model data.
RegCalc (Region Calculator). This new application lets you quickly obtain
pressure, saturation, and fluids in place at any timestep for both your
IREGIONS and any arbitrary I,J,K area (not defined as an IREGION).
DESKTOP-VIP R2003.4 provides numerous enhanced simulation capabilities,
including:
Enhanced Surface Pipeline Network, including optimization of well and
gaslift gas rates, and multiple output streams from nodes.
A basic implementation of injection networks in addition to production
networks.
Version independent restarts from R2003.4 forward. (A utility is provided to
convert from R2003.0 to R2003.4)
Option for control of gas re-solution rate. (DRSDT)
Support for multiple water PVT regions, including optional property
variations with salinity.
Optimization of gaslift gas utilization at all targeting levels.
Threshold pressure option for fault flow.
Simultaneous bottomhole and tubinghead pressure constraints.
All new and enhanced functionality is described in the Enhancements and New
Features section of this document.
Restatement of VIP NT to Windows 2000 Considerations
Although most users have already upgraded to Windows 2000, the following
information is being repeated for any users who have not yet installed VIP in a
Windows environment.
VIP NT Users
Note the following suggestions for installing DESKTOP-VIP for Windows
2000.
VIP Unix/Linux Users
Desktop-VIP graphical user interface applications are only available on
Windows 2000. Except as noted below for Geolink and 3DView, only Unix and
Linux simulators are provided and can be found on separate CDs. You can use
the Desktop-VIP on Windows 2000 to submit remote simulation jobs (serial or
parallel) to Unix/Linux machines. GeoLink certified on Solaris and IRIX
platforms is part of the Stratamodel R2003.0 offering. A certified version of
3DView for Solaris and IRIX is part of the OpenVision R2003.0 offering. A
tested version of 3DView for Linux is part of the OpenVision R2003.3 offering.
New Windows 2000 Users
DESKTOP-VIP Release 2003.4 hardware and software requirements are
outlined in the next section. Please read this section carefully prior to obtaining
your hardware.
Install Windows 2000 rather than upgrade!
If you are required to change operating systems, we recommend that you
completely install Windows 2000 rather than upgrade from NT 4.0.
If you choose to upgrade, it is STRONGLY RECOMMENDED that you uninstall
VIP NT and related software before upgrading your machine to Windows 2000.
Related software includes LAM licensing, Exceed 6.1 or 6.2, Nutcracker, and
Genias' PaTENT MPI (if running parallel SMP.) Please refer to Appendix H:
Uninstall Older Versions on page 89 for instructions on how to correctly
uninstall all software.
Desktop-VIP 2003.4 Release Notes Page 11 System Requirements
System Requirements
Windows 2000 Workstations and Windows 2000 Operating Systems
DESKTOP-VIP R2003.4 was certified on Windows 2000 with Service Pack 1
and 2. It has also been tested on Windows XP, with no problems detected.
Release Version 2003.4 was tested on Dells Precision Workstations, IBMs
Intellistations, Compaqs Professional Workstations, and Dell PowerEdge 2650
Xeon Servers. It was also tested on various high-end laptops with no problems
detected.
Additional minimum and recommended configurations are detailed in the
following table.
NOTE: Note that disk space and memory requirements have significantly increased
Please Note:
Because of rapid changes in hardware technology, we cannot guarantee that DESK-
TOP-VIP will work on systems, graphics cards, and graphics drivers other than those
used during testing and certification. No major problems have been encountered
except graphics surrounding 3D applications. Please adhere closely to certified graph-
ics standards should you choose to license 3D applications.
Table 1: Windows 2000 System Requirements
Minimum Recommended
Intel Pentium III Dual Intel Pentium Xeons
512 MB RAM 1024 MB (or better) RAM
19" Color Monitor Dual Color Monitors
MS-compatible 3-button mouse or
pointing device
MS-compatible 3-button mouse or
pointing device
TCP/IP-based network connection, with
minimum bandwidth 10Mbps
TCP/IP-based network connection, with
minimum bandwidth 100Mbps
200 MB available disk space on C drive 400 MB available disk space on C drive
900 MB disk space. Includes installation
of DeskTop-VIP and Adobe Acrobat;
does not include Exceed emulation
software
900 MB disk space. Includes installation
of DeskTop-VIP and Adobe Acrobat;
does not include Exceed emulation
software
Graphics Cards and Drivers
The test workstation graphics cards and drivers are specified below:
18 GB Project Database disk space
(10,000 RPM SCSI)
36 GB Project Database disk space
(15,000 RPM SCSI)
OpenGL-compatible AGP Graphics Card OpenGL-compatible AGP Pro Graphics
Card
16 Megabytes of Memory for Graphics
Adapter
64-128 Megabytes of Memory for
Graphics Adapter
Test Machine Graphics Card Driver Version
Graphics
Memory
Bios
Type
Bios Version
Dell Precision 530 Dual
Xenon
NVIDIA QUADRO4
700XGL
2.8.4.1 64 MB AGP 4.25.0023
IBM Intellistation Mpro NVIDIA QUADRO4
900XGL
2.8.5.6 128 MB AGP 4.25.0029
Dell PowerEdge Server
2560
Cluster Technology -- compute server not graphics server
Dell Precision 420 3DLabs Oxygen GVX210 2.15-0285 32 MB 2.16
Dell Precision 610 ELSA Synergy III Quadro
2 MXR
5.13.01.1240 32 MB AGP 3.11.00.18.10
IBM A310p P4 ATI FireGL 7800 5.13.1.6025 64MB AGP 006.000.006.
007
Dell Precision P4 Model
HM50 laptop
NVIDIA QUADRO4 500
GoGl
6.13.10.2835 64MB AGP 4.17.00.22.F8
IBM ThinkPad T20 P3 S3 Graphics Savage/
IX1014
5.12.12.1.7081 8MB 4.02.50.64
Compaq SP 750 ELSA Synergy III Quadro
2 MXR
5.12.01.0758 32 MB AGP 3.11.00.18.10
Compaq AP550 ELSA Gloria. II 5.03.05.172 64 MB AGP 7.05.00
Compaq Pro Workstation
6000
NVIDIA GeForce MX 5.12.01.0618 32 MB PCI 3.11.00.07
Table 1: Windows 2000 System Requirements
Minimum Recommended
Software Requirements
The following software must be installed:
X Server Software Hummingbirds Exceed 7.1 and Exceed 3D 7.1 (Refer to
Appendix E: Installing Hummingbird Exceed 7.1 on Windows 2000.
Adobe Acrobat Reader 5.05.
Licensing software, FLEXlm 7.2e (or connectivity to another licensed server
on the network).
NOTE: You should install these products using the Administrator account, not a
user with administrator privileges.
X Server
An X Server should be installed on your machine prior to installing DESKTOP-
VIP to enable the automatic setup of environment variables. DESKTOP-VIP
R2003.4 version for Windows 2000 was certified with Hummingbirds Exceed
and Exceed 3D 7.1. To configure Hummingbird Exceed 7.1 to work properly
with the DESKTOP-VIP applications, please refer to Appendix E: Installing
Hummingbird Exceed 7.1 on Windows 2000 on page 79.
NOTE: Although preliminary testing has not found problems, VIP 2003.4 is not
certified to work with Hummingbird Exceed 8.00, nor will problems
associated with this version be supported.
The settings provided in this document are optimized for VIP. If you are also
planning to use your PC for remote display of other Landmark applications,
please refer to the settings and patch level requirements defined in the the most
current Release Notes for the other product(s). Typically, these settings will also
work with VIP.
Adobe Acrobat Reader Version 5.05
This software package is available for installation from the Desktop-VIP
Windows 2000 CD (Volume 17), or it may be obtained free of cost from the
Adobe Acrobat Reader site at:
http://www.adobe.com/prodindex/acrobat/readstep.html
Installation instructions can be found in Appendix F: Installing Adobe Acrobat
on page 85.
FLEXlm Version 7.2e
FLEXlm Client
If you are running a centralized FLEXlm server, then you will not need to install
the FLEXlm server. You only need to point to the location of the license file on
the centralized server.
FLEXlm Server
The FLEXlm server is not included with Desktop-VIP R2003.4. It can be
obtained in one of the following ways, depending on the version you have:
The VIP installation procedure includes instructions to uninstall all previous
versions of VIP and related software, including FLEXlm. All previous versions
of FLEXlm must be uninstalled before you begin installing the new version.
Windows/Unix Configuration
If you are running on a Windows/Unix configuration, it does not matter which
machine is running the FLEXlm license server.
Running the Server Locally
If you plan to have a server running locally, be sure to read the FLEXlm
Installation Guide provided in Appendix D: FLEXlm Licensing on page 65.
Software Version You Have Where to Obtain FLEXlm Server
VIP Windows R2003.0 installed
VIP R2003.3 Unix/Linux installed
You do not need to upgrade FLEXlm. Your server is cur-
rent.
Same as above but not installed Obtain the FLEXlm installation software from CD1
(Windows R2003) or CD3 (Unix/Linux R2003.3).
Version prior to R2003 or new cus-
tomer
Contact Landmark Customer Support.
Unique Parallel Requirements
Parallel-VIP can be run on multiple CPUs using Criticals MPI software
PaTENT. Parallel-VIP was certified on Windows 2000 using the PaTENT
software. In order to run Parallel-VIP, you must have the PVIP and PNPROC
(Parallel Number of Processors) features within your FLEXlm license file.
Software Requirements -- Critical MPI Software
The Critical Software, Inc. MPI (Message Passing Interface) software package,
PaTENT, is required and is supplied on the DESKTOP-VIP CD. A password is
required to install the software and should be obtained from Landmark
Distribution. Refer to Appendix A: Installing PaTENT for Parallel Computing
on page 43 for the location of the PaTENT installation file and instructions.
Hardware Requirements -- Critical MPI Software
Requirements include a Windows 2000 workstation or server with two or more
CPUs in a single machine or a cluster of Windows 2000 workstations (two to
four) with one or more CPUs. It is also recommended that sufficient disk be
added to provide adequate paging and storage space. The information required to
set up multiple Windows 2000 machines to run Parallel-VIP is described in
Appendix A: Installing PaTENT for Parallel Computing on page 43.
For certified parallel cluster configurations, please contact your Landmark sales
representative.
Include File Configuration Requirements
Depending on your machine type(s) and the location of the simulator, working
directory (in relation to the simulator), and include files (in relation to the
working directory), you must adhere to specific configuration requirements.
Each possible configuration and the associated requirements are detailed in the
PDF document IncludeFileRules.pdf, which can be accessed from the Help menu
(Help > Submit > Include Paths). Configurations are also provided in Excel
spreadsheet format in the document BoulderSubmission.xls. Both documents can
be found in %VIPHOME%\doc\help.
Warning
Be sure to read the IncludeFileRules document carefully. This document provides a spreadsheet
to help you find your configuration options and the setup rules that must be met.
Other Issues
Landmark has implemented a Web-based online support database. This database
can be found at www.lgc.com/customersupport/. It provides information on
solutions and workarounds for known issues.
Known System Issues
Windows 2000 users need to be aware of the following issues.
General Known Issue -- pcAnywhere/Exceed Conflict
There is a sporadic problem that can cause Exceed to stop running with
pcAnywhere version 10.5.1. From your host machine, simply stop pcAnywhere,
start Exceed, and restart pcAnywhere.
VIP Issues
Spaces are not permitted in the installation path nor the working directory.
For example: C:\Program files\VIP\ and D:\My Data Sets\
The default installation directory is set for C:\Landmark\VIP. We have
experienced no problems installing to other local hard drives (such as D:\)
should you be short of space on your C:\ drive.
Several applications in the suite for Desktop-VIP for Windows were ported
from UNIX using Nutcracker. You will notice that the older applications have
the same look (Motif) as the UNIX versions of Desktop VIP. Due to the
porting method, the window-close icon (X in the upper righthand corner) is
non-functioning. We recommend using the formal window closing
mechanism; i.e., selecting File > Exit from all windows. For example, to
close the Plotview legend do not click on the Window Manager Close Icon,
X. Use the Plots > Attributes Panel to remove the legend. This condition
does not exist in the native JAVA applications.
The installation of Nutcracker libraries requires Administrator account
privileges. Installing as anything other than Administrator can cause
problems with the uninstallation of Nutcracker libraries. These libraries are a
subset of the MKS toolkit.
The Data Studio Perforation Wizard creates a temporary case called
tempDummyCase in the VDB to allow 3DView to launch. Do not name a case
tempDummyCase or it will be overwritten without warning when you use the
Perforation Wizard.
All on-line Help documents can be reached from the main Desktop menu (last
option on right end of the task bar.) Except for the SimResults application,
Help buttons that exist within individual applications are currently non-
functioning.
When working as a stand-alone system (or on a system previously removed
from a network) it will be necessary to enter a dummy IP address, as both
FLEXlm and Criticals PaTENT software require TCP/IP. For example, if the
system was previously connected to a network: log in as administrator, select
Settings from the start menu, select Control Panel, click on the network icon,
modify the Microsoft TCP/IP properties panel to specify a dummy IP
address.
You should adhere to the following restrictions for parallel simulation:
DESKTOP-VIP has exhibited sensitivity to disk shares and certain file
permissions. Nutcracker ls -l has a known problem of not representing file
permissions correctly. Resharing the drive or modifying the permissions
through the Windows 2000 drive property settings has proven effective in
rectifying most problems.
Node names used in the Job Submittal interface panel are case sensitive.
Be certain that the name is spelled correctly; otherwise, unpredictable results
may occur. From a command prompt, type in "hostname" to get the correct
name of the node.
In order for UNC paths on Windows platforms to be correctly accessed by
VIP, a parent directory in the path must be shared with a user-accessible name.
For instance, if the working directory followed the format
C:\temp\user_remote\studyname\casename\, the following would be sensible
share options:
VIP can use any of the above shared names to create a valid UNC path.
Please note that even though Windows automatically shares root drives, it
shares them as Administrative shares (denoted by $) which is insufficient for
VIP parallel submissions. Shared drives can be viewed and set by typing net
share at a command prompt.
For Windows parallel distributed jobs across several nodes using a network,
all include files must be specified using the UNC. For example, on machine
vipnt the path for c:\spe9\spe9.lgr would be specified as
\\vipnt\c\spe9\spe9.lgr. Spaces in the directory path are not permitted.
If you submit Parallel VIP jobs from the command prompt, the environment
variable pwd should be set to the current working directory. This will allow
proper execution should parallel debug output be required.
Shared Name Local Path
C or Cdrive C:\
or Temp C:\temp\
or Username C:\temp\user_remote
For parallel runs across different machines, at least one process must be run
locally. Specify the local machine name as the first node on the Nodes tab
of the job submittal interface panel.
Node names cannot have spaces.
Integration Issues
VIP and OpenWorks utilize Nutcracker libraries for most applications.
Killing an application (such as Gridgenr) at the Windows Task Manager
Application level will result in killing Nutcracker and therefore all other
applications that are currently utilizing Nutcracker. If necessary to kill, utilize
the End Process button after highlighting the offending executable, under
the Processes tab in Task Manager.
The environment variables "port number" and "machinename" do not work
with the VIP NutCracker applications. The workaround is to make a copy of
the license.dat file on the local machine and set the LM_LICENSE_FILE
variable to point to it.
Well naming conventions, including unique well identifier (UWI), should be
planned prior to populating OpenWorks. If using well information imported
from an OpenWorks project, Gridgenr will create a well database file (*.wdb)
that cross-references the OpenWorks well names with VIP well names. The
VIP simulator has an eight character limit and does not allow special
characters. Well names passed from Gridgenr are truncated to the last eight
characters with special characters replaced by underscores. If populating an
empty OpenWorks project through dbplot, the truncated VIP well name will
be specified as the UWI.
When importing production data from OpenWorks into VIP Data Studio, you
can choose to sum any or all zones in any or all wells, depending on the
simulation area of interest. VIP Data Studio will write the summation to the
OpenWorks Production Data Mart (PDM) tables using VIP as the data
source and SUM as the zone name. There is currently a limit of one SUM
zone. If zones/wells selected are changed or re-summarized, you will be
prompted to choose whether or not to replace the existing OpenWorks SUM
zone.
Scenario names written to the PDM economic tables (PDM_Econ_Monthly)
in OpenWorks are limited to 20 characters currently. The default scenario
name is CaseName$StudyName truncated to this limit. The user will need to
verify that the default does not duplicate an existing scenrio name or the table
will be overwritten.
"Z" null values for grids imported into GridGenr from OpenWorks are
incorrect. To work around this problem
Export the model as .gtf file
Edit the .gtf file to correct the null values
Reimport into GridGenr.
FLEXlm heartbeat detection (loss of) yields two command prompt panels:
one that gives correct information regarding license daemon and one window
that is unintelligible.
Desktop-VIP 2003.4 Release Notes Page 21 Installation
Installation
Setup Information
The following software must be installed before using DESKTOP-VIP R2003.4:
Hummingbirds Exceed 7.1 and Exceed 3D 7.1. Refer to Appendix E:
Installing Hummingbird Exceed 7.1 on Windows 2000.
Adobe Acrobat Reader 5.01 (located on the DESKTOP-VIP installation CD).
Refer to Appendix F: Installing Adobe Acrobat on page 85.
FLEXlm 7.2e (located on the DESKTOP-VIP installation CD). Refer to
Appendix D: FLEXlm Licensing on page 65.
If you have a DESKTOP-VIP version installed that is older than R2003.0, you
must uninstall VIP and all related software before installing DESKTOP-VIP
R2003.4. Related software includes LAM W2000 (version 7.1f for W2000),
Patent, and Nutcracker (Operating Environment and Basic Unix Utilities).
W2000 Nutcracker libraries are incompatible with the new version of VIP.
If you have DESKTOP-VIP version R2003.0 installed, it is strongly
recommended that you uninstall it before installing version R2003.4. However,
you do not have to uninstall the Patent, Nutcracker, and FLEXlm software that
was distributed with version R2003.0. You should uninstall older versions of
Adobe Acrobat Reader since an upgraded/enhanced version is distributed with
this R2003.4 release.
Decide Where to Install the Software
The software can be installed in any location. The default location is
C:\Landmark. The installation creates a VIP directory automatically. For this
documentation, it is assumed the software will be installed in C:\Landmark.
Therefore, whenever C:\Landmark is used in these instructions, the actual
installation location should be used. Please note that, if the software is installed
on a drive other than C:, DESKTOP-VIP still requires 100 Megabytes of free
disk space on the C: drive to successfully complete the installation.
WARNING: Do not use blank spaces for installation directories or working
directories.
Uninstallation of Older DESKTOP VIP Versions
DESKTOP-VIP cannot be uninstalled/reinstalled from Administrator if it was
installed as a user with Administrator privileges. It is strongly recommended to
install as Administrator. Refer to Appendix H: Uninstall Older Versions on
page 89.
Install Acrobat Reader
Acrobat Reader, which is provided on the DESKTOP-VIP installation CD,
should be installed prior to installing DESKTOP-VIP. Refer to Appendix F:
Installing Adobe Acrobat on page 85.
DESKTOP-VIP R2003.4 Installation on Windows 2000
1

The DESKTOP-VIP R2003.4 for Windows 2000 installation should be
performed as Administrator. Verify that the directory C:\TEMP exists. This
directory is available automatically in most Windows 2000 installations. If it
does not exist, create the directory.
The installation will run in an auto-startup mode after the CD is loaded into the
CDROM drive. If, however, auto-start mode is not active on the computer, you
can also execute it by doing the following:
1. Click Start in the Windows Taskbar.
2. Select Run.
3. In the ensuing dialog, type: <CDROM drive letter>:\Install.EXE
4. Click OK.
5. The Landmark Product Screen opens. Click OK on this screen to continue.
6. The first Volume 17 screen opens. Click on DESKTOP-VIP.
7. The second Volume 17 screen opens. Click Install. This initiates the
Installation Wizard
8. Click Next on the Wizard Welcome screen.
9. The User Information screen opens. Verify your user information and click
Next.
1.This product includes software developed by the Apache Software
Foundation (http://www.apache.org/).
10. The Install Location window opens. The default top level directory is
C:\Landmark. If you wish, click the Browse button and filter to the top level
directory you prefer. Click Next when the path is correct.
NOTE: Do not select a directory path that contains a space in the directory name (for
example, the directory C:\Program Files).
11. The Current Settings window opens. Verify your settings and click Next. (Or
click the Back button to make any necessary modifications to your settings.)
12. Read the warning message. You are asked whether or not youd like this
computer to host remote VIP simulation sessions. If you are planning to use
this computer for PC-PC remote submittal, you should click YES.
(The instructions for the process described in this warning are provided in
Appendix C: VIPrshServer & VIPrshClient Utilities on page 61.)
13. You receive a warning message if you do not have OpenWorks installed.
Click OK to close this message.
14. The Setup Complete window opens. Click the Yes I Want to Restart my
Computer Now option on the window. Then click Finish.
The computer will reboot.
Desktop-VIP 2003.4 Release Notes Page 25 Setting the Environment
Setting the Environment
Windows 2000 Systems Setting the Users Environment
It is critical that Windows 2000 users of DESKTOP-VIP be assigned Power
Users privileges. Set up for Windows 2000 users are explained in this chapter.
Setting User Privilege
The user of DESKTOP-VIP must have Power Users or Administrator
privileges. To determine if a user has the proper privileges, type net share in
an MS DOS window. Any user who is unable to execute the command is a
simple user and does not have the proper privileges to run DESKTOP-VIP.
Setting Color
Check the color palette setting of the users display. If possible, it should be set
to True Color. For some Windows 2000 machines, this is not possible because
of the amount of graphic memory that can be added to the machine (64
megabytes is recommended) or some limitation of the graphic card itself. To
check on the color palette setting, perform the following:
1. Select Start >Settings >Control Panel.
2. Double-click on the Display icon.
3. Select the Settings tab.
4. Change the Color Palette setting to True Color, or the highest color setting
possible.
5. Click OK to make the change and exit the dialog.
Setting up the System
You will receive a copy of DESKTOP-VIP on CD. Along with the CD you will
receive installation instructions which also can be found in a pdf format.
Before Installing VIP
Before VIP installation, both Adobe Acrobat and Exceed should be installed.
During the VIP installation, the installer checks for the pathnames of both Adobe
Acrobat and Exceed and sets up the following variables:
VIPACROBAT
VIPEXCEED
If one or both are not installed prior to VIP, then the administrator (or user with
administrative privileges) has to set up the corresponding variables.
ENVIROMENTAL VARIABLES
DESKTOP-VIP uses a variety of environmental variables to define various
installation parameters. These variables are set automatically during installation.
The path specified below is the location that is used when all defaults are
accepted. Deviations from default locations will change the environment
variable pointers. For convenience, all applicable platforms for each
environment variable are listed.
System Variables
During installation, the following System Environment Variables are
automatically set.
Name Default Value Description Name Platform
VIPHOME
(VIPNTHOME)
C:\Landmark\VIP Directory where the
software is installed
VIPHOME
(VIPNTHOME)
All
VIPEXEC $VIPHOME\dtvip\exec Location of the exe-
cutables files, menus,
configuration files,
etc.
VIPEXEC All
VIPSIM $VIPHOME\dtvip\sim Location of the simu-
lators
VIPSIM All
VIPJAVA $VIPHOME\dtvip\lib\j2re1.4.0\bin\java.exe Location of the JAVA
executable
VIPJAVA Windows
Desktop-VIP 2003.4 Release Notes Page 27 September 2001
XENVIRONMENT Resource File Definition
Starting DESKTOP-VIP for Windows 2000 will set the following default
environment variable.
VIPACROBAT C:\PROGRA~1\Adobe\ACROBA~1.0\Acro-
bat\Acrobat.exe
Location of the
Adobe Acrobat exe-
cutable
VIPACROBAT Windows
VIPEXCEED C:\Program Files\Hummingbird\Connectiv-
ity\7.10\Exceed\\Exceed.exe
Location of the
EXCEED executa-
bles
VIPEXCEED Windows
VIPTEMP C:\TEMP Location of the VIP
Temporary Files
VIPTEMP Windows
VIPPLOTTIME YEARS Set to DAYS or
YEARS
VIPPLOTTIME Windows
VIPMAPUNITS ENGINEERING Choices are: ENGIN-
NEERING, MET-
RIC, KG/CC, Name
of specific File
VIPMAPUNITS Windows
VIPPLOTUNITS ENGINEERING Choices are: ENGI-
NEERING, MET-
RIC, KG/CC, Name
of Specific File
VIPPLOTUNITS Windows
VIPWELLSORT If set DBMAP will
sort well perforations.
Default is not to sort
VIPWELLSORT Windows
LM_LICENSE_FILE C:/Landmark/Lam/license.dat LM_LICENSE_FILE C:/Landmark/Lam/
license.dat
Windows
XENVIRONMENT %VIPHOME%/dtvip/exec/DeskTopVIP.NT
Name Default Value Description Name Platform
Simulator Selection Environment Variables Default Executables
Starting DESKTOP-VIP for Windows 2000 will set the following simulator
default environment variables:
If a user chooses to use a different simulator, the particular simulator name can
be changed by setting the appropriate variable before starting DESKTOP-VIP.
Or the user can switch between simulator versions on the Job Submittal panel.
VIP VDB Directory Structure and VDB Conversion
DESKTOP-VIP R2003.4 provides a new directory structure for the database file
(VDB). Among other advantages, this new VDB structure provides faster data
access and more data storage within a single study. The new VDB structure is
described in detail in the Starting and Using DESKTOP-VIP chapter of the
Getting Started manual. Although the old style VDB files will work with version
R2003.4, it is recommended that they be converted.
Convert old VDBs by running this command at the command-line prompt from
within the directory containing the old VDB:
%VIPHOME%\dtvip\exec vdbconverter <old_vdb_name> <new_vdb_name>
Variable Name Default Simulator Name Description Platform
VIPCOREDEF core2003r4.exe Defaulted name of VIP-CORE
executable
All
VIPEXECDEF exec2003r4.exe Defaulted name of VIP-EXEC
executable
All
VIPCORELOCALDEF pcore2003r4_local.exe Defaulted name of Parallel VIP-
CORE executable running local
IBM
VIPEXECLOCALDEF pexec2003r4_local.exe Defaulted name of Parallel VIP-
EXEC executable running local
IBM
VIPCOREDISTDEF pcore2003r4_dist.exe Defaulted name of Parallel VIP-
CORE executable running dis-
tributed
Windows, Sun, SGI,
Linux
VIPEXECDISTDEF pexec2003r4_dist.exe Defaulted name of Parallel VIP-
EXEC executable running dis-
tributed
Windows, Sun, SGI,
Linux
Desktop-VIP 2003.4 Release Notes Page 29 Running DESKTOP-VIP for the First Time
Running DESKTOP-VIP for the First Time
Windows 2000 Systems
Assuming that Exceed and Exceed 3D 7.1 were installed properly, the
DESKTOP-VIP installation was successful, and the license server (FLEXlm) is
running, either of the following two procedures can be used to start DESKTOP-
VIP for Windows 2000:
Select Start Menu > Programs > Landmark VIP.
Start a Command Prompt window and type in dtop. (This option is not
recommended if using default working directories within the Job Submittal
interface.)
If the users license.dat file contains the appropriate feature line, then it should
be possible to execute the suite of DESKTOP-VIP applications. A warning panel
will display if, for some reason, DESKTOP-VIP cannot connect to the license
server or if the users license.dat file cannot be found.
A quick test can be run by selecting one of the studies provided in the demo
directory that was installed under %VIPHOME%/dtvip/demo.
Support Simulator Workflows:
Local serial runs
Parallel runs using Critical PaTENT MPI software. Parallel runs
can be entirely local or spread across distributed systems. See Appendix A:
Installing PaTENT for Parallel Computing on page 43.
Remote UNIX and Linux serial and parallel run. For more information, see
Appendix B: Setup Instructions to Submit Jobs via Remote Shell on
page 49.
Remote PC -> PC serial and parallel runs. For more information, see
Appendix B: Setup Instructions to Submit Jobs via Remote Shell on
page 49.
Warning - Include File Locations
Each possible configuration has associated requirements for valid configurations and include
file locations. These are detailed in the PDF document IncludeFileRules.pdf, which can be
accessed from the Help menu. Configurations are also provided in Excel spreadsheet format in
the document BoulderSubmission.xls. Both documents can be found in %VIPHOME%\doc\help
Desktop-VIP 2003.4 Release Notes Page 30 Running DESKTOP-VIP for the First Time
Desktop-VIP 2003.4 Release Notes Page 31 Enhancements and New Features
Enhancements and New Features
Version R2003.4
This release of DESKTOP-VIP provides the following new and modified
features for both the Unix/Linux and Windows versions.
VIP-Executive
The following notes describe features which were added or modified in VIP-
EXECUTIVE. Some of these features offer new capabilities and others offer
better efficiency. Features that are pertinent only to VIP-CORE or VIP-EXEC
are listed separately.
General
1. Change bars specific to version R2003.4 have been retained in the CORE and
EXEC user manuals to aid the user in quickly locating new/modified
information.
2. Note: VDB and map files have always been required to have ROOT as the
root grid name. If the root grid is renamed in VIP-CORE (LGR ROOTGRID
option), all input data is required to use this name and output files will reflect
this name, but applications such as 3DView that read from the VDB will show
the root grid as ROOT.
New Features
1. Version-independent restart files: The restart files have been restructured
to enable the flexibility of version-independent restart files. For all future
versions, VIP-EXEC will be able to restart from any prior restart files,
eliminating any requirement to rerun the entire study when moving to a new
version. A utility program is provided to convert current R2003.x restart files
to the new structure, enabling R2003.4 to restart from converted R2003.x
restart files.
Converting Restart Files:
Modify script for VIPHOME. Using your text editor (such as Notepad or
vi), open the script file (rstconv.bat on Windows or rstconv.ksh on Unix/
Linux) located in your VIP directory path /vip/dtvip/cvrst. On the following
line, edit the file to point to your VIPHOME location.
set VIPHOME=net/machinename/vip
Save and close the file.
Run the conversion. In the case file directory, type the following at the
command line prompt:
rstconv <oldrestartfilename> <newrestartfilename>
You need only specify the base restart file name (filenamei.rst) for a CORE
run and base output restart file name (filenamer.rst) for an EXEC run. The
script will then read and convert multiple restart files: filenamei.rst,
filenamei.rst0, filenamei.rst1, ... , where a numbered file is expected for each
grid.
2. Control of gas re-solution rate: In conjunction with the new extended form
of the black-oil PVT tables (BOETAB, etc.), a new DRSDT variable has been
added which enables the user to limit the rate of increase of the solution gas-
oil ratio, Rs.
3. Multiple water properties regions: Enables the user to specify different
water PVT regions, with different properties in each region, in a manner
analogous to the specification of different hydrocarbon PVT regions.
4. Water properties variation with salinity: Allows the user to specify the
variation in water properties as a function of salinity for any water PVT
region, enabling more precise modelling of fresh water injection. The salinity
of the injected water can be specified for each water injection well.
VIP-CORE
1. Aquifer connections to LGRs: Enables aquifers to be connected to any
gridblock within any grid, rather than being limited to the base grid, only.
2. Limits removed for the reference depth for the initial pressure in an
equilibrium region which has an active gas-oil contact: The reference
depth for the initial pressure in an equilibrium region involving an active gas
cap is now allowed to be outside of the oil leg, since the phase pressure
profiles will be based on the saturation pressure at the GOC.
3. XREG values can be read for each gridblock. XREG data can also
be read using a value for each gridblock in the window. Previously,
only one value could be applied to the whole window.
Known Issue:
1. The CORE keyword VDB filename.vdb only works for local runs.
VIP-EXEC
1. Enhancements to the production Surface Pipeline Network (SPN) option:
A number of enhancements have been made to the production SPN. These
include the following:
a. Optional well rate and gaslift gas rate optimization.
b. Pseudo well option for satellite field modelling.
c. Allow multiple output streams from nodes.
d. Simplified heat-transfer analysis extended from wells to nodes.
2. Basic implementation of an SPN for injection wells: Enables a separate
network to be defined and used for the injection system.
3. Optimization of gaslift gas utilization at all targeting levels: Enables the
user to solve for the minimum gaslift gas required to make the production
targets at any level, outside of SPN.
4. IMPWEL now available with OPTMBL and Crossflow: The implicit well
option with the IMPES formulation can now be used in conjunction with both
OPTMBL and the wellbore crossflow options.
5. Threshold pressure option for fault flow: Enables the flow across a
specified fault to be blocked until the pressure potential exceeds the specified
threshold. When exceeded, the potential is reduced by the value of the
threshold, and flow is allowed based on the adjusted potential.
Modified Features
VIP-CORE
1. Automatically connect analytical aquifers to only gridblocks below the
water-oil contact: In previous versions, connections were made to all
gridblocks specified, irrespective of whether they were above or below the
contact.
Fixed Problems
1. MULT PLUS data now propagates correctly to children LGRs.
2. MULTFL now works correctly with LGR or DECOMPOSE and no longer
results in convergence failures in EXEC.
3. Some pinchouts across LGRs with OMITs could be missed.
4. Multi level LGR or DECOMPOSE grids no longer have corrupted map files
that cannot be loaded into 3DView.
VIP-EXEC
1. Support for both previous algorithm and iterative damping for
OPTMBL: In the R2003.0 release, iterative damping was introduced with no
ability to request the old algorithm. Now the old algorithm is the default, and
iterative damping may be requested by specifying DAMP on the OPTMBL
card.
2. Support simultaneous THP and BHP constraints for wells: The simulator
will now allow and utilize both THP and BHP constraints for a well
simultaneously, honoring the more restrictive of the two. Previous versions
would use only the last one entered, negating either of the two previously
entered.
3. Make-up gas rate and composition of injected gas: The actual required
rate of make-up gas to satisfy the gas reinjection requirement is now correctly
calculated and reported, as well as the correct injection gas composition
involving the produced gas plus required make-up gas.
4. Default for the automatic solver cutback changed to OFF: In the R2003.0
release, a new feature was introduced within the solver to attempt to
determine either very slow convergence or divergence, and terminate the
solution effort, with the idea being to save the excess CPU time of continuing
to maximum iterations and then cutting the timestep. After finding several
models in which this hurt the overall performance, the default is changed to
OFF, and the user must explicitly turn it on if deemed necessary.
5. Enhanced convergence and constraints on the welbore gradient methods:
Enhanced convergence criteria and tighter constraints within the iterative
wellbore gradient calculations now yield much better performance for a few
special cases wherein the previous versions produced premature shut in of
some wells.
6. Numerous additions to the various output files: Significant additions have
been made to the output capabilities of the spreadsheet, plot, and map files.
Fixed Problem
1. Excessive memory utilization in the solver for inactive gridblocks.
VDB Database
The following notes describe features which were added or modified in the VDB
database.
1. New structure implemented: A new VDB directory structure has been
implemented to replace the single-file VDB model. This new structure:
Allows for faster data access
Allows more simulation runs for a single study without hitting the 2GB
file size limit
Eliminates the need for VDB defragmentation
The new VDB structure is described in detail in the Starting and Using
Desktop-VIP chapter of the Getting Started manual.
Convert old VDBs by running this command at the command-line prompt
from within the directory containing the old VDB:
vdbconverter <old_vdb_name> <new_vdb_name>
All DeskTop-VIP applications can easily handle both old and new style VDB
files. The command-line executable will also convert from the new to the old
format.
2. VDB control file provided: An XML control file has been provided in the
top-level directory of the new VDB allows users to easily see the list of cases
and parent-child relationships among them
3. Simultaneous VDB access: Multiple VIP simulation jobs can now access the
VDB simultaneously.
DeskTop-VIP User Interface
The following notes describe features which were added or modified in the
Desktop.
1. GUI redesign and new features: The DeskTop user interface has been re-
written in Java, eliminating all dependencies on Tk/Tcl. It now has a
Windows look-and-feel, with features including docking/floating toolbars,
mouse-over tooltips, etc.
2. Improved study/case management: The new DeskTop user interface allows
the user to load multiple VIP studies onto the Desktop and easily switch back
and forth between active studies/cases. The VDB study/case hierarchy is now
visible to the user on the Desktop, and studies/cases can be added, deleted, or
modified from the Desktop. Data types contained in the study/case are easily
visible to the user at all times.
3. Study/case comments can be added: The user now has the ability to add
study/case comments which can easily be viewed.
4. Persistence of user preferences: Changes/preferences set by the user are
persisted from session to session.
5. Improved network access. The network can be now accessed from the file
selection dialog box.
VIP Job Submittal
The following notes describe features which were added or modified in VIP Job
Submittal.
1. GUI redesign and new features: The VIP Job Submittal interface has been
totally redesigned, with the emphasis placed on ease-of-use, job queueing,
and remote job submittal.
2. Input, output, and include files shown:. The Job submittal panel now
displays all input files, output files, and include files associated with a given
VIP job.
3. Improved simulation messages: The feedback to the user while jobs are
executing has been improved.
4. More control over the run: Jobs can now be run as a background process
and multiple jobs can run simultaneously. The user can now choose which
simulator version to use for each run.
5. Real-time plotting: A user-configurable feature has been added for real-
time plotting of simulation results while a job is running.
6. Local or remote queueing: Jobs can be queued to run either locally or
remotely.
7. Batch plotting for automatically-generated plots: Batch plotting has been
improved for automatically generating plots of simulation results. Output can
be sent to the default printer, to Microsoft Word document, Excel document,
Powerpoint document, or HTML files.
Known Issues
1. For remote runs using this release version, the directory that is one level
above the Study directory is reserved for remote copy procedures. Therefore,
no primary data files ( i.dat and r.dat ) or restart files ( i.rst and r.rst ) may exist
in the directory immedi-ately above the Study Directory. If they do, they will
be copied to the directory immediately above the remote working directory.
The simulator will not be able to find them during the remote run and the
simulation will fail
2. When specifying the location of include files, it is recommended that the user
always specify fully qualified paths. Relative paths will only work one level
higher (../) and one level lower (./); however there are situations where they
will not work at all.
3. The VDB option in CORE is not supported for remote jobs submitted from
Desktop-VIP, if the *.vdb file is to be automatically copied to the remote
machine. However, if the user manually copies the *.vdb file to the working
directory on the remote machine, the VDB option will function properly.
SimResults / SimResults+
A new Windows-based plotting package has been added to Desktop-VIP to
replace PlotView. (PlotView has been retained on the Desktop for this release.)
1. SimResults drag-and-drop GUI: SimResults provides all the functionality
that was available in plotview, within a drag-and-drop user interface for
creating X/Y plots and 2D maps.
2. SimResults+ enhanced functionality: SimResults+ provides additional
functionality, including:
Full batch plotting support via GRF scripting language
RFT plotting
User definable derived quantities
2D map display for VIP map data
Known Issues
1. If you have a new Windows 2000 machine, Microsoft Office must be installed
in order to run SimResults.
2. If you are a new user or have a new Windows 2000 machine, then the
message prompting for Office 2000 SR-1 disk is produced if SimResults (or
any application that has been compiled using Visual Studio) is run.
Work-around: This issue can be solved by running any office application
once, e.g. start Word then close it down.
VIP Convert
The following notes describe features which were added or modified in the VIP
Convert conversion utility.
1. Additional export capability: VIP Map, VIP CORE, Landmark Active
Field Surveillance (AFS) and Rescue files can now be exported from the
VDB study/case.
2. Additional import capability: RESCUE models can now be imported into a
VDB file.
3. VDB viewing from the VIP Convert application: A new VDB View
panel has been added to allow the numerical data contained in a VDB study/
case to be viewed.
4. Improved status reporting. Status reporting to the user while VIP Convert is
processing files has been improved.
VIP Data Studio
The following notes describe features which were added or modified in VIP-
Data Studio. Features that are pertinent only to VDS-CORE or VDS-EXEC are
listed separately.
1. External data can now be imported or entered: Data can be be parsed,
and unrecognized parsed data is now saved as an include file for import.
2. Summary (error) page provided: A summary page of the model is now
displayed to the user before the data set is generated. The summary provides
basic error checking (missing data, obvious errors).
3. Color-coded icons: Icons have now been added to each data type in the
options tree. A green icon indicates that all required data has been entered. A
yellow icon indicates that no data has been entered but none is required. A
red icon indicates that mandatory data is missing.
VDS-CORE
A user interface has been added to create basic CORE initialization files. It lets
the user parse an existing initialization file and import tables from existing
datasets. It also provides a creation wizard to quickly generate the basic
requirements for an initialization file from scratch.
Data Studio CORE supports the following data:
Basic utility data
Local grid refinement
Limited support for advanced utility features (Dual, Therm, etc.)
Equilibrium tables
Rock tables (relative permeability and compaction)
PVT tables for black-oil, water-oil, gas-water, EOS
Basic correlations to generate relative permeability tables and black-oil/
water-oil, gas-water PVT
EOS separators
Grid data through view for simple grid arrays or as include file
Grid Array functions
Grid Modifiers
Aquifers
VDS-EXEC
New production data options available. The Production Data panel now
supports:
Active Field Surveillance (AFS) file import
User-defined conversion factors through the import wizard
Class header definition for export to OBS format through the import wiz-
ard
Appending of imported pressure data after importing rates/volumes,
allowing different time frequency for pressure measurements
Generation of types and rate constraints from raw production data (no
averaging required)
New output options available: The Output panel now supports:
RFT output (well selection)
SSSUM option
Compositional MAPX/Y/Z and OUTX/Y/Z options
New well perforations options available: The Well Perforations panel now
provides:
An import wizard to generate VIP PERF cards from a simulation grid
within a VDB and some basic well data
Ability to filter displayed perfs by well, date, and/or well name
New well constraints options available: The user can now view all con-
straints for a well. The Well Constraints panel now supports the following
constraints:
Hydraulic table assignment
Gas Producer THP table assignment
Tubing length
Tubing diameter friction factor
Crossflow model activation
Minimum rate scale-back for targeting
New well hierarchy option available: Basic injection and production tar-
geting plus hierarchy ontime factors is now supported.
Known Issue
1. When launching 3DView from the VIP Data Studio perforation wizard, the
3DView main window sometimes locks due to an Exceed problem.
Workaround: close the DOS command window that comes up when
launching 3DView from the perforation wizard. (This will also close the
current 3DView without killing Exceed). Then relaunch 3DView from the
perforation wizard.
Grid Calculator (GridCalc)
The following notes describe features which were added or modified the
GridCalc utility.
1. GUI redesign: The user interface has been redesigned with a Windows
look-and-feel.
2. New trigonometric functions added: Sine, cosine, tangent, and square-root
functions have been added to the calculator pad.
3. Summation capabilities added: The user can now perform summations by
time or by layer.
4. Temporary variables can be created: The user can now create temporary
variables as building blocks for more complex permanent variables. The
temporary variables are deleted at the end of the session.
5. Improved error-checking and messages: The application now performs
more complete error-checking and provides better error messages to the user.
Known Issue
1. In GridCalc expressions, the program only recognizes VDB and Case names
that start with an alpha character. For example "name2" is a recognized VDB
or Case name in an expression, but "2name" is not. Workaround: if you
want to use a VDB or Case name that does not begin with an alpha character
in an expression, select it as the active Project and Case. Then create the
expression without specifying a Project or Case. When not specified, the
program assumes the current Project and Case by default.
Region Calculator (RegCalc)
The following notes describe features which were added or modified the
RegCalc utility, which replaces MapCalc.
1. GUI redesign: The user interface has been redesigned with a Windows
look-and-feel.
2. New features to aid in transfer of data to spreadsheet: A new Copy
feature lets the user easily copy data to the Clipboard to paste into a
spreadsheet application. A new Export feature lets the user quickly create a
tab-delimited file for import into a spreadsheet application.
3. Improved report options: Multiple timesteps can now be included in a single
report. New Print Preview and Column Layout control has been added to give
the user more control over the report hardcopy.
4. Improved error-checking and messages: The application now performs
more complete error-checking and provides better error messages to the user.
E2V
The following notes describe features which were added or modified the E2V
utility.
1. Extended black oil table data converted: Extended black oil table (e.g.
BOETAB) data is now converted to VIP format.
2. Multiplication data now converted: Data for multiplying named faults
(MULTFL) and multiplying transmissibilities between reservoir regions
(MULTIR) is now converted into VIP format.
3. Observed file can now be created: An option has been added to create an
observed data file (*.obs) during the conversion process.
4. Eclipse BHP reference depth can be converted: The default BHP reference
depth (depth to top perforation) from Eclipse has been added as an option.
5. Well scheduling data can now be created: Well scheduling data can now be
created in a compressed format based upon user selection.
6. Conversion improvements have been made: A variety of bug fixes have
been added to make the conversions more complete and reliable.
Known Issues
1. For Eclipse data sets containing non-monotonic PVT data, the converted data
set may report errors when run in VIP. In some cases, E2V slightly modifies
the data to cause monotonic behavior, but in other cases the data is not
adjusted.
2. The conversion of Eclipse gas and oil viscosity in the PVT tables cannot be
guaranteed. You should manually check and verify this data.
3. The conversion of MULTZ data in Eclipse to TMZ data in VIP may have
errors.
4. When Eclipse data has UTM coordinates, you must choose the right-handed
option in order to ensure the correct results. The left-handed option (default)
is not guaranteed to work correctly.
5. For VIP, the matrix and fracture systems must have the same equilibration
region specified by the IEQUIL array; there is no IEQUILF array. Eclipse
allows the matrix and fracture systems to have different equilibration region
specification for each grid block.
6. GASWATER and WATEROIL options are not allowed in VIP-DUAL.
GridGenr
The GridGenr model size limitations were retested with the following results:
1. Grid points per zone. The maximum number of grid points per zone
increased from 60,000 to 300,000.
2. Mesh size. The maximum size of a mesh increased from 500,000 to
1,000,000.
Desktop-VIP 2003.4 Release Notes Page 43 Appendix A: Installing PaTENT for Parallel
Appendix A: Installing PaTENT for Parallel
Computing
Introduction
The Critical MPI (message passage interface) software, PaTENT, allows for
parallel simulation in a limited number of environments using either a single
workstation with multiple CPUs or clusters of workstations with one or more
processors, each connected via a high-speed network (normally a gigabit
network connecting the workstations in the cluster).
This document describes the procedures necessary to perform the installation
and to prepare existing Windows 2000 workstations to use the PaTENT software
for parallel VIP executions. The following topics describe a point solution which
is the best available that is known to work at the time of certification. Do not
attempt to deviate from this procedure without prior consultation from a
qualified agent of Landmark Graphics.
Location of Documentation
For more information on the company, Critical Software and their MPI
software, PaTENT, please refer to the URL below.
http://www.criticalsoftware.com/
On-Site Configuration
This topic describes the steps necessary to configure a machine on the Windows
2000 network.
Assumptions About the Customer's Network
The TCP/IP protocol will be the sole means of communication among SMP
parallel Windows 2000 workstations.
Any existing Windows 2000 workstations must either reside on a static IP
address or are assigned one dynamically via DHCP. In either case, the
Domain Name Server (DNS) on the network should have a proper record of
Parallel Computing Quick Guide
Refer to the Parallel Computing chapter of the Getting Started manual for a helpful
introduction to parallel computing.
the qualified and unqualified hostnames for all machines that will use the
Parallel VIP software across the network.
In other words, if your domain is urdomain.com and there is a machine NTM
that is obtaining an IP address dynamically, the DNS should have a proper
record of both NTM and NTM.urdomain.com which points to this IP address.
If there is no DNS or it is not properly configured, then each client and server
node must have a record of every other node's qualified and unqualified
hostname in its C:\winnt\system32\drivers\etc\HOSTS file.
Verify that the machines to be used in parallel simulations can ping each
other, both by qualified and unqualified hostname, and that the names resolve
to the Ethernet IP addresses. For example, you should get the following
output when you ping NTM and when you ping NTM.urdomain.com:
Reply from 100.100.79.82: bytes=32 time<10ms TTL=128
Configuring the Client Machines
Use the following information to configure the client machines.
Assumptions
Windows 2000 Professional Workstation or Windows 2000 Advanced Server
is already installed on each system.
Each workstation and its hardware/software configuration meet the
requirements for DESKTOP-VIP.
Procedure
On each workstation that will be used to run parallel simulations, perform the
following steps:
1. Login as local administrator.
2. Verify that the machine is running Windows 2000 Service Pack 1 or 2. If not,
upgrade it before continuing.
3. Install the DESKTOP-VIP software. For consistency, it is recommended that
all installations be in the same directory structure, but this is not required.
Please refer to the restrictions at the end of this Appendix before beginning
the installation. The installation of DESKTOP-VIP is required for each
workstation or server that will be used for parallel simulations. The
installation must be done as administrator and the installation directory name
must not contain spaces.
4. Verify that you have received the required parallel FLEXlm license features
and PaTENT installation password and serial numbers from Landmark. If you
have not, contact your sales representative or the Landmark License
Administrator.
5. To install the PaTENT MPI software, perform the following steps:
cd to the location of the PaTENT installation in the VIP directory tree. If
you selected defaults on the DESKTOP-VIP installation, cd to:
C:\Landmark\vip\dtvip\lib\Critical_PaTENT
Execute the PaTENT installation executable, patentmpi4.0.exe.
Accepting the installation defaults will install the software under
C:\Program Files\GENIAS Software\PaTENT MPI. For consistency, it is
recommended that the location of the PaTENT software should be the
same on each workstation.
When prompted, enter the PaTENT installation password and serial
number.
When you are asked for the installation type, select Compact.
After the installation has completed, reboot the machine.
6. Login as local administrator and perform the following steps:
Make the following selection in the Windows Taskbar:
Start Settings Control Panel
Double-click the Administrative Tools Icon.
Double-click the Services Icon.
Locate and highlight PaTENT MPI.
Please notice if the service is up and running. (It will say started in the
status column of the services dialog box.)
With the line highlighter, select the Stop option on the Action menu if the
service was started.
Error Message -- Unzip the file
If you get an error message, unzip the file using WinZip. Then select the file
setup.exe.
Once it is stopped, select the Properties option on the Action menu to
configure the automatic startup. This opens the tabbed Properties dialog
box.
Under the General tab, verify that the Startup Type is set to automatic.
If not, select it from the menu.
Under the Log On tab, activate Log On As, click This Account.
Type administrator in the This Account field.
Enter the appropriate password for administrator on your system, and
verify.
Click Apply to apply the changes. Then click OK.
7. Click Start on the Services Panel. The PaTENT MPI service should indicate
that it has started and will startup automatically.
Click Close.
Once you complete this process for each parallel workstation, Parallel-VIP will
be ready to use.
Restarting MPI Service for TMP/TMPDIR Changes on Remote
Nodes
On any particular node, system temp (scratch) files go to the directory assigned by
the environment variable TMP. VIP scratch restart files go to the directory
assigned by the environment variable TMPDIR. For the remote nodes, the TMP
and TMPDIR values at the start of the Patent MPI service is what is used by any
process that starts on the node. Therefore if either is changed on a remote node,
the Patent MPI service needs to be restarted before the new value takes effect.
Restrictions
You should adhere to the following restrictions:
1. When you submit Parallel runs across workstations, the administrator pass-
word must be the same on all workstations
2. Parallel VIP has exhibited sensitivity to disk shares and certain file permis-
sions. Nutcracker ls -l has a known problem of not representing file permis-
sions correctly. Resharing the drive or modifying the permissions through the
Windows 2000 drive property settings has proven effective in rectifying par-
allel problems.
3. Node names used in Parallel job submittal are case sensitive. Be certain that
the name is spelled correctly; otherwise, unpredictable results may occur.
From a command prompt, type in "hostname" to get the correct name of the
node.
4. For parallel jobs to work correctly, there must not be any spaces in the VIP
install directory. For example, c:\Program Files\VIP... will not work for a
parallel install directory for VIP.
5. If a decomposition is changed in the initialization using vipcore, the Parallel
Options panel may need to have the Grid File reloaded to reflect the new
decomposition in the job submittal. For example, if you change from a serial
run to a parallel decomposed run in the same session of Submittal, then
check the Grids List in the Parallel Options panel and make certain that it
corresponds to the new decomposition. If it does not, or if you are uncertain,
right-click on the Grid-list and select "Load Grids." This should reload any
updated changes to the Parallel Grids.
6. Do not include any spaces in the hostname.
Each possible parallel configuration has associated requirements for valid
include file locations and configuration requirements. Configurations and
requirements are detailed in the PDF document IncludeFileRules.pdf which can
be accessed from the Help menu (Help > Submit > Include Paths).
Configurations are also provided in Excel spreadsheet format in the document
BoulderSubmission.xls. Both documents can be found in
%VIPHOME%\doc\help.
Warning
Desktop-VIP 2003.4 Release Notes Page 49 Appendix B: Setup Instructions to Submit Jobs via
Appendix B: Setup Instructions to Submit Jobs
via Remote Shell
Overview
DESKTOP-VIP Version 2003.4 will supply pre/post applications on Windows
2000 platform only. The only applications provided on Unix and Linux will be
the serial and parallel simulators. The implication of this structure is that all
simulation jobs, both serial and parallel, will be submitted from the Windows
2000 machine. A user can submit jobs locally, remotely to another Windows
2000 machine, or remotely to a Unix or Linux machine.
For remote submittal to work properly, the machines (Windows 2000 and Unix
or Linux) must be able to communicate to each other using remote-copy (rcp)
and remote-shell (rsh) commands. They must be able to ping each other
without having to know the Internet Protocol (IP) address of the other machine.
For this reason Name Resolution is one of the critical requirements for remote
submittal to work properly.
Typically there are two types of network systems that are found in our
customers offices. The first is geared to larger companies who are using a fully
integrated network made up of name servers: DNS (Windows 2000/Unix or
Linux) or WINS (NT) utilizing the dynamic host configuration protocol
(DHCP). They will have both Windows and Unix/Linux machines on a single
network with dynamic IP addressing. The second type is geared to a small
business that has a simple network, is not made up of servers and has fixed IP
addresses and naming conventions. The small business network may also
include Windows, Unix, and Linux machines.
For large and complex networks, the following simplified diagram (Figure 2)
represents the components required for Name Resolution of devices
dynamically across the network.
Each possible remote configuration has associated requirements for valid
include file locations and configuration requirements. Configurations and
requirements are detailed in the PDF document IncludeFileRules.pdf, which can
be accessed from the Help menu (Help > Submit > Include Paths).
Configurations are also provided in Excel spreadsheet format in the document
BoulderSubmission.xls. Both documents can be found in
%VIPHOME%\doc\help.
Figure 2
Every client machine in this architecture can ping the other by name and does
not have to know the IP address of the other machine. The DNS server works in
conjunction with the WINS server to resolve the IP and naming convention.
This is critical because if both NT and Windows 2000 machines are using
DHCP to determine their IP addresses, these IP addresses can change at any
time.
The second, simple type of network is one in which there are no network servers
or if there are, they are not running DNS and not using DHCP. Typically, the IP
address and name of each machine will not change over time. In this case, the
user can modify the /etc/HOSTS file on the Unix or Linux machines and the
C:\winnt\system32\drivers\etc\HOSTS file on the Windows 2000 machines to
specify the IP and hostname relationships.
Warning
NT
Client
Win2K
Client
Unix/
Linux
Client
NT Server
WINS
Windows 2000/Unix/Linux Server
DNS
DHCP Protocol
Assumptions: About the Users Network
The TCP/IP protocol will be the sole means of communication between the
different machines.
The machines must be assigned static IP addresses or addresses must be
assigned dynamically via DHCP. In either case, the DNS server on the
network should have a proper record of the fully qualified and unqualified
hostname for all machines. For example, if your domain is company.com and
the machines name is machine, then the DNS should have proper records of
both machine and machine.company.com that point to the same IP address.
If there is no DNS or it is not properly configured, then each local and remote
machine must have a record of every other machines qualified and
unqualified hostname in the respective machines HOSTS file. On Unix or
Linux machines, this file can be found in the /etc directory. On Windows 2000
machines, this file can be found in the C:\winnt\system32\drivers\etc
directory.
Key Commands
ping Command This command is used to check the communications
between the different machines on the network. It can be found in the
following locations:
SGI - /usr/etc/ping
Solaris - /usr/sbin/ping
IBM - /etc/ping
Linux - /bin/ping
Windows 2000 C:\winnt\system32\ping.exe
It can be executed as follows:
ping machinename
If the network has not been set up properly, then errors such as Time Out or
Connection refused will be given. If this happens then either check the DNS
server in a resolution network or add the proper IP address and qualified/
unqualified hostname information in the respective hosts files for the static IP
networks. On Solaris machines, you may also have to edit the /etc/
nsswitch.conf file to remove the {NOTFOUND=return} parameter on the
line containing the keyword hosts:.
Notes
The user must have root (Unix/Linux) or administrator (Windows 2000) privi-
leges to modify the HOSTS file.
rsh & rcp Commands The DESKTOP-VIP job submittal application uses
rsh and rcp commands to execute commands on the remote Unix or Linux
machine and to copy files to/from the local Windows 2000 machine to the
remote Unix or Linux machine. For these operations to work properly, it is
required for the user to be able to login from the local Windows 2000 machine
to the remote Unix or Linux machine without entering a password. A user can
determine if a password is required on the Unix or Linux machine by trying to
rsh to the Unix or Linux machine from a Windows 2000 machine by typing
the following command:
C:\winnt\system32\rsh Unix/Linuxmachinename l Unix/Linuxusername hostname
If this command returns with the Unix/Linuzmachinename, then everything
should be set up properly. If it fails, then check to see if there is an entry in
the Unix or Linux machines /etc/hosts.equiv file or the users .rhosts file
located in his home directory on the Unix/Linux machine containing the
Windows2000machinename and the Windows2000username. The /etc/
hosts.equiv file and the users .rhosts file contain entries that denote which
machines and users can serve as remote hosts. Be certain that qualified and
unqualified machine names are specified.
VIPrshClient Command - The DESKTOP-VIP job submittal application
uses the VIPrshClient command to execute commands on remote Windows
2000 machines and to copy files to/from the local Windows 2000 machine to
the remote Windows 2000 machine. It is meant to operate much like the Unix/
Linux rsh and rcp commands described above. It communicates with
VIPrshServer running on the remote machine. Refer to Appendix C for a
detailed description of these two programs. To determine if the
communication between the local and remote machines is set up properly, a
user can type in the following command from the
%VIPHOME%\dtvip\exec directory:
VIPrshClient Windows2000machine l Windows2000username n hostname
If it returns with the Windows2000machine name, then everything should be
setup properly. If it fails, then check to see if the remote machines
VIPrshServer service as been stopped.
Key Files
hosts file This is a system file that contains the IP address-hostname
database information. It can be found in the following locations:
SGI, Solaris, IBM, Linux - /etc/hosts
Windows 2000 C:\winnt\system32\drivers\etc\hosts
For networks that do not have DNS servers, these files must be modified to
reflect the IP address-hostname relations of the various machines that will
be communicating with each other. To test that the machines can see each
other use the ping command described above. You should enter both the
fully-qualified and unqualified hostname for all machines, both local and
remote. The hosts file on the Windows 2000 machine should contain the IP
address-hostname of the Unix or Linux machines. The hosts file on the
Unix or Linux machine should contain the IP address-hostname
relationships of the Windows 2000 machines. For more information on the
hosts file, perform a man hosts command on a Unix or Linux machine.
Figure 3 is a sample of a hosts file showing a new entry for the domain
company.com and the machines name machine:
Figure 3
.rhosts and hosts.equiv files These are Unix or Linux system files that
define which users on remote machines are permitted to remotely execute
commands on the local machine. When setup properly, rlogin does not
prompt for a password on the Unix or Linux machine and the rsh command
will complete successfully on the Window 2000 machines. The hosts.equiv
file is located in the /etc directory on the Unix or Linux machines. Users may
expand this authentication scheme based upon trusted hosts by installing a
.rhosts file in their login directory. For more information, perform a man
rhosts command on a Unix or Linux machine.
Figure 4 is a sample hosts.equiv file that describes some of the other
authentication schemes that are permitted. These schemes are also used in the
.rhosts file. You must add both Windows and Unix machine names. For
example, we have added the Windows 2000 machines name
#Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1localhost
164.132.32.01 machine.company.com machine
Window2000machine and the Windows 2000 users name
Windows2000username to the bottom of the file. Please note, that both fully-
qualified and unqualified machine names were entered.
#@(#)611.5 src/tcpip/etc/hosts.equiv, tcpip, tcpip430, 9737A_430 9/27/91 17:11:34
# IBM_PROLOG_BEGIN_TAG
# This is an automatically generated prolog.
#
# tcpip430 src/tcpip/etc/hosts.equiv 1.5
#
# Licensed Materials - Property of IBM
#
# (C) COPYRIGHT International Business Machines Corp. 1985,1989
# All Rights Reserved
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# IBM_PROLOG_END_TAG
#
# COMPONENT_NAME: TCPIP hosts.equiv
#
# FUNCTIONS:
#
# ORIGINS: 26 27
#
# (C) COPYRIGHT International Business Machines Corp. 1985, 1989
# All Rights Reserved
# Licensed Materials - Property of IBM
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# /etc/hosts.equiv
#
# This file, along with a local user's $HOME/.rhosts file, defines which
# users on foreign hosts are permitted to remotely execute commands on
# your host. The rshd, rlogind, lpd, and srcmstr programs all use this
# file to determine remote user access.
#
# The format of this file is as follows:
#
# hostname [username]
#
# Both hostname and username can be preceded by a '-' character to deny
# access. A '+' character can be used in place of hostname or username
# to match any host or user. If you are using NIS, both the hostname and
# username may be in the form:
#
# +@netgroup
# -@netgroup
Figure 4
VIPrshUsers.txt file This is a Windows 2000 file that performs the same
type of function as the .rhosts and hosts.equiv files on Unix or Linux. A
template of this file called VIPrshUsers.temp.txt is located in the
%VIPHOME%\dtvip\exec directory for the users to modify. If a
VIPrshUsers.txt file is found on the VIPrshServer machine in the
%VIPHOME%\dtvip\exec directory, the server will limit access to only the
users defined in the file. Figure 5 is a sample of the template file:
#
# where "netgroup" is an NIS netgroup defined in the netgroup map. The
# '+' form allows access to any host or user in the netgroup, while the
# '-' form denies access to any host or user in the netgroup.
#
# Lines beginning with a '#' character and blank lines are ignored.
#
# Examples:
#
# host user allows access to user on host
# + user allows access to user on any host
# host -user denies access to user on host
# -host denies access to all users on host
# -@group denies access to all users on hosts in group
# +@group1 +@group2allows access to users in group2 on hosts in group
Windows2000machine.company.com Windows2000username
Windows2000machine Windows2000username
Figure 5
.kviprc file For users to submit remote simulation jobs from a Windows
2000 machine to a remote Unix or Linux machine, the location of the Unix/
Linux VIP installation and the location of the License Manager must be
known. This information is provided in a .kviprc file that a user has placed in
his home directory on Unix or Linux, or the site administrator had placed in
the /etc or /usr/local/etc directory. A template of this file (kviprc) is located
in the Unix/Linux VIP installation and is found in the top /vip directory.
If the file is to be placed in the users home directory, make a copy of this file
and rename it to .kviprc (Note the dot before the name). If the site
administrator has placed this file in either the /etc or /usr/local/etc directory,
the dot before the name should not be used.
#VIPrshUsers.temp.txt
# This is a template for an actual VIPrshUsers.txt username/password file
# as is used by the VIPrshServer for remote Windows-to-Windows requests.
# The VIPrshUsers.txt file must be in the VIPEXEC directory.
# List usernames that should be able to gain remote access.
# VIPrshServer IS CASE SENSITIVE!!
jSmith001
JohnBigBoot
AdminFromHeaven
# Note that the usernames are simply text strings passed by the
# VIPrshClient. They do not need to be 'true' network usernames.
# This allows you to use a more obscure word than your username
# much like a password.
# So, instead of executing:
# VIPrshClient RMTHOST -l joesmith . . .
# You can instead use:
# VIPrshClient RMTHOST -l passwdABC123 . . .
# This way simply knowing a username is not enough to access a Server.
# Simply list whatever obscure word(s) you would like to use.
passXYZ
26Dec1941
2cupsInaPint2PintsInMyCup
Edit the file .kviprc and modify the following lines to point to the actual
location of the Unix or Linux installation and the license.dat file:
setenv $VIPHOME /usr/apps/vip
setenv LM_LICENSE_FILE $VIPHOME/licmgr/license.dat
Please notice that there should be a section for each Unix or Linux machine
type on the network. Figure 6 represents a sample of the template file with
sections for Linux, IBM, SGI, and SUN systems.

Figure 6
#!/bin/sh
# Startup file for VIP submissions.
# spf 10/09/2001
#
# The locations of VIPHOME and LM_LICENSE_FILE given below are only examples.
# Modify the location of VIPHOME and LM_LICENSE_FILE to reflect your particular# installa-
tion. Please note that there are sections for the different Unix
# platforms. Please modify the one that is appropriate.
# Platform-specific commands
platform=`uname`
# ++++++++++++++++++ IBM Platform +++++++++++++++++++
if (test "$platform" = "AIX") then
VIPHOME=/usr/apps/vip
export VIPHOME
. $VIPHOME/krun.vip
LM_LICENSE_FILE=$VIPHOME/licmgr/license.dat
export LM_LICENSE_FILE
# ++++++++++++++++++ SGI Platform +++++++++++++++++++
elif (test "$platform" = "IRIX64") then
export VIPHOME
. $VIPHOME/krun.vip
# ++++++++++++++++++ SOLARIS Platform +++++++++++++++
elif (test "$platform" = "SunOS") then
export VIPHOME
. $VIPHOME/krun.vip
# ++++++++++++++++++ LINUX Platform +++++++++++++++++
elif (test "$platform" = "Linux") then
export VIPHOME
. $VIPHOME/krun.vip
# elif ([["$platform" = "Windows*"]]) then
# Put any Windows-specific commands here.
else
echo "$platform is not supported by VIP"
echo "Calling EXIT"
exit
fi
# Platform-independent commands
if (test "$TMPDIR" = "") then
TMPDIR=.
export TMPDIR
fi
if (test "$ERR_LEVEL" = "") then
ERR_LEVEL=4
export ERR_LEVEL
fi
PATH=$PATH:.
export PATH
Job Submission Panels
The job submission panel on the Windows 2000 machine have locations to enter
your login name on the remote machine (necessary if it is different from the local
system), the name of the remote machine, and the location of the temporary
workspace on the remote machine. It is mandatory that you fill in these fields
correctly and then perform a carriage return. Please refer to the VIP Job Submission
document for a complete description of the job submission panels.
Desktop-VIP 2003.4 Release Notes Page 61 Appendix C: VIPrshServer & VIPrshClient Utilities
Appendix C: VIPrshServer & VIPrshClient
Utilities
These instructions detail the implementation and usage of the VIPrshServer and
VIPrshClient utilities.
VIPrshServer:
This program allows Windows 2000 machines to run programs and copy files at
the request of other Windows 2000 machines (running VIPrshClient). It is
meant to operate much like the UNIX rsh and rcp daemons, running
permanently in the background without requiring a local user's attention.
Automatic Installation - The VIP Installation program will give the user a
choice of installing the VIPrshService. If the user opts to have it installed,
the Service is installed and started automatically by the installation program.
If the user opts not to use VIPrshService, its executable is still copied and it
may be manually installed and started at a later date by the user.
Manual Installation - The VIPrshServer runs as a Windows 2000 Service,
and therefore requires some special installation instructions.
1. First the administrator must type "VIPrshServer -install" at a DOS
command prompt. This will cause the VIPrshServer to announce its
location on disk to the operating system.
2. Once this is done, the administrator must open the "Services" utility
under "Administrative Tools" in the "Control Panel." The Services
utility lists and allows control over all background services available on
the computer. Once opened, it will display a list of services on the right.
3. The administrator should find and select VIPrshServer in the Services
list and select "Properties" from the "Action" menu.
4. In the "General" panel, the administrator should select "Automatic" as
the Startup Type.
5. In the "Log On" panel, select "Log on as This Account". This activates
the password fields. Enter "administrator" and the password and enter it
again in the confirmation field.
6. Click "Ok."
7. The administrator may decide upon how many connections
VIPrshServer can serve at any one time. The default is 15, but if the
administrator would like fewer or more, a number can be entered in
"Startup Parameters" on the "General" panel. Please note that VIP Job
Submittal uses up to three connections at a time for a single remote job.
8. With VIPrshServer still highlighted in the list, clicking "Start" from the
"Action" menu will start the VIPrshServer.
Operation - The VIPrshServer requires no additional user intervention.
With the above installation, the VIPrshServer should run no matter who is
logged on, and even if no user is logged on at all. If the VIPrshServer should
cease functioning, the administrator can restart it with the Control Panel
(Action: Start) or a reboot of the system.
Security The default operation of VIPrshServer is to execute all client user
requests. If your network is open to external areas, it may be wise to create an
ASCII text file in VIPrshServer's directory (%VIPHOME%\dtvip\exec)
entitled "VIPrshUsers.txt". An example file is shown on the following page.
This file should simply list all trusted usernames that should have access to
the VIPrshServer. The names do not need to be listed one per line, but it
makes editing nice. In addition, you can use the '#' character to denote the
beginning of one line of comments.
Once VIPrshUsers.txt is created (even if blank), VIPrshServer will allow
absolutely no remote request made by a user not listed by name in
VIPrshUsers.txt. Please note that the entries are case sensitive.
VIPrshUsers.txt can be updated at any time, but the change in
VIPrshServer's security will not take place until a reboot or a VIPrshClient
(one on the same machine will work) makes a request with the username as
"guest." No "guest" commands may be executed, but all will reset
VIPrshServer's security. Even adding "guest" as a trusted username in
VIPrshUsers.txt will allow "guest" to do nothing but reset VIPrshServer's
security.
A copy of the file VIPrshUsers.txt is located in VIPrshServer's directory
{%VIPHOME%\dtvip\exec} entitled "VIPrshUsers.temp.txt". This file
may be used as a template or guide for creating your own "VIPrshUsers.txt"
file, should one be needed.
Notes on Installation
If you are running VIP over a network, and your LAM server and
license.dat file are on another Windows 2000 machine, then you must do
the following:
1. As Administrator, map the network drive that contains the license.dat file.
2. As Administrator, open the Windows 2000 Services panel, select
VIPrshServer and select Properties from the "Action" menu.In the "Log
on" panel, select Log on as "This Account" and type Administrator and
its password.
3. Click "Ok."
## VIPrshUsers.temp.txt
# This is a template for an actual VIPrshUsers.txt username/password file
# as is used by the VIPrshServer for remote Windows-to-Windows requests.
# The VIPrshUsers.txt file must be in the VIPEXEC directory.
# List usernames that should be able to gain remote access.
# VIPrshServer IS CASE SENSITIVE!!
jSmith001
JohnBigBoote
AdminFromHeaven
# Note that the usernames are simply text strings passed by the
# VIPrshClient. They do not need to be 'true' network usernames.
# This allows you to use a more obscure word than your username
# much like a password.
# So, instead of executing:
# VIPrshClient RMTHOST -l joesmith . . .
# You can instead use:
# VIPrshCLient RMTHOST -l passwdABC123 . . .
# This way simply knowing a username is not enough to access a Server.
# Simply list whatever obscure word(s) you would like to use.
passXYZ
26Dec1941
2cupsInaPint2PintsInMyCup
# Please keep in mind that ONLY words listed in the VIPrshUsers.txt file
# will gain access. So, if you have an empty VIPrshUsers.txt file,
# NOBODY will have access.
# If you would like ANYONE to have access, simply Do Not make a
# VIPrshUsers.txt file.
VIPrshClient
This program allows Windows 2000 machines to request remote program
execution and file copies from any Windows 2000 machine running
VIPrshServer. It is meant to operate much like UNIX rsh and rcp clients,
running on a 'per request' basis.
Automatic Installation The VIPrshClient will be installed
automatically with the other DESKTOP-VIP application.
Operation - VIPrshClient is really written to be used by VIP's Job Submittal
program, but the occasional user may desire to run it as a stand-alone utility.
In this case, there are four basic ways to submit requests:
1. To request that an application be run on the VIPrshServer remote
machine:
VIPrshClient {servername} -l {username} -n command [parameters]
2. To request that a local file be sent to the VIPrshServer remote machine:
VIPrshClient {servername} -l {username} -s {localfilepath} {remotefilepath}
3. To request that a remote file be received from the VIPrshServer remote
machine:
VIPrshClient {servername} -l {username} -r {localfilepath} {remotefilepath)
4. To request that the VIPrshServer reset its security by reloading its
VIPrshUsers.txt file:
VIPrshClient {servername} -l guest -n {anycommand}
When a remote command is executed that provides text-based output, it will
be displayed on the user's VIPrshClient computer. If a faulty request is made
or the VIPrshServer is not found, the VIPrshClient will alert the user of the
problem. Otherwise, when the VIPrshServer has completed its task,
VIPrshClient will cease execution and return the user to the command
prompt.
Security VIPrshClient should not be considered a security risk, as it
can only make requests, and only at the user's desire.
Desktop-VIP 2003.4 Release Notes Page 65 Appendix D: FLEXlm Licensing
Appendix D: FLEXlm Licensing
Introduction
Landmarks license system (LAM) is based on Globetrotter Softwares
FLEXlm licensing server package.
This document describes the procedures for installing, configuring, and
managing the license system to control the usage of Landmark
applications, including the following topics:
Version Compatibility described below
Using the License System with Third-Party Software on page 66
LAM 2003.0 Guide Windows on page 67
Version Compatibility
Each Release of a Landmark application has a version of FLEXlm with
which it is certified.
Release 2003.0 and later use new security enhancements incorporated
into FLEXlm server and license files for version 7.2e and later. As a
result, Release 2003.4 applications will not work with earlier FLEXlm
versions.
The LAM 2003 Server software must be installed and new license files
must be obtained prior to attempting to run any Release 2003.4
applications. The detailed procedures to perform these tasks are
contained in the platform-specific chapters of this guide.
Landmark Release FLEXlm Version Operating System
2003.0, 2003.4 7.2e Windows, Solaris, IRIX, AIX
2003.0.1 7.2e Solarix, IRIX
2003.1 7.2e Windows
2003.3, 2003.4 7.2g Linux
Landmark Appendix D: FLEXlm Licensing
Understanding the License Process
The license process is described in detail in the LAM Guide that was
included in the R2003.0 release. Refer to the Guide for a detailed
explanation of licensing.
Using the License System with Third-Party Software
Because Landmarks License System uses FLEXlm from Globetrotter,
administrators must be careful when installing other third-party
software that also uses FLEXlm (Suns compilers, Charisma, etc.).
When your environment contains Landmark applications (either VIP
only or in combination with other products such as OpenWorks) and
other third-party software, there are two ways to manage the license
system:
The first (and easiest) way produces separate license systems.
Landmark applications reference one license system while third-
party software references the other license system.
The second (more complicated) way produces a single license
system that is used by both Landmark applications and the third-
party software.
Procedures for each type of license set-up are described in the LAM
Guide. The Guide assumes that your license file is in the OpenWorks
environment. When reading these procedures, substitute your VIP path
(or wherever FLEXlm is installed) for the OpenWorks path.
LAM 2003.0 Guide Windows
Introduction
This chapter describes LAM on Windows and contains the following
major topics:
Obtaining a Server License File on page 67
Installing LAM Server on page 68
License Server Startup on page 70
LAM Technical Notes on page 73
LAM Server Uninstall on page 75
LAM System Requirements
Operating System
Windows 2000 Server with Service Pack 1 or 2.
Hardware Requirements
The memory, disk storage, and bandwidth needed for the License
Server is minimal when compared with the capability of modern
workstations, servers, and networks. For instance, as a base the
FLEXlm daemon, lmgrd, uses about 160 KB of memory, and the
Landmark daemon, licsrv, uses about 180 KB; however, with a large
license file and with a large number of users, both daemons may use
about two or three megabytes of memory.
The storage requirements remain relatively static, around seven or eight
megabytes.
Obtaining a Server License File
A license file must be obtained from Landmark Graphics Corporation
before you can start the license server and run the Landmark
applications.
1. Log on to the server using the configuration you want to license
and run under (for example, vip2003.4).
2. Enter the following command in a Command Prompt window:
ipconfig / all
3. If the machine has more than one Ethernet card or is a stand-alone
system, enable the correct card using the Hardware Manager.
4. Note the Host Name here: _________________________
5. Note the Physical Address here: _________________________
(On Windows 2000 systems, this is a 12 digit string; for example,
00-C0-3D-68-F9-2B.) Do not include the hyphens;
00C03D68F92B would be the entry for the Physical Address.
6. Request the license file from the following address:
http://www.lgc.com/support/licensing
You will be asked for the Host Name and Physical Address, as
well as type of license, number of users for the license, platform,
model, and operating version.
7. Place the license file in the LAM 2003.0 destination folder
specified during the product installation (for example,
C:\Landmark\Lam).
If this folder does not exist, create it now.
If you do not place the license file on the server you cannot use
the NT Service that automatically starts the license server upon
reboot. See Using LAM Server Without NT Service on
page 73.
Installing LAM Server
The steps to install LAM server are contained in this section.
Before you proceed with the steps in this section, uninstall all previous
versions of LAM Server that have been installed on the machine.
Failure to uninstall all previous versions of LAM Server before
installing LAM2003.0 will result in a duplicate FLEXlm service that
replicates itself until it crashes Windows. See LAM Server Uninstall
on page 75.
1. Log on to the server as administrator.
2. Put the appropriate Release 2003.0 CD in the CD-ROM drive. The
installation will run in an automatic startup mode; if is does not,
use the following steps:
Select Start > Run. The Run dialog box opens.
In the Open text field, type
CDROMDriveLettter:\Setup.exe
Click OK.
The installation screen appears.
3. Click on Install Products.
4. When the installation screen changes, click on LAM Server. A
Setup box will appear briefly.
5. Individual product installation processes automatically install
LAM Client. When prompted to Upgrade the Installation to LAM
Server, click Yes.
The User Information and the LAM 2003.0 destination folder
specified during the product installation will be used.
6. When prompted to reboot the machine, click Yes, reboot now, then
click Finish.
7. Remove the CD from the CD-ROM drive.
The license server will start automatically when the machine reboots.
Landmark strongly recommends
using the products HOME directory as the location for the LAM 2003
destination folder
placing the license file in the LAM 2003 destination folder.
NOTE: Following these guidelines will ensure ease of use by Landmark
applications.
License Server Startup
The license server is configured during LAM installation to become an
NT Service that starts automatically. However, you may need to
perform a few customization steps.
If you did not place the license file on the server you cannot use the NT
Service described in this section. See Using LAM Server Without NT
Service on page 73.
If you did place the license file on the server, make sure the file is
placed in the correct folder. To verify this:
1. Select Start > Programs > LAM2003.0 > License Tool
Manager.
2. Click the radio button labelled Configuration Using Services. You
should see LGC License Application Manager listed and already
selected in the list box. If it is not pre-selected, select it now.
3. Click on the Configure Services tab. Note the path to the license
file (for example, C:\Landmark\Lam\license.dat). Your license file
should have been copied to this location.
4. During installation, the LAM Server was set to automatically start
when Windows starts up. Verify this by looking at the Start
Server at Power Up checkbox. If it is not checked, click on it,
then click on Save Service, then click on Yes to confirm the save.
5. If you installed a new license file after rebooting and automatically
starting the server, you must re-read the license file to make the
server aware of the new file.
To re-read the license file, go to step 6. Otherwise, skip to step 8.
6. Click on the Start/Stop/Reread tab. If it is not already
highlighted, select LGC License Application Manager, then
click the ReRead License File button.
7. If you receive an error message, click on Stop Server then click on
Start Server. A Server Starting message should appear in the
status bar at the bottom of the window.
8. Exit the License Tool Manager by selecting File> Exit or by
clicking the X box in the top right corner of the window.
LAM Technical Notes
Using LAM Server Without NT Service
In order to use LAM Server on a PC as an NT Service, the license file
MUST reside on the local hardware, not across the network.
If the license file resides across the network, the server can still be
launched, but not as an NT Service. It must be run in a Command
Prompt window as follows:
lmgrd.exe -c <license_file_path>
LAM Server Installation Warnings
The recommended operating system for a LAM Server installation is
Windows 2000 Server.
LAM Server may be installed on Windows 2000 Workstations, but this
is not the recommended configuration. Windows 2000 Workstations
have networking limitations that prevent a high number of network
connections and could result in dropouts of service for a license server.
A Windows 2000 Server is much better equipped for handling large
volume network services.
InstallShield will not install LAM Server on any systems running
Windows 95 or Windows 98 operating systems. You must install either
LAM Client on these operating systems or install LAM Server
manually by copying files over the network.
If Applications Cannot Find License File
Environment variables locating the license are normally set up by the
installation program. The variable can contain either the full path to the
license file including the machine name on which it resides, or it can
contain the port number and machine name of the license server that
serves that license file. For example:
LM_LICENSE_FILE 2013@MyMachineName
LM_LICENSE_FILE \\MyMachineName\Landmark\Lam\license.dat
Workaround for NutCracker Applications
Port number and machinename do not work with the VIP NutCracker
applications. The workaround is to make a copy of the license.dat file
on the local machine and set the LM_LICENSE_FILE variable to point to it.
FLEXlm performs background operations to speed-optimize access to
the license file when it is run from an application for the first time.
If it is necessary to change the location or name of the license file being
used, use the following procedures:
FLEXlm writes the path to the license file in the Windows registry in
HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\LICSRV_LICENSE_FILE
You may need to remove this key to get FLEXlm to use the new license
file if the path has changed.
Overriding LM_LICENSE_FILE
Landmark generally makes use of the LM_LICENSE_FILE
environment variable. Applications running for the first time may
incorrectly override the setting of the LM_LICENSE_FILE variable.
You may need to set
FLEXLM_NO_CKOUT_INSTALL_LIC 1
in order to disable the usage of the Windows registry setting to override
LM_LICENSE_FILE.
Use the Advanced tab of the System Control Panel to set
FLEXLM_NO_CKOUT_INSTALL_LIC this variable.
Known Problems
1. You may be unable to run versions of LAM prior to version 2003.0
on computers with multiple Ethernet adapters (such as laptops
with docking stations) using the Windows 2000 operating system.
Landmark recommends installing and running LAM 2003.0
Server on these computers, in order to take advantage of the new
FLEXlm 7.2 functionality.
2. The LAM W2003 folder may be displayed by default on startup.
This behavior can be corrected by using the following steps:
a. Right click on Start.
b. Select Open All Users.
c. Double-click on Programs.
d. Double-click on Startup.
e. Select LAM W2003 icon.
f. Click on Edit menu or right click on LAM W2003 icon.
g. Select Cut.
h. Click on Back toolbar button.
i. Click on Edit menu or right click on the blank or empty area.
j. Select Paste.
LAM Server Uninstall
Before installing LAM 2003 Server, please uninstall all existing
previous versions of LAM Server. Failure to uninstall all previous
versions of LAM Server before installing LAM2003 will result in a
duplicate FLEXlm service that replicates itself until it crashes
Windows.
Stop and Remove the License Service
The license service must be stopped and removed prior to running the
LAM Uninstaller. To stop the server, do the following
1. Run LMTOOLS.EXE. The default installation location for
LMTOOLS.EXE is C:\Landmark\Lam\bin. You can use Windows
Explorer to access and run this executable.
2. Select the Configuration Using Services radio button, then select
LGC License Application Manager if more than one entry is listed.
3. Select the Start/Stop/Reread tab and click on the Stop
Server button.
4. Select the Configure Services tab.
5. Click on the Use Services check box to clear / disable both of the
check boxes.
6. Click the Remove Services button.
7. Exit the LMTOOLS application by selecting File> Exit or by
clicking the X box in the top right corner of the window.
Uninstall Previous Versions of LAM Server
Note: The license file itself is not removed during a LAM uninstall.
1. Log on to the server as a user with administrator privileges.
2. Select Start > Setting > Control Panel > Add/Remove Programs.
The Add/Remove Programs Properties control panel opens with
the Install/Uninstall tab active.
3. In the Add/Remove Programs Properties control panel
Select Landmark LAM 2003, then click Add/Remove.
When the Confirm File Deletion box opens, click OK.
You may get a Details message box saying that a registry value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Co
ntrol\Session Manager\Environment\HOME could not be
removed. Click OK.
If prompted whether to uninstall specific files, select Yes to All.
4. Repeat Step 3 for each version of LAM that is listed in the Install/
Uninstall tab.
5. Click OK to close the Remove Programs Properties control panel.
6. Reboot.
Uninstalling LAM 2000 Server Manually
Note: This section is from the LAM 2000 Release Notes.
1. Remove the registry entries related to LAM W2000 product.
2. Click on Start->Run
3. Type regedit.
Note
The following process removes LAM from your computer by editing the registry.
Changes to the registry can have serious consequences to your computers
performance. You should follow these instructions precisely to avoid possible
problems.
4. Press OK button.
5. Expand HKEY_LOCAL_MACHINE by clicking on +.
6. Expand SOFTWARE by clicking on +.
7. Expand Landmark Graphics Corporation by clicking on +.
8. Select LAM.
9. Press Delete Key or Select Delete from Edit menu.
10. Confirm Key Delete by Pressing Yes button.
11. Expand HKEY_LOCAL_MACHINE by clicking on +.
12. Expand SOFTWARE by clicking on +.
13. Expand Microsoft by clicking on +.
14. Expand Windows by clicking on +.
15. Expand Current Version by clicking on +.
16. Expand Uninstall by clicking on +.
17. Select {99F2697D-EDC1-11D2-B8C3-00C04F8EEBF9}.
18. Press Delete Key or select Delete from Edit menu.
19. Confirm Key Delete by pressing Yes button.
20. Exit Registry Editor by Clicking on Registry menu and selecting
Exit.
21. Remove the LAM directory using the Windows Explorer program.
Desktop-VIP 2003.4 Release Notes Page 79 Appendix E: Installing Hummingbird Exceed 7.1 on
Appendix E: Installing Hummingbird Exceed
7.1 on Windows 2000
DESKTOP-VIP Version 2003.4 using Hummingbird Exceed
and Exceed 3D

Version 7.1 was certified to ensure that the X-server functions and integrates
properly with the DESKTOP-VIP for Windows 2000 applications, follow these
general guidelines:
When prompted by the Exceed and Exceed 3D installation wizards, choose
the option that allows all users of this machine to see the installation.
Continue with the other default installation options, except for tuning the
server. Do not tune the server skip that step. When tuning a server, it is
better to tune the X-server manually after the installation is complete. For
more information about manually tuning the server, see the Optimizing the
Hummingbird Exceed 7.1 X-server for Desktop-VIP on page 81.
NOTE: R2003.4 version of Desktop-VIP installs JAVA Runtime Environment and
creates the VIPJAVA environment variable and sets it up automatically.
Hummingbird Exceed X-Server Installations and Exceed 3D Version 7.1
Use the following steps while installing Hummingbirds Exceed to ensure that all
of the components required for the proper operation of Desktop-VIP will be
installed and that the X-server functions and integrates properly with the
Desktop-VIP applications.
NOTE: Although preliminary testing has not found problems, VIP 2003.4 is not
certified to work with Hummingbird Exceed 8.00, nor will problems
associated with this version be supported.
Exceed-X Installation Procedures
1. Log on to the system as Administrator.
2. Put the Exceed CD into the CD-ROM drive. The installation will run in an
auto-startup mode; if it does not, use the following steps:
a. Select Start > Run. The Run dialog box opens.
b. In the Open text field, type: <CD-ROM drive letter>:\Msetup.exe
c. Click OK.
3. The Hummingbird install screen appears.
4. On the main menu, select the Install Exceed option.
5. Select the Personal Installation option.
6. Follow the installation instructions on your screen, noting the following:
On the License page, select the I accept the terms of the license option
before proceeding. This is not the default.
On the Customer Information page, enter your username and organization
name. Make sure the default option Install Application for All Users is
selected.
On the Setup Type page, make sure the default Typical Installation is
selected.
Ignore the Xconfig Password page by clicking the Skip button.
Ignore the Xserver TuneUp page by clicking the Skip button.
7. When the installation is completed, click the Finish button on the final page.
Then click the Back button. Then click the Exit button.
8. Remove the Exceed CD from the CD-ROM drive.
Exceed 3D Installation Procedures
1. Log on to the system as Administrator.
2. Put the Exceed 3D CD into the CD-ROM drive. The installation will run in
an auto-startup mode; if it does not, use the following steps:
b. In the Open text field, type: <CD-ROM drive letter>:\Msetup.exe
c. Click OK.
3. The Hummingbird install screen appears.
4. On the main menu, select the Install Exceed option.
5. Select the Personal Installation option.
6. Follow the installation instructions on your screen, noting the following:
On the License page, select the I accept the terms of the license option
before proceeding. This is not the default.
On the Customer Information page, enter your username and organization
name. Make sure the default option Install Application for All Users is
selected.
On the Setup Type page, make sure the default Typical Installation is
selected.
7. When the installation is completed, click the Finish button on the final page.
Then click the Back button. Then click the Exit button.
8. Remove the Exceed 3D CD from the CD-ROM drive.
CAUTION: Even though Exceed does not ask you to reboot, we highly recommend you
reboot your machine now to ensure the registry settings are honored.
Optimizing the Hummingbird Exceed 7.1 X-server for Desktop-VIP
Optimize the X Server
The X-server must be tuned manually after it is installed in order for all
DESKTOP-VIP applications to function properly. After installing Exceed 7.1,
perform the following steps to tune the X-server:
1. Log on to the system as a user with administrative privileges.
2. Select Start > Programs > Hummingbird Connectivity > Exceed >
Xconfig. The Xconfig control panel opens.
NOTE: Your system may be set up with a required password.
3. Double-click the Screen Definition icon. The Screen Definition dialog box
opens.
4. Modify the settings on the Screen 0 tab to match those shown below. Make
sure the Server Visual option is set to True Color.
5. Select the Common Settings tab. Uncheck the Close Warning On Exit box.
6. Click OK. The Screen Definition dialog box closes.
7. Double-click the Performance icon in the Xconfig control panel. The
Performance dialog box opens.
8. Click the Tune. button. The Xperf dialog box opens.
9. Click Run All. A series of graphics will appear in the upper left corner of the
monitor and the Xperf dialog box will become inactive. (These tests will take
a while.)
10. After the tests are complete the Xperf dialog box will become active again.
Click OK. The Xperf dialog box closes.
11. Click OK in the Performance dialog box and exit the Xconfig control panel.
Desktop-VIP 2003.3.0 Release Notes Page 85 December 2001
Appendix F: Installing Adobe Acrobat
Installation
Note: If Acrobat Reader 5.01 is already installed on the server, you may skip this
section.
1. If you are not already logged on to the server as Administrator, do so now.
2. Put the Desktop-VIP CD(Volume 17) in the CD-ROM drive.
3. The installation will run in an auto-startup mode; if it does not, use the
following steps:
b. In the Open text field, type: <CD-ROM drive letter>:\Install.exe
c. Click OK.
4. The Landmark Graphics Corporation installation screen appears. Click the
Acrobat option. An Unpacking Acrobat Setup screen appears.
5. When the Setup dialog box opens, click Next.
6. When the License Agreement box opens, click Accept.
7. When prompted, verify or correct the destination directory, then click Next.
8. Installation begins. A series of status messages will appear during installation.
9. When the Setup confirmation box opens, click OK. The Acrobat Setup screen
closes and the Landmark Graphics installation screen appears.
10. When prompted to reboot, click Yes.
Printing Books from Adobe
Acrobat
Reader
When printing ranges of pages in Acrobat, you must use the status bar at the
bottom of the Adobe Acrobat Reader to get the most accurate indicator of which
page you are looking at. The page numbers at the bottom of an online page or
other page number references in the online document are not the page numbers
that Acrobat uses when you select a range of pages in its Print dialog. This
situation is especially true in online books, where the table of contents uses one
page numbering scheme and the body of the book uses another.
For instance, in the 3DVIEW Users Guide online book, if you wanted to print a
Desktop-VIP 2003.3.0 Release Notes Page 86 December 2001
chapter, follow a procedure similar to the following:
11. In the bookmark frame of Acrobat, select the name of the chapter that you
want to print.
12. Note the page number in the status bar.
13. Display the last page in the chapter.
14. Note the page number of the last page in the status bar.
15. Select File Print to display the Print dialog.
16. Enter the page numbers that you noted in the From and To text boxes in the
Print dialog.
17. Click OK. Acrobat will then print the pages of the chapter.
Desktop-VIP 2003.4 Release Notes Page 87 Appendix G: OpenWorks Install after VIP
Appendix G: OpenWorks Install after VIP
The VIP install will automatically recognize an existing OpenWorks
environment. However, if you install OpenWorks after VIP, you must do one of
the following after OpenWorks is installed to set up the VIP installations:
Uninstall/reinstall VIP.
Make the manual changes to the VIP installation that will allow it to
recognize the OpenWorks environment. These manual changes are described
below.
Setting up VIP in a New OpenWorks Environment
Perform the following steps to set up VIP data in a new OpenWorks application:
1. Open the command prompt: Start -> Programs -> Command Prompt.
2. Copy images of VIP applications with OpenWorks connections to the
necessary executable:
a. Go to the following directory:
cd %VIPHOME%\dtvip\exec
b. Copy the following files:
copy gridgenr_ow.exe gridgenr.exe
copy dbplot_ow.exe dbplot.exe
2. Register the DLL associated with VIP DataStudio that creates the proper link
to Openworks in directory %VIPHOME%/dtvip/exec:
a. Go to the following directory:
cd %VIPHOME%\dtvip\exec
b. Enter the following command:
regsvr32 VIPOWReader.dll
You receive a notification prompt that the DllREgisterServer succeeded.
Click OK to close the prompt.
Desktop-VIP 2003.4 Release Notes Page 88 Appendix G: OpenWorks Install after VIP
Desktop-VIP 2003.4 Release Notes Page 89 Appendix H: Uninstall Older Versions
Appendix H: Uninstall Older Versions
You must uninstall older versions of Desktop-VIP before installing version
R2003.4.
If you have Desktop-VIP version R2003.0 installed, only need to uninstall
Desktop-VIP. You do not need to uninstall Nutcracker, LAM, or Critical Patent.
If you have Desktop-VIP version W2000 installed on your Windows 2000
machine, you must uninstall VIP and all related software before installing
Desktop-VIP R2003.4. Related software includes LAM W2000 (version 7.1.f
for W2000), Critical PaTENT, and Nutcracker (both pieces). W2000 Nutcracker
libraries are incompatible with the new version of VIP. Uninstall procedures are
described below.
All uninstall procedures must be done as Administrator.
In our experience, uninstalling any software under Windows operating systems
has proven to be fairly unstable. Therefore, it is recommended that you shutdown
and restart ( just not reboot) the machine to clean up dlls and registry entries after
you uninstall any software. This should be done each time you uninstall LAM
software, Critical MPI software and Desktop-VIP NT software.
Uninstall LAM
The procedures for uninstalling LAM W2000 are provided below.
Perform the following steps to uninstall the LAM W2000.
2. Select Program Files -> LAM W2000 -> License Tool Manager. The
LMTOOLS window opens.
3. Click the Configuration using Services radio button.
4. Under the Stop/Stop/Reread tab, click Stop Server to stop the daemon.
5. Under the Configure Services tab, click Remove Service to remove the
service.
6. Click Yes in the Confirmation dialog box.
7. After removing the service, go to Control Panel -> Add/Remove Programs.
8. Select Landmark LAM W2000 and click Change/Remove.
9. Shutdown and restart the computer.
10. Click Yes on the Confirm File Deletion panel.
Uninstall Critical MPI Software
Perform the following steps to uninstall the Critical MPI software (only required
if you are running parallel SMP):
2. Select Settings -> Control Panel.
3. Double-click the Services icon (located under Control Panel ->
Administrator Tools for W2000.
4. On the Services panel, click on PATENT MPI to highlight it.
5. Click Stop.
6. Click Close.
7. Double-click the Add/Remove Programs icon on the Control Panel.
8. Click on PATENT MPI 4.0 to highlight it.
9. Click on Add/Remove to remove the installation.
11. Click OK to close the panel.
12. Shutdown/Restart the machine.
Uninstall Nutcracker Software
Perform the following steps to uninstall the Nutcracker software.
1. Click Start on the Windows Taskbar.
3. Double-click the Add/Remove Programs icon.
4. Highlight Nutcracker Operating Environment to select it and click
Change/Remove.
6. Highlight Nutcracker UNIX or Linux Utilities to select it and click
Change/Remove.
8. Close the Control panel.
9. Shutdown and restart the computer.
Uninstall Older Versions of Desktop-VIP Software
Perform the following steps to uninstall any older versions of Desktop-VIP
software:
4. Click on Landmark VIP <version> to highlight it.
7. Click OK.
8. Click OK on Add/Remove Panel.
9. Shutdown/Restart the machine.
Desktop-VIP 2003.4 Release Notes Page 93 Appendix I: Uninstall Desktop-VIP R2003.4
Appendix I: Uninstall Desktop-VIP R2003.4
Perform the following steps if you need to uninstall the the current version of
Desktop-VIP (R2003.4).
NOTE: 1. All uninstall procedures must be done as Administrator.
2. You do not need to uninstall NutCracker, Genias, etc. if you plan to
reinstall at a later date. The install process will detect this software
and ignore that step in the load process.
4. Click on Landmark VIP Version R2003.4 to highlight it.
6. Confirm (click OK) on the File Component Deletion message.
7. You receive a Locked File Detection message for the Viprshserver.exe. Click
Reboot. This will reboot the service and continue.
8. You receive a second Locked File Detection message. Click Reboot. This will
reboot the service and continue.
9. The Setup Complete window opens. Click the Yes I Want to Restart my
Computer Now option on the window. Then click Finish.
The computer will reboot.
Desktop-VIP 2003.4 Release Notes Page 94 Appendix I: Uninstall Desktop-VIP R2003.4

Release Notes

Uploaded by

Copyright:

Available Formats

Release Notes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Release Notes

Uploaded by

Copyright:

Available Formats

Landmark Desktop-VIP

Desktop-VIP 2003.4 Release Notes Page 1

You might also like