dms 5000.3.1 release notes - landmark software manager

Landmark Decision Management System (DMS)

R5000.3.1 of 47 December 2009

DMS 5000.3.1

Release Notes

What’s In This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Third Party Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

International Trade Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing and Configuring the DMS Software . . . . . . . . . . . . . . . . . . . . . 11

New Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Fixed Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Known Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Appendix A: Running DMS on the DMS Grid . . . . . . . . . . . . . . . . . . . . . . 26

Appendix B: Running DMS on a Torque Cluster . . . . . . . . . . . . . . . . . . . 33

Contacting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


R5000.3.1 of 47 December 2009

What’s In This Release

The R5000.3.1 release of the DMS software provides limited new functionality and bug fixes.

To go directly to the enhancements, bug fixes, and known issues for the DMS software, click on the blue links below:

New Functionality

Fixed Problems

Known Problems

The following sections are also provided in this document:

Introduction

System Requirements

Installing and Configuring the DMS Software

Licensing

Troubleshooting


R5000.3.1 of 47 December 2009

Introduction

Landmark's Decision Management System (DMS) software is an uncertainty analysis and decision management tool for optimizing field development and production strategies. Users can create jobs that model uncertainty using a variety of methods and that explore alternative solutions using an optimizer.

The DMS software incorporates workflows for each of the following products:

• VIP™ software

• Nexus™ software

• FieldPlan®software

• Microsoft® Office Excel©

• MBAL™

• GAP™

• ECLIPSE®

• OptQuest®

• CMG® (IMEX, STARS, and GEM)

These workflows are enabled by particular keys in the Landmark license file. The VIP, Nexus, FieldPlan, MBAL, GAP, ECLIPSE, and CMG workflows require that you have licensed versions of these applications.

All DMS workflows are documented in the DMS online help system.


R5000.3.1 of 47 December 2009

System Requirements

The DMS software runs primarily on Windows workstations. However, when appropriately configured, the software can submit simulation jobs to remote Windows or Linux workstations.

In order to use this functionality, you must install the required simulator executables on the remote machines and configure the DMS job agent, job agent registry, and grid application to be used. Results from the remote jobs are returned to the Windows machine from which the jobs were submitted.

For information on how to run DMS jobs on a DMS Grid, see “Appendix A: Running DMS on the DMS Grid”.

For information on how to run DMS jobs on a Torque cluster, see “Appendix B: Running DMS on a Torque Cluster”.

Upgrades to Existing Project Stores and Data Stores

LWOS

Important: The DMS software will upgrade the R5000.3.0 LWOS (or any earlier versions) the first time you run R5000.3.1. The LWOS upgrade may require that DMS be restarted to complete the upgrade process. The DMS software will prompt you if a restart is necessary.

If the LWOS upgrade procedure is unsuccessful you will need to create a new LWOS.

As a precaution, before you install this version of DMS, you should make a copy of your existing lightweight object server folder (LWOS) and your existing job results databases (.mdb’s).

If you have problems running the new version of DMS with any of your existing DMS projects, you may have to create a new LWOS. To do this, close DMS, remove the existing LWOS folder, and restart DMS. A new LWOS directory will be created automatically. Your LWOS folder is located in the Documents and Settings folder:

C:\Documents and Settings\<username>\Landmark\DecisionSpace\lwos

Access Databases

The DMS software will upgrade your DMS R5000.0 Access databases the first time that you attempt to load data from them. A notification message will prompt you to that the upgrade is about to occur. You should make copies of your .mdb's before you allow them to be upgraded.


R5000.3.1 of 47 December 2009

Hardware Requirements

The table below lists the hardware requirements for Windows workstations running R5000.3.1. The DMS software will run on the minimum requirements listed below. However, performance may not reach acceptable levels with large or complex data sets.

Hardware Recommended Configuration

CPU Intel Xeon

Intel 64 or AMD Opteron (running 32-bit operating system)

Memory (RAM) 2.0 GB or greater

Hard Disk 300 MB Installation size only.

Display Dual monitor in TwinView: 1280 x 1024 per monitor

Color Depth: True Color (32 bit)

Installation Device Drive CD-ROM


R5000.3.1 of 47 December 2009

Software Requirements

R5000.3.1 has been tested on Windows XP workstations and laptops only. Some grid configurations on Linux have also been tested.The table below lists the Windows software requirements necessary to run client installations of R5000.3.1 on Windows workstations.

For information on installing LAM 5000.0.0, refer to the LAM Guide for Release 5000.0.0.

Software Version (for PC Client)

Operating System Windows XP Professional - Service Pack 3

LAM 5000.0.0 LAM 5000.0.0 is required to run R5000.3.1. The installation program and the documentation for LAM 5000.0.0 can be downloaded from the Landmark Software Manager web site.

VIP simulators Needed for running VIP workflows.

Nexus simulators Needed for running Nexus workflows.

FieldPlan Needed for running FieldPlan workflows.

GAP Needed for running GAP workflows.

MBAL Needed for running GAP and MBAL workflows.

ECLIPSE Needed for running ECLIPSE workflows.

PROSPER May be needed for running GAP workflows that incorporate links to PROSPER projects.

CMG Needed for running IMEX, STARS, GEM, Report workflows.

MS Excel 2003 or 2007 The DMS software will not run spreadsheet workflows with Excel 2000.

MS Access 2003® or 2007

Needed for writing DMS results directly to a database. An alternative is to use Microsoft SQL Server.

SQL Server SQL Server can be used instead of Access 2003 or 2007 for the DMS results database. The DMS software has been tested with SQL Server 2005 and SQL Server 2008, including the Express versions of those versions.

OPTTEK OptQuest 6.4 Needed for running optimization workflows.

Note: OPPTEK OptQuest is installed automatically as part of the DMS install.

Perl Needed for some VIP, Nexus, and ECLIPSE workflows that involve Perl scripts.

Adobe Acrobat Reader™ Adobe Reader 7.x or later.


R5000.3.1 of 47 December 2009

DMS Configuration

The DMS workflows include interaction with the following products. If you intend to use workflows that require these applications, you must install the applications independently of DMS. (OptQuest is an exception. It gets loaded automatically when you install DMS.)

• VIP simulators

• Nexus simulators

• FieldPlan

• Microsoft® Excel 2003 or 2007(necessary for spreadsheet workflows)

• Microsoft® Access 2003 (necessary for writing output data directly to a database)

• Spotfire® (optional)

• MBAL

• GAP

• ECLIPSE

• CMG (IMEX, STARS, GEM, Report)

• OptQuest

• SQL Server (optional)


R5000.3.1 of 47 December 2009

Third Party Applications

Halliburton uses various third-party applications in the development of its software.

Halliburton acknowledges that certain third party code has been bundled with, or embedded in, its software. The licensors of this third party code, and the terms and conditions of their respective licenses, may be found at the following location:

..\DecisionSpaceDMS5000.3.1\help\com\lgc\dspx\Third_Party.pdf


R5000.3.1 of 47 December 2009

International Trade Compliance

This application is manufactured or designed using U.S. origin technology and is therefore subject to the export control laws of the United States. Any use or further disposition of such items is subject to U.S. law. Exports from the United States and any re-export thereafter may require a formal export license authorization from the government. If there are doubts about the requirements of the applicable law, it is recommended that the buyer obtain qualified legal advice. These items cannot be used in the design, production, use, or storage of chemical, biological, or nuclear weapons, or missiles of any kind.

The ECCN’s provided in Release Notes represent Halliburton’s opinion of the correct classification for the product today (based on the original software and/or original hardware). Classifications are subject to change. If you have any questions or need assistance please contact us at:

[email protected]

Under the U.S. Export Administration Regulations (EAR), the U.S. Government assigns your organization or client, as exporter/importer of record, responsibility for determining the correct authorization for the item at the time of export/import. Restrictions may apply to shipments based on the products, the customer, or the country of destination, and an export license may be required by the Department of Commerce prior to shipment. The U.S. Bureau of Industry and Security provides a website to assist you with determining the need for a license and with information regarding where to obtain help.

The URL is:

http://www.bis.doc.gov

mailto:[email protected]

http://www.bis.doc.gov


