Inst Conf

Z-MAP Plus
Installation
and
Z-MAP Plus Installation and

Configuration Guide
2003 Landmark Graphics Corporation
Part No. 161329 October 2003

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, DecisionSpace
Atomic 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.
Landmark Z-MAP Plus Installation and Configuration Guide
Contents
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
R2003.12.0 Contents iii

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
R2003.12.0 Contents iv
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
R2003.12.0 Contents v
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
R2003.12.0 Contents vi
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
R2003.12.0 Contents vii

Appendix B. Z-MAP Plus Graphics Environment

Introduction ........................................................................................................ 95
Applications That Use ZIGS ........................................................................ 95
What 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
R2003.12.0 Contents viii

Introduction
Overview of This Guide

The Z-MAP Plus Installation and Configuration Guide covers the
information and procedures for installing and maintaining an
environment for the Z-MAP Plus family of products. The following
illustration shows the products you will install and configure.
Z-MAP Plus and ZCL are applications. The other components are
utilities, including utilities that support hardcopy systems.
This guide is the first one you should examine when you receive the
software. It explains the procedures for installing or upgrading the
software, configuring your system for various utilities, producing
hardcopy, 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 applicationit is available
only if you have purchased this option.
R2003.12.0 Introduction 1
Z-MAP Plus Installation and Configuration Guide Landmark
Who Should Read This Guide

This guide is for the site manager or system administrator. To
understand 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 a
system 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 are
needed.
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
2 Who Should Read This Guide: Introduction June 1994

Text you should replace with your own entry appears in

monospaced 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. With
neither queuename nor job number entered, the command cancels
the 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
R2003.12.0 Introduction: How to Use This Guide 3

Z-MAP Plus Installation and Configuration Guide Landmark
Contents of This Guide

The Z-MAP Plus Installation and Configuration Guide consists of the
following sections:
Introduction An overview of content and organization.
Installing and Configuring Z-MAP Plus Detailed instructions
for 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 hardcopy
support in particular. The second half shows you how to set up
hardcopy 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 Installation
and Configuration Guide are organized as follows:
Environment Variables for Mapping Products
The Z-MAP Plus Graphics Environment
Canadian Package DLS Data and Utility Programs
4 Contents of This Guide: Introduction June 1994

Installation and Configuration
Introduction
This section contains detailed steps for installing Z-MAP Plus in
OpenWorks 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 install
Z-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 Plus
on Solaris workstations.
Z-MAP Plus Application Licensing Important information
about 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. The
applications 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.
R2003.12.0 Installation and Configuration 5

Setting Up Z-MAP Plus with OpenWorks
Workstations with OpenWorks

The Z-MAP Plus installation CD-ROM is written in OpenWorks
CDINSTALL format. It can be used to install Z-MAP Plus on all
platforms. Additional reference information may be found in the
OpenWorks installation documentation. See Installing Applications
with CDinstall in the OpenWorks System Administration: Installing
OpenWorks guide, and Managing the License System in the
OpenWorks System Administration: Managing the System guide.
The following sections contain step-by-step installation instructions, as
well 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 OpenWorks
License 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 the
Z-MAP Plus Command Menu options is defined in the file
MappingLauncher.dat in each users home directory. The format for
MappingLauncher.dat is similar to the format for the OpenWorks
Command Menu, launcher.dat. The original copy of the
MappingLauncher.dat file is stored in the following location:
<install_dir>/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 does
not contain a copy of the MappingLauncher.dat file, it is automatically
copied to your home directory. If a version exists from a previous
release, delete it so a new updated file can be automatically copied to
your 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 an
OpenWorks connection, add the following line to the
MappingLauncher.dat file:
Z-MAP Plus Non-OpenWorks zmapplussh -n &
R2003.12.0 Installation and Configuration: Setting Up Z-MAP Plus with OpenWorks 6

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

Note the following disk space requirements before unloading the
software.
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.
Establishing a Directory Structure

The files on the CD-ROM are organized under a top level directory
named /ZMAPPlus, which contains several subdirectories. When the
CD-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 <install_dir> the
ZMAPPlus top level directory <install_dir>/ZMAPPlus will be
created. The examples in this section assume the CD-ROM will be
restored in the directory <install_dir>/.

Installing Z-MAP Plus with OpenWorks

Use the following procedures for preparing to install Z-MAP Plus with
OpenWorks.
If you are upgrading from an earlier version of Z-MAP Plus and have
customized files, back up these files to use with the new Z-MAP Plus
installation. The files you may have customized and need to back up
are listed in the following table.
Table 2: Files to Save from Previous Versions of Z-MAP Plus

File Description Directory
HDCOPY_nnn or site-specific hardcopy binaries bin

HDBAT_nnna
MFDs or ZGFs 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
a. This suffix is site-specific.
Compare the contents of the WDFILE used with the previous version of
Z-MAP Plus to the new WDFILE provided with this CD-ROM. Merge
the 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.
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 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
When you restore backup files, be careful not to overwrite the

pre-linked hardcopy binaries provided with the installation CD-ROM.
Do not install a new version of Z-MAP Plus into a directory that

contains a previous version of Z-MAP Plus.

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 a
graphical status display of the installations 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 these

steps:
1. If you are installing to another computer on your network, set the
DISPLAY environment variable to see the installation screens on
your 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 system
administrator to prepare the drive for remote access. Change
directories 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.

3. Enter the full pathname to the OpenWorks installation.

OWHOME is set to: /home/<install_dir>/OpenWorks
4. Watch the response of the Release Manager: It returns the

OWHOME directory path, automatically detects the operating
system of your machine, then issues a message telling you which
OS version of Z-MAP Plus it will install.
Release Manager will use OWHOME =
/home/<install_dir>/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, the
version number of the application, the space in MB required to
install 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

There are five buttons at the bottom of the window:

Start Begin installation.
System Info Display a window showing information about
your systems configuration.
Release Notes Display a window containing the release note
document for a selected application.
Display log Display messages (if any) written by the
installation 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 the
default selection.)
6. Select a location for installing the application.
The Chg Loc column shows the default locations. To change the
location displayed, click the ellipisis button next to the location.
The Location Selection dialog box appears:

The Location Selection dialog box shows all file systems to which
your system is mounted and the space available on each. To select
a file system, click it. Available directories on the file system
appear 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 name
of the directory in the Selection box instead of selecting it.)
8. Click OK to select the directory and close the Location Selection
dialog box, or Cancel to close the window without selecting a
directory.
9. Repeat steps 5 through 8 for each application you want to install.

10. After you have selected the applications you wish to install, and
the locations in which to install them, click Start in the Software
Selection window. The following dialog box appears:
11. The installation program begins to copy files to the selected file
system. 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.

14. Check the installation status area of the Release Manager - Product
Selection dialog box to determine if the installation was
successful. 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 delete
log 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 run
the new version you must first delete the existing
MappingLauncher.dat and .mapinit files from each users home
directory:
rm $HOME/MappingLauncher.dat
rm $HOME/.mapinit
A new file for displaying the Z-MAP Plus Command Menu is
automatically placed in each user accounts home directory the
first 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 the
OpenWorks 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

To turn environmental variables off, close the Z-MAP Plus

