Ss Rel Notes

SeisSpace 2003.12.1.
1
Release Notes
Solaris and Linux
Contents
Release Letter for SeisSpace 2003.12.1.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Patch List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Cluster Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Starting SeisSpace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Enhancements and New Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Fixed Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Known Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Release Notes
Page 1 of 48
January 2006
Landmark
Release Notes
SeisSpace 2003.12.1.1 Release Notes
Page 2 of 48
January 2006
Landmark
Release Letter for SeisSpace 2003.12.1.1

(first functional upgrade to 2003.12.1)
January 2006
SeisSpace 2003.12.1.1 software version
Dear Landmark Customer:
Landmark is pleased to provide the enclosed SeisSpace 2003.12.1.1 software release.
This release is being made generally available for all Linux users and is available on
request for Solaris users who would like to use the Navigator / FlowBuilder. The Solaris
distribution only offers an optional user interface for ProMAX flow, and ProMAX flow
replication work. No SeisSpace or Hybrid jobs are supported on Solaris.
SeisSpace 2003.12.1 was made available when Landmark felt that it was a viable tool to
use to do work. We knew of some limitiations, but wanted to get some idea of what the
level of customer usage would be and what the major issues across the entire user base
would be. While we were waiting for feedback we started addressing some of the issues
that we were fairly certain would be common amongst many of the initial users. This
functional upgrade addresses some of these issues which are predominantly associated
with performance and usablity in the Navigator/Flowbuilder.
For a detailed list of the functional changes you can refer to the Enhancements and Bug
Fixes listed near the back of this document.
As always, feel free to contact the ProMAX/SeisSpace support team with any issues that
you feel need to be addressed.
Sincerely,
Dan Grygier
Program Manager
Seismic Data Processing Applications
Release Notes
Page 3 of 48
January 2006
Landmark
Introduction
This is a combination of the original 2003.12.1 release notes with new information
appended for the 2003.12.1.1 functional upgrade. You can find all of the new text
associated with this upgrade by searching on 2003.12.1.1.
2003.12.1.1
This functional upgrade to SeisSpace is paired with the 2003.12.1.1 ProMAX functional
upgrade. Some components will not work as expected if you run this version of SeisSpace
with the original 2003.12.1 ProMAX release.
When we send out an upgrade to ProMAX we usually send out a tar file with a series of
menus, documentation files, executables, and libraries that are just inserted into an
existing ProMAX installation. For SeisSpace we are making this upgrade available as a
complete new installation. This is because SeisSpace is delivered as a combination of
individual files and some jar files that are combinations of several files. It is a lot safer for
us to repackage the entire jar files instead of trying to patch a jar file in your existing
installation.
To install this upgrade to SeisSpace you should:
Stop your existing work and site managers, clients, netdir admins and make sure all
FFDB managers are also killed.
Back up your current installation directories.
Install this upgrade in the same place as your existing 2003.12.1 installation.
Restart the managers.
Restart the clients and the FFDB managers.
If you want to run two versions simultaneously then you should
Make a new logs directory.
Copy the netdir.xml file from the 2003.12.1 logs directory into the 2003.12.1.1 logs
directory.
Install this version in a separate location from the original 2003.12.1.
set up a new set of manager start scripts to point to the 2003.12.1.1 directory and the
new log directory.
Start a second set of managers on a different port.
Release Notes
Page 4 of 48
January 2006
Landmark
DO NOT attempt to have two sitemanagers running on two different ports accessing the
same netdir.xml file.
There is a comment in the Limitations section from the original release notes that
discusses a recommendation to put Hybrid and Pure SeisSpace flows in the flows list of
a SeisSpace project. After further consideration, the current recommendation is to put all
flows and Tables in the ProMAX project and only put SeisSpace datasets in the
SeisSpace projects.
Overview
These Release Notes provide the necessary information to correctly install and configure
SeisSpace on Solaris and Linux machines. These notes also contain operating system
requirements and descriptions of required third party software, as well as information for
setting up parallel configurations, network dependencies and tested hardware
configurations.
See Enhancements and New Functionality on page 43 and Fixed Problems on
page 45 for a description of the changes associated with this release.
SeisSpace and ProMAX are Landmarks seismic data processing applications. ProMAX
was originally designed for single workstation, small scale, 2D land data processing QC
applications. Over the years ProMAX has grown to be a full featured 2D, 3D, 4D, land,
marine and VSP data processing package. However, ProMAX does not parallelize
efficiently over a large number of distributed computers.
SeisSpace was originally designed for multiple CPUs and multiple workstations, or cluster
computing environments, for large scale, 3D marine data processing applications. There
are many land 3D applications as well, but SeisSpace does not support surface consistent
processes, such as refraction or residual statics.
SeisSpace is a major subsystem of the processing portfolio. ProMAX is the main system
with subsystems of General Processing Tools, The User Interface/Flow Builder, Tape
Input/Output, Queuing, Plotting, ProMANAGER, and its Development kit. SeisSpace adds
a new Navigator/Flow Builder/Flow Replicator User interface and a new processing
executive which runs in a different environment than that of the ProMAX executive.
This version of SeisSpace is an optional addition integrated with ProMAX. It features 3D
Prestack Time Migration and introduces the SeisSpace Navigator/Flow Builder that can
be used for all of your processing work in one consolidated user interface instead of three.
You can use the SeisSpace user interface to build and manage all ProMAX flows, all
SeisSpace flows and the flow replication previously handled by ProManager.
Release Notes
Page 5 of 48
January 2006
Landmark
Linux vs. Solaris

The fundamental difference between the Linux and Solaris releases is that SeisSpace
specific flows are not supported on Solaris. The Solaris release only offers a consolidated
Navigator / Flow Builder / Flow Replicator for ProMAX work. The Linux release
additionally offers a SeisSpace Prestack Time Migration workflow and the ability to run
hybrid jobs running in parallel over many nodes of a cluster.
Hybrid Flows - Combining SeisSpace and ProMAX processes

Hybrid flows combine the parallel input of SeisSpace with a separate instance of ProMAX
running on each of the selected nodes.
This Hybrid flow runs as if you were physically running a separate ProMAX job on each
node. Hybrid flows allow you to distribute the work required to process a data volume over
several nodes in parallel with each node receiving only a subset of the input traces. The
advantage of hybrid flows is that you can read and write to a single SeisSpace data file
while the job is distributed over a number of nodes taking advantage of the parallel input
and output of the SeisSpace infrastructure. (This parallel I/O is only available when
reading and writing SeisSpace datasets.)
Note: The hybrid flows are limited to running ProMAX processes in between SeisSpace
Input and Output modules. Hybrid flows are also restricted to individual trace or
ensemble processes, where the ensemble type is the same as the input ensemble type.
Some processes, such as those that write to the database, are also disabled.
SeisSpace/ProMAX Compatibility
SeisSpace and ProMAX come as a matched set. You must make sure that the correct
versions of ProMAX and SeisSpace are installed and configured to ensure compatibility
between the two systems.
SeisSpace Process List

The SeisSpace-specific processes list is limited to processes that directly support the
Prestack 3D time migration workflow.
When building SeisSpace flows, a subset of the ProMAX processes list is also available
for building hybrid flows. The released list of ProMAX processes in the Hybrid processes
list have been tested to the extent that the output data from a multi node hybrid job and a
single node ProMAX jobs will create comparable stacks.
Release Notes
Page 6 of 48
January 2006
Landmark
ProMAX Process List