R5000.3.1 of 47 December 2009

Definitions

CCATS (Commodity Classification Automated Tracking System) - the tracking number assigned by the U.S. Bureau of Industry and Security (BIS) to products formally reviewed and classified by the government. The CCATS provides information concerning export/re-export authorizations, available exceptions, and conditions.

ECCN (Export Control Classification Number) -The ECCN is an alpha-numeric code, e.g., 3A001, that describes a particular item or type of item, and shows the controls placed on that item. The CCL (Commerce Control List) is divided into ten broad categories, and each category is further subdivided into five product groups. The CCL is available on the EAR Website.

The ECCN Number, License Type, and the CCATS Numbers for this product are included in the table below. Also included is the date the table was last updated.

Product/Component/R5000ECCN

Number LicenseCCATS Number

Last Date Updated

DMS 5D002 ENC G031851 2/11/2008

DMS Utilities 5D002 ENC G054691 2/11/2008

http://www.access.gpo.gov/bis/ear/ear_data.html#ccl

http://www.access.gpo.gov/bis/ear/ear_data.html#ccl


R5000.3.1 of 47 December 2009

Installing and Configuring the DMS Software

Installation

1. Log into the client machine with a Windows XP user account that belongs to the Administrators group on the machine to which you are installing the software.Caution: Performing the install as the system Administrator can be risky, particularly if you delete existing folders, since all child folders will be deleted.

2. Download the DMS 5000.3.1 install image from the Landmark Software Manager (LSM) site.

3. Navigate to the directory where the install image resides.

4. Double click on “setup.exe.”The DMS 5000.3.1installer displays.

5. Click Next in the Introduction panel of the wizard.

6. If you agree to comply with the Landmark software agreement, toggle the “I accept the terms of the License Agreement.” radio button ON.By toggling the button ON, you agree to comply with the license agreement. If you do not toggle this button ON, you cannot continue with the install.

7. Click Next.

8. If you want to view the release notes, toggle the Release Notes option ON.

9. Click Next.

10.Specify where you want the DMS 5000.3.1 installation to reside on your machine. The location that you specify can not have spaces or special characters.

11. Click Next.

12.Specify Typical.( For this installer, the Typical and Custom options perform the same installation.)

13.Click Next.


R5000.3.1 of 47 December 2009

14. If you are installing on a system where DMS 5000.3.1 has already been installed, and if there are still modules from the previous installation in the selected folder, the following tab will display.

Select whether you want to launch the uninstall wizard, specify a new location, continue and overwrite the existing installed folders, or abort the job.Caution: If you select Delete Existing Folders, you may delete some folders and data that are not related to the Nexus-VIP installation.

15.Click Next.

16.Review your selections and check that you have sufficient disk space on your machine.

17.Click Install to perform the installation.The installer will immediately install the DMS 5000.3.1software.

InstallAnywhere will display the progress of the installation. When all of the files have been installed, a message will announce that the installation has completed.

18.Click Done.


R5000.3.1 of 47 December 2009

Configuration

You must configure the DMS software to use the simulators that are required for the workflows that you intend to use.

VIP and Nexus Simulator Installation

To obtain the most recent versions of the VIP and Nexus simulators, users should contact their Landmark sales office. The DMS history matching utility requires VIP simulators with the release version “r17” or later.

If you have a Nexus installation available, use the Utilities -> Configuration -> Nexus Configuration option to select the location and executables of the Nexus simulators that you want DMS to use.

If you have a VIP installation available, use the Utilities -> Configuration -> VIP Configuration option to select the location and executables of the VIP simulators that you want DMS to use.

ECLIPSE Configuration

To configure the ECLIPSE installation, use the Utilities->Configuration -> Eclipse Configuration option to specify the path to the $eclipse.bat file. Include the $eclipse.bat file in the path definition.

CMG Configuration

To configure the CMG installation, use the Utilities->Configuration -> CMG Configuration option to specify the path to the IMEX .exe, STARS .exe, GEM .exe, and the report.exe files.

OptQuest Installation

OptQuest gets installed as part of the DMS installation. However, the user must have the DMS_OPT and DMS_OPT_OPTQUEST license keys enabled in the Landmark license.dat file to run OptQuest.

SQL Server Installation

DMS now can store results databases and exported databases in SQL Server (in addition to MS Access) . The SQL Server installation must be configured as follows:

• SQL Server or SQL Server Express must be installed, either on the local machine or on a machine accessible via the user's local area network.

• TCP/IP must be enabled as a SQL Server protocol.

• Dynamic TCP ports must be disabled (i.e., set to blank/no value).


R5000.3.1 of 47 December 2009

• A static TCP port number must be assigned (“1433” is the suggested value).

• The DMS users Windows IDs must be added to SQL Server's Logins list, since DMS uses Windows integrated security to log into SQL Server.

• DMS users must able to create databases on SQL Server, so they must be assigned the "dbcreator" role in SQL Server.


R5000.3.1 of 47 December 2009

New Functionality

This release of DMS provides the following new functionality:

• Multi-scenario licensing for running Nexus jobs on multiple nodes of a cluster.

• Compatibility with Nexus 5000.0.2 (which uses different names for spreadsheet columns generated by the simulator)

• Support for the new Nexus-VIP observed data format (.csv).

Multi-scenario Licensing

This release of DMS provides a special licensing feature that allows multiple licenses to be checked out by DMS for parallel jobs submitted on DMS Grid and Torque clusters. A new field in the job submittal dialog box allows the user to specify how many NEXUSPM licenses should be checked out. This field becomes active if the DMS installation has a valid multi-scenario license.

multi-scenariolicensing option


R5000.3.1 of 47 December 2009

The Number of processor licenses Nexus will use per invocation option specifies how many NEXUSPM processor licenses will be checked out by DMS. This number must correspond to the number of processors specified in the Nexus parallel processing scripts used by Nexus Grid or Torque. Changing this setting does not change the number of processors allocated to Nexus. The Nexus multi-scenario job will fail if the specified value does not exactly correspond to the number of processes specified in the parallel processing scripts.

Compatibility with Nexus 5000.0.2

The Nexus 5000.0.2 simulators require batch commands that use the arguments -c <case> and -s <study>. DMS honors the new command syntax when submitting jobs with the Nexus 5000.0.2 simulators.

The Nexus 5000.0.2 simulator writes different column headings to results spreadsheets than were used in previous Nexus releases. DMS R5000.3.1 allows you to select whether you want to use the new column headings or retain the old (pre-R5000.3.1) column headings when running jobs with the Nexus R5000.0.2 simulators.

You can specify which type of column heading to use in the DMS - Configuration for Nexus dialog box (Utilities -> Configuration -> Nexus Configuration).

Toggle on the Use Old Nexus Spreadsheet Column Names in Nexus Model Builder option to use the original column headings.

With this option enabled, the pre-Nexus 5000.0.2 column names will be listed in the Nexus job builder, stored in the results database, and displayed with the results browser and post-processing utility.

Without this options enabled, the new Nexus 5000.0.2 column names will be listed in the Nexus job builder, stored in the results database, and displayed with the results browser and post-processing utility. If you have jobs that you built while using earlier versions of the Nexus simulators, and you save them without enabling this option, the old jobs will be updated with the new Nexus 5000.0.2 column names.


R5000.3.1 of 47 December 2009

New Observed Data Format

The Nexus 5000.0.2 release introduced a new observed data format (.csv) that is more flexible than the pre-5000.0.2 format (.obs). DMS 5000.3.1 history matching supports both the new Nexus 5000.0.2 observed data format and the previous format.

Note: You must use the “.csv” extension for observed data files that use the new observed data format. If you use the “.obs” extension, the history matching wizard will issue an error message that the data format is invalid.

For a discussion of the new and old observed data formats, see “Appendix A: OBS File Formats” in the Nexus SimConvert User Guide.

Fixed Problems

• DMS failed when processing lines that contain only spaces. (tar 819315)

• New dates could not be created in the one-line jython script used in expressions. (tar 819318)

• DMS did not include flux boundary files in the simulation deck. (tar 818879)

• In the history matching workflow, the default scaling type “Max” was not computed for each node unless you selected Max in the data table. (tar 809914 )

