InstConf

8/20/2019 InstConf

1/118

Z-MAP Plus Installation and Configuration Guide

© 2003 Landmark Graphics Corporation

Part No. 161329 October 2003

Z-MAP PlusInstallation

and

8/20/2019 InstConf

2/118

© 2003 Landmark Graphics Corporation

All Rights Reserved Worldwide

This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also

protected by Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed,

stored in a retrieval system, or translated into any human or computer language, in any form or by any means,

electronic, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of:

Landmark Graphics Corporation

Building 1, Suite 200, 2101 CityWest, Houston, Texas 77042, USA

P.O. Box 42806, Houston, Texas 77242, USA

Phone: 713-839-2000

FAX: 713-839-2401

Web: www.lgc.com

Trademark Notice

3D Drill View, 3D Drill View KM, 3Dview, Active Field Surveillance, Active Reservoir Surveillance, ADC,

ARIES, Asset Development Center, Asset Development Centre, Automate, BLITZ, BLITZPAK, CasingSeat,

CDDM, COMPASS, Contouring Assistant, Corporate Data Archiver, Corporate Data Store, DataStar, DBPlot,

Decision Suite, Decisionarium, DecisionDesktop, DecisionSpace, DecisionSpace AssetPlanner, DecisionSpaceAtomic Meshing, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace TrackPlanner,

DecisionSpace Well Seismic Fusion, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Extreme,

DepthTeam Interpreter, DESKTOP-PVT, DESKTOP-VIP, DEX, DFW, DIMS, Discovery, Drillability Suite,

DrillModel, DrillVision, DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube,

EdgeCa$h, eLandmark, Engineer's Desktop, EOS-PAK, EPM, Executive Assistant, FastTrack, FZAP!,

GeoDataLoad, GeoGraphix (stylized), GeoGraphix Exploration System, GeoLink, GES, GESXplorer, GMAplus,

GRIDGENR, Handheld Field Operator, I2 Enterprise, iDIMS, IsoMap, Landmark, Landmark and Design,

Landmark logo and Design, LandScape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep,

Make Great Decisions, MathPack, MIRA, Model Builder, MultiWell, MyLandmark, MyWorkspace, OpenBooks,

OpenExplorer, OpenJournal, OpenOrigin, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks,

OpenWorks Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PlotView, Point Gridding Plus,

Pointing Dispatcher, PostStack, PostStack ESP, PowerView, PRIZM, PROFILE, ProMAGIC, ProMAX,

ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx, QUICKDIF,QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, Real Freedom,

Real-Time Asset Management Center, Real-Time Asset Management Centre, Real Time Knowledge Company,

Reservoir Framework Builder, RESev, ResMap, RMS, SafeStart, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace,

SeisVision, SeisWell, SeisWorks, SeisWorks MultiView, SeisWorks PowerSection, SeisXchange, Sierra,

Sierra (design), SigmaView, SimResults, SIVA, SpecDecomp, StrataMap, StrataModel, StrataAmp, StrataSim,

StratWorks, StressCheck, STRUCT, Surf & Connect, SynTool, SystemStart, SystemStart for Clients,

System Start for Servers, SystemStart for Storage, T2B, TDQ, Team Workspace, TeamView, TERAS,

Total Drilling Performance, TOW/cs The Oilfield Workstation, Trend Form Gridding, Turbo Synthetics, VIP,

VIP-COMP, VIP-CORE, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement,

VIP-THERM, WavX, Web Editor, Web OpenWorks, Wellbase, Wellbore Planner, WELLCAT, WELLPLAN,

WellXchange, WOW, Xsection, Xsource, 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 are the property of their respective owners.

Note

The information contained in this document is subject to change without notice and should not be construed as a

commitment by Landmark Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any

error that may appear in this manual. Some states or jurisdictions do not allow disclaimer of expressed or implied

warranties in certain transactions; therefore, this statement may not apply to you.

8/20/2019 InstConf

3/118

Landmark Z-MAP Plus Installation and Configuration Guide

R2003.12.0 Contents iii

Installation and Configuration Guide

Introduction

Overview of This Guide ..................................................................................... 1

Who Should Read This Guide .......................................................................... 2

How to Use This Guide ..................................................................................... 2

Organization of Guide .................................................................................. 2

Conventions ................................................................................................. 2

Typographical Conventions .................................................................. 2

Product Names and Executable Names ............................................... 3

Contents of This Guide ..................................................................................... 4

Installation and Configuration

Introduction ........................................................................................................ 5

Setting Up Z-MAP Plus with OpenWorks ........................................................ 6

Workstations with OpenWorks ................................................................... 6

Setting Up the Z-MAP Plus Command Menu ....................................... 6

Disk Space Requirements ...................................................................... 7

Establishing a Directory Structure ........................................................ 7

Installing Z-MAP Plus with OpenWorks ..................................................... 8

Using Release Manager to Install the Software ........................................ 9

Contents

8/20/2019 InstConf

4/118


R2003.12.0 Contents iv

Installation and Configuration continued

Setting Up Z-MAP Plus Without OpenWorks .................................................. 16

Workstations Without OpenWorks ............................................................. 16

Setting Up the Z-MAP Plus Command Menu ....................................... 16

Disk Space Requirements ...................................................................... 17

Establishing a Directory Structure ........................................................ 17

Installing Z-MAP Plus Without OpenWorks ............................................... 18

Starting Z-MAP Plus .......................................................................................... 22

Starting Z-MAP Plus from OpenWorks ...................................................... 22

Starting Z-MAP Plus in Standalone Mode .................................................. 24

Troubleshooting ..................................................................................... 24

Adding an Alias for the Start-Up Command .............................................. 24

Workstation Notes ............................................................................................. 25

X Windows Template Files ..................................................................... 25

Solaris Notes ........................................................................................... 26

Color Controls ......................................................................................... 27

Z-MAP Plus Application Licensing .................................................................. 28

OpenWorks License Management ................................................................... 30

Licensing Process ............................................................................................. 31

Common Terms ............................................................................................ 31

How Licensing Works .................................................................................. 32

Version Compatibility .................................................................................. 33

Network Configuration ................................................................................ 33

8/20/2019 InstConf

5/118


R2003.12.0 Contents v

Installation and Configuration: Licensing Process continued

License System Architecture ...................................................................... 34

License Server ........................................................................................ 34

License File Components ...................................................................... 35

License Options File ............................................................................... 37

License Server ................................................................................................... 38

Starting and Stopping the License Server ................................................. 38

Setting the Environment Variable ............................................................... 38

Defining License Groups ............................................................................. 39

NFS with the License System ........................................................................... 40

Licenses and Third-Party Software ................................................................. 41

Managing the License System .................................................................... 41

Separate License Systems .......................................................................... 41

Single License System ................................................................................ 42

License Management Without OpenWorks ..................................................... 43

License Location for Non-OpenWorks Installations ........................... 43

License File Components ...................................................................... 43

Using the License Server on Non-OpenWorks Installations .............. 46

Setting the Environment Variable ......................................................... 48

Configuring Hardcopy

Introduction ........................................................................................................ 49

Hardcopy and Hardcopy Batch ........................................................................ 50

Z-MAP Plus Plotting for OpenWorks Users ............................................... 50

Z-MAP Plus Plotting for Non-OpenWorks Users ....................................... 50

Hardcopy Batch (HDBAT) Input Files ................................................... 52

8/20/2019 InstConf

6/118


R2003.12.0 Contents vi

Configuring HardCopy: Hardcopy and Hardcopy Batch continued

HP-GL Drivers ............................................................................................... 54

Coordinate Space ................................................................................... 54

Roll Feed .................................................................................................. 55

Driver Output ........................................................................................... 55

Eavesdrop Mode ..................................................................................... 55

Prompt Mode ........................................................................................... 56