The processes lists for ProMAX are divided into ProMAX 2D, 3D, 4D, and VSP. The
storage structure for the processes differs a little from the conventional ProMAX user
interface where there are a lot of duplicate menus in the different product directories. In
SeisSpace, there is just one directory (promax) for all the menus that are common
between the products and only the product specific menus are in the separate product
directories. You can change the processes list by using the Product pull down menu at the
top of the flow builder tab.
When building ProMAX flows, the SeisSpace Input/Output processes list is also available
for building Hybrid flows. If you choose the SeisSpace Input/Output modules, the list of
ProMAX modules will switch to the hybrid processes list.
Data Exchange
SeisSpace and ProMAX use different data storage formats. However, you can access the
alternate formats. For example. SeisSpace Disk Data Input, in SeisSpace, directly reads
ProMAX datasets and SeisSpace Data Input, in ProMAX, directly reads SeisSpace
format data files. At this time, neither system will write to the alternate system data format.
Note: ProMAX datasets are not read in parallel. You may see some distribution of the
data over a series of nodes but in general you should not read ProMAX format data to
drive hybrid flows. You can read ProMAX format data for a SeisSpace 3D PSTM flow if
you have set the switch in the SeisSpace Disk Data Input to have each node read all of
the data.
SeisSpace directly accesses ProMAX tables. There are no SeisSpace-specific tables at
this time. ProMAX is used to pick mutes, and design gates and velocity tables to use in a
SeisSpace 3D Prestack Time Migration workflow.
Limitations
As with any complex, full-featured software product, SeisSpace 2003.12.1 contains some
bugs. However, none were considered serious enough to stop shipment of the release. A
Known Problems list for this release is available online through Landmark's website. This
list is frequently updated. See Known Problems on page 46 in the System Administration
manual for information on downloading this list.
Here are listed some know issues related to day to day use of the SeisSpace Navigator/
Flow Builder:
In a multi-user environment the site and work managers must be owned and running
as root. (This is not an absolute requirement for the sitemanager - but it is highly
Release Notes
Page 7 of 48
January 2006
Landmark
recommended). You can have multiple manager sets running as different users for
different reasons by using different communication port specification in the
PROWESS_PORT environment variable in the startup scripts. Landmark
recommends against having each user run their own set of managers.
After you restart the workmanager(s) for whatever reason, you must also restart the
Flat File Database (FFDB) managers. The recommended approach is to start the
Network View user interface immediately after restarting the launcher after restarting
the workmanager(s) and select any FFDB managers that are running and kill them.
The most obvious symptom of the need to do this is that jobs will not submit. To restart
the FFDB managers select the HOST folder at the top of the tree view and then do a
CTRL-MB1 click on the refresh icon to force a reread of the tree from disk.
As you expand the tree view and select projects, the retrieving data text is the sign
that the FFDB manager for that project is being started.
Testing of the 3D Prestack Time Migration jobs on large clusters has led us to the
recommendation that you not use more than about 30 nodes per job and that you not
attempt to hold more than about 1gb of image space in memory per node.
The Navigator does its best to prevent you from adding the wrong dataset types to the
wrong projects. Make sure that you add ProMAX datasets to the ProMAX project and
SeisSpace datasets to the SeisSpace projects. The Navigator also does its best to
prevent you from selecting the wrong type of data for a menu parameter.
The Flow Builder does its best to prevent you from building "interleaved" hybrid flows
where you have ProMAX and SeisSpace tools interleaved in the flow. These flows
may or may not work. You should restrict hybrid flows to being a single block of
ProMAX processes surrounded only by SeisSpace processes.
The Flow Builder does its best to prevent you from building "inverse-hybrid flows
where you could insert SeisSpace processes inside a flow that is driven by ProMAX
Input and Output modules. These flows might work but are not supported and should
not be built.
You can build and execute pure ProMAX flows under a SeisSpace Project and you can
build pure SeisSpace flows under a ProMAX project. In either case, these jobs should
work. It is recommended, however, that you build all pure ProMAX flows in the
ProMAX project and pure SeisSpace flows in the SeisSpace project. Hybrid flows can
be built in either project, and it may be easier for flow management to build hybrid flows
in the ProMAX project, but be aware that SeisSpace datasets for these flows need to
be managed in the SeisSpace project.
When working on ProMAX flows, the flow builder will allow you to choose datasets
from Areas and Lines in other projects (other PROMAX_DATA_HOMEs). Flows that
are built with data file from other projects or data homes will not work. You can only
choose datasets from other Lines in Areas within the same ProMAX project (or
Release Notes
Page 8 of 48
January 2006
Landmark
DATA_HOME). The ability to directly choose datasets from other lines in the same
area, or other lines in other areas in the same project is only available in Disk Data
Input, Disk Data Insert, Tape Data input, Tape Data Insert, 2D Supergather Formation,
3D Supergather Formation and Splice Datasets. All other modules must select data
from the same line. Tables must also be chosen from the same line.
Although it seems that you should be able to copy objects from one project to another,
these copy operations are not yet supported. You can make a copy of a flow by
opening the flow in the Flow Editor and copying the processes from that flow to the
new flow in a different project with the Copy and Paste or Drag and Drop functions.
There is currently no way to copy datasets from one Data_Home to another in the
Navigator.
When working with a hybrid flow in a SeisSpace project, you must select the tables for
ProMAX processes from the associated ProMAX Line. When working with a hybrid
flow in a ProMAX project, you must select the tables for ProMAX processes from the
same ProMAX Line.
As a general rule, be very careful when selecting datasets from other areas / lines for
ProMAX processes. In the ProMAX user interface, Disk Data Input, Disk Data insert,
Tape Data Input, Tape Data Insert, ESI Disk Data Input, ESI Disk Data Insert,
Supergather formation, 2D Supergather Formation, 3D Supergather Formation and
Splice Datasets allow you to choose input datasets from a different Area/Line. This is
done using the Read data from other lines / surveys option in these menus. In the
SeisSpace flow builder, this option is not necessary, and the parameter is not exposed
because you can directly select the datasets from a list in another line or Area/Line in
the same Data_Home. The ESI input modules do not work this way and can only be
used to read local datasets in the SeisSpace Flow Builder. When you build a flow in
this manner in the ProMAX user interface and edit it in the SeisSpace flow builder, you
will only see the dataset name in the parameter selection without the area and line.
(You can see the area and line for which the data belongs if you hover the mouse on
the dataset name in the menu.) When you save or submit a flow from the SeisSpace
flow builder that has selected input data from another area/line, the packet file copy of
the flow will be saved as appropriate for the ProMAX user interface and the xml files
will be saved as appropriate for the SeisSpace flow builder. When you move back and
forth between the SeisSpace flow builder and the ProMAX flow builder, there may be
incompatibilities in the way that the variables are assigned values from the menu. This
is not a problem so long as the datasets are selected from the same line as the line
containing the flow. The behavior can be summarized as follows:
When a flow is read for the first time from the packet.job file, it is scanned for
processes with parameters FOREIGN=1 and LABEL_AL=Area Line Dataset
triplet. The processes with this combination will be altered such that FOREIGN=0
and LABEL=Area LineFlow triplet and LABEL_AL=INVALID.
When a flow is saved or executed, the packet file version of the flow will be saved
as follows. If the flow has a process with FOREIGN=0 and LABEL=Area Line Flow
Release Notes
Page 9 of 48
January 2006
Landmark
triplet then the packet file will be saved with FOREIGN=1 LABEL_AL=Area Line
Flow triplet and LABEL=INVALID. If the process has FOREIGN=0 and
LABEL=Dataset then the packet file will be saved the same way.
There are many macros that utilize Disk Data Input and Disk Data Insert. Most of these
macros do not expose the Read from other lines / surveys option and will always use
the specified dataset as a local dataset. This can lead to some incompatibilities
between the ProMAX and SeisSpace flow builders. For example:
The SeisSpace flow builder will allow you to choose a dataset from another area/
line in these macros and in most cases will read that dataset, but if you try to run
the packet file from this flow in the ProMAX UI, the flow will not work because most
of these macros never exposed the option and have forced FOREIGN=0 in the
exec data of the menu file. These menus also expect to only have the single
dataset pathname and not a triplet.
Flow replication is not supported for any flows in SeisSpace projects.
Flow replication is not supported for Hybrid flows or SeisSpace flows in a ProMAX
project.
You may see occasional Flat File Database (FFDB) manager failures which are
caused by poor exit behavior of some of the native ProMAX routines. These types of
failures can occur when manipulating database objects such as renaming or deleting
objects when permission errors occur. This may also happen if you do a recursive
permission change on a ProMAX Area or Line when no secondary storage is specified
in the config_file. You will usually get some number of error dialog boxes and the folder
icons in the project will go to a gray color. You can restart the FFDB manager by
clicking on the Hosts folder at the top of the tree view, clicking on the refresh icon, and
then navigating down the project again. If you continuously kill the FFDB manager you
will most likely need to do a recursive permission and/or ownership change down the
problem line or area as the root user.
Flat File Database Manager (FFDB) failures may cause interactive jobs started within
that project to not complete correctly. The job log files will usually be truncated. You
can check by reviewing the job log to see if it has the expected number of ensembles
and traces. Jobs will continue for only a finite amount of time after its FFDB manager
disappears.
There are occasions where you may not be able to open the packet file for a flow that
was built in the SeisSpace flow builder using the ProMAX flow builder. You may also
see NIL processes in a flow. In this case, the packet file is generally corrupted and
must be rebuilt. If you encounter one of these NIL processes in the ProMAX user
interface, you will need to kill that instance of the ProMAX user interface and start
another one. Landmark is continuing to find and fix these problems.
Release Notes
Page 10 of 48
January 2006
Landmark
We are making the SeisSpace project archive and restore programs available, but
note that these processes must be run from a top level SeisSpace project. You cannot
properly restore an archive of a subproject at this time. You can archive an entire
project/subproject hierarchy, but not just a subproject.
We have disabled the ability to copy SeisSpace data and have also disabled the ability
to copy or rename SeisSpace projects or subprojects. There is a fundamental
difference in the way that ProMAX datasets are addressed in the flows compared to
how SeisSpace datasets are addressed. In the interest of trying to prevent the user
from accidentally deleting or overwriting the wrong datasets, we require you to
manage the projects and datasets as completely separate entities. ProMAX datasets
and tables are addressed by names that are local, or internal to the project, where as
SeisSpace datasets are addressed by a fully qualified project/subproject/pathname.
You can still easily copy a SeisSpace dataset from one project to another within the
same SeisSpace Data_Home by running a simple Disk Data Input/Disk Data Output
flow.
There are a few modules where we have had to update the ProMAX LISP menus in
order to make them work in the SeisSpace flow builder. These menus(processes) are:
cgmplot_socket.menu (Create CGM+ Plot Files), splc_dset.menu (Splice Datasets),
tapewrite_inc3.menu(Component to all Tape Output menus), seisspace_read.menu
(SeisSpace Data Input), tables.menu (Access Parameter Tables), unisec_build.menu
(Build Unisec Parmfile*), VolumeCompMacro.menu (Volume Comparison Macro*),
shva_edit.menu (Horizon Velocity Analysis), taperead_inc3.menu (Component to all
Tape Input menus), unisec_cgm.menu (UNISEC Create CGM+). You will have to
overlay these processes with the menus from each user interface as you move back
and forth between the UIs
The Navigator allows you to select multiple objects for a common operation, such as
deleting a series of replicated flows or a series of datasets. It has been noted that when
you select several hundred objects to be deleted, the user interface appears to hang
while it is actually deleting the selected objects. We suggest that if you want to perform
such operations, simply start another Navigator to do other work while the first one is
completing the delete operation.
Release Notes
Page 11 of 48
January 2006
Landmark
System Requirements
Hardware Requirements
SeisSpace Server
The SeisSpace Server is designed to run on a Linux cluster. A cluster is a number of PCs,
with a number of processing nodes, and a separate manager node. Landmark
recommends the following hardware:
Server or
Client
Processor Processor
(minimum) (target)
PC - linux
32 bit Intel
Server
512 MHz P3 dual 2.4 GHz 1 GB/CPU