• In the history matching workflow, if you selected “apply this scaling to all nodes,” you got the Max value for that node applied to all nodes. (tar 809924)

• In the history matching workflow, if you set up the weights panel and then deselected the data, DMS would hang or performance would be sluggish. (tar 809929)

• When creating a history matching job, there was a problem in the objective function's clipping behavior for scale types other than Max. (tar 809931)

• When building a spreadsheet with uncertainty optimization job, after calculated result statistics were defined, if the calculator panel was reopened, an error box displayed. (tar 810327)

• The history matching wizard failed while loading an observed data file with tabs in the start date. (tar 810605)

• Calculators were lost when a job was converted from an uncertainty job to an optimization job or vice versa. (tar 810733)

• For CMG jobs, DMS would always run IMEX. (tar 810397)

• A numeric format error would occur with Portuguese (Brazil) regional settings on Windows. (tar 810602)

• Excessive memory was being used when serializing jobs to send to a job agent. (tar


R5000.3.1 of 47 December 2009

810707)

• The regions spreadsheet was not being processed by DMS for Nexus simulation jobs. (tar 820190)

• DMS was taking a long time to open a GAP model in the model builder. (tar 820194)

• The Save function did not work for GAP and MBAL Model builder if two wells had the same PROSPER model. (tar 820195)

• When running an uncertainty plus optimization job on the DMS Grid, the job monitor only showed one bar instead of two. (tar 820196)

• DMS was removing spaces inside quoted strings in expressions. (tar 820197)

• The start date in the spreadsheet was not honored when running a job that used a spreadsheet plus simulator combined model. (tar 820284)

• The database-to-spreadsheet workflow did not pull correct data from the simulator to the spreadsheet under certain circumstances. (tar 820192)

• The database-to-spreadsheet workflow failed if the data from simulator was pulled from an uncertainty and optimization combined model. (tar 820661)

• If a file was created outside of DMS and then added to a DMS file directory, it would not be available for defining file uncertainty parameters. (tar 823330)

• A job using a calculator failed when a vector or time series was returned instead of a scalar. (tar 825114)


R5000.3.1 of 47 December 2009

Known Problems

The following is a partial list of the known problems in this release.

• When you use Nexus multi-scenario licensing option, extraneous LAM messages will be written to the DMS log file. This output will be visible in the DMS console if you have started DMS with the "DecisionSpaceDMS 5000.3.1 with console window" shortcut. The messages are not errors and can be ignored. They have the following appearance:(LAM_VERSION=5000.005) 300000001: LAM: dumpCache BEGINS(LAM_VERSION=5000.005) 300000001: ----(LAM_VERSION=5000.005) 300000001: (0) Name=<DMS>(LAM_VERSION=5000.005) 300000001: (0) Version=<5000>(LAM_VERSION=5000.005) 300000001: (0) Uovr=<010D1DA8>(LAM_VERSION=5000.005) 300000001: (0) Bhrs=<0>(LAM_VERSION=5000.005) 300000001: (0) Seats=<1>(LAM_VERSION=5000.005) 300000001: (0) Lngr=<0>(LAM_VERSION=5000.005) 300000001: (0) ChkdOut=<1>(LAM_VERSION=5000.005) 300000001: ----

• In a file-based model builder, after file parameters were added to scenarios, the DMS model would not get saved or the token would not get replaced properly when running job. (tar 816286)

• The “Export to PPTX or MHT file option” exports files in either PowerPoint or HTML archive format. The PPTX output is written in the PowerPoint 2007 format. To view the data in PowerPoint, you must either install PowerPoint 2007 or download PowerPoint Viewer 2007, which is free. You can download PowerPoint 2007 from here. (tar 801234)

• The Save As option in the model builders is disabled if you edit the existing model before saving it with a new model name. The option works if you invoke it before you perform any edits on the model. (tar 806036)

• PowerPoint files created with the Post-processing utility can not be viewed with PowerPoint 2003. PowerPoint 2007 is needed. You can view the files in either the full PowerPoint 2007 version of the free viewer version. (tar 801234)

• For the export to work correctly for a GAP model that has parameters in an MBAL or PROSPER submodel, the user will have to open the model first, edit something, then save the model. (The user can just edit a parameter and click OK without changing anything. The edit is performed only so that the Save button becomes active). Once the edit has been performed, the model will have the information that is needed for the export to work correctly. (tar 804152)

• DMS R5000.0 results databases do not need to be upgraded. However, DMS will upgrade existing results databases (Access and SQL Server databases) from older

http://www.microsoft.com/downloads/details.aspx?familyid=048dc840-14e1-467d-8dca-19d2a8fd7485&displaylang=en


R5000.3.1 of 47 December 2009

versions of DMS in order to access their data. This upgrade is not backward-compatible. If you want to continue to access the data with previous versions of DMS, you should create a backup version of the results databases before allowing DMS to update them.

• Experimental design does not handle truncated distributions with granularity settings in a predictable way. (tar 761317)

• DMS does not notify you why a job has ended prematurely. For example, an optimization job may complete before the specified number of iterations because all possible combinations of values have been tried. In this case, the job ends with a “Finished” message, but no message informs you why the job finished prematurely. (tar 718031)

• Experimental design fails if the DMS model contains more than twenty continuous distribution uncertainty variables. (tar 761101)

• IMEX doesn’t have an output type of Field. It does have an output type of Group, and by default it creates two groups, one for all producers and another for all injectors. To create an optimization job based on IMEX field level results, you can do the following:1. Create an IMEX-based DMS model that contains decision variables.2. Create a job and select the following as outputs in the Results Settings dialog box:Type of Summary = GroupName of Node = Default-Field-PROColumn in Summary File = output to be optimized(The results will include production data only, without injection data.)

• Some GAP results cannot be retrieved from OpenServer, even though the results appear in the GAP results table and the OpenServer string can be extracted from the table. This problem occurs with results that appear in the Results table after running prediction. The workaround is to use only OpenServer strings that are listed in the Results tables before running prediction.

• Results browser: When launching the data browser, you can select a job that does not have data in the database because the data has been deleted or because the original database has been replaced. Making this selection will cause a DecisionSpace Recovery Dialog Box message to display. (tar 731222)

• DMS has been tested on Windows XP in English only. Applying different language settings to the Windows XP has not been tested.

• The security setting on MS Access may prevent DMS from using Access database. The workaround is to set the Access security level to low. (tar 617355)

• Windows XP Service Pack 3 may cause problems displaying the help system. SP3 automatically sets the Internet Explorer security to a higher level than previous service


R5000.3.1 of 47 December 2009

packs did. As a result, you may have to approve the display of each page of the help system. To eliminate this requirement, you can reset the IE security settings to allow active content. (Tools -> Internet Options -> Advanced -> Security -> Allow Active Content to Run in Files on My Computer). (tar 627476)

• DMS does not stop running if the individual VIP, Nexus, MBAL, GAP, etc., jobs fail to produce the desired outputs. (tar 630452)

• DMS does not monitor whether simulation or spreadsheet inputs are valid. You must check that the original project files are valid and that uncertainty parameters, expressions, and scripts do not generate invalid inputs that will cause the simulation application or spreadsheet to fail. (tar 630963)

• Large models that run without a problem in their primary application may cause DMS to fail due to insufficient memory. (tar 700976)

• Entering large integer numbers (for example, “1e10”) in a parameter setting field may cause unpredictable values to appear in the field. (tar 617378)

• GAP jobs launched by DMS will fail if spaces occur in the paths of the associated GAP and MBAL projects. To avoid this problem, place the GAP and MBAL projects in directories whose paths do not contain spaces. (tar 718098)

• DMS results will be lost if the Access database size exceeds 2 GB. Access databases used in DMS will become unusable if the size of the database exceeds 2 GB. Workarounds are to create a new database as the size gets close to 2 GB and to store smaller amounts of information in the database. An alternative workaround is to use SQL Server, which typically can hold larger amounts of data than Access. (tar 719070)

• When viewing the DMS “About DecisionSpace” in Mozilla Firefox, if you click on the More Information link, Firefox displays a blank page. (tar 807299)