Absolute Mode ........................................................................................ 56

Workstation Description File for HP-GL Driven Devices .......................... 57

Workstation Type .................................................................................... 57

Workstation Name .................................................................................. 57

Workstation Category ............................................................................ 57

Display Size ............................................................................................. 58

Display Type ............................................................................................ 59

Locator Device Numbers ....................................................................... 59

Color ........................................................................................................ 59

Driver Code ............................................................................................. 59

Device Number ........................................................................................ 60

CGM Drivers ....................................................................................................... 61

Output File .................................................................................................... 61

Elements Generated .................................................................................... 61

Scaling Mode and VDC Extent ............................................................... 62

Color ........................................................................................................ 62

Workstation Description File ...................................................................... 63

Versatec Support ............................................................................................... 64

Using CGMs with Versatec Plotters ........................................................... 64

Customizing Runtime Files ......................................................................... 65

8/20/2019 InstConf

7/118


R2003.12.0 Contents vii

Configuring HardCopy: Versatec Support continued

Running the Hardcopy Programs ............................................................... 66

Workstation Description File (WDFILE)

Introduction ........................................................................................................ 67

Format of a Standard WDFILE .......................................................................... 68

DDENTRY Field Descriptions ........................................................................... 69

DDENTRY Type Number ................................................................................... 71

Driver Codes ...................................................................................................... 72

Device Numbers ................................................................................................ 73

Driver Code Make Numbers .............................................................................. 77

WDFILE Example ............................................................................................... 81

Template Field Descriptions ............................................................................. 88

Template DDENTRY Field ............................................................................ 88

Appendix A.Environment Variables for Mapping Products

Introduction ........................................................................................................ 89

Methods of Setting Environment Variables ............................................... 89

Setting Environment Variables for an OpenWorks User .................... 90

Setting Environment Variables for a Non-OpenWorks User .............. 91

8/20/2019 InstConf

8/118


R2003.12.0 Contents viii

Appendix B. Z-MAP Plus Graphics Environment

Introduction ........................................................................................................ 95

Applications That Use ZIGS ........................................................................ 95What ZIGS Is ................................................................................................. 96

ZIGS and ZGFs ........................................................................................ 96

Device Support .................................................................................................. 97

Workstation Support .................................................................................... 97

Plotter Support ............................................................................................. 97

WDFILES ....................................................................................................... 98

Hardcopy Plotting .............................................................................................. 99

Plotting with HP-GL and CGM Metafiles .................................................... 100

HP-GL ....................................................................................................... 100

CGMs ....................................................................................................... 100

Hardcopy and CGM ...................................................................................... 102

Appendix C. Presentation Quality Fonts

Introduction ........................................................................................................ 103

Filled Font Support ............................................................................................ 104

CGM Text Feature Parameters ......................................................................... 104

Font Mapping Configuration Parameters ........................................................ 105

Font Replacement Parameters ......................................................................... 106

Rules and Syntax ............................................................................................... 107

Font Mapping File Example .............................................................................. 108

Font Replacement Results ............................................................................... 109

Enabling and Disabling Font Replacement ..................................................... 110

8/20/2019 InstConf

9/118


R2003.12.0 Introduction 1

Introduction

Overview of This Guide

The Z-MAP Plus Installation and Configuration Guide covers theinformation and procedures for installing and maintaining an

environment for the Z-MAP Plus family of products. The followingillustration shows the products you will install and configure.

Z-MAP Plus and ZCL are applications. The other components areutilities, including utilities that support hardcopy systems.

This guide is the first one you should examine when you receive thesoftware. It explains the procedures for installing or upgrading thesoftware, configuring your system for various utilities, producinghardcopy, and working with the license application manager (LAM)..

.

The installation program load the products on the Applications and Utilities menus. 3D Viewer is an optional application—it is available

only if you have purchased this option.

8/20/2019 InstConf

10/118

Z-MAP Plus Installation and Configuration Guide Landmark

2 Who Should Read This Guide: Introduction June 1994

Who Should Read This Guide

This guide is for the site manager or system administrator. Tounderstand the concepts and procedures discussed, you must have:

• An understanding of Unix commands

• Familiarity with the Unix file system structure

• Knowledge of a text editor

If you are unfamiliar with these subjects, call your Landmark customer representative for help setting up the system and the software.

How to Use This Guide

Organization of Guide

This guide is organized according to the typical requirements of asystem administrator. It covers the procedures for installing and configuring Z-MAP Plus and hardcopy. Procedures that are platform-

or environment-specific are described in the context in which they areneeded.

Conventions

This topic describes the typographical and naming conventions used to

indicate features of the program.

Typographical Conventions

• Computer printouts, text shown on screens, program entries, and responses you enter appear in a monospaced font:

setenv ZTARGET /usr/ZMAPPlus

ps -eaf | grep lmgrd

8/20/2019 InstConf

11/118


R2003.12.0 Introduction: How to Use This Guide 3

• Text you should replace with your own entry appears inmonospaced italic:

cd directoryname

For example, the entry above means that you should enter cd and

the name of the appropriate directory.

• Entries that are optional appear in brackets:

lprm [-Pqueuename] [-] [job#]

In the example above, you can enter a queue name and a job

number to cancel a specific job from the printer queue. Withneither queuename nor job number entered, the command cancelsthe next job in the queue, provided that you own the job.

Product Names and Executable Names

The following products included on the delivery media are registered trademarks of the Landmark Graphics Corporation:

• Z-MAP Plus

• ZCL

8/20/2019 InstConf

12/118

Z-MAP Plus Installation and Configuration Guide Landmark

4 Contents of This Guide: Introduction June 1994

Contents of This Guide

The Z-MAP Plus Installation and Configuration Guide consists of thefollowing sections:

• Introduction — An overview of content and organization.

• Installing and Configuring Z-MAP Plus — Detailed instructionsfor installing Z-MAP Plus. Relevant aspects of the software and

hardware are discussed, including disk space requirements,directory structures, differences between OpenWorks and non-OpenWorks environments, and platform differences.

• Configuring Hardcopy — The first part of this section describes

the Z-MAP Plus graphics environment in general and hardcopysupport in particular. The second half shows you how to set uphardcopy output to HP-GL and CGM graphics devices.

• Workstation Description File (WDFILE) — Example WDFILE

entries and descriptions of WDFILE fields.

• Appendixes — The appendixes for the Z-MAP Plus Installationand Configuration Guide are organized as follows:

— Environment Variables for Mapping Products

— The Z-MAP Plus Graphics Environment

— Canadian Package DLS Data and Utility Programs

8/20/2019 InstConf

13/118


R2003.12.0 Installation and Configuration 5

Installation and Configuration

Introduction

This section contains detailed steps for installing Z-MAP Plus inOpenWorks and non-OpenWorks environments.

This section covers the following main topics:

• Setting Up Z-MAP Plus with OpenWorks — Information about preparing to install Z-MAP Plus as an OpenWorks application.

• Using Release Manager to Install the Software — Steps for

using the installation program on the CD-ROM.

• Workstations Without OpenWorks — Information about preparing to install Z-MAP Plus as a standalone application.

• Installing Z-MAP Plus Without OpenWorks — How to installZ-MAP Plus from the CD-ROM.

• Starting Z-MAP Plus — How to start the program after you

install it.

• Workstation Notes — Requirements for installing Z-MAP Pluson Solaris workstations.

• Z-MAP Plus Application Licensing — Important informationabout the new application licensing option groups.

• OpenWorks License Management provides steps for installing,starting, and stopping the license manager.

• License Management Without OpenWorks — Steps for installing, starting, and stopping the license manager for standalone or non-OpenWorks installations.

The Z-MAP Plus installation CD-ROM contains a complete set of files

to install and configure Landmark surface modeling applications. Theapplications included on the CD-ROM are Z-MAP Plus, ZCL, and Contouring Assistant products, and various hardcopy and file

conversion programs.

Z-MAP Plus is not available for Hewlett-Packard, IBM-AIX, or DEC platforms.

8/20/2019 InstConf

14/118


R2003.12.0 Installation and Configuration: Setting Up Z-MAP Plus with OpenWorks 6

Setting Up Z-MAP Plus with OpenWorks

Workstations with OpenWorks

The Z-MAP Plus installation CD-ROM is written in OpenWorksCDINSTALL format. It can be used to install Z-MAP Plus on all

platforms. Additional reference information may be found in theOpenWorks installation documentation. See “Installing Applicationswith CDinstall” in the OpenWorks System Administration: Installing OpenWorks guide, and “Managing the License System” in theOpenWorks System Administration: Managing the System guide.

The following sections contain step-by-step installation instructions, aswell as information about application license management.

After you install the software with the installation program, read “Z-MAP Plus Application Licensing” on page 28 and “OpenWorksLicense Management” on page 30.

Setting Up the Z-MAP Plus Command Menu

The Z-MAP Plus Command Menu is a program that executes the other programs in the Z-MAP Plus suite. The data used to build theZ-MAP Plus Command Menu options is defined in the file MappingLauncher.dat in each user’s home directory. The format for MappingLauncher.dat is similar to the format for the OpenWorksCommand Menu, launcher.dat . The original copy of the

MappingLauncher.dat file is stored in the following location:/ZMAPPlus/templates.

The first time you select Z-MAP Plus from the OpenWorks Command Menu or start Z-MAP Plus from a script, if your home directory doesnot contain a copy of the MappingLauncher.dat file, it is automaticallycopied to your home directory. If a version exists from a previous

release, delete it so a new updated file can be automatically copied toyour home directory. This ensures that the current applications and utilities appear in the Z-MAP Plus Command Menu.

To provide users with an option to use Z-MAP Plus with or without anOpenWorks connection, add the following line to the MappingLauncher.dat file:

“Z-MAP Plus Non-OpenWorks” “zmapplussh -n &”

8/20/2019 InstConf

15/118



The only difference between this line and the default line is that itcontains the -n flag that prevents Z-MAP Plus from connecting toOpenWorks. If you edit the MappingLauncher.dat file, remember thatthe only valid way to indent a line is to use tabs.

Disk Space Requirements

Note the following disk space requirements before unloading the

software.

Establishing a Directory Structure

The files on the CD-ROM are organized under a top level directorynamed /ZMAPPlus, which contains several subdirectories. When theCD-ROM is restored, the /ZMAPPlus top level directory and subdirectories are created “relative” to the current working directory.

For example, if you unload the CD-ROM in theZMAPPlus top level directory/ZMAPPlus will becreated. The examples in this section assume the CD-ROM will berestored in the directory /.

Table 1: Disk Space Required for each Platform

Platform Space

SOLARIS 347 Mb

SILICON GRAPHICS 277 Mb

Finding Out about Available Disk Space

To verify that the amount of free disk space is sufficient, use the df (report

number of free disk blocks and files) command.

All Unix examples use C shell syntax. You can use Korn shell or Bourne shell

equivalents as appropriate.

8/20/2019 InstConf

16/118



Installing Z-MAP Plus with OpenWorks

Use the following procedures for preparing to install Z-MAP Plus withOpenWorks.

If you are upgrading from an earlier version of Z-MAP Plus and havecustomized files, back up these files to use with the new Z-MAP Plusinstallation. The files you may have customized and need to back upare listed in the following table.

Compare the contents of the WDFILE used with the previous version of Z-MAP Plus to the new WDFILE provided with this CD-ROM. Mergethe two files if you are missing needed information.

You can make backup copies of the following directly (without

comparing): site-specific hardcopy binaries, data files, color table file,

and license files.

When you restore backup files, be careful not to overwrite the

pre-linked hardcopy binaries provided with the installation CD-ROM.

Table 2: Files to Save from Previous Versions of Z-MAP Plus

File Description Directory

HDCOPY _ nnn or

HDBAT _ nnna

a. This suffix is site-specific.

site-specific hardcopy binaries bin

MFD’s or ZGF’s data or pictures from old system data

WDFILE plotter/digitizer definitions files

ZYCOLOR default color table definition file files

license.dat LAM license file lam

Giving Distinctive Names to Site-Specific Hardcopy Binary Files

If you have designed custom binary files for use with plotters, back these up

before installing the new software. To avoid overwriting the pre-linked

hardcopy binaries from theinstallationCD-ROM, Landmarkadvises youto use

file names that are different from the names of the following pre-linked

hardcopy programs:

HDCOPY

HDBAT

Do not install a new version of Z-MAP Plus into a directory that

contains a previous version of Z-MAP Plus.

8/20/2019 InstConf

17/118



Using Release Manager to Install the Software

The Release Manager program provides a consistent GUI-based interface for installing Z-MAP Plus and other Landmark applications

released on CD-ROM. After you specify the programs to be installed

and the directories in which to install them, the program provides agraphical status display of the installation’s progress. Use the following procedure to install Z-MAP Plus on Solaris and SGI platforms.

The following topic explains how to:

• Start the Release Manager program from a local CD-ROM drive.

• Select the applications to be installed or upgraded.

• Select the file systems in which the applications are to be installed or upgraded.

To install Z-MAP Plus on Solaris and SGI platforms, follow thesesteps:

1. If you are installing to another computer on your network, set theDISPLAY environment variable to see the installation screens onyour machine:

setenv DISPLAY YourMachineName:0.0

2. Insert the Z-MAP Plus CD-ROM into the local drive. If you are

installing from a remote CD-ROM drive, see your systemadministrator to prepare the drive for remote access. Changedirectories to your CD-ROM drive. Change the directory to install

and enter the following command:

./setup

The following messages appear:

|----------------------------------------------|

| Landmark Graphics Corporation |

| Release Manager |

| snapshot #, setup modified on Date |

|----------------------------------------------|

Log files are written to CDINSTALL_LOG

CDINSTALL_LOG is set to: /tmp

Is this correct [y]?

Release Manager will use CDINSTALL_LOG=tmp.

Answer Y for yes and press the Return key.

8/20/2019 InstConf

18/118



3. Enter the full pathname to the OpenWorks installation.

OWHOME is set to: /home//OpenWorks


4. Watch the response of the Release Manager: It returns theOWHOME directory path, automatically detects the operating

system of your machine, then issues a message telling you whichOS version of Z-MAP Plus it will install.

Release Manager will use OWHOME =

/home//OpenWorks

Release Manager (cdi.exe) starting now ...

snapshot #, Date

After a few moments, the following window appears.

This window shows the applications that are available for

installation, any special installation parameters to be used, theversion number of the application, the space in MB required toinstall the application, and the location where the application is to be installed.

Use this window to select the applications you wish to install and to specify the location where they are to be installed

8/20/2019 InstConf

19/118



There are five buttons at the bottom of the window:

• Start — Begin installation.

• System Info — Display a window showing information aboutyour system’s configuration.

• Release Notes — Display a window containing the release notedocument for a selected application.

• Display log — Display messages (if any) written by theinstallation program.

• Exit — Terminate installation.

5. Select the application(s) to install. When you click an option in the

Install Option column, the following menu appears:

• Upgrade — DO NOT USE THIS OPTION.

• Install — Installs the application.

• No Action — Does not install the application. (This is thedefault selection.)

6. Select a location for installing the application.

The Chg Loc column shows the default locations. To change thelocation displayed, click the ellipisis button next to the location.

The Location Selection dialog box appears:

8/20/2019 InstConf

20/118



The Location Selection dialog box shows all file systems to whichyour system is mounted and the space available on each. To selecta file system, click it. Available directories on the file systemappear in the Path area.

7. Click the directory to use for installing Z-MAP Plus. The name of the directory appears in the Selection box. (You can enter the nameof the directory in the Selection box instead of selecting it.)

8. Click OK to select the directory and close the Location Selectiondialog box, or Cancel to close the window without selecting adirectory.

9. Repeat steps 5 through 8 for each application you want to install.

8/20/2019 InstConf

21/118



10. After you have selected the applications you wish to install, and the locations in which to install them, click Start in the SoftwareSelection window. The following dialog box appears:

11. The installation program begins to copy files to the selected filesystem. As the installation proceeds the status bars at the bottom of

the window are updated.

12. When the installation is complete, an xterm window opens and lists the products that were installed.

Finished installing Z-MAP Plus, ...

Press the Return key to continue

The Product License Information screen appears. Click OK .

13. Click Close to close the Release Manager window.

8/20/2019 InstConf

22/118



14. Check the installation status area of the Release Manager - ProductSelection dialog box to determine if the installation wassuccessful. Click Exit to close this dialog box.

15. A confirmation box appears and asks if you want to exit the

installation program. Click Yes.

16. Another confirmation box appears and asks if you want to deletelog files. Click Yes. The Release Manager closes.

17. When you restore the CD-ROM, the top level directory/ZMAPPlus is created, along with the following subdirectories:

OW_SYS_DATA/app-defaults/, bin/, bitmaps/, camacros/, conf/,

data/, docs/, files/, for016/, frame/, help/, htmlhelp/, install/,

kbase/, lam/, lib/, macros/, mfds/, sh/, sys/, and vi/.

18. If a previous version of Z-MAP Plus was installed, before you runthe new version you must first delete the existing MappingLauncher.dat and .mapinit files from each user’s homedirectory:

rm $HOME/MappingLauncher.dat

rm $HOME/.mapinit

A new file for displaying the Z-MAP Plus Command Menu isautomatically placed in each user account’s home directory thefirst time Z-MAP Plus starts.

19. The installation program automatically generates the soft link

from OpenWorks to Z-MAP Plus. Exit your account, then login,start OpenWorks and Z-MAP Plus should execute from theOpenWorks Command Menu.

To enable environmental variables in an OpenWorks environment,enter the environment variable you want to use in an xterm

window before you start OpenWorks or Z-MAP Plus. For example:

setenv MULTI_WINDOW yes

8/20/2019 InstConf

23/118



To turn environmental variables off, close the Z-MAP Pluswindow and the Z-MAP Plus Command Menu, then enter thecommand that reverses the setenv command. For example:

unsetenv MULTI_WINDOW

In most cases, you can add the line to your .cshrc file or .lgcloginto set environment variables, thus automatically enabling thefeature supported by the environment variable at login.

For a list of environmental variables that can be used with mapping products, see “Appendix A. Environment Variables for MappingProducts” on page 89.

20. Z-MAP Plus incorporates FLEXlm license management softwarefrom Globetrotter which utilizes software versioning in thelicense.dat file. License files (license.dat ) from any previousrelease of Z-MAP Plus will not work successfully due to this

feature. A new license.dat file must be obtained from theLandmark representative before Z-MAP Plus 1998.1 can besuccessfully executed. Activate and configure the applicationlicenses. (For details, see “OpenWorks License Management” on page 30.)

21. Read “Configuring Hardcopy” starting on page 49.

22. Begin a Z-MAP Plus session from the OpenWorks Command Menu: Select Applications → Z-MAP Plus to initialize the

Z-MAP Plus Command Menu (as described in “Starting

Z-MAP Plus from OpenWorks” on page 22).For information about Z-MAP Plus, see the Introduction section in theZ-MAP Plus Reference Manual or select Help → Online Manuals →Reference Manual from the Z-MAP Plus Command Menu.

A good place to begin learning about Z-MAP Plus is the User’s Guide(Help → Online Manuals → User Guide). This book provides atutorial and introductions to the most important concepts and features

of the program.

To learn what is new in each release, see the Help → Helpcontext-sensitive, browser-based system. The home page features the

newest features and changes for each version of Z-MAP Plus.

8/20/2019 InstConf

24/118


R2003.12.0 Installation and Configuration: Setting Up Z-MAP Plus Without OpenWorks 16

Setting Up Z-MAP Plus Without OpenWorks

Workstations Without OpenWorksInstalling Z-MAP Plus in a non-OpenWorks environment is verysimilar to installing in the OpenWorks environment, except for four important differences:

• Setting the environmental variable OWHOME during theinstallation. (OWHOME is not a directory.)

• The location of the license file.

• Starting the Licensing Manager.

• Modifying the MappingLauncher.dat file to indicate that you do

not want OpenWorks connections for Z-MAP Plus and ZCL.Before installing Z-MAP Plus, you must be prepared to meet systemrequirements, and you should be familiar with the directory structureon the product CD-ROM.

Setting Up the Z-MAP Plus Command Menu

The Z-MAP Plus Command Menu executes the programs in theZ-MAP Plus suite. The data used to build the Z-MAP Plus Command

Menu options is defined in the file MappingLauncher.dat in each user’s

home directory. The original copy of this file is located at/ZMAPPlus/templates.

The first time you start Z-MAP Plus from the OpenWorks Command Menu or from a script, the MappingLauncher.dat file is automatically

copied to your home directory, if the file does not already exist. If aversion exists from a previous release, delete it so an updated file can be automatically copied to your home directory. If you are using anoutdated MappingLauncher.dat file, the Z-MAP Plus Command Menudoes not display new options that have been added in the currentrelease.

8/20/2019 InstConf

25/118



Disk Space Requirements

Note the following disk space requirements before unloading the

software.

Establishing a Directory Structure

The files on the CD-ROM are organized under a top-level directorynamed /ZMAPPlus, which contains several subdirectories. When theCD-ROM is restored, the /ZMAPPlus top level directory and

subdirectories are created relative to the current working directory.For example, if you unload the CD-ROM in theZ-MAP Plus top-level directory /ZMAPPlus is created.

The examples in this section assume the CD-ROM is restored in thedirectory / .

Table 3: Disk Space Required for each Platform

Platform Space

SOLARIS 368 Mb

SGI 310 Mb

Finding Out about Available Disk Space

To verify that the amount of free disk space is sufficient, use the “df” (report

number of free disk blocks and files) command.

All Unix examples use C shell syntax. You can use Korn shell or Bourne shell

equivalents as appropriate.

8/20/2019 InstConf

26/118



Installing Z-MAP Plus Without OpenWorks

This section contains the procedures for installing Z-MAP Plus withoutOpenWorks.

If you have been using an earlier version of Z-MAP Plus, you maywant to back up certain files for use with the present version. The filesthat you may have customized and may want to save are listed in thefollowing table.

Compare the contents of the WDFILE used with the previous version of Z-MAP Plus to the new WDFILE provided with this CD-ROM. Mergethe two files if you are missing needed information.

You should make backup copies of the following directly (withoutcomparing): site-specific hardcopy binaries, data files, color table file,

digitizer files and license files.

When you restore the backup files, be careful not to overwrite the pre-linked hardcopy binaries provided with the installation software.

Table 4: Files to Save from Previous Versions of Z-MAP Plus

File Description Directory

HDCOPY _ nnn or

HDBAT _ nnna

a. This suffix is site-specific.

site-specific hardcopy binaries bin

MFD’s or ZGF’s data or pictures from old system data

WDFILE plotter/digitizer definitions files

ZYCOLOR default color table definition file files

license.dat LAM license file lam

Giving Distinctive Names to Site-Specific Hardcopy Binary Files

If you have custom binary files for use with plotters, back these up before you

restore theCD-ROM. To avoidoverwriting thepre-linked hardcopy binaries on

the installation CD-ROM, Landmark advises you to use file names that are

different from the names of the following pre-linked hardcopy programs:

HDCOPY

HDBAT

Do not install a new version of Z-MAP Plus into a directory that

contains a previous version of Z-MAP Plus.

8/20/2019 InstConf

27/118



1. Install the CD by following the instructions described in “UsingRelease Manager to Install the Software” on page 9. The onlydifference will be setting the location of OWHOME — you should substitute the full pathname to the new install directory:

The following message appears:

|----------------------------------------------|

| Landmark Graphics Corporation |

| Release Manager |

| snapshot #, setup modified on date |

|----------------------------------------------|

Log files are written to CDINSTALL_LOG

CDINSTALL_LOG is set to: /tmp


Release Manager will use CDINSTALL_LOG=tmp.

2. Complete the installation as previously described.

3. When you restore the CD, the top level directory /ZMAPPlus iscreated, along with the following subdirectories:

app-defaults/, bin/, bitmaps/, camacros/, conf/, data/, docs/, files/,

for016/, frame/, help/, htmlhelp/, install/, kbase/, lam/, lib/,

macros/, mfds/, and sh/.

8/20/2019 InstConf

28/118



4. For a standalone installation, login as root and modify the/ZMAPPlus/templates/MappingLauncher.dat filewith a -n flag as shown in the following examples. The -n flagindicates that you do not want to initialize an OpenWorks

connection for Z-MAP Plus or its related applications.”Z-MAP Plus” ”zmapplussh -n &”

”ZCL” ”zclsh -n &”

Remember, the only valid way to indent is to use tabs.

5. Make the software available to users by modifying login files and appending an alias definition to execute the ZMAPPlus shell script.Insert the following line in each user’s .cshrc file:

alias ZMAPPlus /ZMAPPlus/sh/ZMAPPlus

6. If a previous version of Z-MAP Plus had been installed, before

running the new version you must first delete the existing MappingLauncher.dat and .mapinit files from each user account’s

home directory:

rm $HOME/MappingLauncher.dat

rm $HOME/.mapinit

A new MappingLauncher.dat is copied automatically to each user account’s home directory when Z-MAP Plus starts.

7. In a non-OpenWorks environment, enter the environment variableyou want to enable in an xterm window before you start theZ-MAP Plus Command Menu or Z-MAP Plus. In most cases, youcan add a line to the .cshrc file to set environment variables, thusautomatically enabling the feature supported by the environment

variable. For example:

setenv MULTI_WINDOW yes

To turn an environment variable off, close the Z-MAP Pluswindow and the Z-MAP Plus Command Menu, then enter thecommand that reverses the setenv command. For example:

unsetenv MULTI_WINDOW

To review a master list of environmental variables you can use

with mapping products, see “Appendix A. Environment Variablesfor Mapping Products” on page 89.

8/20/2019 InstConf

29/118



8. Z-MAP Plus incorporates FLEXlm license management softwarefrom Globetrotter which utilizes software versioning in thelicense.dat file. License files (license.dat ) from any previousrelease of Z-MAP Plus will not work successfully due to this

feature. A new license.dat file must be obtained from theLandmark representative before Z-MAP Plus can be successfullyexecuted.

Activate and configure the application licenses. For details, see“License Management Without OpenWorks” on page 43.

9. Read Section 3, “Configuring Hardcopy.”

10. You are now ready to begin a Z-MAP Plus session. You can startZ-MAP Plus two different ways. See “Starting Z-MAP Plus inStandalone Mode” on page 24.

For information about Z-MAP Plus see the Introduction section in theZ-MAP Plus Reference Manual or choose Help → Online Manuals →

Reference Manual from the Z-MAP Plus Command Menu.

For beginners, a good place to learn about Z-MAP Plus is the User’s

Guide (Help → Online Manuals → User Guide). This book providesa tutorial and introductions to the most important concepts and featuresof the program.

To learn what is new in each release, see the Help → Helpcontext-sensitive, browser-based system. The home page featuresinformation about the newest features and changes for each version of

Z-MAP Plus.

8/20/2019 InstConf

30/118


R2003.12.0 Installation and Configuration: Starting Z-MAP Plus 22

Starting Z-MAP Plus

Once the software is properly installed and configured, you can startZ-MAP Plus by using any of the following interfaces:

• OpenWorks Command Menu

• Z-MAP Plus Command Menu

• xterm window

Determining which method is right for you depends on how your

particular environment is defined. The remainder of this sectiondescribes how to use each of these three methods.

In the following discussion, refers to the pathname toyour installation of Z-MAP Plus. For example, if you installZ-MAP Plus in the directory /home/user/ZMAPPlus,

indicates the partial pathname /home/user and the full pathname to theZMAPPlus start-up script is /home/user/ZMAPPlus/sh/ZMAPPlus.

Starting Z-MAP Plus from OpenWorks

To display the Z-MAP Plus Command Menu, the OpenWorkslauncher.dat file must contain the following entry. (The launcher.dat

file is located in the user’s home directory and is copied during accountsetup from $OWHOME/templates/launcher.dat .

"ZMAPPlus/PowerView"

"ZMAPPlus 2>$HOME/run/zmap.err 1>&2 &"

8/20/2019 InstConf

31/118



From the OpenWorks Command Menu, select Applications →Z-MAP Plus / PowerView.

The Z-MAP Plus Command Menu appears.

You can now select Z-MAP Plus or a related application from theApplications menu in the Z-MAP Plus Command Menu.

8/20/2019 InstConf

32/118



Starting Z-MAP Plus in Standalone Mode

If you operate in an X Windows environment, but do not useOpenWorks, you can use an xterm window to display the Z-MAP Plus

Command Menu and start Z-MAP Plus.

You can display the Z-MAP Plus Command Menu by executing thefollowing command from a Unix xterm window (where is the path to the Z-MAP Plus installation directory):

/ZMAPPlus/sh/ZMAPPlus

You can now select Z-MAP Plus, ZCL, or a related application fromthe Applications menu in the Z-MAP Plus Command Menu.

Troubleshooting

If you cannot start Z-MAP Plus, try these procedures:

• Delete MappingLauncher.dat from your home directory.

• Delete the .mapinit file from your home directory.

• Verify that the path to /ZMAPPlus/sh is correct.

• Verify two LAM processes are active: lmgrd and licsrv.

• Verify Z-MAP Plus features exist in the license.dat file(ZMAPPLUS, ZCL, and at least one of the following: ZFULL,ZSEIS, or ZENG).

Adding an Alias for the Start-Up Command

To make the start-up command easier to remember and use, add it toyour .cshrc file as an alias.

Add the following line to your .cshrc file.

alias ZMAPPlus /ZMAPPlus/sh/ZMAPPlus

Once you logout and log back in, you can start the mapping productsmenu by entering:

ZMAPPlus

Z-MAP Plus Command Menu Available from OpenWorks and Xterm

The Z-MAP Plus Command Menu is identical whether you run it from

OpenWorks or from an xterm windowby using the shell command ZMAPPlus.

8/20/2019 InstConf

33/118


R2003.12.0 Installation and Configuration: Workstation Notes 25

Workstation Notes

This section describes information you need for installing mapping products on workstations made by a particular manufacturer. Solaris

requirements are described here. In addition, this section includesinformation about X Windows template files.

X Windows Template Files

System-level files required for running Z-MAP Plus with theX Windows system on a Solaris workstation must be configured correctly if OpenWorks is installed at your site.

If OpenWorks is not installed, you may need to make some changes insome X Windows initialization files.

The file .Xdefaults contains X Windows resources recommended for Z-MAP Plus. When X Windows are initialized on a Solaris system, the.Xdefaults file in a user’s home directory is used to load theX Windows resources. Similarly, the .mwmrc file contains resourcesfor creating the root menu in an X Windows session. Make sure bothfiles are in the user’s home directory. If these files are not in the user’shome directory, or if they do not contain the features needed to run theZ-MAP Plus application, obtain a copy of these files.

The /ZMAPPlus/templates subdirectory contains filesyou can reference and copy. In the templates directory, some file names

use the prefix dot , which indicates the file is a template. The templatessubdirectory contains example initialization files for configuring the

X Windows environment. These template files are dotXdefaults and dotmwmrc.

If a user’s directory does not have a copy of .Xdefaults or .mwmrc, youcan copy and edit the template files dotXdefaults and dotmwmrc. Whenyou have edited the template files to meet the requirements for running

Z-MAP Plus, rename the template files to .Xdefaults and .mwmrc.Place these files in the user’s home directory and restart theZ-MAP Plus Command Menu or ZMAPPlus script.

8/20/2019 InstConf

34/118



Solaris Notes

The CD-ROM includes template files for configuring a Sun

environment. The template files are dotlogin and dotxinitrc.

The template file dotlogin contains some necessary Openwindowsenvironment definitions. A copy of .login should be in each user’shome directory. Enter the following lines in the .login file (assuming

Openwindows is in /usr/openwin):

setenv OPENWINHOME /usr/openwin

setenv LD_LIBRARY_PATH

$OPENWINHOME/lib:/usr/lib

set path=($OPENWINHOME/bin $OPENWINHOME/xview

$OPENWINHOME/demo $path)

The template file dotxinitrc contains logic to execute the Motif window

manager, and not the OpenLook window manager. A copy of .xinitrcshould be in each user’s home directory. Enter the following lines inthe .xinitrc file and comment out the line that executes OpenLook:

# .. use the Motif

/usr/bin/X11/mwm

# .. do not use OpenLook

# olwm

If OpenWorks Is Installed

These files should already be configured correctly if Landmark OpenWorkssoftware is installed on your workstation.

8/20/2019 InstConf

35/118



Color Controls

Z-MAP Plus users can control color environments to minimize palettelimitations and color flashing by setting the Z_COLORMAP_CHOICEenvironment variable. These environments need to be set before you

start Z-MAP Plus or OpenWorks. The Z_COLORMAP_CHOICEvariable has three settings:

OpenWorks Setting

When you set the Z_COLORMAP_CHOICE environment variable tothe OpenWorks setting, Z-MAP Plus uses the OpenWorks color

palette as it did in release 3.0. This is the Z-MAP Plus default setting. If you need to set the color map option, enter the following command:

setenv Z_COLORMAP_CHOICE OpenWorks

Private Setting

This setting forces Z-MAP Plus to allocate a private color map. Thissetting allows the user to access more colors, at the expense of color flash.

setenv Z_COLORMAP_CHOICE Private

Screen Setting

The Screen setting tells Z-MAP Plus to use the default colormap of the screen on which Z-MAP Plus is displayed. This setting allows users

access to the same color paradigm that was used prior to the 3.0 release.

The Screen setting is best suited for Unix users who are not runningOpenWorks and want to avoid color flashing. Using the screen’s colorseliminates color flashing between Z-MAP Plus and other applications,especially applications that are already running when you start

Z-MAP Plus. Running the Screen setting with OpenWorks generatessimilar results to the OpenWorks setting itself, but severely restrictsthe number of colors available to the user.

To use the Screen setting, enter:

setenv Z_COLORMAP_CHOICE Screen

OpenWorks Private Color Map

OpenWorks will allocate a private colormap if it cannot find enough colors, no

matter what setting you choose. This causes color flash between OpenWorks

and other applications.

8/20/2019 InstConf

36/118


R2003.12.0 Installation and Configuration: Z-MAP Plus Application Licensing 28

Z-MAP Plus Application Licensing

Z-MAP Plus has three licensing option groups:

• ZFULL — complete Z-MAP Plus Suite

• ZSEIS — Z-MAP Plus Seismic Suite

• ZENG — Z-MAP Plus Reservoir Engineering Suite

Each new Z-MAP Plus license file (license.dat) containsZMAPPLUS, ZCL, CONTRASSIST and ZMS feature lines plus one of

the following groupings of features - ZFULL, ZSEIS or ZENG. Thefollowing tables show the composition of the licensing option groups.

Table 5: ZFULL — Complete Z-MAP Plus Group

LicensingComponent Description

GEOPHYS_PAK Geophysical package (Line Gridding, Line Grid Plus,

Mistie, 3-D Time to Depth, 3-D Time Slice, Time

Migration)

CARTO_PAK Cartographic Package (Z-label, Lease Posting)

RESERVOIR_PAK Reservoir Package (CTOG, Volumetrics, Water

Saturation Averaging)

CANADIAN_PAK Canadian Package (DLS Posting, NTS Posting)

DXF ZGF to AutoCad DXF tool

ORTHO Orthogonal ContouringTREND Trendform Gridding

PSBUILDER Pointset Builder

8/20/2019 InstConf

37/118


R2003.12.0 Installation and Configuration: Z-MAP Plus Application Licensing 29

Table 6: ZSEIS — Z-MAP Plus Seismic Group

Table 7: ZENG — Z-MAP Plus Reservoir Engineering Group

LicencingComponent

Description

GEOPHY_PAK Geophysical package (line gridding, mistie, 3-D timeto depth, 3-D time slice, time migration




ORTHO Orthogonal Contouring

TREND Trendform Gridding


DXF ZGF to AutoCAD DXF tool

LicencingComponent

Description




ORTHO Orthogonal Contouring

TREND Trendform Gridding


DXF ZGF to AutoCAD DXF tool

8/20/2019 InstConf

38/118


R2003.12.0 Installation and Configuration: OpenWorks License Management 30

OpenWorks License Management

This section describes the procedures for configuring and managing thelicense system to control the usage of Landmark applications, including

the following topics:

• basic networking concepts

• basic concepts of application licensing

• the License System architecture

• the syntax of file license.dat

• the use of LM_LICENSE_FILE

• the options file

• starting and stopping the license server on the command line

• using license groups

• using NFS

• making the Landmark license system coexist with other third-party

software vendors

8/20/2019 InstConf

39/118


R2003.12.0 Installation and Configuration: Licensing Process 31

Licensing Process

Before trying to manage the licensing process, you should understand the basic concepts involved. These are discussed on the following

pages.

Common Terms

Certain key terms are used in this section to describe Landmark’s

license system. The most important are listed in the table below.

Table 8: Common Network Licensing Terms

Term Definition

Client An application that can communicate with a server process. A

client can reside on either the same system as the server or on a

networked system.

Daemon

(Server)

A program serving clients. Sometimes referred to as a server, a

daemon process usually “lives” before, during, and after an

application program runs.

License A “key” allowing applications to execute. A license contains a

password that prevents it from being reproducible.

License File A file containing a description of the license servers, the various

application daemons to service application license requests, and

all the licenses that are available to the applications.

License

Server

A daemon running on a workstation and communicating with

licensed applications. It collects license requests from

applications and passes the information to the appropriate

application’s license daemon to service the requests. In

addition, the license server maintains information about current

applications’ users, the number of licenses per application, and

other crucial data.

8/20/2019 InstConf

40/118



How Licensing Works

Licensing allows controlled use of Landmark applications in a network environment. When you purchase a Landmark application, you also purchase one or more licenses, which give users the right to use theapplication.

The number of licenses an application has determines the number of users who may access the application simultaneously. As customer requirements grow, customers may purchase additional licenses thatallow more users to access applications simultaneously. The License

System should be transparent to the user and require minimalconfiguration and maintenance by the network administrator.

Log File A file that is created automatically by the license server. It

contains information about license usage, connections withother servers, and status of connections with other license

servers.

Host An actual machine that resides on the network. It may be the

machine on which the license server runs, it may be a machine

on which licensed applications run, or it may be a machine on

which the license server and licensed applications are running.

Application Any Landmark program licensed to a customer on a per-user

basis.

Table 8: Common Network Licensing Terms (Continued)

Term Definition

8/20/2019 InstConf

41/118



Version Compatibility

Landmark’s license system is based on Globetrotter Software’sFLEXlm licensing server package. The following table shows which

versions of OpenWorks are compatible with which versions of the

FLEXlm License Manager.

Network Configuration

For a licensed application and the License Server to communicate properly, the network configuration should be properly set up. A proper network configuration requires the following:

• The machine on which the licensed application runs must have

access to the License Server.

• Landmark applications use port 2013 for license requests. Thisvalue appears in fourth column of the SERVER line(s) of thelicense.dat file. Each application determines this port number by

reading the license.dat file. This occurs automatically when theapplication tries to check out a license.

Table 9: License Manager/OpenWorks Compatibility

OpenWorks FLEXlm

OpenWorks 3.1x FLEXlm 2.4c

OpenWorks 4.0 FLEXlm 4.1

OpenWorks 5.0 FLEXlm 5.12

OpenWorks 2003.0 FLEXlm 7.2e

8/20/2019 InstConf

42/118



License System Architecture

The License System provides the following architecture for licensed Landmark applications. The major components of the License System

are discussed on the following pages.

License Server

The License Server (also called the LAM Manager ) is a group of daemons that control the distribution of application licenses. When you

attempt to use a licensed application, the application must obtain alicense from the License Server before the application is madeavailable to the user. If the license request is rejected, the user will not be able to use the application. The License Server can be any

workstation that runs the license server process lmgrd. This process isordinarily started when the system boots up.

Application

licsrv

(Landmark)

License File

Application builds license request

License File

Licenserequest

by examining the

licsrv servicesthe application’slicense request

lmgrd

(FLEXlm)

lmgrd receivesrequest andsends the licenserequest to the

correct applicationdaemon for service

using the licensefile

license file

andresponse

Denotes the License Server

8/20/2019 InstConf

43/118



License File Components

The License File (license.dat) file contains all the information needed

by the License Server to manage application licenses. This file containsall licenses that are available to applications using the License System.

The License File has a well-defined syntax that system administratorsshould understand. The file is created in $OWHOME/lam/license.dat.The following is an example of a license.dat file where the OpenWorkshome directory is /pa/OpenWorks:

SERVER procyon 230002ca 2013

SERVER antares 230001a7 2013

SERVER spanky 5100f681 2013

DAEMON licsrv /pa/OpenWorks/lam/bin/licsrv

/pa/OpenWorks/lam/licsrv.opt

FEATURE 2DPLUS licsrv 1.000 1-jan-00 1 Passwd1 "Landmark"

FEATURE 3DPLUS licsrv 1.000 1-jan-00 2 Passwd2 "Landmark"

Each component of the License File license.dat is described in more

detail below.

SERVER

This component defines the license servers in the network. The formatis as follows:

SERVER nodename hostid port

In the example above, one of the license servers is called spanky, with ahost ID of 5100f681 and a port number of 2013. All Landmark applications use port 2013. The port number can be changed to meetsite requirements. However, the port number in all license files on allworkstations using a particular license system must be the same.

Some license files have multiple SERVER lines while others have asingle SERVER line. Multiple SERVER lines denote a “redundant”License System configuration that will minimize down time due tohardware failure or network failure. Landmark currently supports only

one or three SERVER lines in a license.dat file. This is a FLEXlmrestriction.

8/20/2019 InstConf

44/118



DAEMON

This component identifies and defines the location of the license server

executables. The format is as follows:

DAEMON serverID filename optfilename

All Landmark applications use the licsrv daemon (server). Third-partyvendors will have their own DAEMON line. The options file /pa/OpenWorks/lam/licsrv.opt contains reservation and reportlogging information. This is described in detail later in this section.

FEATURE

This component defines the actual application being licensed, theLicense Server used by the application, the version, expiration, number

of users, password, vendor string (used for security), and whether or not this is a demo version. The format is as follows:

FEATURE app servID vrsn date numusr passwd vstr

[DEMO] [hostid ]

where DEMO and hostid are optional.

An expiration date of 1-jan-00 is used if the license will never expire.

In DEMO licenses, the number of concurrent users is 0 and theexpiration date is not 1-jan-00. The license password is generated atLandmark and depends on:

• host ID’s of the SERVER line(s) in the license.dat file

• order of the SERVER lines if multiple SERVER lines exist

• DAEMON line contents

• number of users specified

• expiration of the license (i.e. in a DEMO)

The last entry on this line will contain the word DEMO if the license isa DEMO license. Previous versions of OpenWorks had lock licenses.

As a result, the ninth column may contain a hostid in older OpenWorkslicense.dat files.

8/20/2019 InstConf

45/118



License Options File

The file licsrv.opt specified in the license.dat file modifies the way that

the License Manager logs and checks out licenses. The followingoptions can be specified in licsrv.opt .

REPORTLOG

This option specifies the file to be used to store information about

application usage. In the next example, the file is /usr/adm/lgc.log. The+ before the file name means the License Manager will append to thatfile instead of overwriting the file every time it is started:

REPORTLOG +/usr/adm/lgc.log

RESERVE

This option specifies that a license should be reserved for a particular user or host. In the following examples, one license for SEIS3D is

reserved for user John and one license for ZAP is reserved for hostneptune.

RESERVE 1 SEIS3D USER john

RESERVE 1 ZAP HOST neptune

See the FLEXlm User’s Guide for further options available in the

license options file.

8/20/2019 InstConf

46/118


R2003.12.0 Installation and Configuration: License Server 38

License Server

You can start or stop the License Server on the workstation that runs it,or set the environment variable.

Starting and Stopping the License Server

The system startup file on the License Server is modified at installationtime to start up the license daemon. Use the following steps to start and

stop the License Server.

1. To start the server manually, log in as root to the workstation

containing the license server, change to the LAM bin directoryunder OpenWorks, and enter the startup command. For example:

telnet novalogin: root

setenv OWHOME /pa/OpenWorks (C Shell), or OWHOME=/pa/OpenWorks;export OWHOME (Bourne or Korn Shell)

cd /pa/OpenWorks/lam/bin

./startlmgrd

2. To stop the License Server, use the same procedure as indicated inthe previous step, but substitute the following command:

./stoplmgrd

Setting the Environment Variable

The LM_LICENSE_FILE environment variable is an environmentvariable provided by the FLEXlm license server package. It performsthe following functions:

• Allows users to designate a license.dat file that the application willuse to attempt to check out a license

• Allows users to specify a list of license.dat files that theapplication has available to use in checking out licenses.

LM_LICENSE_FILE has a syntax exactly like that of PATH. For example, C shell users would use the following commands:

setenv LM_LICENSE_FILE $OWHOME/license1.dat

setenv LM_LICENSE_FILE

$OWHOME/license1.dat:$OWHOME/license2.dat

8/20/2019 InstConf

47/118


R2003.12.0 Installation and Configuration: License Server 39

Defining License Groups

A License Group is one or more workstations using a single LicenseSystem, including a license.dat file and one or more License Servers

(represented by SERVER lines in the license.dat file).

Large sites may want to partition their workstations into distinctgroups. Each workstation group would have a License Systemincluding:

• a license.dat file

• one or more workstations designated as License Servers.

The user defines LM_LICENSE_FILE to point to the license.dat filethat is to be used by applications running in the group.

Group License Sharing

Groups may “share” licenses with other groups through the use of theLM_LICENSE_FILE environment variable:

• Each group has a copy of each license.dat file from the other groups (hopefully all named appropriately).

• The user environment contains the LM_LICENSE_FILE defining

the exact location of each of the above license.dat files. In addition,LM_LICENSE_FILE defines an order that the application willfollow when trying to check out a license from one of the groups.

Be aware of licenses common to one or more of the above license.dat

files and the problem associated with searching LM_LICENSE_FILE.An example of a LM_LICENSE_FILE variable setting for a group isshown below:

setenv LM_LICENSE_FILE

“/etc/license_g1.dat:/etc/license_g2.dat”

8/20/2019 InstConf

48/118


R2003.12.0 Installation and Configuration: NFS with the License System 40

NFS with the License System

The License System architecture allows easy configuration for OpenWorks NFS clients (clients that NFS mount the OpenWorks tree).

• All OpenWorks 4.0 and greater applications by default look for alicense in $OWHOME/lam/license.dat.

• OpenWorks NFS clients NFS mount $OWHOME. By doing this,

$OWHOME/lam/license.dat is made available to the OpenWorksapplications.

• The $OWHOME NFS server is typically the License Server.

However, multiple workstations can serve as the License Server if multiple SERVER lines exist in $OWHOME/lam/license.dat.

• OpenWorks NFS clients do not need to run the License Server unless they are one of the designated license servers. The

OpenWorks NFS clients that are to be used as license servers mustnot be dataless or diskless clients.

• Applications running on the NFS clients have license.dat availableto permit license checkouts.

Applications will add $OWHOME/lam/license.dat to theLM_LICENSE_FILE variable definition if this variable is defined.This ensures that Landmark’s license.dat is always included in theLM_LICENSE_FILE path.

8/20/2019 InstConf

49/118


R2003.12.0 Installation and Configuration: Licenses and Third-Party Software 41

Licenses and Third-Party Software

Because Landmark’s License System uses FLEXlm from Globetrotter,

administrators must be careful when installing other third-party

software that also uses FLEXlm (Sun’s compilers, Charisma, etc.).

Managing the License System

When your environment contains both OpenWorks and other third-party software, there are two ways to manage the license system:

• The first (and easiest) way produces separate license systems.OpenWorks applications reference one license system whilethird-party software references the other license system.

• The second (more complicated) way produces a single licensesystem that is used by both OpenWorks applications and thethird-party software.

Separate License Systems

To create separate license systems for OpenWorks and for thethird-party software perform the following:

1. Locate license.dat in the OpenWorks environment.

2. Locate the SERVER line(s) within the above license file.

Notice that the fourth column in the SERVER line is a number representing the port number that the OpenWorks license server will use to listen for license requests.

3. Change the port number to a number that is different from the port

number used by any of the third-party vendor’s license servers.

4. Stop and restart the OpenWorks license server using the procedures earlier in this section.

5. Copy the OpenWorks license file to any OpenWorks clients if any

such clients exist. NFS OpenWorks clients are exempted from this.The result is two separate license system (servers) each listening on adifferent socket port. OpenWorks applications will use the license file

in $OWHOME/lam/license.dat, so it will know what port number touse. Third-party applications will continue using their license file and will know what port number to use.

8/20/2019 InstConf

50/118


R2003.12.0 Installation and Configuration: Licenses and Third-Party Software 42

Single License System

To create a single license system that is shared by both OpenWorks and other third-party applications:

1. View the file $OWHOME/lam/license.dat. For example:

more $OWHOME/lam/license.dat

2. View the license file(s) used by the third-party applications.

3. Verify that the SERVER lines match in number and host id.

4. Make backup copies of both files.

5. Copy SERVER lines (no duplicates).

6. Copy DAEMON lines (no duplicates).

7. Copy FEATURE lines (no duplicates).

8. Copy the new license.dat file into $OWHOME/lam/license.dat for

OpenWorks.

9. Copy the new license.dat file into a suitable location for eachthird-party vendor that will use the single license system.

8/20/2019 InstConf

51/118


R2003.12.0 Installation and Configuration: License Management Without OpenWorks 43

License Management Without OpenWorks

The following describes the differences and procedures relating toLicense Management in a standalone environment. Please refer to

“OpenWorks License Management” on page 30 for a detailed discussion of individual components of LAM.

Differences in Licensing between OpenWorks andnon-OpenWorks installations

• The license.dat file location (directory) is different. You donot use an OpenWorks upper level directory for the lam/

directory

• Starting the license manager is slightly different. You use the

executable lmgrd rather than startlmgrd.

License Location for Non-OpenWorks Installations

Install the license.dat file in the/ZMAPPlus/lam directory. Modify the SERVER line to reflect the name of the machine and the hostid number. Modifythe DAEMON line to point to the directory that contains the licsrv

and licsrv.opt files as described below.

License File Components

The License File (license.dat) file contains all the informationneeded by the License Server to manage application licenses. This filecontains all licenses that are available to applications using the LicenseSystem.

The License File has a well-defined syntax that system administratorsshould understand. The following is an example of a license.dat filewhere the directory is

8/20/2019 InstConf

52/118



SERVER

This component defines the license servers in the network. The format

is:

SERVER nodename hostid port

In the example above, one of the license servers is called spanky, with ahost ID of 5100f681 and a port number of 2013. All Landmark

applications use port 2013. The port number can be changed to meetsite requirements. However, the port number in all license files on allworkstations using a particular license system must be the same. Somelicense files have multiple SERVER lines while others have a singleSERVER line. Multiple SERVER lines denote a “redundant” LicenseSystem configuration that will minimize down time due to hardware

failure or network failure. Landmark currently supports only one or three SERVER lines in a license.dat file. This is a FLEXlmrestriction.

DAEMON

This component identifies and defines the location of the license server executables. The format is:

DAEMON serverID filename optfilename

All Landmark applications use the licsrv daemon. Third-party vendorswill have their own DAEMON line.

8/20/2019 InstConf

53/118



FEATURE

This component defines the actual application being licensed, the

License Server used by the application, the version, expiration, number of users, password, vendor string (used for security), and whether or

not this is a demo version. The format is:

FEATURE app servID vrsn date numusr passwd vstr

[DEMO] [hostid ]

where DEMO and hostid are optional.

An expiration date of “1-jan-00” is used if the license will never expire.In DEMO licenses, the number of concurrent users is 0 and theexpiration date is not “1-jan-00”. The license password is generated atLandmark and depends on:

• the host ID’s of the SERVER line(s) in the license.dat file• the order of the SERVER lines if multiple SERVER lines exist

• the DAEMON line contents

• the number of users specified

• the expiration of the license (i.e. in a DEMO)

The last entry on this line will contain the word DEMO if the license is

a DEMO license.

License Options File

The file licsrv.opt specified in the license.dat file modifies the way thatthe License Manager logs and checks out licenses. The followingoptions can be specified in licsrv.opt :

REPORTLOG

This option specifies the file to be used to store information aboutapplication usage. In the following example, the file is /usr/adm/lgc.log . The plus (+) symbol before the file name means theLicense Manager will append to that file instead of overwriting the file

every time it is started.

REPORTLOG +/usr/adm/lgc.log

8/20/2019 InstConf

54/118



RESERVE

This option specifies that a license should be reserved for a particular

user or host. In the following examples, one license for SEIS3D isreserved for user John and one license for ZAP is reserved for host

neptune.

RESERVE 1 SEIS3D USER john

RESERVE 1 ZAP HOST neptune

See the FLEXlm User’s Guide for further options available in the

license options file.

Using the License Server on Non-OpenWorks Installations

The system startup file on the License Server is modified at installation

time to start up the license daemon. Use the following steps to start and stop the License Server.

To start the server manually, log in as root to the workstationcontaining the license server, change to the/ZMAPPlus/lam/bin directory and enter thestart-up command. For example:

login: root

cd /ZMAPPlus/lam/bin

./lmgrd -c /ZMAPPlus/lam/license.dat >

lic.log &

The two lam manager processes start and a process log named lic.log writes to your /ZMAPPlus/lam/bin

directory. The log contains import

InstConf

Documents

Transcript of InstConf