Zeon or
greater. 16
nodes or
greater
PC - linux
64 bit AMD
opteron
Server
dual 1.8 Ghz 1 GB/CPU

AMD opteron
or greater. 16
nodes or
greater
2 GB or
greater /
node
PC - linux
Server
64 bit Intel EMT
dual 1.8 Ghz 1 Gb/CPU

Intel EMTor
greater. 16
nodes or
greater
2 GB or
greater /
node
Platform
Memory
Memory
(minimum) (target)
2 GB /
node
NOTE: Intel Itanium chips are not supported at this time and the software will not run on
these systems.
You need a minimum of 512 Megabytes of memory per CPU and at least 1 Gigabyte
of swap or paging space.
Augment additions to the main memory by expanding the paging space; a Main
Memory: Paging Space ratio of 4:1 is recommended. For very high memory
machines the 4:1 ratio can be relaxed somewhat. Monitor the swap space under
normal load conditions to decide the amount of required swap space. It is critical to
have more swap space available than the amount equal to main memory and this
requirement can vary some from one node to another.
Release Notes
Page 12 of 48
January 2006
Landmark
The Manager node should have at least swap = main memory and a value of 1.5 to 2
times main memory is recommended.
The Login-nodes or nodes where a lot of interactive jobs will be running will require
more swap. On these nodes you should allocate at least 3 times if not 4 times the
amount of main memory as swap space.
The Processing nodes should be setup to have at least 2 times the amount of swap as
main memory but try to go to 3 times if possible.
SeisSpace Client
The SeisSpace Client can run on either a Linux or Solaris platform. Landmark
recommends the following hardware:
Server or
Client
Processor Processor
(minimum) (target)
PC - linux
32 bit Intel
Client
512 MHz P3 2.4 GHz Zeon 256 MB

or greater
1 GB or
greater
PC - linux
64 bit AMD
Client
512 Mhz P3
1.8 Ghz
256 MB
AMD opteron
or greater
1 GB pr
greater
Solaris
Client
167 Mhz
Ultra
Dual 300
512 MB
Mhz Ultra II
1GB
Platform
Memory
Memory
(minimum) (target)
Note: SeisSpace Server is NOT supported on Solaris.

SeisSpace can only be used on Solaris for the purpose of building and executing ProMAX
flows. No SeisSpace or hybrid flows are supported on Solaris. You do need to have a site
and work manager running on Solaris for the Navigator/Flowbuilder to operate.
Operating System Requirements

SeisSpace is built on the Landmark 2003.0 standards which include operating systems
Linux RedHat 7.2 and Solaris 2.8. SeisSpace is not available for Windows, IRIX or AIX.
The tested runtime platforms are RedHat AWS3.0 Update 2, 3 or 4 and Solaris 2.8.
Release Notes
Page 13 of 48
January 2006
Landmark
Linux 32-bit
Landmark recommends installing all packages of RedHat Linux as a custom installation.
We also recommend to set up the system with no firewalls.
Linux Red Hat Version AWS3.0 Update 2 or 3 32-bit with the following packages is
needed for ProMAX and SeisSpace:
pdksh-5.2.14-21
mysql-3.23.58-1
mysql-server-3.23.58.1
perl-DBD-MySQL-2.1021-3
mt-st-0.7-11 (for tape devices)
and for the ProMAX Dev Kit:

gcc3-c++-3.0.1-3
gcc3-3.0.1-3
gcc3-g77-3.0.1-3
There are a variety of kernel versions with various system patches as well. For RedHat
AWS 3.0 the minimum recommended kernel version is:
2.4.21-20.ELsmp #1 SMP Wed Aug 18 20:46:40 EDT 2004 i686 i686 i386 GNU/Linux
Although not officially supported for RedHat 7.3, the recommended minimum kernal
version is:
2.4.18-18.7.xsmp #1 SMP Wed Nov 13 19:01:42 EST 2002 i686
Linux 64-bit
Landmark recommends installing all packages of RedHat Linux as a custom installation.
We also recommend to set up the system with no firewall.
Linux Red Hat Version AWS3.0 Update 2, 3 or 4 64-bit with the following packages is
Release Notes
Page 14 of 48
January 2006
Landmark
needed for ProMAX and SeisSpace:

pdksh-5.2.14-21
php-mysql-4.3.2-14.ent
mysoql-bench-3.23.58-2.3
libdbi-dbd-mysql-0.6.5-5
mysql-devel-3.23.58-2.3
mysql-server-3.23.58-1
mod_auth_mysql-20030510-1.ent
mysql-3.23.58-2.3
perl-DBD-MySQL-2.1021-3
mt-st-0.7-11 (for tape devices)
The ProMAX Development Kit is not supported on 64-bit machines.

There are a variety of kernel versions with various system patches as well. For RedHat
AWS 3.0 the minimum recommended kernel version is:
2.4.21-27.ELsmp #1 SMP Wed Aug 18 20:34:58 EDT 2004 x86_64 x86_64 x86_64 GNU/
Linux
If you do not know the operating system, windowing environment, or the release version
for your installation, enter the following command from a Linux platform:
Operating System
% uname -a
Motif /X11
% grep -i revision /usr/include/X11/IntrinsicP.h
Microsoft Windows
The SeisSpace Windows Client is not supported or distributed.
Solaris
Limited testing was done on Solaris 2.8. SeisSpace is only supported on Solaris for
working with ProMAX flows.
Note: in order to get PBS/Torque queues set up on Solaris you will need to have the gcc
compiler installed. If you do not have the compilers, contact support and they can provide
a tar file that can be used to perform the make install step without the compilers.
Release Notes
Page 15 of 48
January 2006
Landmark
Note: Please remember to pay attention to the Solaris-specific requirements to install and
configure MySQL for the flow replication database. This information is in the Setting Up the
MySQL Database section of the SeisSpace System Administration guide in the online help
system.
Installation Disk Space Requirements