• If you specify constraints for an optimization job in the Constraints tab, and then load a suggested solutions file in the Suggested Solutions tab, the constraints will be lost. You must load the suggested solutions file before you define the constraints. (tar 807423)

• Scripts of an existing history matching job may be overwritten by scripts that have been created for a new history matching job. This problem occurs if the new history matching job has the same name as the existing script but has different capitalization. (tar 807504)

• If you export and then restore your jobs, models, and databases, you may have to restore certain Petex files manually. The import/export utility exports only .gap, .mbi, and .out files. It does not export other auxiliary files which may be used by the Petex models. If you export and then restore a Petex model that has auxiliary files, you will have to copy the auxiliary files to your ../Documents and Settings/<user_name>/Landmark/DecisionSpace/dms/import/data/models/<model name> folder. (tar


R5000.3.1 of 47 December 2009

804078)

• When setting the Orthogonal Arrays sampling rules, you must set the Number of Iterations parameter to 4 or greater and the Level parameter to a value of 2 , 3, or 4 (no more, no less). If your parameters do not meet these requirements, you will not be able to save the job. Instead, the wizard will provide a Close button instead of a Finish button, and you will be queried whether you want to close the job without saving your changes. The job builder will reset the sampling rules to Base Case the next time you open the job.


R5000.3.1 of 47 December 2009

Licensing

DMS functionality is enabled by various license keys.

DMS Licenses

To run all of the workflows bundled with this version of DMS, a workstation must have the following licenses:

• DMS - Allows you to build models and jobs in DMS without executing workflows.

• DMS_Nexus - Allows you to run workflows with Nexus.

• DMS_ECLIPSE - Allows you to run workflows with ECLIPSE.

• DMS_GRID - Allows you to use DMS in a distributed environment using DMS Grid or using a third-party queueing system such as Sun Grid Engine or Torque or Platform LSF.

• DMS_GRID_UD - Allows you to run DMS in a distributed environment with a United Devices (UD) grid.

• DMS_HIST - Allows you to run the DMS history matching utility.

• DMS_OPT - Allows you to run optimization jobs with DMS.

• DMS_OPT_OPTQUEST - Allows you to run optimization jobs with OptQuest software. (OptQuest is currently the only optimizer that runs with DMS.)

• DMS_PETEX - Allows you to build models and run workflows with Petroleum Experts software (MBAL, GAP, and, if required by GAP models, PROSPER).

• DMS_SPREADSHEET - Allows you to run spreadsheet workflows (using Excel spreadsheets).

• DMS_VIP - Allows you to run VIP workflows using VIP-CORE and VIP-EXEC.

• DMS_POSTPROC - Allows you to use the DMS post-processing utility to view database results in histograms, time series plots, crossplots, tornado charts, correlation matrices, and various tables.

• DMS_CMG - Allows you to run IMEX workflows.

Nexus Licenses for Multi-scenario Parallel Job Submission on a Cluster

In addition to the standard Nexus licenses, multi-scenario Nexus jobs require the following Nexus license keys:

• NEXUSMS - Enables the multi-scenario feature.

• NEXUSPM - Enables parallel processing on a single processor. You must have a


R5000.3.1 of 47 December 2009

NEXUSPM license for each processor to be used in the parallel job.

Other Licenses

Depending on which workflows you want to use, you may also need one or more active licenses for the following products:

• VIP - Allows you to run VIP, a Landmark reservoir simulation product.

• Nexus - Allows you to run Nexus, a Landmark reservoir simulation product.

• FieldPlan - Allows you to run FieldPlan, a Landmark field development planning product.

• GAP - Allows you to run GAP, a Petroleum Experts product.

• MBAL - Allows you to run MBAL, a Petroleum Experts product.

• PROSPER - May be needed for some GAP models that also invoke PROSPER, a Petroleum Experts product.

• Spotfire - Allows you to run Spotfire®, a third party data analysis product.

• ECLIPSE - Allows you to run ECLIPSE, a Schlumberger reservoir simulation product.

• CMG - Allows you to run the IMEX, STARS, and GEM CMG reservoir simulation products.


R5000.3.1 of 47 December 2009

Troubleshooting

Obtaining General Log Information

The main DMS window provides a log pane where you can view messages related to the the actions that you perform with the application. You can filter the messages that appear in this pane by selecting among the following filter settings:

• ALL - Displays all messages that get generated by the application, including warnings, severe warnings , and much routine information that is related to software services, modules, and objects. Some of this information may be useful for debugging. Much of it is predictable and not significant.

• INFO - Displays warnings, severe warnings, and messages related to actions that you perform. Some of this information may be useful for debugging.

• WARNING - Displays warnings and severe warnings only.

• SEVERE - Displays severe warnings only.

In general, the various settings filter the information in order to control the volume of messages displayed. ALL displays the most messages. SEVERE displays the fewest.

You can also save the contents of the log window at any time by clicking on the Save Log Content to File icon and specifying a text file where the contents will be saved.


R5000.3.1 of 47 December 2009

Appendix A: Running DMS on the DMS Grid

Overview

DMS Grid is a small-scale queue management system that is designed to allow a user to run multiple jobs on two to four Windows PCs at the same time.

The grid consists of the following components:

• DMS installation - a system where DMS has been installed. The DMS installation is used to create jobs and submit them to DMS Grid.

• nodes - a set of networked computers where multiple DMS jobs can be run simultaneously

• job agent - a process that can accept jobs from DMS and assign them to grid runners on nodes of the grid

• jog agent registry - a list of known machines running job agents. (Note: Typical cases of DMS grid use only a single job agent running on the same node as the DMS GUI.)

• grid runner - a process that runs on the grid nodes. It accepts jobs from the job agent, executes them, and sends back the results.

• file staging directory - a shared directory used by DMS to share files and other inputs for jobs that will be executed by each of the assigned DMS GRID runners. This file staging directory is where grid runners read job inputs and write job outputs.

Prerequisites

• The appropriate simulators must be accessible from all nodes of the grid. Simulator installation requirements depend on the job types to be run.

• DMS software must be installed in a folder that is accessible to all nodes of the grid. (Alternatively, DMS can be installed on each node of the grid.)

• All nodes of the grid must have network connectivity to a Landmark license server that has valid licenses for the various DMS features that will be used by the remote jobs. The license server must also have a valid DMS_GRID license.

• All nodes of the grid must have network connectivity to valid licenses for the particular simulators that will be run.

• All nodes of the grid must have read/write access to a “file staging directory” where job submit files are assigned to grid runners by the DMS job agent.


R5000.3.1 of 47 December 2009

How a Job Agent Works

The job agent assigns jobs to “grid runners” on the various nodes of the grid. Jobs that have been assigned appear in the shared directory as .job files. Each job submitted by the DMS job agent has a unique subdirectory created according to this pattern: ({ip address}_{time_value}_{counter}) . The subdirectory contains the following files:

• algorithm file (alg.obj)• argument input files (argin_##.obj)• argument output files (argout_##.obj)

Once a DMS grid runner has finished its assigned .job file, it renames .job extensions to .done to alert the DMS job agent that it is available for another task.

Configuring the DMS Grid

Configuration consists of creating an environment variable and setting the appropriate entries in the JobAgent.properties and SgsRunner.properties files. These files reside in the ../modules/jobagent/batch directories of the system where DMS is installed. If DMS is installed on the individual nodes of the grid, the SgsRunner.properties files reside on the nodes where the simulators will run.

Configure the Job Agent

1. Install DMS on the system that will run the DMS application.

2. Create a DMS file staging directory on the system that will run the DMS application.For example, the default file staging directory defined in the JobAgent.properties files isc:/dms/sgs/stagingYou could create an equivalent directory on the system where you have installed DMS. Or you could create a different directory and edit the JobAgent.properties files accordingly.

3. Grant read/write access to the staging directory so that other nodes in the DMS grid have access to the directory.

4. Create a COM_LGC_EDMS_JOB_REGISTRY environment variable that points to the local machine as the job agent.For example, if the local machine is TRISTRAM, create a COM_LGC_EDMS_JOB_REGISTRY environment variable and set it to “TRISTRAM.”


R5000.3.1 of 47 December 2009

5. In the ..\modules\jobagent\batch folder, edit the JobAgent.properties file as follows:Set the shared files directory:

com.lgc.edms.fileStagingDirectory=C:/dms/sgs/staging

(i.e., the directory that you shared in Step 2)Set the job agent to use the local algorithm dispatcher.

com.lgc.edms.algorithmDispatcher=Sgs


R5000.3.1 of 47 December 2009

Configure the Grid Runners

Perform the following steps to configure the grid runners on the nodes of DMS Grid.

Note: If you have installed DMS on each of the nodes of the grid, you edit the individual SgsRunner.properties file in the batch directory on each of the nodes. If you have installed DMS in a shared directory that is mounted from each of the nodes of the grid, you edit the SgsRunner.properties file in the DMS installation’s shared batch directory. (In the latter case, the same SgsRunner.properties file is used by all the nodes.)

In the example shown below, items that will need to be customized for the deployment environment are shown in red.

1. Check that the node machine can access the shared directory on the system where you installed DMS.

2. In the ..\modules\jobagent\batch folder, edit the SgsRunner.properties file as follows:Set the file staging directory to the shared files directory on the system where you installed DMS:Example:

com.lgc.edms.fileStagingDirectory= \\\\<machine_name>\\staging Important: At the top of the .properties file, see the instructions on how paths must be defined. The paths that you define must conform to these rules or the job grid runner will not find the shared directory. Note in particular, the following statement:

# Path separators should be entered using '\\' or '/'. A single '\' will not work.Set the number of seconds that the grid runner should remain idle before scanning the shared directory for additional job files:Example:

com.lgc.edms.sgsIdle=1Set the paths for the simulators to be used by the DMS jobs. Example:# VIP properties

com.lgc.edms.VIPCore=C:/Landmark/Nexus-VIP5000.0.2/nexussimulators/Windows32/core32_5000_0_2.exe


R5000.3.1 of 47 December 2009

com.lgc.edms.VIPExec=C:/Landmark/Nexus-VIP5000.0.2/nexussimulators/

Windows32/exec32_5000_0_2.exe

Running DMS with DMS Grid

In a typical configuration, running DMS jobs on the DMS grid requires launching a job agent and job registry on the machine where DMS is installed.

Launching the Job Agent and Job Registry on the Node where DMS Runs

Perform the following steps on the system where you have installed DMS.

1. Within the DMS install directory, locate the start-all.bat file in the modules\jobagent\batch directory.

2. Execute start-all either by double-clicking it from Windows Explorer or invoking it from the command line after navigating to its directory.

This will start a job agent registry and a job agent. The machine's network name will be added to the registry that was started. (This is the job registry that is identified by your COM_LGC_EDMS_JOB_REGISTRY setting.)

Launching the Grid Runners on the Grid Nodes

Perform the following steps on the systems that you have configured as grid nodes.

1. Within the DMS install directory, locate the SgsRunner.bat or SgsRunner.sh file in the modules\jobagent\batch directory.

2. If the node is a Windows machine, launch the grid runner by invoking it from the command line as follows:sgsRunner.bat runnerName1(where “runnerName1” is an arbitrary name for the grid runner)

3. If the node is a Linux machine, launch the grid runner by invoking it from the command line as follows:./sgsRunner.sh runnerName1(where “runnerName1” is a unique name for the grid runner)


R5000.3.1 of 47 December 2009

Submitting Jobs to the DMS Grid

This procedure assumes that you have already created the job that you want to submit to the DMS grid. See the DMS online help for instructions on how to create DMS jobs.

With the job agent running locally, and the grid runners running on the nodes of the DMS Grid, perform the following steps on the system where DMS is installed.

1. Launch DMS.

2. Select the job to be submitted in the Jobs List.

3. Click on the Run Job icon.

4. In the Submit Job dialog box, select the job agent option in the Execute Job field.

5. Select the database where the job results should be stored.

6. Click on OK.

As the job is performed, the following events will occur on the DMS Grid:

• On the system where DMS is installed, the DMS Job Agent window will post results as the iterations are performed.

• On the system where DMS is installed, the shared directory will display .job file names as the iterations are performed. When the job is completed, the .job name will be converted to a .done name.

• If you have specified that particular simulation files be saved (outside of the DMS database), these files will be written back to the directory specified by the DMS job.


R5000.3.1 of 47 December 2009

Other Possible Configurations

The configuration described above places the DMS application, job agent/registry, and shared directory on a single machine and launches grid runners on other nodes of the grid. This configuration can be varied as follows:

• The shared directory does not have to be on the same machine as the DMS installation. If you place it on a different machine, you must change the jobAgent.properties and SgsRunner.properties settings for the shared directory accordingly.

• The job agent does not have to run on the same machine as the DMS installation. If you choose to run the job agent on a different system, you must change the jobAgent.properties settings on that machine. You must also change the COM_LGC_EDMS_JOB_REGISTRY setting on the system where DMS is installed to point to the system where the job agent will run. You must launch the job agent on the other system before running DMS, so that DMS can connect to it when DMS gets launched.

• You can run one or more grid runners on the system where DMS is installed. In this case, you must launch the grid runners on the system where DMS runs before you submit a job.

• You can run multiple grid runners on a single node. To do this, simply run the sgsRunner.bat (or sgsRunner.sh on Linux) executable multiple times on a node, each time providing a different runner name. As a rule, you should run only one runner per processor or per core.


R5000.3.1 of 47 December 2009

Appendix B: Running DMS on a Torque Cluster

Overview

The Torque cluster is a distributed computer node system that allows batch job submission and uses the Torque resource manager to queue the jobs. The following discussion describes how to configure DMS to run jobs on a Torque cluster.

The DMS implementation on the Torque cluster consists of the following components:

• DMS installation - a system where DMS has been installed

• Torque cluster - a set of Linux Red Hat 5 workstations where multiple DMS jobs can be run simultaneously. Jobs are managed by the Torque Resource Manager.

• job agent - a DMS process that mediates between DMS and Torque. The job agent submits jobs to Torque, which in turn submits the jobs to the Torque cluster.

• job agent registry - a DMS list of known machines running job agents. (Note: Typical cases use only a single job agent running on the same node as the DMS GUI.)

• file staging directory - a shared directory used by DMS to store files and other inputs for jobs that will be executed by the Torque cluster. This file staging directory is also provides a convenient location for the script files required by the Torque management system to run jobs.

Prerequisites

This set of instructions assumes the following prerequisites:

• A Red Hat Enterprise Linux 5 cluster must be configured and the Torque job and queue management tools must be installed and working.

• The Torque nodes must be a platform supported by DecisionSpace (i.e., 64-bit Red Hat Enterprise 5 on AMD or Intel processors).

• RPMs for OpenMotif 2.2.3 and libXp 1.0.0 must be installed on each of the nodes of the cluster.

• The appropriate DMS-supported simulators must be installed in directories that are accessible from all nodes of the grid. Simulator installation requirements depend on

Important: The assistance of a system administrator will probably be required to complete some of the cluster-side installation and configuration tasks described in this appendix, as well as to provide some of the necessary information for configuring DMS.


R5000.3.1 of 47 December 2009

the job types to be run. DMS supports the following simulators on the Torque cluster -- Nexus, VIP, and ECLIPSE.

• DMS software must be installed in a folder that is accessible from all nodes of the grid.

• All nodes of the grid must have network connectivity to a Landmark license server that has valid licenses for the various DMS features to be used by the remote jobs. The license server must also have a valid DMS_GRID license.

• All nodes of the grid must have network connectivity to valid licenses for the particular simulators that will be run.

• All nodes of the grid must have read/write access to a “file staging directory” where job input files are distributed by the DMS job agent.

Configure Job Agent and Job Registry

Note: These instructions assume that the DMS application, the DMS job registry, and the DMS job agent all run on the same Windows PC.

For this configuration, a directory accessible to both the Windows PC and the cluster machines is required. In the examples below, this directory appears as U:\ on the Windows PC and as /usr/local/dms_staging on the cluster machines.

The shared directory contains a “scripts” subdirectory which will contain some batch files and shell scripts which you or your system administrator must provide. The “Create Script Files and Configuration Files” section below provides examples of the required batch files and shell scripts.

On the Windows PC, you will need to edit the job agent’s properties file. This is located in a folder under the main DMS installation folder called modules\jobagent\batch. The properties file is called JobAgent.properties.

In the example shown below, items that will need to be customized for the deployment environment are shown in red.

Add the following lines to JobAgent.properties:

# Torque

com.lgc.edms.algorithmDispatcher=Sge5

com.lgc.edms.fileStagingDirectory=u:\\

com.lgc.edms.fileStagingDirectoryLinux=/usr/local/dms_staging

com.lgc.edms.runRemote=u:\\scripts\\submitdmsjob.bat

com.lgc.edms.maxPendingCluster=0


R5000.3.1 of 47 December 2009

(Note that backslashes in the properties file are an escape character and must be doubled to denote an actual backslash. Alternatively, you can use a single forward slash.)

If the JobAgent.properties file has been modified previously, be sure that any other settings for com.lgc.edms.algorithmDispatcher are commented out or removed.

Explanation of settings

The algorithmDispatcher=Sge5 string sets the job agent to use the DMS algorithm dispatcher for external job queuing systems.

The fileStagingDirectory and fileStagingDirectoryLinux settings refer to the common folder that is accessible by both the Windows PC and the Linux cluster. The first setting is the folder's name as seen on Windows, and the second setting is the folder's name as seen on Linux.

The runRemote setting is the name of the batch file that DMS will launch on Windows to submit an iteration to the cluster. An example of this batch file is presented later in this document.

The maxPendingCluster setting lets you limit the number of iterations that are simultaneously running on the cluster. This setting is optional. If it is not present or set to 0, DMS dispatches iterations to the cluster as soon as it can generate them. If this setting is present, DMS limits the number of iterations simultaneously running on the cluster to this value.

Configure DMS to Find the Job Registry

DMS uses an environment variable called COM_LGC_EDMS_JOB_REGISTRY to find the job registry. DMS will submit jobs to the job agent via the job registry. Set the environment variable to the Windows machine name of the PC running the job registry.

Example:

set COM_LGC_EDMS_JOB_REGISTRY=%COMPUTERNAME%


R5000.3.1 of 47 December 2009

Create Script Files and Configuration Files

The DMS-Torque configuration uses the batch files and script shells listed below to execute DMS jobs on the nodes of the Torque cluster. Templates for these files are deployed in the following directory:

..\Landmark\DecisionSpaceDMS5000.3.1\modules\jobagent\batch\cluster_examplesYou can copy the templates, place them in the shared "scripts" directory on the system where DMS is installed, and edit them as appropriate for your environment.

In the example files shown below, items that will need to be customized for the deployment environment are shown in red.

Script Files

You must create the following script files and place them in the “scripts” subdirectory of the shared directory where the job inputs and outputs get written.

submitdmsjob.bat

This batch file is executed by the job agent. The function of this batch file is to use SSH to execute a command on the cluster. The example below uses the plink application from PuTTY and a public key identity file to avoid password prompts:

@echo off

setlocal

set CLUSTER_USER=username

set IDENTITY_FILE=c:\Putty\data\MyKey.ppk

set CLUSTER_HOST=torquehost.mydomain.com

set CLUSTER_SUBMIT=/usr/local/dms_staging/scripts/submitdmsjob.sh

plink -l %CLUSTER_USER% -i %IDENTITY_FILE% %CLUSTER_HOST%%CLUSTER_SUBMIT% %*

Explanation of Settings

CLUSTER_USER is the Linux username that will be used to log on to the cluster.

IDENTITY_FILE is the PuTTY public key identity file used with Plink. If you are using a different authentication method (for example, passwords), you will need to modify this batch file to incorporate settings appropriate for the method that you are using.


R5000.3.1 of 47 December 2009

CLUSTER_HOST is the hostname of the cluster node where DMS will log on to submit jobs.

CLUSTER_SUBMIT is the command that will be executed on the Linux cluster to submit the DMS iteration to the queueing system.

submitdmsjob.sh

This script file is executed by submitdmsjob.bat (via SSH), and submits a DMS job to Torque.

#!/bin/sh

DMS_QSUBMIT=/usr/local/bin/qsub

DMS_QSUBMIT_QUEUE_NAME="batch"

DMS_RUNJOB=/usr/local/dms_staging/rundmsjob.sh

DMS_SUBSCRIPT_DIR=/tmp/dms

mkdir -p ${DMS_SUBSCRIPT_DIR}

DMS_SUBSCRIPT=${DMS_SUBSCRIPT_DIR}/${RANDOM}.pbs

echo #PBS -m n >${DMS_SUBSCRIPT}

echo #PBS –q ${DMS_QSUBMIT_QUEUE_NAME} >>${DMS_SUBSCRIPT}

echo ${DMS_RUNJOB} $@ >>${DMS_SUBSCRIPT}

${DMS_QSUBMIT} ${DMS_SUBSCRIPT}

rm ${DMS_SUBSCRIPT}


DMS_QSUBMIT is the command to submit a job to the queueing system.

DMS_QSUBMIT_QUEUE_NAME is the Torque queue name.

DMS_RUNJOB is the command that will be executed when the queueing system runs the submitted job.

DMS_SUBSCRIPT_DIR is the directory where the temporary PBS script will be created for the queue submission command.


R5000.3.1 of 47 December 2009

rundmsjob.sh

This is the script file that actually executes the DMS cluster component, which in turn executes Nexus, VIP, etc.

#!/bin/bash

export LM_LICENSE_FILE=2013@licensehost

DMS_HOME=/usr/local/DecisionSpaceDMS5000.3.1

DMS_SCRIPTS=/usr/local/dms_staging/scripts

# VIP Core and Exec

export COM_LGC_EDMS_VIPCORE=${DMS_SCRIPTS}/vipcore.sh

export COM_LGC_EDMS_VIPEXEC=${DMS_SCRIPTS}/vipexec.sh

# Nexus Standalone and Nexus exe

export COM_LGC_EDMS_NEXUSSA=${DMS_SCRIPTS}/standalone.sh

export COM_LGC_EDMS_NEXUSEXE=${DMS_SCRIPTS}/nexus.sh

# Other DMS environment variables as necessary for additional simulators

DMS_PLATFORM=linux64

JAVA_HOME=${DMS_HOME}/jre

DMS_BIN=${DMS_HOME}/modules/dsinfra_native/bin/${DMS_PLATFORM}

CLASSPATH=${DMS_HOME}/modules/edms/jar/com_lgc_edms.jar:${DMS_HOME}/modules/dsinfra/jar/\*:${DMS_HOME}/modules/dsinfra_native/jar/\*

export CLASSPATH

LD_LIBRARY_PATH=${DMS_BIN}:${LD_LIBRARY_PATH}

export LD_LIBRARY_PATH

${JAVA_HOME}/bin/java \

com.lgc.edms.dispatchers.sge5.SgeRemoteExecute $@


LM_LICENSE_FILE is the FlexLM license setting.

DMS_HOME is the directory where DMS is installed on the cluster.

DMS_SCRIPTS is the directory where various DMS scripts are located.


R5000.3.1 of 47 December 2009

COM_LGC_EDMS_VIPCORE, COM_LGC_EDMS_VIPEXEC, COM_LGC_EDMS_NEXUSSA and COM_LGC_EDMS_NEXUSEXE are the scripts launched by DMS to execute VIP Core, VIP Exec, Standalone and Nexus, respectively.

Simulator Scripts

These are simple wrapper scripts for the simulator executables. They serve as a handy place to put a custom LD_LIBRARY_PATH or other settings. If you already have scripts to handle launching the simulator executables you can use those instead.

nexusvip_env.sh

#!/bin/sh

# environment variables for running flow simulators from DMS

DMS_VIPNEXUS_DIR=/usr/local/Landmark/Nexus-VIP5000.0.2/nexussimulators/LinuxEM64

DMS_VIPNEXUS_LDPATH=${DMS_VIPNEXUS_DIR}/HP-MPI/lib/linux_amd64

DMS_VIPCORE_EXE=${DMS_VIPNEXUS_DIR}/coreEM64_5000_0_2.exe

DMS_VIPEXEC_EXE=${DMS_VIPNEXUS_DIR}/execEM64_5000_0_2.exe

DMS_STANDALONE_EXE=${DMS_VIPNEXUS_DIR}/standaloneEM64_5000_0_2.exe

DMS_NEXUS_EXE=${DMS_VIPNEXUS_DIR}/nexusEM64_5000_0_2.exe

# set the LD path

LD_LIBRARY_PATH=${DMS_VIPNEXUS_LDPATH}:${LD_LIBRARY_PATH}

export LD_LIBRARY_PATH

vipcore.sh

#!/bin/sh

. /usr/local/dms_staging/scripts/nexusvip_env.sh

${DMS_VIPCORE_EXE} $@

vipexec.sh

#!/bin/sh. /usr/local/dms_staging/scripts/nexusvip_env.sh${DMS_VIPEXEC_EXE} $@


R5000.3.1 of 47 December 2009

standalone.sh

#!/bin/sh. /usr/local/dms_staging/scripts/nexusvip_env.sh${DMS_STANDALONE_EXE} $@

nexus.sh

#!/bin/sh

. /usr/local/dms_staging/scripts/nexusvip_env.sh

${DMS_NEXUS_EXE} $@

PuTTY/Plink Notes

The first time you connect to a Linux system using PuTTY or plink.exe, you will be prompted to accept or reject the new (to PuTTY) host key. If this happens while running plink from a batch file from DMS, the batch file will become “stuck.” To prevent this from happening, connect to the Linux system manually using PuTTY or plink outside of DMS before trying to do so from DMS via the batch file. Be sure to use the exact host name that you will use in the DMS batch file.

To use public key authentication with plink, you will need to use the PuTTY utility puttygen.exe to generate a public/private key pair, and then install the public key on the Linux system. See Chapter 8 in the PuTTY User Guide for details on how to generate the key pair and for details on how to install the public key on the Linux system.

The PuTTY home page: http://www.chiark.greenend.org.uk/~sgtatham/putty/

Run DMS

Running DMS jobs on the Torque cluster requires launching a job agent on the machine where DMS is installed.

Launch the Job Agent

Perform the following steps on the system where you have installed DMS.

1. Within the DMS install directory, locate the start-all.bat file in the modules\jobagent\batch directory.

2. Execute start-all either by double-clicking it from Windows Explorer or invoking it from the command line after navigating to its directory.


R5000.3.1 of 47 December 2009

This will start a job agent registry and a job agent. The machine's network name will be added to the registry that was started. (This is the job registry that is identified by your COM_LGC_EDMS_JOB_REGISTRY setting.)

Submit Jobs

This procedure assumes that you have already created the job that you want to submit to the cluster. See the DMS online help for instructions on how to create DMS jobs.

With the job agent running locally, perform the following steps on the system where DMS is installed.

1. Launch DMS.

2. Select the job to be submitted in the Jobs List.

3. Click on the Run Job icon.

4. In the Submit Job dialog box, select the job agent option in the Execute Job field.

5. Select the database where the job results should be stored.

6. Click on OK.

As the job is performed, the following events will occur on the cluster:

• On the system where DMS is installed, the DMS Job Agent window will post results as the iterations are performed.

• On the system where DMS is installed, the shared directory will display .job file names as the iterations are performed. When the job is completed, the .job name will be converted to a .done name.

• If you have specified that particular simulation files be saved (outside of the DMS database), these files will be written back to the directory specified by the DMS job.


R5000.3.1 of 47 December 2009

Contacting Support

Landmark operates Technical Assistance Centers (TACs) in Australia, the United Kingdom, and the United States. Additional support is also provided through local support offices around the world. Local support office information is listed below. If problems cannot be resolved at the district level, our escalation team is called to resolve your incidents quickly.

Support information is always available on the Landmark Graphics Support internet page located at: http://css.lgc.com/CustomerSupport/CustomerSupportHome.jsp.

Technical Assistance Centers

North America7:30 am - 5:30 pm Central Standard TimeMonday - Friday, excluding holidays

713-839-2200 (Houston, TX, USA)Toll Free 1-877-435-7542(1-877-HELP-LGC)Fax: 713-839-2168 (Houston, TX)Fax: 907-275-2655 (Anchorage, AK)Fax: 303-796-0807 (Denver, CO)Fax: 403-262-1929 (Calgary, Canada)

Email: [email protected]

Latin America (Spanish, Portuguese, English)7:00 am - 5:00 pm Central Standard TimeLocal normal business hours

1-713-839-3405 (Houston,TX,USA)Fax: 713-839-3646Email: [email protected]

Toll Free from:Argentina: 0800-800-5263Brazil: 0800-891-0837Chile: 800-201-898Colombia: 01800-915-4743Mexico: 001-888-438-1296Peru: 0800-51634Trinidad: 1-888-438-1296 Venezuela: 0-800-526-3627

Toll Free from local area:Ecuador (Quito) (02)226-1908

Europe, Africa, Middle East8:00 am - 5:30 pm Local TimeMonday - Friday, excluding holidays

44-1372-868686 (Leatherhead, UK)Fax: 44-1372-868601 (Leatherhead, UK)Fax: 44-1224-723260 (Aberdeen, UK)Email: [email protected]

http://css.lgc.com/CustomerSupport/CustomerSupportHome.jsp







mailto: [email protected]




R5000.3.1 of 47 December 2009

Asia, Pacific 8:00 am - 5:00 pm Local TimeMonday-Friday, excluding holidays

61-8-9481-4488 (Perth, Australia)Toll-free 1-800-448-488Fax: 61-8-9481-1580Email:[email protected]

Toll-Free from:China: 10-800-6100-253 Indonesia: 001-803-61284 Japan: 00531-61-0021 Malaysia 1800-803-687 New Zealand 0800-400-555 South Korea 00308-61-0046 Taiwan 0080-161-1350Thailand 001-800-611-2784

Toll Free from local area:Vietnam: 84-8-9191901India: 91-11-622-1885 (c/o Samit Enterprises)

District Support Offices

Algeria (Algiers)8:30 am - 4:30 pm Local TimeSaturday - Wednesday excluding holidays

21-337-7239Email: [email protected]

Angola (Luanda)8:00 am - 5:00 pm Local TimeMonday - Friday, excluding holidays

213 2137 7239Email: [email protected]

Argentina (Buenos Aires)9:00 am - 6:00 pmLocal time

54-11-4312-8411Toll Free 0800-800-5263Fax: 54-11-4311-9566Email: [email protected]

Australia (Perth)8:00 am - 5:00 pm Local TimeMonday - Friday, excluding holidays


Brazil (Rio de Janeiro)8:00 am - 5:30 pmLocal Time

55-21-3974-4000 orToll Free 0800-891-0837Fax: 55-21-3974-4002Email: [email protected]

Brunei (Bandar Seri Bagawan)8:30 am - 5:30 pm Local TimeMonday - Friday, excluding holidays

67-3-233-5319Email: [email protected]









R5000.3.1 of 47 December 2009

Canada (Calgary)7:30 am - 5:30 pm Central Standard TimeMonday-Friday, excluding holidays

Toll Free 1-877-435-7542(1-877-HELP-LGC)Fax: 403-262-1929 (Calgary, Canada)Fax: 713-830-2168 (Houston, TX)Email: [email protected]

Chile (TAO TAC, Houston, Texas)Local normal business hours

Toll Free 800-201-898Fax: 1-713-839-3646Email: [email protected]

Colombia (Bogota)8:00 am - 5:00 pmLocal Time

57-1-326-400057-1-326-6710Toll Free 01800-915-4743Fax: 57-1-326-6717Email: [email protected]

Ecuador (Quito)8:00 am - 5:00 pmLocal Time

59-32-226-1844 Toll Free from Quito (02)226-1908Fax: 59-32-226-2590Email: [email protected]

Egypt (Cairo)8:00 am - 4:00 pm Local TimeSaturday - Wednesday, excluding holidays

20-2-759-1717(ask for Landmark Technical Support)Email: [email protected]

India (New Delhi)9:00 am - 5:30 pm Local TimeLocal Business Days, excluding holidays

91-11-622-1885(c/o Samit Enterprises)Fax: 91-11-647-9246Email: [email protected]

Indonesia (Jakarta)7:30 am - 4:30 pm Local TimeMonday - Friday, excluding holidays

62-21-3003-9039 orToll Free 001-803-61284Fax: 62-21-3003-9088Email: [email protected]

Japan8:00 am - 5:00 pm Local TimeMonday - Friday, excluding holidays

Toll Free 00531-61-0021Email: [email protected]

Malaysia (Kuala Lumpur)8:30 am - 5:30 pm Local TimeMonday - Friday, excluding holidays

603-2164-1121 or Toll Free 1-800-803-687Fax: 603-2164-1135Email: [email protected]










R5000.3.1 of 47 December 2009

Mexico (Reynosa)8:00 am - 6:00 pmLocal Time

52-555-208-353352-555-208-3868Toll Free 001-888-438-1296Local Office Fax: 52-555-514-7646Email: [email protected]

New Zealand (New Plymouth)8:00 am - 5:00 pm Local TimeMonday - Friday, excluding holidays


Nigeria (Lagos)8:00 am - 5:00 pm Local TimeMonday - Friday, excluding holidays

234-1-461-0780(ask for Landmark Technical Support)Fax: 234-1-262-0769Email: [email protected]

People's Republic of China (Beijing)9:00 am - 5:30 pm Local TimeMonday - Friday, excluding holidays

86-10-8486-4501Toll Free 10-800-6100-253 or10-800-810-0209Fax: 86-10-8486-4819Email [email protected] or [email protected]

Peru (Lima)Local normal business hours

Toll Free 0800-51634Fax: 001-713-839-9646Email: [email protected]

Russia (Moscow) 7:00 am - 5:00 pm Local TimeLocal Business Days, excluding holidays

7-495-960-29267-495-960-2927(ask for Landmark Technical Support)Fax: 7-095-755-8301Email: [email protected]

South Korea8:00 am - 5:00 pm Local TimeMonday - Friday, excluding holidays


Taiwan8:30 am - 5:30 pm Local TimeMonday-Friday, excluding holidays


Thailand (Bangkok)8:00 am - 5:00pm Local TimeMonday - Friday, excluding holidays

66-2-278-8100Toll Free 001-800-611-2784Fax: 66-2-278-8199Email: [email protected]












R5000.3.1 of 47 December 2009

Helpful internet links are shown below.

Trinidad & Tobago (TAO TAC, Houston, TX)7:00 am - 5:00 pm Central Standard Time(Houston, TX)Local normal business hours

Toll Free: 1-888-438-1296Fax: 1-713-839-3646Email: [email protected]

United Arab Emirates (Dubai)7:00 am - 5:00 pm Local TimeLocal Business Days, excluding holidays

+971-4-3036446(ask for Landmark Technical Support)Fax: +971-4-3315837Email: [email protected][email protected]

United Kingdom8:00 am - 5:30 pm Local TimeMonday - Friday, excluding holidays

44-1372-868686 (Leatherhead)Fax: 44-1372-868601 (Leatherhead)Fax 44-1224-723260 (Aberdeen)Email: [email protected]

United States (Anchorage)7:30 am - 5:30 pm Central Standard TimeMonday - Friday, excluding holidays

Toll Free 1-877-435-7542(1-877-HELP-LGC)Fax: 907-275-2655Email: [email protected]

United States (Denver)7:30 am - 5:30 pm Central Standard TimeMonday - Friday, excluding holidays

Toll Free 1-877-435-7542(1-877-HELP-LGC)Fax: 303-796-0807Email: [email protected]

United States (Houston)7:30 am - 5:30 pm Central Standard TimeMonday - Friday, excluding holidays

713-839-2200Toll Free 1-877-435-7542(1-877-HELP-LGC)Fax: 713-839-2168Email: [email protected]

Venezuela (Caracas) 8:00 am - 5:00 pmLocal Time

58-212-953-0774Toll Free 0-800-526-3627Fax: 58-212-952-3845Email: [email protected]

Vietnam (Ho Chi Minh City)8:00 am - 5:00 pm Local TimeMonday - Friday, excluding holidays

84-8-910-1901Fax: 84-8-910-1902Email: [email protected]

Name Website Address

Landmark Graphics home page http://www.halliburton.com/landmark

Landmark Graphics FTP Site ftp://ftp.lgc.com

Oracle home page http://www.oracle.com













http://www.lgc.com

ftp://ftp.lgc.com

http://www.oracle.com


R5000.3.1 of 47 December 2009

Trademarks

3D Drill View, 3D Drill View KM, 3DFS, 3D Surveillance, 3DView, Active Field Surveillance, Active Reservoir Surveillance, ADC, Advanced Data Transfer, ARIES, ARIES DecisionSuite, AssetConnect, Asset Decision Solution, Asset Development Center, Asset Journal, AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver, AssetObserver Advisor, Asset Performance, AssetPlanner, AssetSolver, AssetSolver Online, AssetView, BLITZPAK, CasingSeat, COMPASS, Corporate Data Archiver, Corporate Data Store, Data Analyzer, DataManager, DataStar, DBPlot, DecisionSpace, DecisionsSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace AssetView 2D, DecisionSpace AssetView 3D, DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace for Production, DecisionSpace Nexus, DecisionSpace PowerGrid, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir, DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion, DecisionSpace WellSolver, DecisionSuite, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery Asset, Discovery PowerStation, DMS, Drillability Suite, Drilling Desktop, DrillModel, Drill-to-the-Earth Model, DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube, EDM, EDT, eLandmark, Engineer’s Data Model, Engineer's Desktop, Engineer’s Link, ESP, Event Similarity Prediction, Executive Assistant, ezFault, ezSurface, ezTracker, FastTrack, FG+, FieldPlan, Field Scenario Planner, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, GeoLink, GeoProbe, GeoProbe GF DataServer, GES, GESXplorer, GMAplus, GMI Imager, GRIDGENR, Handheld Field Operator, HHFO,

I2 Enterprise, iDIMS, IsoMap, iWellFile, Landmark, Landmark Decision Center, Landmark & Design, Landmark Logo and Design, Landscape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Magic Earth, MagicDesk, Make Great Decisions, MathPack, MIMIC, MIMIC+, Model Builder, MyLandmark, Nexus, Object MP, OpenBooks, Open Explorer, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks Development Kit, OpenWorks Well File, OpenWorks Production, PAL, Parallel-VIP, PetroBank, PetroBank Master Data Store, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PostStack Family, PowerCalculator, PowerExplorer, PowerExplorer Connect, PowerGrid, PowerHub, Power Interpretation, PowerJournal, PowerModel, PowerView, PrecisionTarget, Presgraf, PRIZM, Production Asset Manager, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC Server, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMax 4D, ProMax Family, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+, QUICKDIF, QuickWell, QuickWell+, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+, Real Freedom, Real Time Asset Management Center, Real Time Decision Center, Real Time Operations Center, Real Time Production Surveillance, Real Time Surveillance, Real-Time View, Reference Data Manager, RESev, ResMap, RightTime, RTOC, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks 2D, SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerView, SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert, SimDataStudio,SimResults, SimResults+, SimResults+3D, SIVA, SIVA+, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap, StrataModel, StrataSim, StratWorks, StrataWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf & Connect, SynTool, SystemStart, SystemStart for Clients, SystemStart for Servers, SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, The Engineer’s Desktop, Total Drilling Performance, TOW/cs, TOW/cs Revenue Interface, TracPlanner, Trend Form Gridding, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE, VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, Well Seismic Fusion, WellSolver, WellXchange, WOW, Xsection, You're in Control. Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered trademarks or service marks of Landmark Graphics Corporation.

All other trademarks, service marks and product or service names are the trademarks or names of their respective owners.

FLEXlm license management software http://www.macrovision.com

Microsoft SQL 2005 Server home page http://www.microsoft.com/sql/default.asp

Adobe Acrobat Reader http://www.adobe.com

Name Website Address

http://www.macrovision.com/support/by_category/Software_Licensing.shtml

http://www.microsoft.com/sql/default.mspx

http://www.adobe.com