window and the Z-MAP Plus Command Menu, then enter the
command that reverses the setenv command. For example:
unsetenv MULTI_WINDOW
In most cases, you can add the line to your .cshrc file or .lgclogin
to set environment variables, thus automatically enabling the
feature 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 Mapping
Products on page 89.
20. Z-MAP Plus incorporates FLEXlm license management software
from Globetrotter which utilizes software versioning in the
license.dat file. License files (license.dat) from any previous
release of Z-MAP Plus will not work successfully due to this
feature. A new license.dat file must be obtained from the
Landmark representative before Z-MAP Plus 1998.1 can be
successfully executed. Activate and configure the application
licenses. (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 the
Z-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 Users Guide
(Help Online Manuals User Guide). This book provides a
tutorial and introductions to the most important concepts and features
of the program.
To learn what is new in each release, see the Help Help
context-sensitive, browser-based system. The home page features the
newest features and changes for each version of Z-MAP Plus.

Setting Up Z-MAP Plus Without OpenWorks
Workstations Without OpenWorks

Installing Z-MAP Plus in a non-OpenWorks environment is very
similar to installing in the OpenWorks environment, except for four
important differences:
Setting the environmental variable OWHOME during the
installation. (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 system
requirements, and you should be familiar with the directory structure
on the product CD-ROM.
Setting Up the Z-MAP Plus Command Menu

The Z-MAP Plus Command Menu executes the programs in the
Z-MAP Plus suite. The data used to build the Z-MAP Plus Command
Menu options is defined in the file MappingLauncher.dat in each users
home directory. The original copy of this file is located at
<install_dir>/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 a
version exists from a previous release, delete it so an updated file can
be automatically copied to your home directory. If you are using an
outdated MappingLauncher.dat file, the Z-MAP Plus Command Menu
does not display new options that have been added in the current
release.
R2003.12.0 Installation and Configuration: Setting Up Z-MAP Plus Without OpenWorks 16

Disk Space Requirements

Note the following disk space requirements before unloading the
software.
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.
Establishing a Directory Structure

The files on the CD-ROM are organized under a top-level directory
named /ZMAPPlus, which contains several subdirectories. When the
CD-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 <install_dir> the
Z-MAP Plus top-level directory <install_dir>/ZMAPPlus is created.
The examples in this section assume the CD-ROM is restored in the
directory <install_dir>/.

Installing Z-MAP Plus Without OpenWorks

This section contains the procedures for installing Z-MAP Plus without
OpenWorks.
If you have been using an earlier version of Z-MAP Plus, you may
want to back up certain files for use with the present version. The files
that you may have customized and may want to save are listed in the
following table.
Table 4: Files to Save from Previous Versions of Z-MAP Plus

File Description Directory
HDCOPY_nnn or site-specific hardcopy binaries bin

HDBAT_nnna
MFDs or ZGFs 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
a. This suffix is site-specific.
Compare the contents of the WDFILE used with the previous version of
Z-MAP Plus to the new WDFILE provided with this CD-ROM. Merge
the two files if you are missing needed information.
You should make backup copies of the following directly (without
comparing): site-specific hardcopy binaries, data files, color table file,
digitizer files and license files.
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 the CD-ROM. To avoid overwriting the pre-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
When you restore the backup files, be careful not to overwrite the
pre-linked hardcopy binaries provided with the installation software.
Do not install a new version of Z-MAP Plus into a directory that

contains a previous version of Z-MAP Plus.

1. Install the CD by following the instructions described in Using

Release Manager to Install the Software on page 9. The only
difference 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 is
created, 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/.

4. For a standalone installation, login as root and modify the

<install_dir>/ZMAPPlus/templates/MappingLauncher.dat file
with a -n flag as shown in the following examples. The -n flag
indicates 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 users .cshrc file:
alias ZMAPPlus <install_dir>/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 accounts
home directory:
rm $HOME/MappingLauncher.dat
rm $HOME/.mapinit
A new MappingLauncher.dat is copied automatically to each user
accounts home directory when Z-MAP Plus starts.
7. In a non-OpenWorks environment, enter the environment variable
you want to enable in an xterm window before you start the
Z-MAP Plus Command Menu or Z-MAP Plus. In most cases, you
can add a line to the .cshrc file to set environment variables, thus
automatically enabling the feature supported by the environment
variable. For example:
setenv MULTI_WINDOW yes
To turn an environment variable off, close the Z-MAP Plus
window and the Z-MAP Plus Command Menu, then enter the
command 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 Variables
for Mapping Products on page 89.

8. Z-MAP Plus incorporates FLEXlm license management software

from Globetrotter which utilizes software versioning in the
license.dat file. License files (license.dat) from any previous
release of Z-MAP Plus will not work successfully due to this
feature. A new license.dat file must be obtained from the
Landmark representative before Z-MAP Plus can be successfully
executed.
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 start
Z-MAP Plus two different ways. See Starting Z-MAP Plus in
Standalone Mode on page 24.
For information about Z-MAP Plus see the Introduction section in the
Z-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 Users
Guide (Help Online Manuals User Guide). This book provides
a tutorial and introductions to the most important concepts and features
of the program.
To learn what is new in each release, see the Help Help
context-sensitive, browser-based system. The home page features
information about the newest features and changes for each version of
Z-MAP Plus.

Starting Z-MAP Plus

Once the software is properly installed and configured, you can start
Z-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 section
describes how to use each of these three methods.
In the following discussion, <install_dir> refers to the pathname to
your installation of Z-MAP Plus. For example, if you install
Z-MAP Plus in the directory /home/user/ZMAPPlus, <install_dir>
indicates the partial pathname /home/user and the full pathname to the
ZMAPPlus start-up script is /home/user/ZMAPPlus/sh/ZMAPPlus.
Starting Z-MAP Plus from OpenWorks

To display the Z-MAP Plus Command Menu, the OpenWorks
launcher.dat file must contain the following entry. (The launcher.dat
file is located in the users home directory and is copied during account
setup from $OWHOME/templates/launcher.dat.
"ZMAPPlus/PowerView"
"ZMAPPlus 2>$HOME/run/zmap.err 1>&2 &"
R2003.12.0 Installation and Configuration: Starting Z-MAP Plus 22

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 the
Applications menu in the Z-MAP Plus Command Menu.

Starting Z-MAP Plus in Standalone Mode

If you operate in an X Windows environment, but do not use
OpenWorks, 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 the
following command from a Unix xterm window (where <install_dir>
is the path to the Z-MAP Plus installation directory):
<install_dir>/ZMAPPlus/sh/ZMAPPlus
You can now select Z-MAP Plus, ZCL, or a related application from
the Applications menu in the Z-MAP Plus Command Menu.
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 window by using the shell command ZMAPPlus.
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 <install_dir>/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 to
your .cshrc file as an alias.
Add the following line to your .cshrc file.
alias ZMAPPlus <install_dir>/ZMAPPlus/sh/ZMAPPlus
Once you logout and log back in, you can start the mapping products
menu by entering:
ZMAPPlus

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 includes
information about X Windows template files.
X Windows Template Files

System-level files required for running Z-MAP Plus with the
X 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 in
some 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 users home directory is used to load the
X Windows resources. Similarly, the .mwmrc file contains resources
for creating the root menu in an X Windows session. Make sure both
files are in the users home directory. If these files are not in the users
home directory, or if they do not contain the features needed to run the
Z-MAP Plus application, obtain a copy of these files.
The <install_dir>/ZMAPPlus/templates subdirectory contains files
you can reference and copy. In the templates directory, some file names
use the prefix dot, which indicates the file is a template. The templates
subdirectory contains example initialization files for configuring the
X Windows environment. These template files are dotXdefaults and
dotmwmrc.
If a users directory does not have a copy of .Xdefaults or .mwmrc, you
can copy and edit the template files dotXdefaults and dotmwmrc. When
you 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 users home directory and restart the
Z-MAP Plus Command Menu or ZMAPPlus script.
R2003.12.0 Installation and Configuration: Workstation Notes 25

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 Openwindows
environment definitions. A copy of .login should be in each users
home 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 .xinitrc
should be in each users home directory. Enter the following lines in
the .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 OpenWorks
software is installed on your workstation.

Color Controls
Z-MAP Plus users can control color environments to minimize palette
limitations and color flashing by setting the Z_COLORMAP_CHOICE
environment variable. These environments need to be set before you
start Z-MAP Plus or OpenWorks. The Z_COLORMAP_CHOICE
variable has three settings:
OpenWorks Setting
When you set the Z_COLORMAP_CHOICE environment variable to
the 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. This
setting 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 running
OpenWorks and want to avoid color flashing. Using the screens colors
eliminates 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 generates
similar results to the OpenWorks setting itself, but severely restricts
the 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.

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) contains
ZMAPPLUS, ZCL, CONTRASSIST and ZMS feature lines plus one of
the following groupings of features - ZFULL, ZSEIS or ZENG. The
following tables show the composition of the licensing option groups.
Table 5: ZFULL Complete Z-MAP Plus Group
Licensing
Description
Component
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 Contouring
TREND Trendform Gridding
PSBUILDER Pointset Builder
R2003.12.0 Installation and Configuration: Z-MAP Plus Application Licensing 28

Table 6: ZSEIS Z-MAP Plus Seismic Group
Licencing
Description
Component
GEOPHY_PAK Geophysical package (line gridding, mistie, 3-D time

to depth, 3-D time slice, time migration
DXF ZGF to AutoCAD DXF tool
Table 7: ZENG Z-MAP Plus Reservoir Engineering Group
Licencing
Description
Component

DXF ZGF to AutoCAD DXF tool
R2003.12.0 Installation and Configuration: Z-MAP Plus Application Licensing 29

OpenWorks License Management

This section describes the procedures for configuring and managing the
license 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
R2003.12.0 Installation and Configuration: OpenWorks License Management 30

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 Landmarks
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 A program serving clients. Sometimes referred to as a server, a

(Server) 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 A daemon running on a workstation and communicating with

Server licensed applications. It collects license requests from
applications and passes the information to the appropriate
applications 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.
R2003.12.0 Installation and Configuration: Licensing Process 31

Table 8: Common Network Licensing Terms (Continued)
Term Definition
Log File A file that is created automatically by the license server. It

contains information about license usage, connections with
other 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.
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 the
application.
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 that
allow more users to access applications simultaneously. The License
System should be transparent to the user and require minimal
configuration and maintenance by the network administrator.

Version Compatibility
Landmarks license system is based on Globetrotter Softwares
FLEXlm licensing server package. The following table shows which
versions of OpenWorks are compatible with which versions of the
FLEXlm License Manager.
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
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. This
value appears in fourth column of the SERVER line(s) of the
license.dat file. Each application determines this port number by
reading the license.dat file. This occurs automatically when the
application tries to check out a license.

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.
Denotes the License Server

licsrv licsrv services
the applications
(Landmark) license request
using the license
License file
request
and
response
lmgrd receives
lmgrd request and
Application
(FLEXlm) sends the license
request to the
correct application
daemon for service
Application builds license request by examining the
license file
License File License File
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 a
license from the License Server before the application is made
available 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 is
ordinarily started when the system boots up.

License File Components

The License File (license.dat) file contains all the information needed
by the License Server to manage application licenses. This file contains
all licenses that are available to applications using the License System.
The License File has a well-defined syntax that system administrators
should understand. The file is created in $OWHOME/lam/license.dat.
The following is an example of a license.dat file where the OpenWorks
home 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 format
is as follows:
SERVER nodename hostid port
In the example above, one of the license servers is called spanky, with a
host ID of 5100f681 and a port number of 2013. All Landmark
applications use port 2013. The port number can be changed to meet
site requirements. However, the port number in all license files on all
workstations using a particular license system must be the same.
Some license files have multiple SERVER lines while others have a
single SERVER line. Multiple SERVER lines denote a redundant
License System 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 FLEXlm
restriction.

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-party

vendors will have their own DAEMON line. The options file
/pa/OpenWorks/lam/licsrv.opt contains reservation and report
logging information. This is described in detail later in this section.
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 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 the
expiration date is not 1-jan-00. The license password is generated at
Landmark and depends on:
host IDs 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 is
a DEMO license. Previous versions of OpenWorks had lock licenses.
As a result, the ninth column may contain a hostid in older OpenWorks
license.dat files.

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 following
options 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 that
file 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 host
neptune.
RESERVE 1 SEIS3D USER john
RESERVE 1 ZAP HOST neptune
See the FLEXlm Users Guide for further options available in the
license options file.

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 installation
time 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 directory
under OpenWorks, and enter the startup command. For example:
telnet nova
login: 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 in

the previous step, but substitute the following command:
./stoplmgrd
Setting the Environment Variable

The LM_LICENSE_FILE environment variable is an environment
variable provided by the FLEXlm license server package. It performs
the following functions:
Allows users to designate a license.dat file that the application will
use to attempt to check out a license
Allows users to specify a list of license.dat files that the
application 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
R2003.12.0 Installation and Configuration: License Server 38

Defining License Groups

A License Group is one or more workstations using a single License
System, 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 distinct
groups. Each workstation group would have a License System
including:
a license.dat file
one or more workstations designated as License Servers.
The user defines LM_LICENSE_FILE to point to the license.dat file
that is to be used by applications running in the group.
Group License Sharing

Groups may share licenses with other groups through the use of the
LM_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 will
follow 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 is
shown below:
setenv LM_LICENSE_FILE
/etc/license_g1.dat:/etc/license_g2.dat
R2003.12.0 Installation and Configuration: License Server 39

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 a
license in $OWHOME/lam/license.dat.
OpenWorks NFS clients NFS mount $OWHOME. By doing this,
$OWHOME/lam/license.dat is made available to the OpenWorks
applications.
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 must
not be dataless or diskless clients.
Applications running on the NFS clients have license.dat available
to permit license checkouts.
Applications will add $OWHOME/lam/license.dat to the
LM_LICENSE_FILE variable definition if this variable is defined.
This ensures that Landmarks license.dat is always included in the
LM_LICENSE_FILE path.
R2003.12.0 Installation and Configuration: NFS with the License System 40

Licenses and Third-Party Software

Because Landmarks License System uses FLEXlm from Globetrotter,
administrators must be careful when installing other third-party
software that also uses FLEXlm (Suns compilers, Charisma, etc.).
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 while
third-party software references the other license system.
The second (more complicated) way produces a single license
system that is used by both OpenWorks applications and the
third-party software.
Separate License Systems

To create separate license systems for OpenWorks and for the
third-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 vendors 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 a
different socket port. OpenWorks applications will use the license file
in $OWHOME/lam/license.dat, so it will know what port number to
use. Third-party applications will continue using their license file and
will know what port number to use.
R2003.12.0 Installation and Configuration: Licenses and Third-Party Software 41

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 each
third-party vendor that will use the single license system.
R2003.12.0 Installation and Configuration: Licenses and Third-Party Software 42

License Management Without OpenWorks

The following describes the differences and procedures relating to
License 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 and
non-OpenWorks installations
The license.dat file location (directory) is different. You do
not 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
<install_dir>/ZMAPPlus/lam directory. Modify the SERVER
line to reflect the name of the machine and the hostid number. Modify
the 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 information
needed by the License Server to manage application licenses. This file
contains all licenses that are available to applications using the License
System.
The License File has a well-defined syntax that system administrators
should understand. The following is an example of a license.dat file
where the directory is <install_dir/ZMAPPlus:
SERVER <machine_name> 5100f681 2013
DAEMON licsrv <install_dir>/ZMAPPlus/lam/bin/licsrv \
<install_dir>/ZMAPPlus/lam/licsrv.opt
FEATURE 2DPLUS licsrv 1.000 1-jan-00 1 Passwd1 Landmark
FEATURE 3DPLUS licsrv 1.000 1-jan-00 2 Passwd2
R2003.12.0 Installation and Configuration: License Management Without OpenWorks 43

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 a
host ID of 5100f681 and a port number of 2013. All Landmark
applications use port 2013. The port number can be changed to meet
site requirements. However, the port number in all license files on all
workstations using a particular license system must be the same. Some
license files have multiple SERVER lines while others have a single
SERVER line. Multiple SERVER lines denote a redundant License
System 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 FLEXlm
restriction.
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 vendors

will have their own DAEMON line.

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 the
expiration date is not 1-jan-00. The license password is generated at
Landmark and depends on:
the host IDs 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 that
the License Manager logs and checks out licenses. The following
options can be specified in licsrv.opt:
REPORTLOG
This option specifies the file to be used to store information about
application usage. In the following example, the file is
/usr/adm/lgc.log. The plus (+) symbol before the file name means the
License Manager will append to that file 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 host
neptune.
RESERVE 1 SEIS3D USER john
RESERVE 1 ZAP HOST neptune
See the FLEXlm Users 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 workstation
containing the license server, change to the
<install_dir>/ZMAPPlus/lam/bin directory and enter the
start-up command. For example:
login: root
cd <install_dir>/ZMAPPlus/lam/bin
./lmgrd -c <install_dir>/ZMAPPlus/lam/license.dat >
lic.log &
The two lam manager processes start and a process log named
lic.log writes to your <install_dir>/ZMAPPlus/lam/bin
directory. The log contains important information about your license
processes, similar to the following example (depending on your
individual license options list):

11:23:11 (lmgrd) FLEXlm (v4.1) started on <machine_name>(hp 9000/720)

(9/9/96)
11:23:11 (lmgrd) FLEXlm Copyright 1988-1994, Globetrotter
Software, Inc.
11:23:11 (lmgrd) License file:
<install_dir>/ZMAPPlus/lam/license.dat
11:23:11 (lmgrd) Starting vendor daemons ...
11:23:11 (lmgrd) Started licsrv
11:23:12 (licsrv) Server started on <machine_name>for:
11:23:12 (licsrv) DXF HDCOPY_VGS HORIZON_PEN
11:23:12 (licsrv) HORIZON_PAK CANADIAN_PAK CARTO_PAK
11:23:12 (licsrv) RESERVOIR_PAK Z3D_FENCE Z3D_SURFACE 11:23:12
(licsrv) ZCAP ZCAP_SEIS ZCAP_WLOG
11:23:12 (licsrv) ZFULL ZMAPPLUS ZMS
11:23:12 (licsrv) ORTHO PSBUILDER TREND
11:23:12 (licsrv) GEOPHYS_PAK ZSEIS
To stop the License Server manually, log in as root to the

workstation
containing the license server, change to the
<install_dir>/ZMAPPlus/lam/bin directory and enter the
stop command. For example:
login: root
cd <install_dir>/ZMAPPlus/lam/bin
./stoplmgrd
To check that the license server is alive, you can look for the two lam
processes by using the Unix ps (report processes status) command:
ps -eaf | grep lmgrd
returns something similar to the following:

root 979 1 0 08:33:42 ttyp3 0:00 ./lmgrd
-c <install_dir>/ZMAPPlus/lam/license.dat
ps -eaf | grep licsrv
returns something similar to the following:

root 980 979 0 08:33:43 ? 0:00 licsrv
-T <machine_name> 4 -c
<install_dir>/ZMAPPlus/lam/license.dat

Setting the Environment Variable

The LM_LICENSE_FILE environment variable is an environment
variable provided by the FLEXlm license server package. It performs
the following functions:
Allows users to designate a license.dat file that the application will
use to attempt to check out a license
Allows users to specify a list of license.dat files that the
application 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 <user_dir>/license1.dat
setenv LM_LICENSE_FILE <user_dir1>/license1.dat:<user_dir2>/license2.dat

Configuring Hardcopy
Introduction
You can produce hardcopy for a plotter in Z-MAP Plus or
independently of Z-MAP Plus. This section explains how to configure
the Z-MAP Plus hardcopy environment to get output from the plotter(s)
you use.
This section covers the following aspects of configuring hardcopy:
Hardcopy and Hardcopy Batch summarize requirements for
plotting inside and outside of Z-MAP Plus.
HP-GL Drivers describes how to work with devices that can
interpret HP-GL (Hewlett-Packard Graphics Language).
CGM Drivers shows how CGM files are generated from
Z-MAP Plus, and how they are turned into pictures via rasterizers
or interpreters.
For more information about hardcopy, see Appendix B. Z-MAP Plus
Graphics Environment on page 95.
R2003.12.0 Configuring Hardcopy 49

Hardcopy and Hardcopy Batch
Z-MAP Plus Plotting for OpenWorks Users

CGM files can be generated directly within Z-MAP Plus in the File
Print Plot a Picture (CGM) option. This option will allow the user
to specify the CGM output file name. If OpenWorks is installed on
your system, you can send the CGM directly to the plotter without
exiting Z-MAP Plus.
Z-MAP Plus Plotting for Non-OpenWorks Users

If you do not use OpenWorks, you can still generate CGM files by
selecting the File Print CGM option in the Z-MAP Plus
window. You can send the CGM to the plotter after you exit
Z-MAP Plus, if you like.
You can also generate HP-GL files by selecting the File Print
Other option in the Z-MAP Plus window. This option enables you to
select a plotter device type. Z-MAP Plus uses the entries in the Plotter
Parameters dialog box to create a plotter parameters file. The plotter
parameters file becomes input to the hardcopy batch programs that
begin after you exit from the program.
Dialog Box Entries Are Used to Create Plotter Parameters File
R2003.12.0 Configuring Hardcopy: Hardcopy and Hardcopy Batch 50

Prelinked Hardcopy Available for CGM and HP-GL

The installation media includes Hardcopy already linked with CGM and HP-GL
file generation support. The Hardcopy binary file names for CGM/HP-GL support
are HDCOPY and HDBAT.
You can automatically submit hardcopy batch jobs if the file

HdConf.dat (in the /files subdirectory) is properly configured.
Z-MAP Plus uses the HdConf.dat file to determine which hardcopy
batch binary to execute. If the HdConf.dat is not in the /files
subdirectory, the automatic HDBAT job submission is disabled. When
there is no HdConf.dat file, the only thing that can be generated is a
hardcopy batch parameter file.
For each device type listed on the Plot Parameters dialog box, the
HdConf.dat file must specify a matching hardcopy batch binary.
The default HdConf.dat entries for devices and binaries are:
Table 10: Plotter Devices and Default Hardcopy Batch Programs

Workstation Type Numbera Hardcopy Batch Binary
777 HDBAT
778 HDBAT
779 HDBAT
780 HDBAT
1999 HDBAT
2999 HDBAT
a. The Workstation Type numbers are located in the

WDFILE in the /ZMAPPlus/files subdirectory.
In the HdConf.dat file, the two columns are separated by one blank
space. For example:
777 HDBAT
The second column contains the actual file name for the hardcopy
batch binary that supports output for the plotter type named in the first
column. The binary HDBAT can support both HP-GL and CGM
output. The identical entries for HDBAT in the table above actually
correspond to different HP-GL plotter sizes.

Both Hardcopy (interactive) and Hardcopy Batch use the environment

variables ZYCORCGM1 and PLOTOUT to set the file names for CGM
and HP-GL output. For example, to create a CGM file named my.cgm
or an HP-GL file named my.hpgl issue the following commands:
setenv ZYCORCGM1 my.cgm
setenv PLOTOUT my.hpgl
Environment
Type of
Variable Example Set Environment Variable
Hardcopy
Controlling the Command
Output
Output File Name
CGM ZYCORCGM1a setenv ZYCORCGM1

filename.cgm
HP-GL PLOTOUT setenv PLOTOUT filename.hpgl
a. The 1 in ZYCORCGM1 is used for picture counts. A second picture will use
ZYCORCGM2 and so on.
If the above environment variables are not set, the default output file
names will be ZYCORCGM1 and PLOTOUT.
Hardcopy Batch (HDBAT) Input Files

The program HDBAT (Hardcopy Batch) requires an input file in order
to work properly. The following is an example input file.
BATCH HARDCOPY PARAMETERS
--------------------------INPUT ZGF--------------------------
./colorwheel.zgf
-------------------------------------------------------------
------------------------INPUT PICTURE------------------------
VERSATEC SAMPLE TABLE
-------------------------------------------------------------
SCALE #PLOTS CUTLINE DNUMBER ROTATE

-------------------------------------------------------------
.333 1 0 1999 0
-------------------------------------------------------------

Format Details
Field Line # Start Col. End Col. Description
input zgf 5 1 80 zgf full path

input picture 10 1 80 picture name from zgf
scale 15 6 10 scale factor
#plots 15 20 23 number of copies
cutline 15 33 36 cutline flag (0=no, 1=yes)
dnumber 15 46 52 type number from WDFILE
rotate 15 58 59 rotate flag (0=no, 1=yes)
All the numeric fields on line 15 are right-justified. The dnumber field
is derived from the Workstation Type box from the appropriate plotter
WDFILE entry. The file WDFILE can be found under the /files
subdirectory.
Template HDBAT input files can be created in Z-MAP Plus under the
File Print Plot a Picture (Other) menu. The HDBAT input file
will be created in the current working directory with the file name
HDPARM and a numeric extension.

HP-GL Drivers
This section describes how to work with HP-GL graphics devices.
HP-GL is the Hewlett-Packard (HP) Graphics Language, the language
which HP plotters (and many non-HP graphics devices) understand.
HP-GL/2 is a superset of HP-GL that provides extended functionality
and also supports raster plotters. HP-GL is a human-readable language
based on two letter mnemonic commands. Commands are followed
by parameters separated by commas and a terminator, usually a
semicolon or the next command. An example is
SP1PU100,100PD200,200; (Select Pen 1, move to (100,100) with the
Pen Up, and draw to (200,200) with the Pen Down).
This section describes only the features of HP-GL and HP-GL/2 that
are used by the driver. There are some features of HP-GL, such as axis
rotation, that are not supported by the driver.
To work with your plotter, the HP-GL Driver needs the following
information:
Coordinate space
Roll feed
Driver output
Eavesdrop mode
Prompt mode
Absolute mode
Coordinate Space
Most Hewlett-Packard plotters can be loaded with more than one size
of paper. The size of the paper loaded determines the coordinate space
of the plotter. The driver cannot determine the size of the paper loaded,
so the Display Size in the Workstation Description File must be
correctly specified. The plotter hardware orients the x axis along the
longer dimension of the paper. Some HP plotters have their origin in
the center of the paper. Other plotters have their origin near the bottom
left corner of the paper. The position of the origin must be specified in
the Workstation Description File. See Center Origin (tenthousands
digit) on page 60.

Roll Feed
Some plotters use roll feed paper. If roll feed paper is installed, this
must be indicated in the Workstation Description File. Plotters with roll
feed paper are still best thought of as cut sheet plotters with an
automatic paper load feature. It is not possible to generate plots of
arbitrarily long length. Generally, the page length is limited to about
1.5 times the paper width, but consult the plotter documentation. The
Display Size in the Workstation Description File should reflect the
maximum plot size. The driver will set the page length so that only the
minimum amount of paper necessary is used.
Driver Output
The driver can output to a file or directly to a plotter. The driver opens
file PLOTOUT for output. This typically creates a disk file (PLOTOUT
or PLOTOUT.DAT). The output can be redirected to a plotter.
Eavesdrop mode and prompt mode are intended to be used only
when the driver outputs directly to a plotter, not when output is to a
disk file.
Eavesdrop Mode
Many Hewlett-Packard plotters can operate in eavesdrop mode to allow
a terminal and a plotter to share one computer port. In eavesdrop mode
all data from the computer is passed on to the terminal port of the
plotter until a plotter on command is received. Subsequent data is
interpreted as HP-GL commands for the plotter until a plotter off
command is received. The driver supports eavesdrop mode, allowing
programs to be run from a terminal connected directly to the plotter.
The Workstation Description File entry of a plotter specifies whether
eavesdrop mode is to be used. If eavesdrop mode is to be used, the
plotter itself must also be placed in eavesdrop mode.

Prompt Mode
The driver supports an optional prompt mode. Specify whether to use
prompt mode in the Workstation Description File. If prompt mode is
enabled, then you are asked before each plot (except the first) whether
you want a new sheet of paper. If you want a new sheet, and the plotter
is not loaded with roll feed paper, you will be prompted to load a new
sheet of paper and press Return. Roll feed plotters automatically
advance the paper.
You may want to put several plots on a single sheet of paper. You can
draw multiple plots by instructing the plotter not to provide a new sheet
of paper and by repositioning the pen before the next plot. The driver is
not able to do this with all plotters. It is able to accept pen repositioning
only on plotters that support the type 2 SC command, which includes
all HP-GL/2 plotters and some older ones. Pen repositioning must be
disabled in the Workstation Description File for those plotters that do
not support the type 2 SC command. If you do not want a new sheet of
paper and pen repositioning is enabled, you are prompted to reposition
the pen and press Return when you finish. Otherwise, the next plot
will plot over the last plot.
Absolute Mode
Pen moves and draws can be encoded in absolute (PA) or relative (PR)
instructions. Relative mode generates significantly smaller output files
than absolute mode and thus should be used unless there is good reason
to avoid relative mode. Some devices and software that accept HP-GL
cannot accept relative coordinates, and so absolute mode is provided.
Note that HP-GL/2 supports an even more compact instruction than
PR, the PE instruction. Absolute mode is ignored if PE instructions are
used. PE instructions are always relative. The Workstation Description
File determines whether PA, PR or PE instructions are used.

Workstation Description File for HP-GL Driven Devices

The WDFILE determines the number and kind of graphics devices
available and consists of a file header followed by one or more device
description entries. The WDFILE is required by the Z-MAP Interactive
Graphics System (ZIGS). For more information about the WDFILE,
see the section Workstation Description File (WDFILE) on page 67.
For more information about ZIGS, see Appendix B. Z-MAP Plus
Graphics Environment on page 95.
Each graphics device driven by HP-GL must have an entry in the
WDFILE. An entry for an HP-GL device is identical in format to
entries for other devices and contains the following information:
Workstation type
Workstation name
Workstation category
Display size
Display type
Locator device numbers
Color
Driver code
Device number
Workstation Type
This is an arbitrary integer which uniquely identifies a particular entry
in the file. The driver does not use this number.
Workstation Name
This is a text description for the device in the WDFILE entry. This is
the name by which the user selects the device. The driver does not use
this name.
Workstation Category
This is a number which identifies whether the device is output only (0),
input only (1), or output/input (2). All HP-GL devices are output only.

Display Size
The display size in x and y directions is defined in meters, resolution
units, and internal units. Display size depends on the plotter model and
the size of the paper installed. The user's guide for each plotter model
specifies the maximum plotting area in meters for each size of paper.
The size in internal units is the size in meters times 1000, divided by
the step size, usually .025 mm. The size in resolution units is one
greater than the size in internal units.
If a user's guide is not available, measure the paper size in meters and
subtract 15 mm for margins on the left, top, and right sides and 39 mm
for the margin on the bottom. If the display size is too large, then plots
can extend outside the hard clip limits and be clipped away. If the
display size is too small, then part of the paper will not be available for
plotting.
The x and y dimensions for an A-size HP-GL plotter are as follows:
METERS RESOLUTION INTERNAL
---------- ------------ ------------
DISPLAY SIZE (X) | .2591| | 10365| | 10365.|
DISPLAY SIZE (Y) | .1990| | 7962| | 7962.|
---------- ------------ ------------
How Values for Internal Number and Resolution Are Calculated

The numbers in each box are calculated as follows:
Meters = (Internal number/1016) *.0254
Resolution = Internal number
Internal Y = (width in inches) * 1016
Internal X = (length in inches) * 1016
There are 1016 HP-GL units-per-inch.
A 36 by 48 inch plotter would have the following x, y dimensions.

---------- ------------ ------------
DISPLAY SIZE (X) | 1.1938| | 47752| | 47752|
DISPLAY SIZE (Y) | .8890| | 35560| | 35560|
---------- ------------ ------------

The x, y dimensions are reduced by 1 inch in the above calculations.

This was done to account for the fact that most plotters cannot access
the full width of the paper.
The WDFILE included on the installation media contains entries for
four different HP-GL paper sizes. Sizes included are:
Table 11: Plotter Paper Sizes

Plotter Paper Size Width Length
A-size 8 11
B-size 11 16
C-size 16 21
D-size 21 32
Display Type
The display type is either vector (0) or raster (1).
Locator Device Numbers

Plotters are output only, so these numbers are not used.
Color
The color available field should contain a 1. The number of colors
determines the number of colors available, including color 0, the
background color. On pen plotters the number of colors is equal to the
number of pens available plus 1 (for the background). Pens must be in
continuous positions in the pen holder starting with pen 1. The pen
colors are implied to be black, red, green, yellow, blue, magenta, and
cyan, in that order. Raster plotters can have more than 8 colors.
Driver Code
The driver code for HP-GL is always 25.

Device Number
The device number field contains a six-digit integer number. Each digit
has a meaning.
absolute mode?
center origin?
eavesdrop mode?
prompt mode?
roll paper?
HP-GL2?
0 0 0 0 0 0
HP-GL/2 (ones digit)

0 - HP-GL/2 not supported
1 - HP-GL/2 supported, do not use PE instruction
7 - HP-GL/2 supported, use 7 bit PE instruction
8 - HP-GL/2 supported, use 8 but PE instruction
Roll Paper (tens digit)

0 - roll feed paper not installed
1 - roll feed paper installed
Prompt Mode (hundreds digit)

0 - prompt mode not enabled
1 - prompt mode enabled
2 - prompt mode enabled but pen repositioning disabled
Eavesdrop Mode (thousands digit)

0 - eavesdrop mode not enabled
1 - eavesdrop mode enabled
Center Origin (tenthousands digit)

0 - plotter origin is in lower left corner of paper
1 - plotter origin is in center of paper
Absolute Mode (hundredthousands digit)

0 - use PR (pen relative) instruction
1 - use PA (pen absolute) instruction

CGM Drivers
The Landmark CGM driver is part of the ZIGS (ZYCOR Interactive
Graphics System) subsystem. It generates ANSI standard CGM
(Computer Graphics Metafile) files using the binary encoding scheme.
Other CGM encoding schemes are available but are currently not
supported by Landmark.
Output File
The CGM driver generates a file named ZYCORCGM on Unix
systems.
Elements Generated
Every Landmark CGM file contains the following elements:
BEGIN METAFILE (ZYCOR CGM)
END METAFILE
BEGIN PICTURE (PICTURE 1, PICTURE 2, . .)
BEGIN PICTURE BODY
END PICTURE
METAFILE VERSION (1)
VDC TYPE (INTEGER)
INTEGER PRECISION (16)
REAL PRECISION (FIXED,16,16)
COLOR PRECISION (16)
COLOR INDEX PRECISION (16)
MAXIMUM COLOR INDEX (255)
COLOR VALUE EXTENT ((0,0,0),(255,255,255))
METAFILE ELEMENT LIST
SCALING MODE (METRIC,0.0635)
VDC EXTENT
INTERIOR STYLE (SOLID)
VDC INTEGER PRECISION (24)
The following elements may also appear in a Landmark CGM:
POLYLINE
POLYGON
LINE TYPE
LINE WIDTH
LINE COLOR
FILL COLOR
COLOR TABLE
VDC INTEGER PRECISION (16)
R2003.12.0 Configuring Hardcopy: CGM Drivers 61

Scaling Mode and VDC Extent

The SCALING MODE element specifies the metric scale factor, i.e.
the size (in millimeters) of a VDC (Virtual Device Coordinate) unit.
The metric scale factor is set to 0.0635, i.e. 1 VDC = 0.0635 mm = 400
dots/inch. With 16-bit integer VDCs, the maximum VDC extent is
about 2.08 meters square, and with 24-bit integer VDCs, the maximum
VDC extent is about 533 meters square. (The application takes care of
selecting the VDC size based on the size of the plot.)
If your CGM rasterizer performs panelling automatically (Zeh Graphic
Systems does), then there is no reason to change the Display Size
entries in the WDFILE; the CGM rasterizer should panel correctly
regardless of the plotter size.
If the CGM rasterizer does not perform panelling automatically, then
you must modify the Display Size entries in the WDFILE to reflect the
plotter size. The physical size of the paper goes in the METERS
column. The numbers in the RESOLUTION column should be the
numbers in the METERS column divided by 0.0000635. The numbers
in the INTERNAL column should be the numbers in the
RESOLUTION column, minus one. Once the Display Size entries
reflect the plotter size, the application program (Z-MAP Plus or
HDCOPY) will write multiple pictures, one per panel, to the same
CGM. Each picture will have a separate VDC extent that reflects the
size of that panel. It is up to you to instruct the CGM rasterizer to plot
those multiple pictures.
Color
The CGM driver supports indexed color mode with a color table of 256
entries. The CGM contains a COLOR TABLE element for a color
index before the first use of that index in a LINE COLOR or FILL
COLOR element, with the exception of indices 0 and 1. These two
indices are excluded from the COLOR TABLE element in the CGM so
that an interpreter can use the appropriate color for the specific output
device in use.

Workstation Description File

An entry must exist in the Workstation Description File (WDFILE) for
a CGM type graphics device. The first field is the Device Description
Field (DDENTRY Field). The proper values for each DDENTRY Field
are shown below:
Describing CGM Type Graphics Device for WDFILE

DDENTRY Fields - Type of Value Expected
Workstation Type - an arbitrary, but unique, integer number
Workstation Name - CGM File, or something similar
Workstation Category - 0 (output)
Display Size - meters (532.676608, 532.676608)
resolution (8388608, 8388608)
internal (8388607., 8388607.)
Locator Device Numbers - not used
Color Available - 1 (yes)
Number of Colors - 256
Driver Code - 24
Device Number - 0

Versatec Support
Versatec cannot directly read CGM files, but you can plot to Versatec
indirectly by using a third party rasterizer or filter to convert a CGM
into something Versatec can understand.
Using CGMs with Versatec Plotters

Zeh Graphics has a program that will rasterize a CGM into a Versatec
Raster format. This raster file can then be sent directly to a Versatec
plotter. This very popular program is supported by Landmark. Some
features of this program are:
It reads standard CGMs (not CGM+).
It produces good-looking dithered colors.
Because it does the rasterization, the Versatec plotter need not have
an RPM (Raster Processing Machine).
A Sun SPARCstation or equivalent is required to run the program.
While a CGM can contain multiple pictures, Zehs program will
only convert a single (selectable) picture at a time, but it will
correctly panel large plots.
It does not allow for picture rotation.
R2003.12.0 Configuring Hardcopy: Versatec Support 64

Larson Software makes INTERPRETERcgm, a program that converts

CGMs into Versatec Color Graphics Language (VCGL), permitting
direct transmission to Versatec plotters for rasterization and plotting.
This product can be used with any of the Versatec rasterizers that
support RPM_VCGL, explained below. Some of the features of this
program are:
While a CGM can contain multiple pictures, Larsons program
will only convert a single (selectable) picture at a time, but it will
correctly panel large plots.
The Versatec plotter must have a VCGL type of RPM.
Because it uses Versatecs rasterizer, the host computer is not used
for the computation-intensive rasterization.
Standard CGM and CGM+ are supported.
Larsons dithered colors are not as bright as Zehs. (They are
working on improving their dithered colors, though, at the time of
this writing.)
Customizing Runtime Files

Each installation includes a file named /ZMAPPlus/files/WDFILE. This
file describes the plotters that are accessible to the hardcopy programs.
The WDFILE file also contains some default entries for commonly
used plotters. You have to add any new entries that came with the
installation media. If you have previous versions of the WDFILE from
earlier versions of Landmarks hardcopy programs, you can transfer the
potter entries from the earlier version of WDFILE to the new file.

To add entries to the WDFILE, use a text editor to insert them by using
the same format as the other entries in the file. Be sure to increase the
number of workstations box at the top of the file by one for each
entry you add. The default entries in the WDFILE are:
X Windows
Versatec plotter
Calcomp 9100 digitizer
Summagraphic 3648 digitizer
Tektronix 4697 digitizer
Gtco digitizer
CGM metafile
Hp-GL plotter
For more information about the WDFILE format, read the section
called Workstation Description File (WDFILE) on page 67.
Running the Hardcopy Programs

Your hardcopy programs appear on the menu of applications that
appears if you select Utilities Hardcopy Hardcopy Batch from
the Z-MAP Plus Command Menu. If you are not running the
Z-MAP Plus Command Menu, you can generate a list of hardcopy
executables by calling the shell script ZMAPPlus. Choose a hardcopy
program from the menu that appears.

Workstation Description File (WDFILE)
Introduction
The Workstation Description File (WDFILE) is a formatted file read by
the Z-MAP Interactive Graphics System (ZIGS) at initialization time.
The WDFILE determines the number and kind of graphics devices
available. It consists of a file header followed by one or more device
description entries. Each entry in the WDFILE is a Device Description
Entry (DDENTRY).
This section contains the following topics:

Format of a Standard WDFILE The components of a
WDFILE.
DDENTRY Field Descriptions The components of a

WDFILE header.
DDENTRY Type Number How to create a unique

DDINTRY number.
Driver Codes A list of codes for identifying interactive

graphics, digitizers, and plotters.
Device Numbers How to identify a device and its

characteristics using a unique set of numbers.
Driver Code Make Numbers How to assign subcategories

of driver codes.
WDFILE Example How the values for the above parameters

look in a real WDFILE.
Template Field Descriptions Additional requirements for

TEMPLATE device drivers.
R2003.12.0 Workstation Description File (WDFILE) 67

Format of a Standard WDFILE

---- --
NUMBER OF WORKSTATIONS TYPES | 1| Z-MAP PLOT UNITS (IN|CM) |CM|
---- --
======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 410700| |TEKTRONIX 4107 | | 2|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | .240| | 480| | 4095.|
DISPLAY SIZE (Y) | .180| | 360| | 3119.|
---------- ------------ ------------
TYPE
----
DISPLAY | 1|
----
---- ---- ---- ----

LOCATOR DEVICE NUMBERS | 1| | | | | | |
---- ---- ---- ----
AVAILABLE ? NUMBER OF COLORS

------------ ----------------
COLOR | 1| | 16|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 1| | 1410700|
---- -------------
======================================================================
END OF WORKSTATION DESCRIPTION FILE
R2003.12.0 Workstation Description File (WDFILE): Format of a Standard WDFILE 68

DDENTRY Field Descriptions

This section contains an explanation of the WDFILE header and the
descriptions for each field in a single DDENTRY.
(E) Indicates that the field contains a right justified enumeration
code
(I) Indicates that the field contains a right justified integer number
(R) Indicates that the field contains a right justified floating point
number
(T) Indicates that the field contains a left justified text string
The WDFILE header occupies the first five lines of the file and
contains the following fields:
Line Starting Field

Contents
Number Column Width
3 31 4 Number of Workstation Descriptions

to Follow (I)
Maximum of 20 DDENTRIES
3 65 2 Inches or Centimeters (T)
This field is not applicable to
Z-MAP Plus prior to Version 1.4 or
Stratview prior to Version 11.0
Each DDENTRY occupies a minimum of 32 lines and contains the data

fields in the following table. Line numbers are relative to the first line
of the entry, not the first line of the file.
R2003.12.0 Workstation Description File (WDFILE): DDENTRY Field Descriptions 69

Line Starting Field

Contents
Number Column Width
5 14 10 Type Number (I) (See DDENTRY Type

Number on page 71.)
5 27 32 Name (T)
5 62 8 Category (E)
0 - Output Only (Plotter)
1 - Input Only (Digitizer)
2 - Output/Input (Graphics Display)
10 19 10 Width in Meters of Display Surface (R)
10 32 12 Horizontal Resolution of Display Area (I)
10 47 12 Maximum X Device Coordinate (R)
11 19 10 Height in Meters of Display Surface (R)
11 32 12 Vertical Resolution of Display Area (I)
11 47 12 Maximum Y Device Coordinate (R)
16 10 4 Display Type (E)
0 - Vector
1 - Raster
2 - Other
20 25 4 Number of Locator Devices (I)
20 32 4 Device Number of First Locator Device (I)
20 39 4 Device Number of Second Locator Device
(I)
20 46 4 Device Number of Third Locator Device
(I)
25 9 12 Color or Monochrome (E)
0 - Monochrome
1 - Color
25 24 16 Number of Colors (I)
30 9 4 Device Driver Code (E)
(See Driver Codes on page 72.)
30 16 13 Device Number (I)
(See Device Numbers on page 73.)
Additional lines are added to the WDFILE for TEMPLATE display

devices. Please refer to the Template Field Descriptions on page 88.
R2003.12.0 Workstation Description File (WDFILE): DDENTRY Field Descriptions 70

DDENTRY Type Number

The type number is used to uniquely identify each DDENTRY in the
WDFILE.
A DDENTRY type number has two fields:
an arbitrary identifier field Often this will be the same as the
model number of the device being used.
the number of choice buttons for digitizers For other devices
this is 00 or absent.
For example, the DDENTRY type number for a Calcomp 9160
digitizer with 16 buttons is:
9160 16
number of choice buttons for digitizers (other devices = 00)
arbitrary numeric field (usually device model number)
The DDENTRY type number for a Tektronix 4207 can be:

4207 00
either 00 or absent
an arbitrary but unique number to identify the DDENTRY

for the Tektronix 4207
R2003.12.0 Workstation Description File (WDFILE): DDENTRY Type Number 71

Driver Codes
Driver codes identify major device categories. A driver code can
support many different devices of the named device category. Specific
devices are identified by a unique Device Number and Make Number.
(For more information, see Device Numbers on page 73 and Driver
Code Make Numbers on page 77.)
The following list contains the driver codes available for use by
Landmark products for interactive graphics, digitizers, and plotters.
Driver
Code Manufacturer
1 Tektronix
2 Plotter
3 Precision Visuals DI-3000
4 IBM GASP
5 DEC Regis
6 Ayden Aygraf
7 Calcomp Vistagraphic FSP
8 Megatek Template
9 Megatek Wand
10 Apollo GPR
11 Hewlett-Packard DGL/Starbase
12 GeoQuest IES
13 IBM GDDM
14 GSS*CGI
15 DEC VAX GKS
16 Digitizers
17 DEC Vaxstation (UIS)
18 Western Geophysical Crystal
21 X Windows
24 CGM metafile
25 HPGL
R2003.12.0 Workstation Description File (WDFILE): Driver Codes 72

Device Numbers
A device number uniquely identifies a specific device and specifies
device characteristics.
With a few exceptions, a device number descriptor has three fields:
the make identifier
the model number (such as 4207)
the host-to-device communications method (IBM only)
For example, below is a device number for a Tektronix 4207 graphics
terminal:
01 4207 00
communications method: On IBM VM and IBM VMS

only, 0 = ADIN/OUT, 10 = CSIN/OUT, 11 = PCIIN/
OUT.
model number
make identifier: See Driver Code Make Numbers
on page 77.
R2003.12.0 Workstation Description File (WDFILE): Device Numbers 73

For Driver Code 2 and Make Code 4 (Versatec plotters), a device

number descriptor has four fields:
Versatec software release flag
make identifier
model number
plotter identification number (Geoquest workstations only)
For example, below is a device number for a Versatec 3444 using
Versatec software release 2.1 or Versatec VGS software:
21 4 3444 00
normally 00, except on Geoquest workstations. For

Geoquest, the final two digits indicate the virtual
device number to which a plotter is assigned.
Versatec model number
make identifier (always 4 for Versatec plotters)
Versatec software release flag
(release 2.1 or higher, VGS)
00 = release 2.1 or higher, VGS not available
21 = define in RGB mode (darker colors)
22 = define in HLS mode (lighter colors)
23 = same as 21, but no line dithering
24 = same as 22, but no line dithering

For Driver Code 16 (digitizer), a device number descriptor has six

fields:
the host-to-device communications method (IBM only)
the make identifier
the model number
the number of buttons on the puck
the format identifier
units flag (0 = imperial, 1 = metric, 2 = counts)
For example, below is a device number for a Calcomp 9480 with 12
buttons using format 1 (see Driver Code Make Numbers on page 77)
using imperial units:
0 01 9480 12 01 0
units flag (0=imperial, 1=metric, 2=counts)
format identifier
(in Calcomp, Altek, and Summagraphics digitizers)
number of buttons
model number
make identifier
host-to-host terminal communication method

(only tested on IBMs with COAX communications)

For Driver Code 25 (HPGL) a device number descriptor has six fields:
absolute mode?
center origin?
eavesdrop mode?
prompt mode?
roll paper?
HP-GL/2?
For example, below is a DEVICE NUMBER for an HPGL plotter
which supports roll feed paper and HP-GL/2:
0 0 0 0 11
HP-GL/2 support (0 = no, 1 = yes)
roll paper (0 = no, 1 = yes)
prompt mode
(0 = no, 1 = yes, 2 = yes with no pen repositioning)
eavesdrop mode (0 = no, 1 = yes)
center origin (0 = no, 1 =yes)
absolute mode (0 = use pen relatives, 1 = use pen

absolutes)

Driver Code Make Numbers

Make Numbers identify subcategories of driver codes.
Driver Code 1 (Tektronix or Tektronix Emulators)

01 - Tektronix and Tektronix Plotters
02 - Petrographics enhanced
03 - Ramtek
04 - Lexidata
05 - Visual
06 - Envision
07 - Genisco
08 - C. Itoh
09 - Selanar
10 - Modgraph
11 - Intecolor
12 - Tab
13 - Westward
14 - IBM PC Terminal Emulators
15 - Monterey
Driver Code 2 (Plotters)

01 - Calcomp
02 - Houston Instruments
03 - Nicolet Zeta
04 - Versatec
05 - Benson
06 - Xynetics
07 - Hewlett-Packard
Driver Code 16 (Digitizers)

01 - Calcomp digitizer
02 - Houston Instruments digitizers
03 - Tektronix graphics locator device
04 - Tektronix digitizer (not attached to the back of a terminal)
05 - Summagraphics (non-microgrids)
06 - GTCO
07 - Altek
08 - Summagraphics Microgrid
09 - Numonics digitizers
R2003.12.0 Workstation Description File (WDFILE): Driver Code Make Numbers 77

For each digitizer make number, the following information is necessary

to build a valid digitizer Device Number.
01 - Calcomp Digitizer
Valid model numbers: 9120, 9136, 9148, 9160, 9240, 9360, 9480,
9600, 6480, 6220, 6140, 6110, 8120, 8220, 8400, 8480, 8600, 4000
Valid cursor values: 1, 4, 12, 16
Formats for 9100 and 9000 series:
imperial format
1 : TMFXXXXXYYYYYC
2 : XXXXX,YYYYY,TMFC
3 : FUXXXXXYYYYYC
4 : SXX.XXX,SYY.YYY,TMFC or BXX.XXX,BYY.YYY,TMFC
metric format
1 : TMFXXXXXXYYYYYYC
2 : XXXXXX,YYYYYY,TMFC
3 : FUXXXXXXYYYYYYC
4 : SXXXX.XX,SYYYY.YY,TMFC or
BXXXX.XX,BYYYY.YY,TMFC
counts format
1 : TMFXXXXXYYYYYC
2 : XXXXX,YYYYYTMFC
3 : FUXXXXXYYYYYC
4 : SXXXXX.,SYYYYY.,TMFC or BXXXXX.,BYYYYY.,TMFC
Where
F = flag character
( ) = optional character
C = character return
L = line feed
T = tablet identifier
Q, R = blank or special character
S = sign (+ or -)
B = blank
U = status (up or down)
M = mode status (point, stream, etc.)
Format 3 is the standard format for 6000 and 8000 series.

02 - Houston Instruments Digitizer

Note: the format and units used are set by the program and cleared
upon exiting.
Valid model numbers: 7012, 7024, 7048, 7060
Valid cursor values: 1, 12
03 - Tektronix Graphics Locator Device

Note: Format and units flags are not used.
Valid model numbers:4100 - attached to a TK4100 device
4010 - attached to a TK4010 device
04 - Tektronix Digitizer (Not Attached to a Tektronix Terminal)

Note: Format and units flags are not used.
Valid Model numbers: 4957 (11 x 11); 4958 (24 x 36)
05 - Summagraphics (Non-Microgrids)
inches format
1 : TFSXXXXXSYYYYY(C)(L)
2 : TFSXX.XXX,SYY.YYY/CL
3 : QTFSXX.XXX,SYY.YYY/CLR
millimeters
1 : TFSXXXXXSYYYYY(C)(L)
2 : TFSXXXX.X,SYYYY.Y/CL
3 : QTFSXXXX.X,SYYYY.Y/CLR
06 - GTCO
GTCO 5 - Model number (0050)
GTCO 5A Model number (0051)
Note: the format and units used are set by the program and cleared
upon exiting.

07 - Altek
A30: (Model number 0030)
format =
1 : FBSXXXXXBSYYYYYC11 : FXXXXXBYYYYYC
2 : FSXXXXXSYYYYYC12 : FXXXXXYYYYYBC
3 : F,SXXXXX,SYYYYYC13 : XXXXX,YYYYY,FC
4 : FBXXXXXBYYYYYC14 : FBXXXXXBYYYYYC
5 : FUSXXXXXSYYYYYC15 : FSXXXXXYYYYYC
6 : Not supported16 : Not supported
7 : $F,SXXXXX,SYYYYYC17 : $F,XXXXX,YYYYYC
A40: (Model number 0040)
imperial or metric metric only
format =
1 : FBXXXXXBYYYYYC11 : FBXXXXXXBYYYYYYC
2 : FXXXXXYYYYYC12 : FXXXXXXYYYYYYC
3 : F,XXXXX,YYYYYC13 : F,XXXXXX,YYYYYYC
4 : FXXXXXBYYYYYC14 : FXXXXXXBYYYYYYC
5 : FUXXXXXBYYYYYC15 : FUXXXXXXYYYYYYC
6 : Not supported16 : Not supported
7 : $F,XXXXX,YYYYYC17 : $F,XXXXXX,YYYYYYC
Note: The program sets the format to either 1 or 11 internally and
resets it upon exiting, but it will use the provided format number to
determine if it is reset to 1 or 11.
08 - Summagraphics Microgrid
Format and units are set by the program and reset upon exiting.
09 - Numonics Digitizers
Valid model number: 2200
Format is determined by the program, units are set by the program to
inches.
Note: The digitizer is not reset upon exiting; this needs to be done by
hand.

WDFILE Example
---- --
NUMBER OF WORKSTATIONS TYPES | 11| Z-MAP PLOT UNITS (IN|CM) |CM|
---- --
=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 999| |X Window System | | 2|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | 0.| | 700| | 0.|
DISPLAY SIZE (Y) | 0.| | 700| | 0.|
---------- ------------ ------------
TYPE
----
DISPLAY | 1|
----
---- ---- ---- ----

---- ---- ---- ----

------------ ----------------
COLOR | 2| | 0|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 21| | 0|
---- -------------
=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 324400| |OpenWorks_CGM_Plot_Queue | | 0|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | 1.0668| | 16800| | 42.0|
DISPLAY SIZE (Y) | 10.6680| | 168000| | 420.0|
---------- ------------ ------------
R2003.12.0 Workstation Description File (WDFILE): WDFILE Example 81

TYPE
----
DISPLAY | 1|
----
---- ---- ---- ----

LOCATOR DEVICE NUMBERS | | | | | | | |
---- ---- ---- ----

------------ ----------------
COLOR | 1| | 256|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 2| | 4324400|
---- -------------
=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 344400| |VERSATEC 3444 | | 0|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | 10.6680| | 168000| | 420.0|
DISPLAY SIZE (Y) | 1.0668| | 16800| | 42.0|
---------- ------------ ------------
TYPE
----
DISPLAY | 1|
----
---- ---- ---- ----

---- ---- ---- ----

------------ ----------------
COLOR | 1| | 256|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 2| | 214344400|
---- -------------
=======================================================================

TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 323600| |VERSATEC 3236 | | 0|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | 8.6870| | 68400| | 342.0|
DISPLAY SIZE (Y) | .8687| | 6840| | 34.2|
---------- ------------ ------------
TYPE
----
DISPLAY | 1|
----
---- ---- ---- ----

---- ---- ---- ----

------------ ----------------
COLOR | 1| | 256|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 2| | 214323600|
---- -------------
=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 914816| |CALCOMP 48X36 DIGITIZER (9100) | | 1|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | 1.2192| | 48000| | 48.0|
DISPLAY SIZE (Y) | 0.9144| | 36000| | 36.0|
---------- ------------ ------------
TYPE
----
DISPLAY | 0|
----
---- ---- ---- ----

---- ---- ---- ----


------------ ----------------
COLOR | 0| | 2|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 16| | 001914816030|
---- -------------
=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 364816| |SUMMAGRAPHICS MICROGRID 36X48 | | 1|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | 1.2192| | 48000| | 48.0|
DISPLAY SIZE (Y) | .9144| | 36000| | 36.0|
---------- ------------ ------------
TYPE
----
DISPLAY | 0|
----
---- ---- ---- ----

---- ---- ---- ----

------------ ----------------
COLOR | 0| | 2|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 16| | 008364816000|
---- -------------
=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 495704| |TEKTRONIX 4957 DIGITIZER | | 1|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | .2972| | 11888| | 11.888|
DISPLAY SIZE (Y) | .2972| | 11888| | 11.888|
---------- ------------ ------------

TYPE
----
DISPLAY | 1|
----
---- ---- ---- ----

LOCATOR DEVICE NUMBERS | 1| | 0| | | | |
---- ---- ---- ----

------------ ----------------
COLOR | 0| | 0|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 16| | 004495704010|
---- -------------
=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 777| |HP PLOTTER | | 0|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | .2578| | 10365| | 10365.|
DISPLAY SIZE (Y) | .1981| | 7962| | 7962.|
---------- ------------ ------------
TYPE
----
DISPLAY | 0|
----
---- ---- ---- ----

---- ---- ---- ----

------------ ----------------
COLOR | 1| | 8|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 25| | 00000|
---- -------------
=======================================================================

TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 1999| |CGM METAFILE - Color | | 0|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) |532.676608| | 8388608| | 8388607.|
DISPLAY SIZE (Y) |532.676608| | 8388608| | 8388607.|
---------- ------------ ------------
TYPE
----
DISPLAY | 1|
----
---- ---- ---- ----

---- ---- ---- ----

------------ ----------------
COLOR | 1| | 256|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 24| | 0|
---- -------------
=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 2999| |CGM METAFILE - Black & White | | 0|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) |532.676608| | 8388608| | 8388607.|
DISPLAY SIZE (Y) |532.676608| | 8388608| | 8388607.|
---------- ------------ ------------
TYPE
----
DISPLAY | 1|
----
---- ---- ---- ----

---- ---- ---- ----


------------ ----------------
COLOR | 0| | 2|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 24| | 0|
---- -------------
=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 5016| |GEOQUEST GTCO DIGITIZER | | 1|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | 1.2192| | 1280| | 1279.|
DISPLAY SIZE (Y) | .9753| | 1024| | 1023.|
---------- ------------ ------------
TYPE
----
DISPLAY | 0|
----
---- ---- ---- ----

---- ---- ---- ----

------------ ----------------
COLOR | 0| | 2|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 12| | 2|
---- -------------
=======================================================================
END OF WORKSTATION DESCRIPTION FILE

Template Field Descriptions
Template DDENTRY Field

If the device driver is TEMPLATE, there are five additional lines (for a
total of 37 lines) in the DDENTRY:
Line Starting Field

Contents
Number Column Width
35 11 7 Device Acronym (T)
Sample TEMPLATE DDENTRY:

=======================================================================
TYPE NAME CATEGORY

---------- -------------------------------- --------
WORKSTATION | 4115| |TEKTRONIX 4115/TEMPLATE | | 2|
---------- -------------------------------- --------

---------- ------------ ------------
DISPLAY SIZE (X) | .343| | 1280| | 4095.|
DISPLAY SIZE (Y) | .274| | 1024| | 3119.|
---------- ------------ ------------
TYPE
----
DISPLAY | 1|
----
---- ---- ---- ----
---- ---- ---- ----

------------ ----------------
COLOR | 1| | 64|
------------ ----------------
CODE DEVICE NUMBER

---- -------------
DRIVER | 1| | 1411500|
---- -------------
ACRONYM
-------
TEMPLATE |TEK |
-------
R2003.12.0 Workstation Description File (WDFILE): Template Field Descriptions 88

Appendix A. Environment Variables

for Mapping Products
Introduction
This appendix is a master list of environment variables you can use
with mapping products.
Methods of Setting Environment Variables

The way you set environment variables depends on whether you:
Run Z-MAP Plus from OpenWorks or from a non-OpenWorks
environment
Want the variable settings to remain the same most or all of the
time, or prefer to toggle a given variable on and off
For any given environment variable, choose the solution that best suits
your needs.
For System Administrators

You can set many of the environment variables for users by editing the
MapConfig.dat file located in the /files subdirectory. This file contains all
the definitions for environment variables in mapping applications. We do not
recommend that you allow users to modify this file. You can identify the
environment variable settings that best suit the user environment and site
requirements and enable these variables whenever a mapping application is
executed.
R2003.12.0 Appendix A. Environment Variables for Mapping Products 89

Setting Environment Variables for an OpenWorks User

The two main options are:
Modify the .lgclogin file, setting custom environment variables.
Each time you start OpenWorks, the environment variable settings
take effect.
Enter the environment variable settings before you start
OpenWorks, either in the xterm window you use to run
OpenWorks, or from the front-end prompt (after you login, but
before you enter the command to start OpenWorks).
For Environment Variables You Want to Retain

You probably know which aspects of the user environment you want to
keep constant in all OpenWorks and Z-MAP Plus sessions. Here are a
few examples of preferences that are likely to stay the same:
Display the graphic window separately from the main application
window when Z-MAP Plus starts.
Substitute presentation quality fonts for Z-MAP Plus fonts when
sending plots to CGM rasterizers.
Using a text editor, modify the .lgclogin file, adding the environment
variable settings that you expect to remain the same under most
circumstances. On the rare occasions when you wish to disable a given
variable, comment it out of the .lgclogin file.
For Environment Variables You Want to Change Often

Some environment variables need to change from one program session
to another. Examples of variables you may want to change include
those which are device specific. If you work with different plotters or
digitizers, for example, you may want to point to different
configuration files depending on the device configuration you are
using. Any variable enabling infrequent or one-time use can be set and
unset in the terminal window (or from the front-end prompt). In order
to disable a variable you have set from a terminal window or console,
you must exit Z-MAP Plus and OpenWorks, enter the unset command
(unsetenv variable), and restart OpenWorks and Z-MAP Plus.

Setting Environment Variables for a Non-OpenWorks User

The two main options are:
Modify the .cshrc file with custom environment variables. Each
time you login, the environment variable settings take effect.
Enter the environment variable settings before you display either
the Z-MAP Plus Command Menu or the Z-MAP Plus window.
For Environment Variables You Want to Retain

The principles you use to determine which environment variables to
add to the .cshrc or .login file are the same as for OpenWorks users.
Identify the aspects of the environment you want to remain the same
for all program sessions. If you prefer to enable presentation quality
fonts, or use the MULTI_WINDOW configuration for Z-MAP Plus, set
these environment variables in the .cshrc file.
For Environment Variables You Change Frequently

When you know that you want to toggle an environment variable on
and off frequently, enter the variable settings before you start the
Z-MAP Plus Command Menu or Z-MAP Plus. To disable the setting,
exit the program(s) and enter the unset command (unsetenv
variable) for that variable. Then restart the Z-MAP Plus Command
Menu by using the ZMAPPlus script.
Variable Name, Applications, and Default Settings

Used by
Variable Name Default Value Purpose
Apps.
BROWSER Z-MAP Plu $ZTARGET/ Identifies the web browser to

s htmlHelp use for viewing HTML Help.
BROWSER_START_ Z-MAP Plu $ZTARGET/ Specifies the command-line
ARGS s htmlHelp arguments for your web
browser.
DISCONT Z-MAP Plu $ZTARGET/files/ Maps discontinuity to
s and ZCL Discont_codes symbol information.
DLSFILE Z-MAP Plu $ZTARGET/files/ Defines DLS posting
s and ZCL DLS.BIN information.
ERR_LEVEL all 4 Determines level of
information if errors occur.
Valid values are 0 (most
information) 4(least
information).


Used by
Apps.
FONT_MAP Z-MAP Plu UNSET Enables Presentation Quality

s Fonts to be output to CGM
files. Requires font
configuration file. Set to:
path/filename.cfg
FOCUS_TIME_OUT Z-MAP Plu 1000 Time lapse in milliseconds
s before icon label is
displayed.
HDCONF Z-MAP Plus $ZTARGET/files/ Configures hardcopy
HdConf.dat information.
HELP_ICON Z-MAP Plus UNSET (NO) OBSOLETE
(HPUX
only)
LD_LIBRARY_PATH all Application and Search path for shared
platform dependent library files.
LM_LICENSE_FILE all UNSET Overrides default location
for LAM license file. By
default, applications search
$OWHOME/lam,
$ZTARGET/lam or
/etc for the license file.
LOGOFILE Z-MAP Plu UNSET Configures information for
s and ZCL custom title block logos. Set
to: path/filename
MAP_CONFIG Mapping $ZTARGET/files Configures all definitions for
applications MapConfig.dat Mapping application
environment variables.
MULTI_WINDOW Z-MAP Plu UNSET (NO) If set, allows graphic window
s to be displayed separately
from the main application
window.
NADCFILES Z-MAP Plu $ZTARGET/files Specifies location of grid
sand ZCL files used by NADCON for
grid-to-lat/lon conversion.
NTSFILE Z-MAP Plu $ZTARGET/files/ Defines NTS posting
sand ZCL ZNTS.DAT boundary.


Used by
Apps.
ORACLE_HOME OpenWorks UNSET Directory location of Oracle

applications libraries and runtime.
Set to: path/oracle
ORACLE_SID OpenWorks UNSET Oracle system database
applications identifier.
OWHOME OpenWorks $ZTARGET (if not Directory location of
applications externally defined) OpenWorks runtime and
libraries.
Set to: path/OpenWorks
PATH Unix UNSET Unix executable file search
applications path.
PLOTOUT Hardcopy PLOTOUT Sets the file name for
HP-GL hardcopy HP-GL output.
PRINT_ENV Mapping UNSET If set, prints all environment
applications variable values to the screen.
SYMFILE Mapping $ZTARGET/files/ Defines extended symbols.
applications SYMFILE
TMPDIR Various UNSET Directory for temporary files.
If not set, /tmp is used. Not
consistently applied on all
platforms.
VEROUT Hardcopy VEROUT OBSOLETE
VGS
WDFILE Mapping $ZTARGET/files/ Contains device-specific
applications WDFILE information about plotters
and digitizers.
WORKGROUP Z-MAP Plu UNSET Directory path files
s Z-MAP Plus needs to run,
such as LASPRM.ZCL and
POSMEM.
WRITE_GEO_NAM Z-MAP Plu UNSET (NO) Controls wether the surface
E s and name should be included as a
Pointset z-field on files copied from
Builder the database to MFDs, and
appends the GEO_NAME to
the field name.
ZAUTORAISE Z-MAP Plu UNSET (NO) OBSOLETE
s


Used by
Apps.
ZBACKSTORE Z-MAP Plu UNSET (NO) Controls whether drawing is

s performed to offscreen
pixmap, making redraws on
window exposure faster. The
trade-off is slower full
displays.
ZIGS_ICON Z-MAP Plu UNSET (NO) If set, iconifies the display
s area if it is separate from
main window at startup.
ZTARGET Mapping Directory where sh/ Location of mapping
applications ZMAPPlus is found, products installation.
usually $OWHOME/
ZMAPPlus
ZMAPHOME OpenWorks $OWHOME/ Location of mapping
applications ZMAPPlus products installation.
ZYCOLOR Mapping $ZTARGET/files/ Defines default color values.
applications ZYCOLOR
Z_COLORMAP_ Z-MAP Plu OpenWorks (Default Controls color handling.
CHOICE s value)
Private, Screen
ZCORCGM1 Hardcopy ZCORCGM1 Sets the file name for
CGM hardcopy CGM output.

Appendix B.
Z-MAP Plus Graphics Environment
Introduction
The section Configuring Hardcopy starting on page 49 has
step-by-step instructions for setting up a hardcopy environment. This
appendix provides additional background you may need to configure
the plotter for hardcopy with the Z-MAP Plus family of products.
This appendix describes the Z-MAP Plus graphics environment in
general and hardcopy support in particular. Major topics include:
ZIGS The history and purpose of the Z-MAP Interactive
Graphics Subsystem (ZIGS), as well as Z-MAP Graphics Files
(ZGFs).
Device Support and Workstation Description File How the
WDFILE makes it possible for workstations, digitizers, plotters,
and plotter driver languages to work with Z-MAP Plus and
Hardcopy.
Hardcopy Plotting Options for plotting with CGM and HP-GL
metafiles.ZIGS
This section introduces the history of ZIGS, and provides basic
information about the ZIGS graphics subsystem.
Applications That Use ZIGS

Most of the products in a Z-MAP Plus system use ZIGS (the Z-MAP
Interactive Graphics system) for their graphics applications.
The following programs use ZIGS:
Z-MAP Plus
Hardcopy
ZCL
ZGF import/export
and the obsolete programs Z-MAP, B-MAP, Z-EDIT, STRATVIEW,
TRILAT, Z-CAP, ZDGN, Z3D-FENCE, Z3D-BLOCK and
Z3D-SURFACE.
R2003.12.0 Appendix B. Z-MAP Plus Graphics Environment 95

What ZIGS Is
ZIGS is the graphics subsystem that supports the Z-MAP Plus
products. ZIGS has the following characteristics:
Handles interactive devices (terminals), input devices (digitizers),
and output devices (plotters).
Supports many interactive device interfaces, and is now mostly
used for the X Windows system.
Can produce output to plotters via CGM or HP-GL
Is proprietary. It is used only in Landmarks products.
Maintains Z-MAP Graphics Files (ZGFs), which are described
below.
Occupies a diminishing role, since it is being superseded by newer
technology.
Advantages of ZIGS
ZIGS
supports over 300 devices (e.g. Tektronix terminals, Summagraphics digitizers,
Houston Instruments pen plotters, X-terminals, etc.).
supports a wide variety of application data in addition to graphics primitives,
such as historical information for Z-MAP Plus data editing, process history,
and parametric information. ZIGS also supports Application Data Records for
special purposes.
allows simple CAD-like editing of primitives.
has an extended symbol set with over 870 symbols.
comprehends map scale and projection parameters.
ZIGS and ZGFs

A ZGF, or Z-MAP Graphics File, is a disk file that contains one or
more pictures or maps stored in a proprietary binary format. Each
picture contains groups of picture elements known as Logical
Graphics Blocks (LGBs) or segments. There are over 80 different
LGB types, including contours, text, posted control points, colorfilled
polygons, log annotation, and rock type annotation. Each LGB may
contain any number of graphics primitives, such as lines, text,
polygons, and markers.
Each picture on a ZGF has its own color table stored with it. The color
table has 256 entries, each defined by an RGB triple. The color table
may be different from one picture to the next. Each graphics primitive
references an entry in the color table.

Device Support
Device support is provided for digitizers, workstations, and plotters, as
well as for metafiles that are classified as devices. The Workstation
Description File (WDFILE) is the vehicle which allows Z-MAP Plus,
Hardcopy, and Hardcopy Batch to work with these many different
devices. The WDFILE provides the link between the Z-MAP Plus
family of products and the manufactured input/output device.
This section describes support for the major device types and the role
of the WDFILE in providing this support.
Z-MAP Plus and Hardcopy provide support for workstations, plotters,
and CGM and HP-GL metafiles.
Workstation Support
Many applications require the X Windows system, if you use a Solaris
system. These applications cannot make use of ZIGSs ability to drive
other types of displays.
Plotter Support
Plotter support is described in the next topic, Hardcopy Plotting on
page 99, and in Configuring Hardcopy on page 49.

WDFILES
To work correctly with each device, ZIGS must know some basic
information about the device, such as its size, internal resolution,
whether it supports color (and if so, how many colors), and the type of
device it is (plotter, terminal, etc.). ZIGS gets this information from a
WDFILE.
A WDFILE is an ASCII disk file containing descriptions of each
device that the program will interact with. CGM and HP-GL metafiles
are considered devices and have their own WDFILE entries.
A WDFILE is included with each installation tape we send out, and the
current version contains entries for these devices:
The X Windows system
Versatec 3444 plotter
Versatec 3236 plotter
Calcomp 48x36 series 9100 digitizer
Summagraphics Microgrid 36x48 digitizer
Tektronix 4957 digitizer
Geoquest GTCO digitizer
HP-GL
CGM
You can add device descriptions to the WDFILE or change it by using
the format guidelines in Workstation Description File (WDFILE) on
page 67.

Hardcopy Plotting
There are three basic ways to use the software in the Z-MAP Plus
product system to make a hardcopy plot.
1. The Hardcopy program You can run the interactive program
Hardcopy, which will plot the picture to a CGM or HP-GL file.
2. Z-MAP Plus/Hardcopy Batch You can make a plot by
following these steps:
a. In the Plot a Picture (Other) utility, specify the ZGF,
picture, and picture elements you wish to plot and the device
you want to plot to.
b. When you exit Z-MAP Plus, you will be asked if you wish to
run Hardcopy Batch, the batch version of Hardcopy. If so, it
will read the parameter file that the Plot a Picture (Other)
utility made and will send the picture to the specified device.
3. Z-MAP Plus Plot a Picture (CGM)

You can plot CGMs directly.
Pictures get from Hardcopy to the plotter by Plotting to a metafile,
then to a plotter. This is described in Plotting with HP-GL and
CGM Metafiles on page 100.

Plotting with HP-GL and CGM Metafiles

Hardcopy can output a picture to a CGM or HP-GL file.
HP-GL
An HP-GL file contains one or more pictures written in the
Hewlett-Packard Graphics Language. This is a proprietary format that
HP plotters (and many non-HP graphics devices) understand.
We also support HP-GL/2, which is a superset of HP-GL, providing
extended functionality and support for raster plotters.
HP-GL files and their relationship to our programs are discussed in
detail in HP-GL Drivers on page 54 of this guide.
CGMs
A CGM, or Computer Graphics Metafile, is a standard way of
describing a picture in a binary file format. It is a nonproprietary,
international (ANSI and ISO) standard. CGM+ is a superset of CGM
that provides support for seismic trace extensions.
Rasterizing and Quality Assurance Software

This section summarizes the uses you can make of CGMs with Zeh,
Larson, and Metacheck software.
Zeh Graphics Software

Zeh has a program that will rasterize a CGM into a Versatec raster
format. This raster file can then be sent directly to a Versatec plotter.
Since the CGM is a popular format for picture storage, and since
Versatec does not support CGM, many of our Z-MAP Plus sites use
Zehs rasterizer.

Larson Software
Larson has introduced a product that converts CGMs into Versatec
Color Graphics Language (VCGL), permitting direct transmission to
Versatec plotters for rasterization and plotting. This product,
INTERPRETERcgm, can be used with any of the Versatec rasterizers
that support RPM VCGL. For more information, see Versatec
Support on page 64.
Larson also makes another CGM product called MOSAICcgm. Unique
in the market at this time, it can be used to montage, edit, and merge
CGMs.
Metacheck
This program, available from a company called Advanced Technology
Center, verifies the validity of a CGM. It will print a summary (at a
user-selectable level of detail) of the CGM.

Hardcopy and CGM

The interactive Hardcopy program can produce output to a CGM.
CGM Precision
The CGM standard allows CGMs to be written many different ways.
In Z-MAP Plus, starting with version 2.0, the Virtual Device
Coordinate (VDC) precision is 16-bit or 24-bit integer (rather than
floating point or 32-bit integer), depending on the size of the picture.
Small pictures are written in 16-bit precision, large pictures in 24-bit
precision. In version 1.4.2 and earlier versions, the precision is always
16-bit.
Colors are written in indexed color (as opposed to direct color).
The scaling mode is metric (versus abstract), and is set to .0635 mm per
VDC (so that there are 400 VDCs per inch) in Z-MAP Plus version 2.0
and later, and .1mm per VDC in earlier versions.
For details, see CGM Drivers on page 61.
It is important to note that the CGMs that we write are completely
portable even though they are in binary format.

Appendix C. Presentation Quality Fonts
Introduction
Presentation quality maps require clear, bold, and attractive lettering.
Z-MAP Plus provides support for plots with filled fonts. In order to
produce Z-MAP Plus hardcopy with filled fonts, however, you must
own a CGM rasterizer. Z-MAP Plus replaces the outline fonts available
through CGM rasterizers with filled fonts.
You Can Replace a Maximum of Four Fonts

You can replace up to four fonts by using one font-mapping configuration file.
The work flow below depicts the major steps in the font replacement
process:
Work Flow for Creating Replacement Fonts
Create a font-mapping configuration file using an ASCII text editor.
Turn on font replacement by setting the FONT_MAP environment

variable to point to your font instructions (font mapping configuration)
Make a CGM file using Z-MAP Plus File Scaled Plot Plot a Picture
(CGM) or the CGM File ZCL process.
The CGM contains filled font instructions.
Send the CGM file to the plotter/rasterizer.

The output plot contains the new fonts
Turn off font replacement with the unsetenv FONT_MAP

command.
R2003.12.0 Appendix C. Presentation Quality Fonts 103

Filled Font Support

The initial plan to support filled fonts in Z-MAP Plus is to use the
ability of CGM (Computer Graphics Metafile) to record font names
and text metrics. The plotter device, such as Zeh (or some other CGM
rasterizer) then renders the specified presentation-quality fonts. The
text generated by these fonts is actually rendered only at CGM
rasterization time; that is, you cannot see the results of the font
replacement on the screen.
Z-MAP Plus and ZCL provide only support for filled fonts. The filled
fonts themselves must be purchased separately. If you use the Zeh
CGM rasterizer, you can purchase the Adobe-35 filled fonts from Zeh
or from Landmark as a separate product. There are two kinds of
parameters that control the results of the font replacement process:
CGM text feature parameters
font replacement parameters
CGM Text Feature Parameters

The Zeh CGM rasterizer supports all the CGM features that relate to
text rendering. These parameters can be specified in the CGM file.
CGM Feature Definition
Text Alignment Text alignment allows you to position text in

relation to the coordinates of the picture, such as
center-justified, lower left justified, etc.
Text Font Index The text font index is an index into the Font List.
This index specifies which font to use for
rendering the text.
Font List The font list is a list of the font names to be used
in a particular CGM file.
Text Color Text color determines the color of resulting text
by accessing the CGM color table.

CGM Feature Definition
Restricted Text Restricted Text refers to a maximum bounding

box for the text. The bounding box is set to the
area of the original Z-MAP font and cannot be
changed.
Character Character Orientation consists of vectors
Orientation describing the angle at which each character is to
be positioned.
Font Mapping Configuration Parameters

This section describes the configuration file that enables the font
replacement in terms of its purpose, function, rules and syntax. You
must have a font-mapping configuration file.
The purpose of the font-mapping configuration file is to map Z-MAP
fonts to fonts that are specific to a manufactured plotter device. Consult
the plotter documentation for a list of available fonts.
You control how the Z-MAP Plus fonts are replaced using a
font-mapping configuration file, a flat ASCII file that contains the font
mappings you want to use. You can prepare the font-mapping
configuration file using any standard text editor. Z-MAP Plus reads the
FONT_MAP environment variable which represents the path name of
the configuration file. An example font-mapping configuration file has
been included in the 'Rules and Syntax' section below.

Font Replacement Parameters

The font replacement parameters are specified in the font-mapping
configuration file. There are five fields in each font replacement
statement. While you must have a font-mapping configuration file, you
can default any fields except for the first two, namely, the Z-MAP font
and the name of the replacement font. The values you supply for these
fields must appear in the order shown in the definitions below.
Font Replacement Parameters Font-Mapping Configuration File
Font
Parameter
Replacement Definition Possible Values
Name
Parameter
ZF Z-MAP Z-MAP default fonts are available PLAIN

Font in any of the mapping products SIMPLEX
that have text posting, including COMPLEX
Z-MAP Plus and ZCL. The DUPLEX
default fonts are the ones being ITALIC
replaced.
DSF Device The Device Specific Font is the See names for purchased fonts.
Specific name of a font available for the
Fonts plotter. DSF is the font that
replaces the default Z-MAP font.
HS Character The Character Height Scale A value of 1.0 does not change
Height Factor is a multiple of the height the character height as
Scale of characters in the Z-MAP determined from the Graphics
Factor Graphics File (ZGF) where the File (ZGF). A value of 0.5
picture resides. halves the character height as
compared with that on the ZGF,
while 2.0 doubles the character
height. The default is 1.0.
CEF Character The Character Expansion Factor A value greater than 1.0 causes
Expansio works much like spread ratio in the text to appear wider than
n Factor printing. As compared with the normal; a number less than 1.0
spread ratio for any given height makes the text appear thinner.
built in by the font designer, the The default is to keep the CEF as
CEF can add or subtract from the is: 1.0.
width of the characters or letters.

Font Replacement Parameters Font-Mapping Configuration File
Font
Parameter
Replacement Definition Possible Values
Name
Parameter
CS Character The value for Character Spacing If the value of CS is 0.0, the
Spacing is a fraction of Character Height. characters have the default
Character Spacing is the distance spacing designated by the font
between characters. Character designer. If the value of CS is
spacing specifies the amount of positive, additional space is
additional space inserted between inserted between characters. If
adjacent characters. the value of CS is negative,
adjacent characters overlap
(although the character symbols
themselves may not overlap).
The default value for CS is 0.0.
Rules and Syntax

Field values for the font-mapping configuration file must be in the
following order: ZF, DSF, HS, CEF, and CS. In addition, you must
follow these rules when you build the font-mapping configuration file.
1. Each font mapping configuration file can replace up to four
Z-MAP default fonts.
2. If column 1 of the line contains a # character, the line is a
comment. Blank lines are permitted.
3. You must supply the first two fields in any given font replacement
statement.
4. You can use default values for any other fields, if the default fields
have no intervening fields with values assigned. (For example, you
can use default values for fields 3 through 5, or 4 and 5, or 5 only,
but you cannot use default values for fields 3 and 5 and assign a
value to field 4.)

Font Mapping File Example

This is an example of a font mapping file for Z-MAP Plus:
# This file is used to map Z-MAP fonts to device specific fonts.
DUPLEX, TRIUMVIRATE, 1.0, 1.0, 0.125
COMPLEX, TIMES, 1.25, 0.75
ITALIC, TIMES ITALIC
In this example, the line beginning with DUPLEX substitutes the device
font TRIUMVIRATE for the default Z-MAP DUPLEX font and has
correlated values for fields 1 through 5 as illustrated in the following
table:
Field Names and Values from the Above Example
Field 1 2 3 4 5
Abbreviation ZF DSF HS CEF CS

Example DUPLEX TRIUMVIRATE 1.0 1.0 0.125
Values
The second (COMPLEX) and third (ITALIC) lines of the example file
illustrate ways to use the default field values. The second line that
contains COMPLEX in the first field defaults the value of the fifth field
(character spacing) by leaving it blank. The line with ITALIC in the
first field defaults all fields except the Z-MAP font name and the
replacement font.

Font Replacement Results

Font Replacement parameters affect the size of the fonts that are
printed on rasterized plots. Since every font software acts differently,
Z-MAP Plus offers you size parameters to help create the effect you
want.
Predicting the Size of Replacement Fonts

The CGM Restricted Text Feature makes adjustments to the Font Replacement
Parameters as necessary to prevent the replacement fonts from taking up more
room than the original Z-MAP fonts. While we cannot predict results exactly, the
rules below summarize results we have observed with Zeh rasterizing software.
Here are some options you can use in setting values for the parameters,
along with their expected results:
Font Mapping Parameters and Their Effect on Replacement Fonts
Options for Setting the Value Possible Effect on Replacement

of HS, CS and CEF Fonts
CEF = 2 Causes the replacement font to

take up the same room as the
original font.
Default values for HS, CEF and Causes the replacement font to
CS take up less room than the
original font.
HS and CS set to large number Restricted Text Handling resets
the values to fit in the area of the
original Z-MAP font.

Enabling and Disabling Font Replacement

Once you compose the font-mapping configuration file, you must
provide a pointer to it. You can also turn font replacement off if you
want to resume using the standard Z-MAP fonts supplied with
Z-MAP Plus and ZCL.
Enabling Font Replacement

The environment variable for font replacement is FONT_MAP
combined with the standard Unix setenv command. For example, if
you create a font-mapping configuration file named fontlist.cfg
in your home directory, set the FONT_MAP variable as follows:
setenv FONT_MAP ~/fontlist.cfg
Disabling Font Replacement

You can turn off font replacement and resume using the default Z-MAP
fonts with the unsetenv command to disable the FONT_MAP
environment variable. Do this when you no longer require
presentation-quality plots. To disable FONT_MAP, enter:
unsetenv FONT_MAP

Inst Conf

Uploaded by

Document Informationclick to expand document informationInstConf

Document Informationclick to expand document information

Copyright:

Available Formats

Inst Conf

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Inst Conf

Uploaded by

Copyright:

Available Formats

Z-MAP Plus

Z-MAP Plus Installation and

Part No. 161329 October 2003

Landmark Graphics Corporation

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

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

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

Installation and Configuration

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

R2003.12.0 Contents iii

Installation and Configuration continued

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

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

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

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

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

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

Installation and Configuration: Licensing Process continued

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

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

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

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

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

Configuring HardCopy: Hardcopy and Hardcopy Batch continued

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

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

Configuring HardCopy: Versatec Support continued

Workstation Description File (WDFILE)

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

R2003.12.0 Contents vii

Appendix B. Z-MAP Plus Graphics Environment

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

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

Appendix C. Presentation Quality Fonts

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

R2003.12.0 Contents viii

Overview of This Guide

The installation program load the products on the Applications and

Who Should Read This Guide

How to Use This Guide

ps -eaf | grep lmgrd

2 Who Should Read This Guide: Introduction June 1994

Text you should replace with your own entry appears in