The amount of disk space required for SeisSpace depends on the number of components
selected from the CD. The following table summarizes the disk space requirements when
running the standard CDInstall procedures:
2003.12.1
Release Notes
Linux
Solaris
SeisSpace
239 MB
247 MB
SeisSpace Client
164 MB
183 MB
ProMAX
1231 MB
1241 MB
Page 16 of 48
January 2006
Landmark
Patch List
This release was tested and certified using the patches as listed below. The exact patch
number as shown may not be available from Sun as they continually update version
numbers. Sun recommends installing the latest version of any patch. According to Sun,
patches are downward compatible. The patches are listed by the certified UNIX(R)
platforms and versions.
Solaris 8 (10/00) with OpenGL 1.2.1

109543
OpenGL libraries bug fixes (32-bit)
109544
OpenGL libraries bug fixes (64-bit)
108576
SunOS 5.8: Expert3D IFB Graphics Patch
108604
SunOS 5.8: Elite3D AFB Graphics Patch
108605
Creator 8 FFb Graphics Patch
108652
Motif Patch
108940
Motif Patch
109154
SunOS 5.8: PGX Colormap Patch
We recommend downloading the recommended patch set from the Sun web site and
installing it. This ensures that all patch dependences are handled.
Release Notes
Page 17 of 48
January 2006
Landmark
Cluster Environments
Basic questions to consider for clusters
Installing and configuring SeisSpace on a cluster is a complex process and many issues
are involved in determining the optimal configuration. The following list of questions will
be helpful in discussing your installation with a Landmark representative.
Who is the Manufacturer of the system?
What processor is installed and how many CPUs/node?
How much internal disk does each node have and how are the file systems set up?
Can you see the file systems on any node from any other node with exactly the same
name?
Which Operating System is loaded on the nodes?
How was the O/S loaded? That is, workstation or custom install with which packages
selected?
Was the installation done with installing the Linux firewall?
What type of network is between the nodes?
Is the internal networking of the cluster accomplished via a multiport hub or via a
programmed high speed switch?
Are the processing nodes visible from your desktop or only from the manager node?
Does the manager node have multiple IP addresses?
Do the processing nodes have multiple IP addresses for fibre or copper network
connections?
Which network hardware is enabled: copper or fiber?
Are ssh rsh telnet ftp rlogin enabled from node to node and to and from the
manager as a user or root?
Is a password required to rsh or ssh from node to node as root or a user?
Is automount running? Is it amd, autofs, or something else?
What is the base automount prefix for accessing the automounted disks on other
machines?
Release Notes
Page 18 of 48
January 2006
Landmark
What is the general disk setup, centralized vs. distributed?
Will you use the local disks on the processing nodes for storage? Do you have disk
storage or a file server external to the cluster?
Are home directories common, that is exactly the same disk on each node?
Do all users have the same user id number on all of the nodes?
Is ProMAX installed? Which version? Is there a required patch installed?
Which Queues are set up on the cluster? SeisSpace only communicates with PBS or
Torque.
Is the processing software installed on each node or is it installed on a network

mounted/automounted directory which can be accessed by exactly the same name on
all of the nodes?
How are the nodes named?
Do the nodes have constant IP addresses? DHCP need to be set up so that the nodes
always have the same IP address.
Is NIS/Yellowpages enabled for etc and hosts?
What type of system imaging is available to clone nodes?
Does a command exist to run the same command on all nodes in parallel as root and
a user?
Routing Issues
A special routing problem can occur if a Linux cluster mayor or manager node has two
ethernet interfaces: one for an external address and one for an internal cluster IP address.
If the mayor's hostname corresponds to the external address, then the machine
misidentifies itself to other cluster nodes. Those nodes will try to route through the external
interface.
Quick Fix
You can use the internal address of the mayor node as the external address of the mayor
node.
% route add -net 146.27.172.254 netmask 255.255.255.255 gw 172.16.0.1
Release Notes
Page 19 of 48
January 2006
Landmark
where 172.16.0.1 is the internal IP address of the mayor node and 146.27.172.254 is
the external address of the mayor node.
Better Fix
Set the route on all cluster nodes to use the internal address of the mayor for any unknown
external address:
% route add -net 0.0.0.0 netmask 0.0.0.0 gw 172.16.0.1
This fix makes the previous fix unnecessary.
Adding Routes
Outside machines might not have a route to the cluster nodes. To add a route to a PC
needing a cluster node, set the route to use the external address of the mayor node to all
cluster node addresses:
% route add 172.16.0.0 mask 255.255.0.0 146.27.172.254
where 172.16.0.0 with a mask of 255.255.0.0 specifies the address range of the cluster
nodes and 146.27.172.254 is the external address of the cluster mayor node.
Diagnosing routing problems

To diagnose problems with routing on a cluster, check the following information on the
mayor node and on a worker node. You must have direct routes to all other nodes:
%
%
%
%
route
route -n
netstat -r
netstat -rn
Make sure your nodes IP address is associated with the ethernet interface.
% ifconfig -a
Hardwire the correct association of IP addresses with hostnames. Use the same file for
all nodes, including the mayor.
Release Notes
Page 20 of 48
January 2006
Landmark
% cat /etc/hosts
See how hostnames are looked up:
% cat /etc/nsswitch.conf
% cat /etc/resolv.conf
Use the lookup order hosts: files nis dns.

If you are not using DNS, then /etc/resolv.conf must be empty. If you are using DNS,
then the following lines must be present:
nameserver <ip address of name server>

search domain.com domain2.company.com
Cluster configuration considerations

When you get ready to set up a cluster you need to consider what application components
will be running on which components of the cluster. For a cluster that is meant to primarily
run ProMAX and SeisSpace you can use the following recommendations. For other uses,
you will have to adapt these recommendations appropriately.
The main consideration is to not overload any particular component of the cluster. For
example, it is very easy to overload the Manager node with a variety of cluster
administration daemons as well as a variety of user processes. For a ProMAX and
SeisSpace installation you may want to segregate the work as follows:
You may decide to run the following on the Manager:
the PBS server and scheduler

the MySQL server
the FlexLM license manager
the SeisSpace sitemanager
aar_promax for ProMANAGER flow replication
You may decide to use a couple of the nodes as user "login" nodes to run:
the SeisSpace, ProMAX and ProMANAGER User Interfaces / Flow Builders

a SeisSpace workmanager
Interactive/direct submit ProMAX and SeisSpace jobs
Release Notes
Page 21 of 48
January 2006
Landmark
ProMANAGER server for ProMANAGER flow replication
You should only run the following on the "invisible" cluster nodes:
PBS - mom
SeisSpace workmanager
ProMAX and SeisSpace jobs released from the queue or jobs directed to run on those
nodes.
Additional Considerations
In addition to the above, you will need to ensure that the manager node and the "login"
nodes are set up with multiple IP addresses so that they are visible on both networks. The
internal cluster network and the external user network.
For SeisSpace Host specification, the "login" node will need to be the primary
administrative host. This will make is so that direct submit jobs will run on the "login" node
instead of on the manager.
Running jobs on the manager should generally be avoided so that this node can be
available to do the system management work that it is intended to do.
You want to avoid having a PBS-mom running on the "login" node(s) to prevent jobs from
the queue from running on these nodes. The "login" node should be reserved for
interactive display jobs and small direct submit test jobs.
Release Notes
Page 22 of 48
January 2006
Landmark
Installation
Overview
The software is delivered on CD-ROMs. You can install the applications using the
Landmark CD Release Manager (CDINSTALL).
This install media contains the shell script setup and the necessary tools to extract the
application from the CD and transcribe the application to disk.
Note: For some Linux 64 installations, the xterm included on the CD and called by
CDINSTALL will not run properly. The installation does seem to work fine on 64 bit
machines running RedHat AWS3.0 Update4. If the installation does not complete
successfully, you must copy the files from the CD to disk, and replace copylocation/bin/
Linux/xterm with the one from your operating system (typically found in /usr/bin). The
xterm is used to run the post-installation script so if you do not replace the xterm,
CDINSTALL will report an error. You could also run CDINSTALL from the CD and then
execute the post-install script manually. In this case, execute SeisSpaceInstall in the
$PROWESS_HOME/install directory after setting the PROWESS_HOME environment
variable as the same user which performed the installation.
Note: The software installation starts from a script that prompts for input; you do not need
root privileges.
The CD Release Manager program provides a consistent graphical user interface for
installing SeisSpace and other Landmark applications. 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 installation progress. Do not use the upgrade option as it is not
functional.
The SeisSpace software distribution is on one CD-ROM which includes all necessary files
for installing SeisSpace:
SeisSpace
SeisSpace Client
The installation procedure is generally platform independent. You will need to install both
SeisSpace and SeisSpaceClient on Linux or Solaris and the installation directory
hierarchy can be identical for both platforms.
Using the CDROM Release Manager

Use the following procedure to read the CD and install Landmark applications onto your
file system.
Release Notes
Page 23 of 48
January 2006
Landmark
The following section explains:
How to start the Release Manager (CD Installer) program.

How to select the applications to be installed.
How to select the file systems where the applications are to be installed.
1. Insert the application CD into a CD drive that is visible from the machine where you
wish to run the installer.
2. In a terminal window, change directories to your cdrom drive. For a typical Linux
installation, type the following command:
cd /mnt/cdrom
3. Change directories to the install directory and type the following command:
cd install
./setup
The following message appears:

|------------------------------------------|
|
Landmark Graphics Corporation _ _ _ _|
| Release Manager for R2003.12.1 __|
|------------------------------------------|
Log files are written to CDINSTALL_LOG
CDINSTALL_LOG is set to : /tmp
Is this correct [y]?
Typically /tmp is acceptable and you can enter y and press the enter key. The
installation script will continue with the following prompt:
**************************************************************
*
*
*
If you are not installing an OpenWorks Related Product
*
*
the OWHOME directory only refers to a target directory
*
*
*
**************************************************************
OWHOME must be set. A full path is required.
Please enter path :
Enter the full path to your installation directory. This path is used to determine where
to install the application. For example, if you want to install SeisSpace in a subdirectory
Release Notes
Page 24 of 48
January 2006
Landmark
from /usr/apps, then set OWHOME to /usr/apps and SeisSpace will be installed in /usr/
apps/SeisSpace. Landmark recommends that you install SeisSpace in the same root
directory where ProMAX is installed.
If you want to add the SeisSpace and SeisSpace client directories to the /
automountrprefix/hostname/disk/file-system/apps directory where ProMAX is
installed enter this full path name during your installation. (OWHOME when running
CDInstall). We use the name /apps for brevity.
When installed, you should have a directory structure similar to the following:
.../apps/ProMAX
.../apps/revisions
.../apps/SeisSpace
.../apps/SeisSpaceClient
If the environment variable OWHOME is defined before starting the CD install

procedure, then the question above never appears and the predefined OWHOME
directory path is used as the installation location. The application will be installed in a
directory relative to the installation location. For example, if the installation location is
/usr/apps/OpenWorks, the application is typically installed in /usr/apps/OpenWorks/
application.
4. Watch the Release Manager for the installation location. For example:
OWHOME is set to: /usr/apps/OpenWorks2003.12.1

Is this correct [y]?
The Software Selection window appears along with the Release Manager Release
Release Notes
Page 25 of 48
January 2006
Landmark
Notes window. After reading the release notes choose OK to continue.
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.
Release Notes
Page 26 of 48
January 2006
Landmark
Icons
Start continues with the installation process.

System Info is inactive in this version of the Release Manager.
Release Notes displays a window containing release notes for a selected application.
Display log displays any messages written by the Release Manager.
Exit terminates the installation procedure.
5. Select the applications to install. You must install both SeisSpace and
SeisSpaceClient. When you click on a field in the Install Option column, a popup
menu appears. Select one of the following:
No Action to not install the application. This is the default selection.

Upgrade should not be used for SeisSpace installation - use Install option
Install installs the application to your system. NOTE that the Install option will prompt
you to delete the target directory before installing the new one.
6. Select the filesystem for installation. The Location column shows the default
locations. To change the default location displayed, click on the ... button next to the
location.
The Location Selection Dialog appears:
This window shows all file systems on which your system is mounted and the space available on each. To select a file system, click on it. Available directories on the file system
appear in the Path area.
7. Select the directory for installation. The name of the directory appears in the
Selection field. You can create a directory by typing the name in the Selection field.
Click OK to select the directory and close the window.
Click Cancel to close the window without selecting a directory.
Release Notes
Page 27 of 48
January 2006
Landmark
8. After you have selected the applications and installation locations, click Start. The
following window appears:
9. 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.
10. When the installation process is complete, an information window opens:
Release Notes
Page 28 of 48
January 2006
Landmark
Click OK to close this information window.

11. The Product License Information window appears showing detailed information that
is required to receive your licenses.
Click OK to close this window.

12. Click on Close to close the Installation Status Window.
13. Click on Exit to close the Software Selection window and respond Yes to the final two
dialogs.
14. Part of the CDinstallation includes the running of a post install script. For the
SeisSpace product post installation the .../SeisSpace/etc/sitemgr and workmgr scripts
are edited so that the PROWESS_HOME line is set to the directory path where it was
installed. For the SeisSpaceClient product post installation the .../SeisSpaceClient/
etc/SSclient script is edited so that the PROWESS_HOME line is set to the directory
path where it was installed.
15. Add a logs directory to the.../apps directory and open its permissions:
cd .../apps
mkdir logs
chmod R 777 logs
Release Notes
Page 29 of 48
January 2006
Landmark
The logs directory is used to store the netdir.xml file. This file is the master
configuration file for the SeisSpace installations. Keep it in a directory outside of the
main installation directories to avoid deleting it when you reinstall or update the
installation version later. The site and work managers also write log files to this
directory.
Note: You should also move the ProMAX etc and queues directories outside the
ProMAX installation tree for safe keeping as well.
It is advantageous to put the following directories together under the .../apps directory:
.../apps/ProMAX
.../apps/revisions
.../apps/SeisSpace
.../apps/SeisSpaceClient
.../apps/logs
.../apps/etc
.../apps/queues
.../apps/bin
You can store the startup and maintenance scripts in the../apps/bin directory.
You will need to add the environment variables PROMAX_ETC_HOME and
PROMAX_QUEUES_HOME to the environments that start ProMAX. Also include them in
the ProMAX project environments described in Configuring SeisSpace.
DO NOT PROCEED UNTIL YOU HAVE RECEIVED A VALID LICENSE FILE FROM LANDMARK.
License Manager
This release is licensed under the FLEXlm licensing software (LAM). SeisSpace uses
ProMAX license features for the Navigator/Flowbuilder and for running ProMAX and
SeisSpace jobs. If you have a ProMAX 2003.0 license running against 2003.0 LAM
Release Notes
Page 30 of 48
January 2006
Landmark
license software, then you will not need a new license file and you will not have to reinstall
LAM.
Obtaining a license to run the software

After installing any point product, the following message will prompt you to obtain a
proper licence:
Attention Landmark Customer
Please contact Landmark for your new software licenses. To receive your licenses,
contact the license administration team via email (license@lgc.com), the World Wide
Web (http://www.lgc.com), or phone (The Americas 281-560-1110, and outside
the Americas at 44-1932-832100). Please refer to the LAM 2003.3.3 Release Guide
for instructions on how to retrieve your lmhostid information.
Please have the following information in your email or available when you call:
Company name:_____________________
Location:________________________________
Server lmhostid:_________________ Client
lmhostid(s):____________________________
Server Hostname:__________________
Platform:__________________________________
Model:____________________________ Operating System
Version:__________________
Site#:____________________________
Reference#:_______________________________
Send the license to:
Name:_____________________________
Phone#:________________________________
Send the license via:
email - email address__________________________________________
diskette - shipping address____________________________________
fax - fax number_______________________________________________
This window is for information only. Click on OK to continue.
Activating the LAM Manager

The LAM (or FLEXlm) executables are delivered with ProMAX in the PROMAX_HOME/
sys/bin/flexlm directory. You can start the license server using the lmgrd command as
follows:
Release Notes
Page 31 of 48
January 2006
Landmark
$PROMAX_HOME/sys/bin/flexlm/lmgrd -c licensefile > /apps/logs/

license.log
When you activate LAM, it creates a hidden file on your home directory called .flexlmrc.
This file contains a speed-optimization to help FLEXlm locate the license file and the
license server. You need to remove the file before changing your configuration.
Landmark suggests that you disable the creation of this file by including the following line
in your environment file:
FLEXLM_NO_CKOUT_INSTALL_LIC 1
You will still want to use the variable:

LM_LICENSE_FILE /your/license.dat
Release Notes
Page 32 of 48
January 2006
Landmark
Starting SeisSpace
Overview
This section discusses building startup scripts, starting the managers, starting SeisSpace
and setting up the administrator host. Once the host has been selected, you then
configure your SeisSpace environment. We also discuss the Administrator Tool (this tool
modifies or creates the same information as the SeisSpace wizards), and setting up the
SQL database.
Below is a summary of the steps needed to start and run SeisSpace:
Build (or copy and edit) the startup scripts
Start the sitemanager and workmanager
Start SeisSpace
Add the administrative host
Run the SeisSpace configuration wizards within SeisSpace.
Both Solaris and Linux installations require an operational sitemanager and

workmanager(s). The difference is that workmanagers will be required to be running on
all nodes of the cluster. For Solaris, since there is only one host (one computer), only one
workmanager is required.
All of the system configuration is virtually identical between Solaris and Linux except that
there is no need to set up VFSs, scratch directories or SeisSpace Data Homes on Solaris.
(Since running SeisSpace or Hybrid jobs on Solaris is not supported)
Note: SeisSpace is dependent on ProMAX. You must have a fully-functional ProMAX
installation prior to configuring SeisSpace.
Starting the managers

The target system configuration is such that the site and work managers will start when
the machines boot. There is one sitemanager for the cluster and one workmanager for
each node on the cluster.
To start the configuration procedure, it is advised to begin in a temporary environment as
a non-root administrative user and then reconfigure the production environment later.
Release Notes
Page 33 of 48
January 2006
Landmark
Building startup scripts

To start the managers, you must build the startup scripts (.../apps/bin/ sitemgr and
workmgr) where you will add in some environment variables and then call the production
start up scripts from the installation directory.
DO NOT COPY THE sitemanger and workmanager SCRIPTS FROM YOUR
PROWESS_HOME/port/bin directories as a starting point. These are the production
startup scripts that will probably change from release to release and with patches. Make
new scripts as described below. You can easily make these new scripts by copying the
examples provided in the $PROWESS_HOME/etc directories. These scripts are called .../
SeisSpace/etc/sitemgr, .../SeisSpace/etc/workmgr and .../SeisSpaceClient/etc/SSclient
1. Change directory to the .../apps/bin directory.
2. You will build the scripts: sitemgr, workmgrr, and SSclient in this directory.
3. The example sitemgr script in .../SeisSpace/etc is shown below:
Note: Lines beginning with "#change# indicate variables whose value you will need
to supply. Lines beginning with "#default#" indicate variables that have a default value
that you may want to change. Lines beginning with "#optional#" are optional and do
not have a default value.
#!/bin/ksh
#
#
#
#
This script sets up some environment variables, then calls the

system workmanager script to start and stop a sitemanager for
SeisSpace. There is usually only one sitemanager. Multiple
workmanagers and clients can connect to this sitemanager.
# Usage: sitemgr [start|stop|restart]

# Lines beginning with "#change# indicate variables whose value youll
# need to supply. Lines beginning with "#default#" indicate variables
# that have a default value that you may want to change. Lines beginning
# with "#optional#" are optional and do not have a default value.
#======================================================================
#
#
#
#
Specify where SeisSpace was installed. This should should already

be set to the installation directory you specified to the CD
installer. All jobs on which you want to run jobs will use the
installation specified by this variable.
#change# export PROWESS_HOME=<seisspace_install_path>

#
#
#
#
You can run multiple sitemanagers by using different port numbers.

workmanagers connect to a specific sitemanager by specifying the
hostname and port number of the sitemanager. Use higher numbered
port to avoid conflicts eg. you can run SeisSpace 2003.12.1 on port
Release Notes
Page 34 of 48
January 2006
Landmark
# 5312.
#default# export PROWESS_PORT=5006
# Specify the path to the logs directory. This is where youll find
# log files and the netdir.xml file for the sitemanager.
#default# export PROWESS_LOGDIR=$PROWESS_HOME/../logs
# Execute the system sitemanager script.
$PROWESS_HOME/port/bin/sitemanager $1
Do not change this line!
4. The example workmgr script in .../SeisSpace/etc is shown below:

#!/bin/ksh
#
#
#
#
This script sets up some environment variables, then calls the

system workmanager script to start and stop a workmanager for
SeisSpace. For each host that executes jobs, there is usually
one workmanager.
# Usage: workmgr [start|stop|restart]

#=======================================================================
#
#
#
#
Specify where SeisSpace was installed. This should should already

be set to the installation directory you specified to the CD
installer. All jobs on which you want to run jobs will use the
installation specified by this variable.
#change# export PROWESS_HOME=<seisspace_install_path>

# Because the workmanager may execute ProMAX processes, it needs to
# know where to find the associated ProMAX installation. The ProMAX
# and SeisSpace versions must be compatible.
#change# export PROMAX_HOME=<promax_install_path>
# This is the port of the sitemanager to which you want to connect.
# The sitemanager by default starts on port 5006. See the sitemgr
# script to find out the port number of the sitemanager.
#default# export PROWESS_PORT=5006
Release Notes
Page 35 of 48
January 2006
Landmark
# Declare the hostname of the sitemanager to which you want to

# connect. This is the hostname where you started the sitemanager
# using the startsm script.
#change# export PROWESS_HOST=<hostname>
# Specify the path to the logs directory. This is where youll find
# log files from the workmanager.
#default# export PROWESS_LOGDIR=$PROWESS_HOME/../logs
# Specify the full path to the license file that serves ProMAX license
# features. The workmanager must find a valid license before it can
# start
#change# export LM_LICENSE_FILE=<license.dat>
# If you are working in a full OpenWorks environment, and are having
# trouble connecting to PD, use static PD instead by setting this to NO.
#optional# export PD_USE_SESSION_MGR=NO
# Execute the system workmanager script.
$PROWESS_HOME/port/bin/workmanager $1
Do not change this line!
5. The SSclient script in .../SeisSpaceClient/etc is shown below:

Note: PROWESS_HOME is set to the SeisSpaceClient directory.
#!/bin/ksh
# This script sets up some environment variables, then calls the
# system client script to start the SeisSpace client. The client
# connects to a sitemanager.
# Usage: SSclient
#======================================================================
# Specify where the SeisSpace client was installed. This should
# should already be set to the installation directory you specifed to
# the CD installer. This variable is used internally by this script to
Release Notes
Page 36 of 48
January 2006
Landmark
# determine the location of the system SeisClient.sh script.

#change# PROWESS_HOME=<seisspace_client_install_path>
# Because the client accesses ProMAX data, it needs to know where to
# find the associated ProMAX installation. The ProMAX and SeisSpace
#change# export PROMAX_HOME=<promax_install_path>
# The sitemanager port field in the SeisSpace login dialog box will be
# initialized to this value. It doesnt need to be set. However, its
# convenient to set it if you are always connecting to the same port.
#optional# export PROWESS_PORT=5006
#
#
#
#
The sitemanager hostname field in the SeisSpace login dialog box

will be initialized to this value. It doesnt need to be
set. However, its convenient to set it if you are always connecting
to the same host.
#optional# export PROWESS_HOST=<hostname>

# Specify the full path to the license file that serves ProMAX UI license
# features. The client checks out ProMAX UI license features.
#change# export LM_LICENSE_FILE=<license.dat>
# ProMAGIC uses this variable, if it is set, to automatically populate
# its menus.
#optional# export GEOPROBE_PROJECT_DIR=<geoprobe_project_directory>
# If ProMAX 3dViewer is installed outside of the ProMAX installation,
specify
# where OpenWorks is installed. Or you may use it to specify the location
# of the conf directory for the SeisWorks bridges (eg. SeisWorks Input).
#default# export OWHOME=$PROMAX_HOME/port/OpenWorks
# Specify the location of the OpenWorks conf directory for the
# SeisWorks bridges (eg. SeisWorks Input)
#default# export OW_PMPATH=$OWHOME/conf
# Set this if you plan to access data from a tape catalog set.
# Also use "Admin Tool->ProMAX Data Home" to specify this
# environment variable to a tape job during runtime.
#optional# export PROMAX_TOPCAT_HOME=<tape_catalog_location>
# Execute the system client script
$PROWESS_HOME/SeisClient.sh &
6. Add execute permission to these three files.

Release Notes
Page 37 of 48
January 2006
Landmark
Note: The site and workmanager scripts take an input argument. This argument is
passed to the main $PROWESS_HOME/port/bin/sitemanager and workmanager
scripts. The argument can be start, stop, or restart.
Starting the sitemanager

Landmark recommends to start the sitemanager for the first time as a non-root
administrative user. If you first start the sitemanager as a non-root administrative user,
two initial users are added to the netdir file: the administrative user and another user
called "useradmin". If you first start the sitemanager as root, only the user "useradmin" is
added and you will need to add the non-root administrative user manually.
Start the sitemanager with the sitemanager script:
..../apps/bin/sitemgr start
Text similar to the following appears in the window:

[1] 380
--- Starting Sitemanager with:
PROWESS_HOST=hostname
PROWESS_PORT=5006
PROWESS_HOME=/export/d03/apps/SeisSpace
[ssuser@hostname logs]$ --- Sitemanager started with PGID
saved PGID to /export/d03/apps/logs/
sitemanager_ssuser_hostname_5006.pgid
output logged to /export/d03/apps/logs/
sitemanager_ssuser_hostname_5006.log
380.
If you ls -al on the logs directory, the following appears:

[ssuser@hostname logs]$ ls -al .../apps/logs
total 20
-rw-r--r-- 1 ssuser users 946 Oct 31 21:28 netdir.xml
-rw-r--r-- 1 ssuser users 2579 Oct 31 21:28
sitemanager_ssuser_hostname_5006.log
-rw-r--r-- 1 ssuser users 4 Oct 31 21:28
sitemanager_ssuser_hostname_5006.pgid
The .../apps/logs/netdir.xml file should look similar to the following:

<parset name="lgc.com">
Release Notes
Page 38 of 48
January 2006
Landmark

<parset name="user">
<parset name="useradmin">
<parset name="permissions">
<par name="verifier" type="string">
26cf2045,1c4228b7a7b72799f6fd977c311847f1 </par>
<par name="actions" type="string"> administrator </par>
</parset>
</parset>
<parset name="ssuser">
<parset name="permissions">
<par name="verifier" type="string">
3319e0df,373f16579c6de15082cf59017be5b17 </par>
<par name="actions" type="string"> administrator </par>
</parset>
</parset>
</parset>
parset name="product">
</parset>
<parset name="dbinstance_ecollar">
</parset>
<parset name="cluster">
</parset>
<parset name="host">
</parset>
<parset name="dbobject_ecollar">
</parset>
<parset name="admin">
<par name="p2" type="string"> "1FQA=$9I;&5087-S=V]R9 " </
par>
<par name="p1" type="string"> 1FQA=$9I;&5-86YA9V5R </par>
</parset>
</parset>
The netdir.xml file and the log files will be owned by the non-root administrative user.
Eventually these files will be managed by root and will need to be owned by root with
permissions of rwxr_xr_x. You will change ownership and permissions on the files later in
the configuration procedures.
If you started the sitemanager for the first time as root

Log into SeisSpace as useradmin (with no password) and then add an administrative
user using the User Wizard. This administrative user must be valid users on the system
where the site and workmanagers are running. Make sure you make this user an
administrative user.
Log out
Log in as the administrative user you just created
Go to the Administrator tool to start the system configuration
Release Notes
Page 39 of 48
January 2006
Landmark
In a production environment, the site and workmanagers are started and owned by root
when the system boots, but the administrative user(s) will have permission to update the
netdir.xml configuration file.
Starting the workmanager

Start the workmanager with the workmanager script:
.../apps/bin/workmgr start
Text similar to the following appears in the window:

[ssuser@hostname ssuser]$ --- Starting Workmanager for user
ssuser on host hostname with:
PROWESS_HOST=dangmpro
PROWESS_PORT=5006
PROWESS_HOME=/export/d03/apps/SeisSpace
PROMAX_HOME=/export/d03/apps/PM2333/ProMAX
LM_LICENSE_FILE=2013@ora1
--- Workmanager started with PGID 18541.
saved PGID to /export/d03/apps/logs/
workmanager_ssuser_hostname_hostname_50
06.pgid
output logged to /export/d03/apps/logs/
workmanager_ssuser_hostname_hostname _5006.log
Starting SeisSpace
7. As a non-root, administrative user, start the client by executing the SSclient script.
.../apps/bin/SSclient
The SeisSpace Connection window appears with Host and Port defaulted to the values
set for PROWESS_HOST and PROWESS_PORT in the SSclient startup script. The User
name is set as the current user running the script. (This should be the same user as is
Release Notes
Page 40 of 48
January 2006
Landmark
currently running the sitemanager.)
8. Click login.
The Launcher Bar appears:
This completes the SeisSpace installation and configuration of the basic managers.
You are advised at this time to select Help and navigate to the System Administration
section and complete the System and Data-Home setup.
If you started the sitemanager the first time as root and you start the Client the first time
Release Notes
Page 41 of 48
January 2006
Landmark
as root:
The SeisSpace Connection window appears with Host and Port defaulted to the
values set for PROWESS_HOST and PROWESS_PORT variables in the SSclient
script.
When SeisSpace is first initiated, your username is not registered as a SeisSpace

user. Enter the username, useradmin, and login with no password. (This is the only
time you will use useradmin as a login name since it is not a valid user login name in
the /etc/passwd file.)This will allow you to add users to SeisSpace. See Adding
Users to SeisSpace.
You will be presented with a single icon on the launcher bar that is the admin tool and
this will have only the user wizard available
Add an administrative user, exit and log back in as that user you just added.
Release Notes
Page 42 of 48
January 2006
Landmark
Enhancements and New Functionality

2003.12.1.1 General
All of the updates for 2003.12.1.1 relative to 2003.12.1 are related to usability,
performance and preference settings for the Navigator/Flow Builder
Client startup- The client startup scripts were enhanced to allow you to optionally start
the navigator or job viewer or admin tool or network view without requiring you to log in
to start the launcher bar. The SSclient script was enhanced to add a $* on the last line to
pass arguments to the SeisSpaceClient/SeisClient.sh script that will accept arguments of
-nav, -jobview, -admin, or -netview (or -v for the list of options). If you have a password
you will also need to provide the -pw argument.
Preferences
Local Submit host- A preference was added to the Navigator pane of the preferences
GUI that asks where the local submit host is. There are two choices: Project and Client.
This feature was put in place for the sites that have a cluster with administrative nodes, or
login nodes, and the users have Linux boxes on their desktops that are viable for running
interactive and test jobs. In this case, you can still use the login node as the
administrative host and run the FFDB managers there, but locally submitted jobs can run
on the users Client desktop instead of the login node.
Program for executing command on remote machine - A preference was added
allowing for the use of ssh as an option to rsh to get commands to run on remote
machines. This is typically related to rshing or sshing to the queue server to run the Qsub
command to put jobs into the queue.
Job Submit
Improved the performance of the job submit from about 8 seconds per job to about 1
second per job. This is a significant benefit when youre submitting large numbers of jobs
at one time using the job table in flow replication.
The job submit user interface was simplified somewhat and re-arranged to better handle
the building the #PBS nodes=#:property:ppn=# line in the qsubmit q directives. The slider
bars for number of nodes, number of threads, and progress report interval have been
replaced with simple numeric entries. An option was enabled where you can automatically
choose the property if the property is the same as the queuename.
Also added an option to the Job Submit user interface where the queue directive equals
the queuename for a property.
Release Notes
Page 43 of 48
January 2006
Landmark
Navigator
Name Column- The name column in the table view of the navigator is now painted with
a different color compared to the other columns in the table. This is meant to be a visual
clue that this column is different from the rest and has different functions and options
Type Column- The type column, which is the column that is occupied by either a folder,
or table, or datasets icon can be used to select mutiple/sequential entries in the table by
holding down MB1 on the rows of interest.
Multiple object and project delete- The action of deleting multiple flows, or datasets or
entire lines or entire areas is significantly faster. The user interface now has an additional
level of verification before performing this operation.
Initial list of Areas/Lines- The action of getting the initial list of areas and lines under
areas is significantly faster.
Flow Replication
Mass Job Submit- The action of submitting jobs from the the job table to the queue is
significantly faster. It has been improved from approximately 8 seconds per job to about
1 second per job.
Job Viewer
Deletion from the Queue- The action of deleting jobs that are in the queue from the Job
Viewer is significantly faster
Release Notes
Page 44 of 48
January 2006
Landmark
Fixed Problems
2003.12.1.1
General
Host names with capital letters- There should no longer be a problem queuing up jobs
on host with capital letters in the host name.
Navigator
Job submit stalling flow rep job submit- The action of submitting a job from the flow
editor tab or from the Navigator tab directly from the tree or table listing no longer halts the
batch job submit operation being performed from the job table.
2003.12.1
General
User Interface - There were not a lot of defects in the original user interface, but we made
hundreds of changes and upgrades to it.
VFS directory paths - In the original version of SeisSpace that some sites have been
using for a while, the project directory paths in the vfs directory have had blanks in the
paths. It was felt that this was not the best way to do this. So we changed it so that the
project directory paths are squished. This makes the project directory paths in the project
directory and the project directory paths in the vfs directory consistent. (squished means
that blank spaces and some reserved characters are removed)
There should be no huge backward compatibility issue with this. You can read all
previously existing datasets. You will now see two different directory paths in the vfs
though. The original non-squished path and the new squished paths. Both directories will
be removed from the vfs if you delete the project from the navigator.
Both directories will be archived, but when restored there will only be the squished
directories.
Release Notes
Page 45 of 48
January 2006
Landmark
Known Problems
The Known Problems List is a list of all the significant problems that we know exist at the
time the software was released.
You can click the link below and see all the known problems for SeisSpace.
SeisSpace Known Problems list
You can view the Known Problems for ProMAX by clicking the following link:
ProMAX Known Problems list
Release Notes
Page 46 of 48
January 2006
Landmark
License Acknowledgements
The Open Group
Copyright 1985, 1986, 1988, 1998 The Open Group
Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above
copyright notice appear in all copies and that both that copyright notice and
this permission notice appear in supporting documentation.
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE OPEN GROUP
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
ImageMagick Studio LLC

ImageMagick software provided by ImageMagick Studio LLC. ImageMagick Studio LLC
neither endorses nor recommends SeisSpace or any other Landmark software.
Release Notes
Page 47 of 48
January 2006
Landmark
Landmark/Asia Pacific
11th Floor Menara Tan & Tan
207 Jalan Tun Razak
50400 Kuala Lumpur
Malaysia
Tel: 011-60-3-2164-1121
Fax: 011-60-3-2164-1135
Help Desk: 011-61-8-9481-4488
Email: apsupport@lgc.com
Landmark/EAME
Hill Park South
Springfield Drive
Leatherhead, Surrey GU22 7NL
England
Tel: 011-44-1372 868-600
Fax: 011-44-1372 868-601
Help Desk: 011-44-1372-868-686
Email: eame_helpdesk@lgc.com
Landmark/The Americas
2101 CityWest Blvd., Building 2
Houston, TX 77042-3021
P.O. Box 42806, Houston, TX 77242
U.S.A.
Tel: 713-839-2000
Help Desk: 713-839-2200
Fax: 713-839-2168
Email: support@lgc.com
3DFS, 3D Drill View, 3D Drill View KM, 3DView, 3D Surveillance, Active Field Surveillance, Active Reservoir
Surveillance, ADC, Advanced Data Transfer, ARIES, Asset Development Center, AssetJournal, Asset
Performance, AssetView, Atomic Meshing, Automate, BLITZ, BLITZPAK, CasingSeat, COMPASS,
Contouring Assistant, Corporate Data Archiver, Corporate Data Store, DataManager, DataStar, DBPlot,
DecisionSuite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner, DecisionSpace AssetView,
DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace
Nexus, DecisionSpace PowerGrid, DecisionSpace PowerModel, DecisionSpace PrecisionTarget,
DecisionSpace Reservoir, DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion, DepthTeam,
DepthTeam Explorer, DepthTeam Express, DepthTeam Extreme, DepthTeam Interpreter, Desktop
Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery Asset, Drill-to-the-Earth
Model, Drillability Suite, Drilling Desktop, DrillModel, DrillVision, DSS, Dynamic Reservoir Management,
Dynamic Surveillance System, EarthCube, EDM, eLandmark, Engineers Data Model, The Engineer's
Desktop, Engineers Link, Executive Assistant, ezFault, ezSurface, ezTracker, FG+, FastTrack,
FieldWorks, FZAP!, GeoDataLoad, GeoGraphix (stylized), GeoGraphix Exploration System, GeoLink,
GeoProbe, GeoProbe GF DataServer, GES, GESXplorer, GMAplus, GRIDGENR, Handheld Field Operator,
I2 Enterprise, iDIMS, IsoMap, iWellFile, Landmark, Landmark & Design, Landmark Logo & Design,
Landmark Decision Center, Landscape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep,
Magic Earth, MagicDesk, Make Great Decisions, MathPack, MIMIC, MIMIC+, MIRA, Model Builder,
MyLandmark, Nexus, Object MP, OpenBooks, Open Explorer, OpenJournal, OpenSGM, OpenVision,
OpenWells, OpenWire, OpenWorks, OpenWorks Well File, PAL, Parallel-VIP, PetroBank, PetroWorks,
PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP,
PowerCalculator, PowerExplorer, PowerHub, Power Interpretation, PowerJournal, PowerModel,
PowerView, Presgraf, PRIZM, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect,
ProMAGIC Server, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP,
pSTAx, Query Builder, Quick, Quick+, QUICKDIF, QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP,
Quickwell, Quickwell+, RAVE, RayMap, RayMap+, RTOC, Real Time Asset Management Center, Real
Time Asset Management Centre, Real Time Knowledge Company, Real Time Operations Center, Real Time
Production Surveillance, Real Time Surveillance, Reference Data Manager, Reservoir Framework Builder,
RESev, ResMap, RightTime, RMS, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision,
SeisWell, SeisWorks, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection,
SeisXchange, Sierra, Sierra (design), SigmaView, SimResults, SIVA, SIVA+, smartSECTION, Spatializer,
SpecDecomp, StrataAmp, StrataMap, StrataModel, StrataSim, StratWorks, StressCheck, STRUCT, Surf &
Connect, SynTool, SystemStart for Servers, SystemStart, SystemStart for Clients, SystemStart for Storage,
Tanks & Tubes, TDQ, Team Workspace, TERAS, Total Drilling Performance, TOW/cs, TOW/cs Revenue
Interface, TracPlanner, Trend Form Gridding, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-COMP, VIPCORE, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web
Editor, Well Seismic Fusion, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT,
WELLPLAN, WellXchange, WOW, Xsection, You're in Control. Experience the difference, ZAP!, and Z-MAP
Plus are trademarks, registered trademarks or service marks of Landmark Graphics Corporation.
2006 Landmark Graphics Corporation. All rights reserved.
Release Notes
Page 48 of 48
January 2006

Ss Rel Notes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ss Rel Notes

Uploaded by

Copyright:

Available Formats

SeisSpace 2003.12.1.

SeisSpace 2003.12.1.1 Release Notes

SeisSpace 2003.12.1.1 Release Notes

Release Letter for SeisSpace 2003.12.1.1

SeisSpace 2003.12.1.1 Release Notes

Back up your current installation directories.

Restart the managers.

Restart the clients and the FFDB managers.

If you want to run two versions simultaneously then you should

Make a new logs directory.

Install this version in a separate location from the original 2003.12.1.

Start a second set of managers on a different port.

SeisSpace 2003.12.1.1 Release Notes

SeisSpace 2003.12.1.1 Release Notes

Linux vs. Solaris

Hybrid Flows - Combining SeisSpace and ProMAX processes

SeisSpace Process List

SeisSpace 2003.12.1.1 Release Notes

ProMAX Process List

SeisSpace 2003.12.1.1 Release Notes

SeisSpace 2003.12.1.1 Release Notes

SeisSpace 2003.12.1.1 Release Notes

Flow replication is not supported for any flows in SeisSpace projects.

SeisSpace 2003.12.1.1 Release Notes

SeisSpace 2003.12.1.1 Release Notes

512 MHz P3 dual 2.4 GHz 1 GB/CPU

dual 1.8 Ghz 1 GB/CPU

dual 1.8 Ghz 1 Gb/CPU

SeisSpace 2003.12.1.1 Release Notes

512 MHz P3 2.4 GHz Zeon 256 MB

Note: SeisSpace Server is NOT supported on Solaris.

Operating System Requirements

SeisSpace 2003.12.1.1 Release Notes

and for the ProMAX Dev Kit:

SeisSpace 2003.12.1.1 Release Notes

needed for ProMAX and SeisSpace:

The ProMAX Development Kit is not supported on 64-bit machines.

SeisSpace 2003.12.1.1 Release Notes

Installation Disk Space Requirements

SeisSpace 2003.12.1.1 Release Notes

Solaris 8 (10/00) with OpenGL 1.2.1

OpenGL libraries bug fixes (32-bit)

OpenGL libraries bug fixes (64-bit)

SunOS 5.8: Expert3D IFB Graphics Patch

SunOS 5.8: Elite3D AFB Graphics Patch

Creator 8 FFb Graphics Patch

SunOS 5.8: PGX Colormap Patch

SeisSpace 2003.12.1.1 Release Notes

Who is the Manufacturer of the system?

What processor is installed and how many CPUs/node?

Which Operating System is loaded on the nodes?

Was the installation done with installing the Linux firewall?

What type of network is between the nodes?

Does the manager node have multiple IP addresses?

Which network hardware is enabled: copper or fiber?

Is a password required to rsh or ssh from node to node as root or a user?

Is automount running? Is it amd, autofs, or something else?

SeisSpace 2003.12.1.1 Release Notes

What is the general disk setup, centralized vs. distributed?

Is ProMAX installed? Which version? Is there a required patch installed?

Is the processing software installed on each node or is it installed on a network

How are the nodes named?

Is NIS/Yellowpages enabled for etc and hosts?

What type of system imaging is available to clone nodes?