Promanager.book

Contents1 ProMANAGER User Guide

ProMANAGER User Guide Contents

Configuring ProMANAGER 5➲ ProMANAGER User Guide Contents 1

➲ Introduction 3

➲ Configuring ProMANAGER 4

➲ Configuring aar_promax and the Service Port 5

➲ Setting Up the MySQL Database 9➲ Installing MySQL

➲ Initializing the ProMANAGER database 21➲ Running ProManagerInstall➲ Menubar options for ProManagerInstall tool➲ Running ProMANAGER on Linux Clusters

➲ ProMANAGER User Interface 28

➲ Windows 29

➲ Menubars and Icons 33➲ Navigation Menubar➲ Navigation Icons➲ ProMAX Explorer Menubar➲ ProMAX Explorer Icons➲ Status Window Menubar➲ Status Icons

➲ Using ProMANAGER 44

➲ Getting Started 45➲ Starting ProMANAGER➲ Setting the default connections➲ Setting the server environment➲ Building a Template➲ Substituting Parameters➲ Building and Executing Flows➲ Using Flow chains (optional; does not work on IBM)

➲ Converting 1998.6 MySQL Databases 67

Other Docs Known Problems

Contents2 ProMANAGER User Guide

➲ Troubleshooting 69

➲ Checklist 70➲ Installation and Configuration➲ Starting ProMANAGER

➲ ProMANAGER Service Port Problems 76➲ aar_promax➲ Port conflicts➲ Unsuccessful MySQL Database Connection➲ MySQL database access error

➲ Replicating a ProMAX Flow 79➲ Select substitute parameters

➲ Building Jobs 81➲ Good Build➲ Bad Builds

➲ Miscellaneous 85

➲ Glossary 89

➲ Appendix A: SQL Commands 91

➲ Appendix B: Optional MySQL Database Administration 93

➲ Adding Host and Database Entries 94➲ The MySQLAdmin tool in ProMAX


3 ProMANAGER User Guide


Introduction

ProMANAGER is a flow replication, job submission, andproject management tool designed to work with ProMAX toassist in large scale seismic processing projects.ProMANAGER helps increase productivity by reducing theeffort required to build, submit, and monitor jobs for projectswith hundreds of lines. ProMANAGER reduces errors byeliminating many of the repetitive tasks required to createand submit flows. It also helps you keep data organized byproviding a single location for processing flows and lineparameters.

Flow replication is similar to creating form letters. You builda master flow using standard ProMAX tools. You then enterthe parameters that vary from flow to flow in a spreadsheet.This is similar to changing names and addresses in a formletter. At build time, ProMANAGER clones the master flowand inserts the parameter variations into the appropriatefields.

ProMANAGER submits the flow to any server on the ProMAXnetwork. A JobStatus tool graphically tracks all jobs for alllines in a project and can simultaneously monitor allProMANAGER projects in your processing center. This allowsyou to easily identify lines or projects falling behind scheduleand better plan resource needs.

Organizing large 3D surveys or projects of 2D lines becomeseasier, and results in faster turnaround.

ProMANAGER can be used for selected steps of a project,such as when data management requires a large number ofdiscrete flow executions. There is no requirement that aproject be processed exclusively with ProMANAGER. You canuse ProMANAGER as needed, and run directly from ProMAXfor the less repetitive steps of the processing sequence.


Configuring ProMANAGER

This chapter explains the installation and configuration stepsfor each of the components of ProMANAGER projectmanagement and flow replication with ProMAX.

There are a variety of ways to configure MySQL, and weexplain a limited range of options. Carry out the steps in theorder that they are presented to ensure a successfulinstallation.

Click ProMANAGER 2003.3.3 User Guide to see theprevious version of the ProMANAGER User Guide. 2003.3.3may be a useful reference, particularily if an earlier version ofProMANAGER was installed and configured.

In This Chapter

➲ Configuring aar_promax and the Service Port 5

➲ Setting Up the MySQL Database 9➲ Installing MySQL

➲ Initializing the ProMANAGER database 21➲ Running ProManagerInstall➲ Menubar options for ProManagerInstall tool➲ Running ProMANAGER on Linux Clusters


Configuring aar_promax and the Service Port5 ProMANAGER User Guide

Configuring aar_promax and the Service Port

The ProMANAGER’s service port executes ProMAX jobs. Itmust have:

• a complete ProMAX installation and configuration. SeeInstallation in the ProMAX Release Notes.

• a license to run ProMAX.

• aar_promax and the service port configured correctly.

For more information on aar_promax, see Enabling theAccount/Remote Execution Server. See Troubleshootingfor descriptions of common errors.

Use the following steps to configure your system to runaar_promax and the service port:

UNIX

1. As root user, add two lines to the /etc/inetd.conf file. Theaar_promax line starts the accounting server whenrequested. The ProManagerServer script allows you tocommunicate with the ProMAX service port.

Note: All fields must be tab separated. The \ indicates acontinuing line:

pmgrserver stream tcp nowait root <PROMAX_HOME>\/port/bin/ProManagerServer ProManagerServer

aar_promax/2 stream rpc/tcp wait root <PROMAX_HOME>\/port/bin/aar_script aar_script

Note: If your ProMAX config_file is NOT located in your$PROMAX_HOME/etc directory, you must add thefollowing line to $PROMAX_HOME/port/bin/aar_promaxfile:

export PROMAX_ETC_CONFIG_FILE_HOME=/location/of/config_file

This can be inserted immediately after the first line of thescript.

LINUX

1. As root user, copy $PROMAX_HOME/sys/misc/aar_promax tothe /etc/xinetd.d directory. Confirm, and if needed, edit/etc/xinetd.d/aar_promax, checking that your



$PROMAX_HOME path is specified correctly in the serverand env entries. The following example shows the relevantentries where $PROMAX_HOME is /apps/ProMAX:

server = /apps/ProMAX/sys/bin/aar_promax

env += PROMAX_HOME=/apps/ProMAX

Note: If your ProMAX config_file is NOT located in your$PROMAX_HOME/etc directory, you must add thefollowing entry to the /etc/xinetd.d/aar_promax file:

env += PROMAX_ETC_CONFIG_FILE_HOME=/location/of/config_file

If you use an external etc directory you need to make sureof the following items:

• The your_etc_dir/config_file must be edited so that theaar_log poins to the your_etc_dir/Account file and thisfile has open permissions rwxrwxrwx.

• The your_etc_dir/ProMAX_RMI_log must have open per-missios rwxrwxrwx.

• the /etc/xinetd.d/aar_promax file must have the

env += PROMAX_ETC_HOME=/location/of/etcdir

line added so that aar_promax is reading the correct config_file that ispointing to the Account file here and aar_promax will also write to theProMAX_RMI_log file in this external etc directory

Copy $PROMAX_HOME/sys/misc/pmgrserver to the /etc/xinetd.ddirectory. Confirm, and if needed, edit/etc/xinetd.d/pmgrserver, checking that your$PROMAX_HOME path is specified correctly in the serverand env entries. The following example shows the relevantentries where $PROMAX_HOME is /apps/ProMAX:

server = /apps/ProMAX/port/bin/ProManagerServer

env += PATH=/apps/ProMAX/sys/jre/bin:/bin:/usr/bin

Note: Be careful that you do not have multiple enabledversions of the aar_promax and pmgrserver files in the/etc/xinetd.d directory. You can have multiple files ofdifferent names but you need to make sure that the oldones have been disabled by setting the "disable" variablein the file to "yes." Failure to do so will result in havingmultiple aar_promaxs and pmgrservers running fromdifferent versions of ProMAX simultaneously which willnot work.

The path to ProMAX in both of these scripts must point to



the correct version of ProMAX. Do not try to use existingversions of these files in the /etc/xinetd.d directorywithout editing the PROMAX_HOME paths if this path haschanged with the new installation.

UNIX and Linux

2. Edit $PROMAX_HOME/etc/config_file (or the config_filespecified in your aar_promax script) by removing thecomment “*” from the first column of the following lines:

accounting: taccounting host: <hostname>aar_log: <PROMAX_HOME>/etc/Account

Be sure to update the accounting host entry with thehostname of the machine that will run aar_promaxaccounting daemon. This enables the accountingprocedures used by ProMANAGER.

Some ProMAX installations use numerous config_files thatare identified by the environmental variablePROMAX_ETC_CONFIG_FILE_HOME. The Account filename should be the same for all config_files that are usedwith ProManager, even in a distributed environment. Thisis because aar_promax can only reference a singleAccount file. The Account file needs to be accessibleacross your network. If you wish to maintain multipleinstances of Account files for different parts of youroperation, you must configure aar_promax on a separatehost for each instance. These instances will beindependent of each other.

3. Add the following line to the /etc/services file:pmgrserver 8860/tcp

This must be tab separated.

4. Add the following line to the /etc/rpc file to connect it withthe inetd.conf file:

aar_promax 536876325

This must be tab separated. Confirm that the entry isconsistent with these instructions if there is a previousentry for aar_promax.

5. Reread inetd configuration.

On Linux:service xinetd restart



On Sun:/bin/kill -1 ‘ps -e | grep inetd | cut -c1-6‘

Note: Type the back tic as indicated. The function is to getthe process id number for the inetd process.

On SGI:/etc/killall -HUP inetd

6. Check that pmgrserver can be started through the inetdservice call telnet host port, where port is the pmgrserverentry in the /etc/services file.

For Example:telnet janus 8860

If pmgrserver is configured correctly, you receive amessage like the following:

Trying... <ip address>...

Connected to janus.advance.com.

Escape character is '^]'.

Click the Return key to close the connection.

The pmgrserver is not configured correctly if you receive amessage like the following:

Trying <ip address>...

telnet: Unable to connect to remote host: Connection refused

If you get the above message, carefully review Steps 3through 5, looking for spelling or typographical errors,then do Step 6 again.

7. Execute rpcinfo -p | grep aar to confirm that aar_promax iscorrectly configured. The output should look like:

536876325 2 tcp 1031 aar_promax

Linux: If you do not get the above message, executechkconfig aar_promax on, then try the rpcinfo command again.

8. Confirm configuration of aar_promax with:rpcinfo -t ‘uname -n‘ aar_promax 2

If uname -n does not work, substitute your hostname. Youshould see a response like:

program 536876325 version 2 ready and waiting

The response could indicate “not ready’ or "not available”



instead of “...ready and waiting”. If this happens on aUNIX system, enter refresh -s inetd or kill inetd. If this happenson a Linux system, type service inetd restart as root and retrythe rpcinfo command.

Caution: The inetd process is essential for rlogincapabilities. Killing it makes rlogin inoperable.

If an error is reported instead, check system message filesfor the cause. Normally the system messages are foundunder /var/adm for Unix and /var/log for Linux.

If this still does not work, rebooting the system may benecessary.


Setting Up the MySQL Database10 ProMANAGER User Guide

Setting Up the MySQL Database

ProMANAGER requires that you install and setup a MySQLdatabase. We have included the MySQL files for Solaris andIRIX on the ProMAX installation CD, and they areautomatically copied into your installation directory into the$PROMAX_HOME/sys/bin/MySQL directory. MySQL forLinux is available on the RedHat CDs. We suggest you refer tothe Release Notes for possible updated information.

MySQL uses a master database to control which users fromwhich hosts can connect to which working database. Userdatabases will be added to store the tables used for theProMANAGER data storage.

The data stored in the database are used in building flows,job status and statistics, and environment definitioninformation. This data requires no more security than theyour ordinary ProMAX data. It is the system administrator’schoice regarding what access control is implemented forMySQL. If you wish to use higher levels of security, we referyou to the MySQL documentation found atwww.MySQL.com.

In this document we will describe the simplest configurationwhich provides for general access to the information in thedatabases for all users.

The setup of the working database(s) depends on yourproduction environment. Production environments vary fromsingle machine with a single user to multiple process serverswith multiple users at multiple desktops. However, we onlydescribe the case for one mysql database server for anyconfiguration.

The size of the MySQL database will depend on the amountyou use ProMANAGER. Small installations may needconsiderably less than one gigabyte of disk space. Largeproduction shops may require 5-10 gigabytes or more.Consider your anticipated use of ProMANAGER whendeciding whether to use the default database locations orselecting a larger disk partition for the database. The defaultdatabase locations are called /usr/local/mysql/data forUNIX and /var/lib/mysql for Linux. Check the available



space on those partitions to decide whether you shouldinstall the database in the default location.

If disk space is a concern, the easiest solution is to move theMySQL database directory to a larger partition, and thencreate a link from the default location to the actual databasedirectory location.



Installing MySQL

In this step you will install the MySQL binary files andidentify the location for the MySQL database. There are twosets of intructions: one for UNIX (Solaris and IRIX64) whichbegins below and another for Linux.

UNIX (Solaris and IRIX64)

It is recommended to do this installation as root.

The following compressed files are located in$PROMAX_HOME/sys/bin/MySQL:

• mysql-3.23.44-sgi-irix6.5-mips.tar.Z

• mysql-3.23.44-sun-solaris2.8-sparc.tar.Z

Copy, uncompress, and untar the file compatible with yoursystem into your /usr/local directory, which is the defaultinstallation point for MySQL. For example:

cp $PROMAX_HOME/sys/bin/MySQL/mysqlxx.tar.Z /usr/local/.

cd /usr/local

uncompress mysqlxx.tar.Z

tar -xvf mysql......tar

ln -s mysql..... mysql

cd mysql

chmod +x ./support-files/mysql.server

Edit (using vi or other editor) the script ./support-files/mysql.server to add "--user=root" to line number 107as shown here:

.$bindir/safe_mysqld --datadir=$datadir --pid-file=$pid_file --user=root&

Alternatively to this change, you may choose to add a systemusername called mysql. Refer to the MySQL documentationat www.MySQL.com for details.

Note: The binary MySQL distributions assume /usr/local as theparent directory. If you install under /usr/local, you arefinished with this step and can proceed to "Initializing theMySQL Database". However, if you choose to install MySQLbinary files or database files in a different location, you mustedit the following two scripts to match your chosen locations:

bin/safe_mysqld

support-files/mysql.server



In the bin/safe_mysqld script, after the ELSE statement, edit thefollowing three lines, replacing your MySQL installation pathfor /usr/local (these are line numbers 76-78):

• MY_BASEDIR_VERSION=

• ledir=

• DATADIR=

In the support-files/mysql.server script, alter the following threelines, replacing your MySQL installation path for /usr/local(these are line numbers 24-26):

• basedir=

• datadir=

• pid_file=

Proceed to "Initializing the MySQL Database"

Initializing the MySQL Database

In this section you will create the initial database tables,configure the MySQL daemon to start automatically onsystem boot and create a password for the MySQL root user.

The following steps should be done as the system root user.

1. Initialize the database with the following command (bydefault, this is under the /usr/local/mysql directory):

./scripts/mysql_install_db

This will return a number of messages as shown below:

mysqlserver xxx# ./scripts/mysql_install_dbPreparing db tablePreparing host tablePreparing user tablePreparing func tablePreparing tables_priv tablePreparing columns_priv tableInstalling all prepared tablesdate time ./bin/mysqld: Shutdown Complete

To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL rootUSER !This is done with:



./bin/mysqladmin -u root -p password ’new-password’

./bin/mysqladmin -u root -h mysqlserver.domain.com -p password’new-password’See the manual for more instructions.

You can start the MySQL daemon with:cd . ; ./bin/safe_mysqld &

You can test the MySQL daemon with the benchmarks in the ’sql-bench’ directory:cd sql-bench ; run-all-tests

Please report any problems with the ./bin/mysqlbug script!

The latest information about MySQL is available on the web athttp://www.mysql.comSupport MySQL by buying support/licenses athttps://order.mysql.com

2. Start the MySQL server daemon with the followingcommand (by default, this is under the /usr/local/mysqldirectory):

./support-files/mysql.server start

You may need to hit Enter to get the command promptback.

3. To start MySQL when your workstation boots:

Copy support-files/mysql.server into the /etc/init.d directory. In the/etc/rc2.d directory create the following link

ln -s ../init.d/mysql.server S96mysql

In the /etc/rc0.d directory create the following link:ln -s ../init.d/mysql.server K05mysql

4. cd to the mysql/bin directory, /usr/local/mysql/bin forUNIX if you are using the default locations

5. Set a MySQL root password using the following command:./mysqladmin -u root password <new password>

Note: This is the root user of MySQL. Do not use confusethis with the system root user. You are strongly advised touse different passwords for MySQL root and system root.

For example:./mysqladmin -u root password rootpw

This has worked if no message is returned.



On SGI machines repeat the previous command with theaddition of the -h mysqlserver flag: Skip this line for SUN.

(replace the "mysqlserver" with your mysql serverhostname)

./mysqladmin -u root -h mysqlserver password rootpw

6. Add the root password for the hostname entry in the usertable. Add a database access user using the "grant"command and create a database for use by ProManager.

At the command prompt type the following command toconnect to the database

./mysql -u root -p<password>

Note there is no space between the -p and the password.

For example:[root@mysqlserver bin]# mysql -u root -prootpwWelcome to the MySQL monitor. Commands end with ; or \gYour MySQL connection id is x to server version: 3.23.44Type ’help;’ or ’\h’ for help. Type ’\c’ to clear the buffer.

mysql>

(type the following commands in as a single line andreplace the "mysqlserver" with your mysql serverhostname)

On SUN machines enter following line. Skip this line forSGI

mysql> set password for root@mysqlserver=PASSWORD(’rootpw’);

Query OK, 0 rows affected (0.00 sec)

Add the user access privileges using the grant command:The first two lines set up access from the local machineand the third one using the "%" wildcard set up accessfrom other machines.

mysql> GRANT ALL PRIVILEGES ON *.* TO dbuser@mysqlserverIDENTIFIED BY ’dbuserpw’ WITH GRANT OPTION;

mysql> GRANT ALL PRIVILEGES ON *.* [email protected] IDENTIFIED BY ’dbuserpw’WITH GRANT OPTION;

mysql> GRANT ALL PRIVILEGES ON *.* TO dbuser@"%"IDENTIFIED BY ’dbuserpw’ WITH GRANT OPTION;

If you plan to use the MySQLAdminTool later to enhancethe default permissions then add the following:



mysql> GRANT ALL PRIVILEGES ON *.* [email protected] IDENTIFIED BY ’rootpw’ WITHGRANT OPTION;

All grant commands should show the following response:Query OK, 0 rows affected (0.00 sec)

Add a database for storing the ProMANAGER data.mysql> create database pmgrdb;

Query OK, 1 row affected (0.00 sec)

Exit from the mysql administration session.mysql> quit

Bye

You may want more than one database depending on howyou want to split up your work. Some sites have separatedatabases for each user, other have separate database fordifferent projects. We recommend that at this time youonly add one database. After you complete the next step ofbuilding the data model, populate the database with theexample data and set up the run time environments, theeasiest way to make more databases is to go to thedirectory where the databases are stored and copy thedatabase directories and then restart the mysql server.

See Appendix B: Optional MySQL DatabaseAdministration for additional information and optionssetting up the MySQL database. The appendix will discussthe host and db tables which can be edited using theMySqlAdminTool to set up more complex mysql databaseaccess.

This completes "Setting Up MySQL: UNIX". The next sectionis "Setting Up MySQL: Linux." If you’re working on UNIX(Solaris or IRIX64 ), skip the next section and proceed toInitializing the ProMANAGER database.



Linux

The following "rpm" packages are presumed to be in place forthe implementation of MySQL as described here.

libdbi-dbd-mysql-0.6.5.5

mod_auth_mysql-20030510-1.ent

mysql-3.23.58-1

mysql-bench-3.23.58-1

mysql-devel-3.23.58-1

mysql-server-3.23.58-1

php-mysql-4.3.2-11

Verify whether the necessary packages are already installedby using the following command:

rpm -qa | grep mysql

These package versions are available on the RedHat WS 3.0CD disc3. If they are not installed, get them from your CDs orfrom the internet and install via the standard rpm method.Higher version numbers probably will work.

NOTE: mysql-server-3.23.58-1 is NOT on the RedHat CD set.You must get it from the internet. Use a good search engineand look for:

mysql-server-3.23.58-1.i386.rpm for 32 bit operatingsystems, or

mysql-server-3.23.58-1.x86_64.rpm for 64 bit operatingsystems.

Download the server rpm and then install it with an rpm -icommand.

If you cannot get access to the internet contact support andthey will make the rpm available to you.

If you choose to install MySQL executables somewhere otherthan the default location of /usr/bin, you will need to installfrom a "source distribution" rather than from the "rpm". Youcan find source distribution packages at www.MySQL.comand elsewhere on the internet.

1. Initialize the database with the following command (bydefault, this is under the /usr/bin directory):

./mysql_install_db



This will return a number of messages as shown below:

[root@mysqlserver bin]# ./mysql_install_dbPreparing db tablePreparing host tablePreparing user tablePreparing func tablePreparing tables_priv tablePreparing columns_priv tableInstalling all prepared tablesdate time /usr/libexec/mysqld: Shutdown Complete

To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQLroot USER !This is done with:/usr/bin/mysqladmin -u root password ’new-password’/usr/bin/mysqladmin -u root -h mysqlserver password ’new-password’See the manual for more instructions.

You can start the MySQL daemon with:cd /usr ; /usr/bin/safe_mysqld &

You can test the MySQL daemon with the benchmarks in the ’sql-bench’ directory:cd sql-bench ; run-all-tests

Please report any problems with the /usr/bin/mysqlbug script!

The latest information about MySQL is available on the web athttp://www.mysql.comSupport MySQL by buying support/licenses athttps://order.mysql.com

If you wish to specify the location for the database files(the default location is /var/lib/mysql), run the commandas follows:

./mysql_install_db --ldata=/your/preferred/location

The mysql_install_db script generates new MySQL privilegetables and database entry called "test". This commanddoes not affect other data that might already exist, and itdoes nothing if the privilege tables are already installed.



2. Start the MySQL server daemon with the followingcommand:

service mysqld start

3. Ensure that mysqld will start on boot by setting thefollowing:

chkconfig mysqld on

4. cd to the bin directory, /usr/bin for Linux if you are usingthe default locations

5. Set a MySQL root password using the following command:./mysqladmin -u root password <new password>

Note: This is the root user of MySQL. Do not confuse thiswith the system root user. You are strongly advised to usedifferent passwords for MySQL root and system root.

For example:./mysqladmin -u root password rootpw

This has worked if no message is returned.

6. Add the root password for the hostname entry in the usertable. Add a database access user using the "grant"command and create a database for use by ProManager.

At the command prompt type the following command toconnect to the database

./mysql -u root -p<password>

Note there is no space between the -p and the password.

For example:[root@mysqlserver bin]# mysql -u root -prootpwWelcome to the MySQL monitor. Commands end with ; or \gYour MySQL connection id is x to server version: 3.23.58Type ’help;’ or ’\h’ for help. Type ’\c’ to clear the buffer.

mysql>

(type the following commands in as a single line andreplace the "mysqlserver" with your mysql serverhostname)

mysql> set password for root@mysqlserver=PASSWORD(’rootpw’);

Query OK, 0 rows affected (0.00 sec)

Add the user access privileges using the grant command:

The first two lines set up access from the local machine



and the third one using the "%" wildcard set up accessfrom other machines.

mysql> GRANT ALL PRIVILEGES ON *.* TO dbuser@mysqlserverIDENTIFIED BY ’dbuserpw’ WITH GRANT OPTION;

mysql> GRANT ALL PRIVILEGES ON *.* [email protected] IDENTIFIED BY ’dbuserpw’WITH GRANT OPTION;

mysql> GRANT ALL PRIVILEGES ON *.* TO dbuser@"%"IDENTIFIED BY ’dbuserpw’ WITH GRANT OPTION;

If you plan to use the MySQLAdminTool later to enhancethe default permissions then add the following:

mysql> GRANT ALL PRIVILEGES ON *.* [email protected] IDENTIFIED BY ’rootpw’ WITHGRANT OPTION;

All grant commands should show the following response:Query OK, 0 rows affected (0.00 sec)

Add a database for storing the ProMANAGER data.mysql> create database pmgrdb;

Query OK, 1 row affected (0.00 sec)

Exit from the mysql administration session.mysql> quit

Bye

You may want more than one database depending on howyou want to split up your work. Some sites have separatedatabases for each user, other have separate database fordifferent projects. We recommend that at this time youonly add one database. After you complete the next step ofbuilding the data model, populate the database with theexample data and set up the run time environments, theeasiest way to make more databases is to go to thedirectory where the databases are stored and copy thedatabase directories and then restart the mysql server.

See Appendix B: Optional MySQL DatabaseAdministration for additional information and optionssetting up the MySQL database. The appendix will discussthe host and db tables which can be edited using theMySqlAdminTool to set up more complex mysql databaseaccess.



This completes "Setting Up MySQL: Linux". Proceed toInitializing the ProMANAGER database.


Initializing the ProMANAGER database22 ProMANAGER User Guide

Initializing the ProMANAGER database

ProManagerInstall verifies that the ProMANAGER databasedirectory is accessible, creates the required elements andoptionally inserts example data into the database.

ProManagerInstall also creates a Resources.lax file, whichtypically resides in the user’s home directory. Thisconfiguration file contains database address and accessinformation for retrieving the area/line/template data usedfor flow replication.

Running ProManagerInstall

The following steps initialize a MySQL database and creates aResources.lax file. We assume that the MySQL database isalready installed and started, and the necessary users, hosts,and user specific databases already exist in the MySQLdatabase.

You should do the following steps as an ordinary user (notroot).

1. Set your PROMAX_HOME environmental variable.

2. Start ProManagerInstall by typing:$PROMAX_HOME/port/bin/ProManagerInstall&.

The following window appears:

WarningDelete removes the entire user database. There is no way to recover the database,once deleted. Landmark recommends backing up the database before removing.



3. Enter your hostname and database in db.url, your MySQLusername in db.user, and your MySQL user password indb.passwd. The following is an example of an editedmenu. Note that localhost is used rather than the fullyqualified hostname.

4. Toggle on Verify and click Run to confirm that thedatabase can be accessed. You should get the followingmessages:

Starting database verify

Connection successful

Database verify complete

If the verify does not complete successfully, you will get anerror message. Click Details and use the scroll bar to seethe error messages.

The most common error is when the database directorywas not created in step 8 of the previous section.

5. After verify is successful, toggle on Create and click Runto initialize the table definitions in your database. In thepop-up window, elect Yes to Create database tables. Youshould get the following messages:

Starting database table create...

< numerous lines saying "Creating table ... " >

Create database tables complete

6. Select Insert and click Run to insert an example projectinto your database. Select Yes to Insert sample data intodatabase tables. You should get the following message:

Starting database table insert...

< numerous lines saying "Inserting into table ... " >

Insert database tables complete



7. Select File ➛ Save and enter a filename for Resources.lax.Landmark suggests saving the Resource<database>.lax file inyour home directory. Click Save to create the file.

8. Repeat steps 3 through 7 for all valid user and databasecombinations.

9. Select File ➛ Exit.

Menubar options for ProManagerInstall tool

File

• Open an existing property file.

• Save your specified configuration to a resources.lax file.

• Exit out of ProMANAGER Install.

Toggle Buttons

To use the following options, toggle the buttons at the bottomof the status window and click Run.

• Verify confirms connection properties. A confirmationmessage appears in the window where ProMANAGERwas launched.

• Create initializes empty ProMANAGER database tables.This option does not work if tables already exist.

• Insert populates ProMANAGER database tables in asimple project. This option does not work if tablesalready exist.

• Dump writes all values in the database tables to anASCII file. This is useful for saving an existing project orforwarding a problem database to support.

• Convert converts database tables from a ProManager1998.6 project to an ASCII formatted file compatible withProManager 2003.12. See Converting 1998.6 MySQLDatabases for more information.

• Restore populates database tables from an ASCII filegenerated by Dump or Convert. This option does notwork if tables already exist.

• Delete removes all tables from the database.

Warning: This option deletes your database. You should



make a backup copy. Be sure that you want to deleteyour database!



Running ProMANAGER on Linux Clusters

This section contains general information about runningProMANAGER on Linux clusters. Slight deviations from thesesteps may be necessary on different Linux clusters due tosecurity and configuration issues. If these instructions arenot working for your system, please contact ProMAX Support.

Configuring ProMANAGER on a Linux cluster that uses PBS queues

This configuration allows you to run ProMANAGER on themachine you configured, and have ProMANAGER deliver jobsto your PBS queues for execution on the various nodes of thecluster.

Once ProMANAGER and MySQL are up and running on onenode, you can use the PBS queues to distribute jobs to any ofthe nodes that are included in your PBS configuration. Enterthe same queue names you have in the$PROMAX_ETC_HOME/qconfig file, or if this environmentvariable is not used, $PROMAX_HOME/etc/qconfig, in theEnvironment editor of the ProMANAGER interface. You canthen use the PBS queues to distribute the load to selectednode or group of nodes. The pathnames used in theenvironmental variable designation section must be seen byall the nodes in the PBS queue.

Note: In a rare case, a client had to copy the pmgrserver filefrom the /etc/xinetd.d directory of the node that ProMANAGERwas installed, to the other nodes in the Linux cluster to getProMANAGER jobs to run on the other nodes.

Configuring ProMANAGER to run on any node in the Linux cluster

This configuration allows you to run the ProMANAGERinterface on any node. Job flows that ProMANAGER createscan be sent a PBS for queues to deliver them to anyconfigured node for execution.

1. Get ProMANAGER and MySQL up and running on onenode. This is generally the head node or one of the nodesthat is set up as the log-in node where the users will runtheir ProMAX and ProMANGER user interfaces.

2. You should not need to include the hostnames and fulldomain name of the processing nodes in the mysqldatabase. If you get into a situation where you arerunning ProMANAGER on one of the processing nodes



trying to connect to the mysql instance on the managernode and you cannot connect. They you will need to addin the hostname where they ProMANAGER UI is runningto the user table of the database. See the section onInstalling MySQL earlier in this chapter to use the grantcommand to add the user@host.

3. Check that all pathnames declared in the environmentalvariable designation in the ProMANAGER interface can beseen by all the nodes.

4. Add the following to your config_file to have all clusterprocessor execs report account statistics to theaar_promax running on the master node:

accounting host: machine_to_run_aar

If your master node hostname is supcl1, the line wouldread:

accounting host: supcl1

As root, perform the following steps on the other nodes if youintend the nodes to be directly referenced in theenvironments in ProMANAGER. Typically the processingnodes are "invisible" to the users and you will not need tohave pmgrserver running on them. If you have the managernode as the mysql server and you want to make node01 forexample to be a "host" in ProMANAGER for runninginteractive jobs then you will need a pmgrsever running onnode01

1. Copy the /etc/xinetd.d/pmgrserver files from the nodeProMANAGER is running on to each nodes' /etc/xinetd.ddirectory. Make sure the paths to $PROMAX_HOMEdesignated in the server and env entries can be seen fromall the nodes.

Note: If nis services is running and contains pmgrserver,skip steps 2 and 3.



2. Add pmgrserver to the /etc/services file as you did for the noderunning ProMANAGER. See Service Port for configurationdetails.

3. Run service xinetd.d restart and ensure pmgrserver is up andrunning on each node. See Configuring aar_promax andthe Service Port beginning at step 7 for details.

4. Login as yourself and bring up the ProMANAGER userinterface on any configured node.

• In the Environment Editor, create another environmentby copying over the environment from your first host andrenaming it to your new host. Highlight the hostname inthe Environment editor, click MB3 ➛ copy; MB3 ➛paste. A duplication of you host environment isappended to the end of the Environment list.

• Edit the copied environment, changing the node name tothe name of the new node.

• Rename the ProMANAGER service port to 8860 (underEdit ➛ ProMANAGER service port in the EnvironmentEditor).

• Click on the Pmx icon to check that the ProMAX UserInterface runs under the new environment. If it comesup, and aar_promax and pmgrserver are up and runningfrom your new node, and you should have no problemssubmitting jobs to this node.

Repeat the four bullet points of this step 5 for each node onwhich you wish to run ProMANAGER.

Remember: This step allow you to run the ProMANAGERinterface on a particular node. Typically, you need only oneor at most a few nodes for running ProMANAGER. Jobssubmitted through ProMANAGER can be sent to queues forexecution on any nodes defined to the queue system.



ProMANAGER User Interface

In this chapter, we describe the User Interface, menubar andicon options.

In This Chapter

➲ Windows 6

➲ Menubars and Icons 10

➲ Navigation Menubar

➲ Location Menubar

➲ Navigation Icons

➲ ProMAX Explorer Menubar

➲ Host Menubar

➲ Group Menubar

➲ Environment Menubar

➲ Area Menubar

➲ Line Menubar

➲ Flow Menubar

➲ Dataset Menubar

➲ Parameter Table Menubar

➲ ProMAX Explorer Icons

➲ Status Window Menubar

➲ Status Icons

➲ Status Tabs


Windows29 ProMANAGER User Guide

Windows

The following describes all ProMANAGER windows:

• Navigation window displays project components orga-nized in Area/Line/Flow structure, similar to ProMAX.Areas group similar projects; Lines are master projectdirectories; Templates are the master flows used in rep-lication.

• Work window displays tables, tabs and icons, requestedby commands from the navigation window.

• ProMAX Explorer window manages ProMAX dataobjects across multiple hosts and or

Navigation Window Work Window

Minimized Table

Table Type Tabs



PROMAX_DATA_HOMEs. This tool offers the followingfeatures:

• You can edit any number of selected items at once, suchas deleting a group of flows and datasets.

• You can drag/drop, copy/paste flows and parametertables (not datasets) between PROMAX_DATA_HOMEs.

• You can submit flows, start ProMAX, DBTOOLS, or theparameter table editor from this window.

ProMAX Explorer Window

The Explorer menu works once the Environmentalvariable definition menu is filled out. Click on the nodehandle ( ) to move down successive directories.



• Status window allows you to build, submit. QC, and editflows. Parameter, Template, and Environment menusmust be filled out before you can start building flows.See Building and Executing Flows for more informa-tion.

Status Window

• Parameters window allows you to enter area, line, andsegment based parameters to substitute into templates.See Defining Global Processing Parameters for adescription of how to use this window.

• Template window defines the substitution menu set-tings for a replica. See Building a Template for adescription of how to use this window.

• Relationship window sets up flow chains. Flow chainsdefine how a sequence of flows are executed. Jobs in achain are executed in order unless interrupted by a holdor job failure. See Using Flow Chains for a descriptionof how to use this window.

• Environment window enters the environmental vari-ables and queues that ProManager uses to run ProMAXjobs or service any other requests. See Setting theserver environment for a description of how to use thiswindow.

• Users window contains the userids used to run jobs.This window already contains your userid if youinstalled ProManager or converted an old ProManagerMySQL database to the new MySQL format. If you havenot, add your name using this window’s edit/add option.



You can resize, hide, show, minimize, or close the differentwindows within the Work window. Tabs across the bottom ofthe Work Window organize open tables into logical groupings.


Menubars and Icons33 ProMANAGER User Guide

Menubars and Icons

Navigation Menubar

The main menubar contains three pulldown menus and Help.

File

This selection allows you to create new areas, lines, ortemplates, reload, or exit ProManager.

• Reload refreshes information in the MySQL database.

• New➛ Area, Line, Template, Default flow

• Exit

Edit

The Edit menu allows you to use normal edit functions.

• Copy, Paste, Rename, Delete

Tools

This selection opens the windows for managing the databaseand remote services.

• ProMAX Explorer manages ProMAX data objects acrossmultiple hosts and or PROMAX_DATA_HOMEs.

• Status displays flow, dataset, and table status. In thiswindow you build, submit. QC, and edit the flows. Thisrequires a line level selection in the Navigation tree.

• Parameters define parameters/expressions used forsubstitution during flow building.

• Template maps ProManager parameters/expressionsinto ProMAX parameter fields.

• Relationships defines dataset relationships betweenflows and enables flows chaining.

• Environments defines environmental variables used byservers during service requests.

• Defaults maintains a tree of ProMAX default packet files.Warning: This option is not recommended. See Default-ing Substitute Parameters for more information.



• Users maintains a list of valid ProManager users.

Help

• Help topics launches the help documentation

• About... displays current program version and selectedsystem properties

Location Menubar

This menubar contains bookmarks pulldown menu, locationtextfield, and a file selector button.

Bookmarks

This selection manages database connection resources fordifferent ProManager projects.

• Home returns locator to home location

• Set home sets the current location as home.

• Clear history removes all items from history buffer.

• Add bookmark adds the current location to the book-mark list.

• Remove bookmarks... removes items from bookmarklist.

Location Textfield

This textfield is used for entering the pathname of theProManager database connection resource file, that is theResources.lax file. This file can be a local or on a web server.Up to 20 previous locations are saved in the history buffer.

File Selector Button

This button launches a file selector dialog. The selected fileaddress is placed in the Location textfield.

Navigation Icons

These icons can be used to open the corresponding windowwithin the Work window.

• Explorer displays the ProMAX Explorer window.



• Job Status displays the Job Status window.

• Replication parameters displays the Database Parame-ter window.

• Template Table displays the Template window.

• Relationship modeler defines data relationshipsbetween templates. This is used for creating flow chains.

• Environment parameters displays environment vari-ables used by servers.

ProMAX Explorer Menubar

This menubar displays different functions depending on theProMAX data type that you select. They data types are host,group, environment, area, line, flow, or parameter table.

Host Menubar

Host

• Reset refreshes all the information under a particularhost. For example, if you change your environmentalvariables under a particular host, use this option to seethe data with these new environmental variable settings.

View

• Refresh refreshes information from the highlightedobject down. Highlight a line, select View ➛ Refresh toredisplay the information about that line; showing anynew changes.

Group Menubar

• Refresh refreshes information from the group directorydown.



Environment Menubar

Environment

• ProMAX brings up ProMAX; using the environmentalvariables selected in the Explorer menu.

• Disk Use specifies the available amount of OPF, TRC,and scratch partitions.

View

• Refresh refreshes the information under the highlighteddirectory.

Area Menubar

Area

• ProMAX brings up ProMAX; displaying the lines in thehighlighted area.


Edit

• Rename the highlighted area.

• Delete the highlighted area.

View

• Refresh refreshes the information from the area leveldown.

Line Menubar

Line

• ProMAX brings up ProMAX; displaying the flows in thehighlighted line.

• DBTools brings up DBTools from the highlighted line.


Edit

• Rename the highlighted line.



• Delete the highlighted line.

View

• Refresh: Refreshes the information recursively from theline level down.

Flow Menubar

Flow

• ProMAX brings up ProMAX; displaying the highlightedflow.

• ShowFile displays job.output from the highlighted flow.

• DBTools brings up DBTools from the line of the high-lighted flow.


• Resubmit the highlighted flow.

Edit

• Copy the highlighted flow.

• Paste the highlighted flow.

• Rename the highlighted flow.

• Delete the highlighted flow.

Dataset Menubar

Data

• ProMAX brings up ProMAX; displaying the flows fromthe line of the highlighted dataset.

• DBTools brings up DBTools from the line of the high-lighted dataset.

• Dataset info displays expanded dataset information.(The same information you get by clicking MB2 on adataset in the ProMAX User Interface.)




Edit

• Rename the highlighted dataset.

• Delete the highlighted dataset.

Parameter Table Menubar

Table

• Spreadsheet displays the parameter table informationin a ProMAX spreadsheet.

• ProMAX brings up ProMAX; displaying the flows fromthe line of the highlighted parameter table.

• DBTools brings up DBTools from the line of the high-lighted parameter table.


Edit

• Copy the highlighted table.

• Paste the highlighted table.

• Rename the highlighted table.

• Delete the highlighted table.

ProMAX Explorer Icons

• Disk Usage displays a disk use summary.

• Job.output displays the job.output file of the high-lighted flow.

• ProMAX UI display and/or edit flows in ProMAX.

• DBTools displays the ProMAX line database of the linecontaining the highlighted item.

• Table editor launches the ProMAX spreadsheet editorfor tables after you highlight a parameter table.



• Resubmit starts the highlighted flow.

Status Window Menubar

Flow

These menus, or a subset of these menus are found in theData and Table tabs as well.

• Reload refreshes the information contained in the mysqldatabase, such as the template and parameter informa-tion for the highlighted flow.

• Open allows you to select the following information todisplay in the Status window:

Status displays the current status of each job. Thedefault is inactive.

Environment displays the host, group, andenvironment information for the most recentlysubmitted cells.

Queue displays the host and queue information for themost recently submitted cells.

Job Control displays the host and job controlinformation in the environment window for the mostrecently submitted cells.

CPU displays the CPU time each job took to execute.

Elapse displays the elapsed time for each job execution.

User displays the current username. ProManager does asystem call at startup to determine the username to useduring the session. It must be registered in theProManager database.

Name displays the flow names once they are built.

PID displays the jobs processing identification number,or PID. The PID is used by ProManager to kill and QCjobs. You can also use the PID to manually kill a job if aProManager kill request should fail.

• Save Layout allows you to click on column headers toreorder them and save them.

• Print allows you to print all information contained in thestatus window to a printer or a file. The font of the col-



umns in the current view of the job status are adjustedto fit in 80 cc width. Select printer or file, enter thename of the printer or file, and select Print.

• Print Preview allows you to preview and print informa-tion. Since the preview picture is normally too small, usethe arrow to increase from 10% to 100%.

Edit

These options change the status of a cell. You can also clickMB3 on a highlighted cell to activate an option.

• Inactive leaves cell alone. This is the default cell status.

• Active builds and submits jobs.

• Build creates and saves flows. If successful, cell statuschanges to Build if not, status changes to Build Bad.

• Build/Submit builds a flow and submit for execution.

• Submit executes a previously built flow.

• Good indicates a cell that ran normally. You can alsomanually set a cell to good.

• Validated designates flows that you checked for correct-ness.

• Bad indicates a flow that did not complete normally. Youcan also manually set a cell to bad.

• Kill terminates an executing job.

• Hold keeps a job from executing until it is released. HoldA checkmark in the left part of the cell indicates holdstatus. This option was created to stop the execution ofjobs that have been chained together. Chaining of jobsunder a specific sequence can be created in the relation-ship menu. See Using Flow Chains for details.

• Release takes the hold status off a job.

• Delete removes a flow, dataset, or table from ProMAX.Warning: Use this option with caution. There is no wayto recover deleted items.

View

With this option, you can control the columns displayed inthe job status window.



To turn off a column containing a template, uncheck thetemplate name in the View tab.

To turn on the column, check the template name in the Viewtab. The column is appended to the right side of the jobstatus window.

Tools

• Showfile displays the job.output listing of the high-lighted cell. Make sure only one cell is highlighted.

• ProMAX brings up ProMAX and displays the highlightedflow.

• DBTools activates the database for the line of the high-lighted flow.

• Summary displays information such as flowname, user,status, CPU time, and process ID for the highlightedflow.

• Disk Usage shows the amount of available disk space inyour OPF, TRC, and scratch directories.

Utility

• QC checks the Account file for the status of the high-lighted cell/cells.

• Interval sets the time interval for automatically check-ing the status of all the flows. The default time interval is30 seconds. You must activate the Auto-refresh option atthe upper right hand side of the status window for thisoption to work.

Status Icons

The following icons are available in the status window whenthe flow tab is highlighted. Only the ProMAX icon is availablewhen the data and table tabs are highlighted.

• Build allows you to create and save flows.

• Submit allows you to create, save, and submit a flow.



• Resubmit allows you to set a build, good, bad, or killcell to resubmit the flow without rebuilding.

• Kill allows you to kill a submit cell.

• QC updates selected cells by explicitly checking theaar_promax log.

• Job.output displays the job.output file.

• ProMAX UI allows you to view and/or edit flows in theProMAX user interface.

• DBTools allows you to view the shared ProMAX linedatabase or the database of the individual replica.

• The Auto-refresh checkbox enables a timer to automati-cally redisplay the current table in the Job Status win-dow. The default interval is 30 seconds; reset thisinterval from the Utility menu.

• The Common ProMAX database checkbox at the bot-tom of the window defines how each Replica is built.Thedefault, checked, uses a single ProMAX Line and data-base for the project.

Replicated flows, input/output datasets, and parametertables exist under the same directory structure as thetemplate flows.

If Common ProMAX database is not checked, then eachreplica is built in its own ProMAX line, under thedesignated Area. All replicated flows, input/outputdatasets, and parameter tables exist within that linedirectory and not in the directory defined for thetemplate flows.



This option is good for managing individual 2D linesfrom a central project or for processing marine 3D sail-lines through pre-DMO flows.

Status Tabs

The data and table tabs contain a similar tool for managingdata items defined in the relationship editor. The status ofthese items is reflected by the status of the parent flow. Youcan manually override these states. Deleting a flow does notautomatically delete associated data items.



Using ProMANAGER

In this chapter, we explain how to get started withProMANAGER. We first describe the User Interface and theninstruct you on how to set up the ProMANAGERenvironment. Once the environment is set, we introduce youto how to use ProMANAGER project management and flowreplication with ProMAX.

In This Chapter

➲ Getting Started 38

➲ Starting ProMANAGER

➲ Setting the default connections

➲ Setting the server environment

➲ Building a Template

➲ Substituting Parameters

➲ Building and Executing Flows

➲ Using Flow chains

➲ Converting 1998.6 MySQL Databases 58


Getting Started45 ProMANAGER User Guide

Getting Started

When you first run ProMANAGER, your ProMANAGER projectwill not appear. You must set the ProManager connectionresources to load projects.

Starting ProMANAGER

UNIX

For all machines, type the following commands:setenv PROMAX_HOME <full path name to 2003 PROMAX_HOME>

set path = (${PROMAX_HOME}/port/bin\${PROMAX_HOME}/sys/bin $path)

$PROMAX_HOME/port/bin/ProManager &

AIX machines also need the following command:setenv LIBPATH /usr/lib:$PROMAX_HOME/sys/lib

ProMANAGER should launch. If this is your first time to runProMANAGER, the Resource.lax will not be defined. Go to thenext section, Setting the default connections.

PC

Use the following steps to start ProMANAGER on a PC. Thisassumes that MySQL is set up on UNIX:

1. Create a ProMANAGER directory on your PC.

2. Copy the Resources.lax file to the directory using WindowsExplorer.

3. Copy the following files from $PROMAX_HOME/port/java toyour PC directory:

• ProManager.jar

• Utilities.jar

For Windows 95 users

There are problems using ProManager with Windows 95. In this case, Landmark recommendsusing the 1998.6 MySQL database.



• mysql.jar

• jhall.jar

4. Access www.javasoft.com to install the JRE for Java 1.3.

Select Products & API's.

In the Shortcuts pulldown, select Java 2 RuntimeEnvironment Standard Editions, v1.3.

Select Microsoft Windows.

Click continue under US English version.

Read and Accept their agreement.

Select the FTP Download or HTTP Download (if you arebehind a firewall) to download to your desktop.

Double click on the j2re-1.3.1.exe icon to install the Javaruntime directory on your PC.

To verify installation, enter the full pathname to your java bindirectory and -version. As an example, we use:

c:\progra~1\javasoft\jre\1.3.1\bin\java -version

Note: progra~1 is necessary because of the space after \program.You should see the java version "1.3.1" echo.

5. Override the umask setting by editing the$PROMAX_HOME/port/bin/ProManager script. You change thejava call line with a -Dumask=xxx flag.

.‘promaxpath port/java/ENV.java‘

java -Dumask=002 com.lgc.ProMAX.ProManager.Client

print "\nProManager complete.\n\n"

exit 0

a value of 002 will output files with rw-rw-r-- permission

a value of 000 will output files with rw-rw-rw- permissions

a value of 022 will output files wtih rw-r--r-- permissions

6. Create a ProManager.bat file in your PC directory and editthe execution path as indicated:

@ECHO OFF

Rem Add jars to classpath

set CLASSPATH=mysql.jar

set CLASSPATH=%CLASSPATH%;jhall.jar

set CLASSPATH=%CLASSPATH%;ProManager.jar



set CLASSPATH=%CLASSPATH%;Utilities.jar

Rem execute ProManager (change the path to the full path to yourjava executable)

c:\progra~1\javasoft\jre\1.3.1\bin\java -cp %CLASSPATH%com.lgc.ProMAX.ProManager.Client******************************************************

7. On the UNIX machine, modify mysql, adding your PChostname to the user table:

cd to your mysql location

Type bin/mysql -u (your mysql username-dbuser) -p(yourmysql password-dbuserpw) mysql. For example:

bin/mysql -u sue -psuepw mysql

If you want to let other users access this PC, login as rootand use the root db password. Type the followingcommand (substituting your information in the brackets):

insert into user values:('<PCHOSTNAME>','<dbuser>',password('<dbuserpw>'),

'Y','Y','Y','Y','Y','Y','N','N','N','Y','N','N','Y','Y');

quit;

Note: If you encounter the following error when you startProMANAGER:

Error: java.sql.SQLException: server configuration denies access to datasource

Add your PC IP Address into user table: insert into user values

('<PC_IP_ADDRESS>','<dbuser>',password('<dbuserpw>'),'Y','Y','Y','Y','Y','Y','N','N','N','Y','N','N','Y','Y');

8. As root, stop and start your mysql server:su root

./support-files/mysql.server stop




9. Run ProManager.bat on your PC. ProMANAGER shoulddisplay.

10. Start Exceed or other X-emulation software to startProMAX or view a job.output on your PC spawned fromProManagerInstall.

Setting the default connections

1. Enter the URL to the resources.lax file in the LocationText field. You can also use the File selector button (topright corner of the menubar) to select the file. These filescan be local or on the web. For example:

• file:/d:/promanager/resources.lax

• http://ra.advance.com/dmurray/resources.lax

2. Select Bookmarks ➛ Set Home to save this location asyour home.

3. Exit the session to save these settings in the clientconfiguration file and return to this location at startup.The client configuration file,$HOME/.promanager/client.properties, updates as part of anormal exit of the ProManager client.

Setting the server environment

The ProManager server must have an environment defined toaccurately service requests made by the client. The structureof the environment tree is fixed and the server will notfunction properly if it is changed. That is, each host needs tohave a directory containing subdirectories definingenvironments, Job control and Queue.



The procedure for doing this follows.

1. Select Tool ➛ Environments or ENV icon to start theEnvironment editor. Your current server environmentsare displayed in the editor window. You can expand thetree to see the environmental variable and queuedefinitions.

2. Create a copy of the example environment by highlightingthe host, clicking MB3 ➛ copy, and then MB3 ➛ paste.Alternatively, you can use the drag and drop method. Aduplication of your host environment is appended to theend of the environment list.

3. Rename the copied host environment to the hostname ofyour machine. To rename your host or environment, suchas defining your queue names for the defined host,double-click on a cell, enter the new name and clickReturn to save.

Note: Do not change the name, Job control or Queue.Only change the names under Queue to match the queuenames you are using in ProMAX. Job control does notserve a useful purpose. However, it must be under eachhost entree.

4. Expand your host environment. Under your hostname isyour group name that is a directory containing aliases fordifferent user environments. You can give any name togroup and aliases. Under the aliases are yourenvironmental variable definitions. Edit the currentdefinitions, or highlight and click MB3 to delete or copyvariables. You can also create new variables by specifyingFile ➛ New ➛ Variable.

5. Expand the Queue directory and rename the queues tomatch the names in your ProMAX environment.

6. Once you have filled in the environmental variables andqueuenames for your host, select the host and click Edit➛ ProManager service port. Enter the correct portnumber for the server. The port number, such as 8860,corresponds to the port number found in your /etc/servicesfile for the pmgrserver.

7. To test your environment, highlight the directory definingyour environment and click the ProMAX UI icon. ProMAX



launches on the selected host. If you are running theProManager client on a PC, Exceed must be running.

Building a Template

Templates are generalized Master Flows, built with ProMAX.In most cases, you build all flows required to process atypical data segment or replica before beginningProMANAGER. You parameter test and flow design withProMAX, then build a clean set of flows to use as templates.Each flow is ready for execution when key information, suchas dataset names, field file ID ranges, velocity or deconparameter tables, is substituted.

The Navigation window acts as a map to the replicas. Usingthe Edit, Create, and Area/Line/Template options, youcreate a map to your data. You must enter the exact name ofyour 2D or 3D area. This maps to the correct area inPROMAX_DATA_HOME. Continue to build maps to your Lineand Template. Once completed, your first template is builtand ready for use.

Creating Area/Line/Flow Replicas

1. Select File ➛ New ➛ Area to create a Project Area identicalto your ProMAX area.

2. Select an Area and File ➛ New ➛ Line to create a newLine.

3. Select the Line and File ➛ New ➛ Template to addtemplates that correspond to your ProMAX flow.

Note: It is easier to manage job status if flows are displayedin logical execution order. You can reorder templates from theStatus window by using drag/drop to reorder the templates.Select Flow ➛ Save layout to reorder the correspondingtemplates in the Navigation window.

Note

Area/line/Flow/ template names defined in ProMANAGER must exactly matchthose in ProMAX.



Syntax

Names for Area/Line follow the same rules as naming inProMAX.

Flows are built as aaaaaaaaaa#####, where:

• template names are unique

• the template name is the first 10 alpha characters (if lessthan 10, pad using the underbar character: _)

• the replica number is the next numeric 5 characters

Editing functionality

You can use the functions under the Edit menu to editTemplates, Lines and entire Areas in the MySQL database. Orclicking MB3 offers the same functions.

Copying databases

To copy from one user database to another:

1. Open two browsers or application windows, each pointingto different Resources.lax files.

2. Copy the content from one database and paste into theother database. You can use drag/drop by holding MB1down on one file and dragging it into the other.

Refer to Troubleshooting if you have problems.



Defining Global Processing Parameters

1. Use the Replication parameters icon and select theArea tab to define Area global parameters.

2. Use the Replication parameters icon and select the Linetab to define Line global parameters.

3. Use the Replication parameters icon and select theReplica tab to define Replica global parameters. A typicalreplica is a Marine 3D Sail-line, a Land 3D Swath, a single2D line, or an offset cube.

4. Create new replicas by selecting File➛ New Rows andenter the number of rows to add.

5. Create new replica parameters by selecting File➛ NewColumn. Enter the column name and type (String,Integer, or Float).

6. To fill Cells, select the cells by using MB1 on the first celland Shift MB1 on the last cell. Select Edit ➛ Column Fillto automatically populate the cells in the parametercolumn.

• For the Numeric Fill menu, enter the starting number,the increment number, and press OK.



• For the String Fill menu, enter the information for thefollowing column and row headings:

Each Column in the String row is appended to the columnbefore it, to form the total alpha-numeric string. In thiscase we are setting up an alphanumeric string to look likethe following:

Iline:###-###_Xline:###-###

The ### represents the values in the Start andIncrement rows. For the first string, Start values areadded into the appropriate columns yielding the followingalphanumeric string:

Iline:1-10_Xline:1-100

Subsequent lines increment by the Increment value. Forexample, the second line in this case is:


Since the starting and ending inline in the alphanumericstring are to increment by 10 and the starting and endinginline in the alphanumeric string are to increment by 0,additional lines would look like the following:




In this way, useful alphanumeric strings are automaticallygenerated. For longer or shorter alphanumeric strings usethe << >> buttons to decrease or increase the number ofcolumns.

PARAMETER[0] [1] [2] [3]

STRING Iline: - _Xline: -

START 1 10 1 100

INCREMENT 10 10 0 0

String Fill Popup Menu



7. Select Test to view the column fill. Click OK if the fill iscorrect.

Importing/Exporting data

Select File➛ Import to import an ASCII file to a selected cell,an entire column, or to appended rows. For complete rowimport, all fields must be separated by the ampersandcharacter: &. The number and type of imported fields mustexactly match those defined in the replica table. Likewise,select File➛ Export to export replica parameters to an ASCIIfile.

Note: To make viewing an import/export text file more user-friendly, use tabs to separate the fields. To do this in the vieditor, use a global substitution command like: %s/&/<tab>/g,where <tab> indicates the tab key.

Substituting Parameters

Once the replicas are created, you will define the keyparameters in your template. These parameters are datasetnames, range of inlines, and anything else that varies from

line to line. Use the Template Table icon to display yourflow information in the Template Parameters tab.

1. Highlight a template and click the Template Table icon.The initial window displays an empty table:



2. Select Tools➛ Server to define a ProMAX environment.

3. Click Reload to view the flow processes. A list of flowprocesses are displayed.

4. Click a process to open a display of its menu parameters.

As you move your cursor over a parameter, thecorresponding ProMAX menu text is displayed. Select thecheckboxes next to the parameters that you want tochange from replica to replica. Processes with parametersselected for change are highlighted in blue.

Caution: Keep substitution to a minimum. Do not selectparameters that alter the menu. For example. if youchange the mute type in Trace Muting, the trace mutingparameters would change in the menu.

Your selections appear in the order in which you checkedthe checkboxes. They do not need to be in order ofappearance in the flow. The contents of the Parametercolumn indicates the name of the process, a counter tohandle multiple occurrences of the same process in a flow,and the lisp menu parameter name. To view the ProMAXflow while making selections, click the ProMAX Icon.

5. Enter substitute parameters into flows based on variablesdefined in Area, Line and Replica Tables. The list of

Click checkbox toadd parameter tosubstitution list

Click on processname to showparameters



available parameters are displayed in a tree in the rightpanel. Use drag/drop to put parameters into the cells.

Syntax

The syntax for this expression is similar to the Java syntaxfor strings. Text within double quotes is passed withoutevaluation, though numeric parameters are substituted.Within a string, the ’+’ symbol indicates concatenation; innumerical expressions, math functions are performed afterparameter substitution. Area/Line/Replica parametersprotected by double quotes are substituted withoutnumerical evaluation. For example, for Seq = 1 and FFID =400 in the Replica table:

"Line=" + replica.Seq + 1 would evaluate to Line=2

"Line= replica.Seq + 1” would evaluate to Line=1 + 1

"Shot=" + replica.FFID + " + 1" would evaluate to Shot=400 + 1

A special syntax exists for multiple fields in a substitution,like specifying a dataset to read from another line: <area> |<line> | <dataset description>. Enter space on either side ofeach pipe symbol For example,

"Manhattan | 3d | " + replica.Name + "_DeconShots "

defines a dataset named <Name>_Decon_Shots to be readfrom Area Manhattan, Line 3d. Regular expressions can beup to 255 characters long.

Note: This syntax substitution does not work using anMSAccess database.

Each list of parameters contains a DISABLE switch. Thisswitch indicates which process is inactive/active based on aparameter substitution. If not turned on, its default value isFALSE.

To activate DISABLE, add a column to the Replica table andenter TRUE/FALSE string values. In the Template window,toggle a ProMAX process from the processes list to DISABLE.This adds a disable line to the TemplateName column.TRUE/FALSE values from the replica spreadsheet are thensubstituted in this line.

The following graphic shows Bandpass Filter turned on forone data swath (DISABLE is FALSE for sequence 5, replica4.):



The following graphic shows the flows built for replicas 1(Bandpass disabled) and 4 (Bandpass turned on):

DISABLE Bandpass Disable line

Bandpass TRUE/FALSE string values to use in flow



Validation

The Validate tab provides a tool for viewing the parsed valuesof the expression for each replica. Toggle Result to displayinvalid expressions in red with an exception message; validexpressions in green with a text rendering.

You can adjust the order or size of the template parameterscolumns. Select File➛ Save Layout to save new settings.These setting will also apply to the Parameters tab.

Defaulting Substitute Parameters

(Landmark does not recommended this procedure)

Template parameters, for which no substitution is defined,are defaulted to the parameters set in the template flow. Forcertain situations, you can define parameters which overridethe template but do not change from replica to replica.Examples include: standard settings for displaying 3Dstacked data in Trace Display or always enabling the optionto skip primary storage in Disk Data Output.

Default settings for parameters are defined by buildingdefaulting templates.



1. Create a ProMAX area Default, line Default, and flow(named to identify its use).

2. Insert the list of processes, in any order, for definingdefaults.

The following example, GroupDefaults, shows processesgrouped by function that can be used to set general usedefaults; this need not be an executable flow:

3. For each process, click MB3 on the parameter’sdescriptive text to select that parameter for defaulting. Itwill highlight in red. Set the parameter value to thedesired default value, for example Yes to Skip primarydisk storage.)

4. In ProMANAGER, define the default names using Tools ➛Defaults. In the Defaults catalog, highlight an entry.Select Edit➛ New➛ Sibling for a new entry at the samehierarchical level as the selected default. Select Edit ➛New ➛ Child to put the entry one level down. The



indentation levels do not indicate hierarchy. However, theycan be used for logical grouping.

5. To apply defaulting to a template, select the Defaults tabon the Template Parameters window and drag/drop itemsfrom the tree into the list.

6. The new default must be saved and made available to theNavigation window. Click the Reload icon and the defaultsdisplay, indented below the template name. You can alsoadd/delete/copy/paste defaults from this display, usingthe Edit➛ New➛ Default.

Each entry takes precedence over those listed after it.Settings in the master template are overridden by eachlevel of defaulting and finally by parameters set forsubstitution in the Template parameters table. In thefollowing example, the Stack3D template contains DiskData Input, NMO, Stack3D, Ensemble Redefine, andTrace Display.



A default template called UserDefaults sets theTraceDisplay display location to the user’s workstation.

StkDisplayDefaults defines typical TraceDisplay settingsfor displaying a 3D inline stack section.

You define the input dataset name and Stack3D inlinerange. STkDisplayDefaults and UserDefaults are definedas the default templates.



The resulting flow contains these Trace Display settings:

Building and Executing Flows

Jobs are created and submitted through the Status Table. Werecommend that you select each of the items in this list tofamiliarize yourself with the corresponding tables.

Note: If you are processing many 2D lines, it is helpful todeselect Common ProMAX Database. This allows flows to becreated in each line directory instead of the template linedirectory.



The initial Job Status setting for newly defined flows orreplicas is inactive. Inactive status is used to indicate flowsthat should not be built. Inactive cells must be set to activebefore you can build/submit the corresponding jobs.

1. To activate cells, select cells (selected cells are highlightedin blue) and Edit➛ Active.

• select multiple consecutive cells by dragging MB1

• select discreet cells within a single column or row withcontrol-MB1

You cannot select cells in multi-cell/row combinations.

2. To change a cell’s status, use the first four icons to build,submit, resubmit, or kill. When you change a cell to build,build/submit, or submit, you are prompted for the jobexecution machine and environment information:

Selected cells



To change the host, click on the Environments tab. Thischanges the host and environment.

• When active, a cell can be set to build (create and saveflow) or build/submit (build, save and submit flow).

• A build cell can be set to submit to execute the alreadybuilt flow.

• A cell will indicate submit, execute, good, or bad as thejob is submitted, executed and QC’d with informationfrom the aar_promax accounting log.

• A submit or execute cell can be set to kill.

• A good, bad, or kill cell can be set to resubmit to re-queue the flow without rebuilding.

• If submit is selected for an already executed cell, theflow is rebuilt and submitted

3. The table cell checkbox is the hold status. It is used toprevent submission. New cells are defaulted to the holdstatus. To remove a hold, select the cell and Edit ➛Release. Similarly, use Edit ➛ Hold to add a hold status.

You can scroll all templates. However, you cannot see thereplica and sequence columns when scrolled to the right. Youcan resize several columns to minimum width and/or hidethe Attribute list. To view different combinations of columns,drag a column header to the right or left

Note

If you use a previously opened ProMAX UI to look at a newly built flow, it candisplay INVALID for datasets and tables which were created during the flowreplication. Reselect the ProMAX line, then reopen the flow to view the flow.



.

Save the layout using File➛ Save Layout. These remain yourdisplay preferences. Changing the column order also changesthe order of the templates in the Navigation tree.

Using Flow chains (optional; does not work on IBM)

You can define a sequence of jobs with flow chains. Jobs inthe chain are executed in order unless interrupted by a holdor job failure.

Jobs with the same sequence number can be in a flow chain.Jobs in a flow chain watch for dataset availability. When allinput datasets and tables are in a good state and the flow isbuilt, the job is queued for execution.

The Relationship tool is used for creating dataset/flowrelationships. To use this tool, click the Relationshipmodeler icon or select Tools ➛ Relationships.

The relationship tool is a palette of icons representing definednavigation objects. You can drag these icons into the tool.Expanding the icons exposes inner navigation objects. Bydrilling down to the template level, input/output datasetsand tables are defined. The tool shows the templateinterdependencies by connecting the template objects with aline.

Resize columnDrag column to reorder

with right handle



The following graphic shows a relationship model. Itemsprefixed with an arrow pointing right (toward the datasetname) are inputs. Items prefixed with an arrow pointing left(away from the dataset name) are outputs.

By creating output datasets, entries are created in theProManager database. These dataset entries can be droppedinto output dataset names in template definition.ProManager uses a fixed naming syntax when the flow iscreated. This eliminates the need for a user definedexpression.

You can view dataset states from the Status tool. This toolalso maintains functions for evaluating dataset size andremoval of ProMAX data objects.

You can run chained jobs once the relationship table iscreated and the corresponding datasets are used in thetemplate. Activate flow chaining from the Status window byreleasing all the flows in the flow chain, marking them asactive and then as build/submit. Each of the jobs are builtand the first job is executed. Once this job completesnormally and the next flow is built, the next job in the chainis executed.


Converting 1998.6 MySQL Databases67 ProMANAGER User Guide

Converting 1998.6 MySQL Databases

The following steps copy and converts the 1998.6ProManager MySQL database to a ProManager R2003.0compatible format:

1. cd to your 1998.6 MySQL installation location.

2. Type the following line to create an empty database:./bin/mysqladmin -u <mysql username> -p create <new mysql

database name>

For example:./bin/mysqladmin -u sue -p create suemjdb

You are prompted for your mysql password. It is in yourResources.lax file if you do not remember it. Oncecompleted, you receive the following message:

Database "(new mysql database name>" created

3. Copy the old Resources.lax file to a new name. Replace thenew database name for the old one by editing the followingline:

db.url=jdbc:mysql://sparky/suedb

todb.url=jdbc:mysql://sparky/suemjdb

4. Run a script that will set your 2003.0 PROMAX_HOMEand activate ProManagerInstall:

#! /bin/csh

setenv PROMAX_HOME < full path name to 2003 PROMAX_HOME>/cm/installs/promax/2003.0/SUNSV/ProMAX

set path=(${PROMAX_HOME}/port/bin $path)

ProManagerInstall&

On AIX systems, you also need:setenv LIBPATH $PROMAX_HOME/sys/lib

The ProManagerInstall window displays.


Converting 1998.6 MySQL Databases68 ProMANAGER User Guide

5. Select File ➛ Open and open the new Resources.lax file.In our example: ResourceMJ.lax.

6. Toggle Verify on and click Run. Look in the consolewindow that you started ProManagerInstall for thefollowing message:

1:16 PM> File "/lair/swill/pmspark/ResourcemMJ.lax" opened.

1:16 PM>

1:16 PM> Starting database verify...

1:16 PM> Connection successful.

1:16 PM> Database verify complete.

7. Toggle Create on and click Run. Select Yes to Createdatabase tables. Look in the console window for the Createdatabase tables complete message.

8. Select File ➛ Open and open the 1998.6 Resources.laxfile. Toggle Convert on and click Run. You are promptedfor a conversion file name. Enter a name, such asconvert.txt, and click Save.

9. Select File ➛ Open to open the new Resources.lax file.Toggle Restore on and click Run. You are prompted forthe convert.txt file. Select the conversion filename and clickOpen. Check the console window to ensure it completednormally.

10. Select File ➛ Exit to exit out of ProManagerInstall.

11. Once the 1998.6 database is converted, go to StartingProMANAGER.



Troubleshooting

In this chapter, you will find information to help you identifyproblems you may encounter working with ProMANAGER.Included are examples of error messages, output from goodand bad job builds, and workarounds for any knownproblems.

In This Chapter

➲ Checklist 61

➲ Installation and Configuration

➲ Starting ProMANAGER

➲ ProManager Service Port problems 66

➲ aar_promax

➲ Potential pitfalls with aar_promax

➲ Port conflicts

➲ Unsuccessful MySQL Database Connection

➲ MySQL database access error

➲ Replicating a ProMAX Flow 69

➲ Select substitute parameters

➲ Building Jobs 71

➲ Good Build

➲ Bad Builds

➲ No apparent reason

➲ Display Tools and Execution Hosts

➲ Undefined datasets or tables

➲ Missing datasets or tables

➲ Incomplete substitution definition

➲ Pending Job Status prevents build

➲ Miscellaneous 75

➲ Error copying a line from one ProMANAGER session toanother

➲ Importing large files

➲ File Permissions


Checklist70 ProMANAGER User Guide

Checklist

Installation and Configuration

Note: Perform all steps in the ProMANAGER User Guide in theorder they are presented for successful installation.

1. To test that aar_promax is running, type:rpcinfo -t `uname -n` aar_promax 2

If `uname -n` does not work, substitute your hostname.You should receive the following message:

program 536876325 version 2 ready and waiting.

For problems, see Configuring aar_promax and theService Port.

2. Check that pmgrserver is start able through theinetd/service call telnet host port Where port is thepmgrserver entry in the /etc/services file.

For Example:telnet janus 8860

If pmgrserver is configured correctly, you receive amessage like the following:

telnet janus 8860

Trying...

Connected to janus.advance.com.

Escape character is '^]'.

Double click Return to close the connection.

If pmgrserver is not configured correctly, you receive amessage like the following:

Trying 192.156.212.25...

telnet: Unable to connect to remote host: Connection refused

For problems, see Configuring aar_promax and theService Port.



3. Check your $PROMAX_HOME/etc/config_file. Are accounting:tand aar_log:<PROMAX_HOME>/etc/Account lines uncommentedand the proper PROMAX_HOME set?

4. To check that MySQL is started and owned by root, type ps-ef | grep mysql. You should see:

root 28656 35518 0 16:58:05 pts/5 0:01

/data36a/2003simpmysql/mysql/bin/mysqld

--basedir=/data36a/2003simpmysql/mysql

--datadir=/data36a/2003simpmysql/mysql/data --user=root

--pid-file=/data36a/2003simpmysql/mysql/data/mysqld.pid

--datadir=/data36a/2003simpmysql/mysql/data

root 35518 1 0 16:58:05 pts/5 0:00 sh./bin/safe_mysqld --user=root

--pid-file=/data36a/2003simpmysql/mysql/data/mysqld.pid

--datadir=/data36a/2003simpmysql/mysql/data

For problems, see Setting Up the MySQL Database.

If you followed the steps described in Setting Up theMySQL Database, restart MySQL by cd to the MySQLdirectory, become root, and type:



5. Is your Resources.lax file set up? If not, see RunningProManagerInstall.

Starting ProMANAGER

Start ProMANAGER by typing:set path = (${PROMAX_HOME}/port/bin\

${PROMAX_HOME}/sys/bin $path)

setenv PROMAX_HOME

$PROMAX_HOME/port/bin/ProManager &

AIX machines also need the following command:setenv LIBPATH /usr/lib:$PROMAX_HOME/sys/lib

1. Is the Resources.lax location defined and theenvironmental variables menu setup? If not, see GettingStarted.

2. When Resources.lax file is defined, do you see an area calledExample, a line called Standard, and a template called



ShotProc? If not, there is a problem with your MySQLdatabase.

Check the ProManager window for details.

3. Highlight ShotProc and click on the Template icon.Select Tools ➛ Server and highlight the server containingyour environmental variables.

4. Click the ProMAX icon.

ProMAX should launch. If it does not, check the UNIXwindow that started ProMANAGER for error messages.

The most common problems that occur when ProMAXdoes not launch are:

• incomplete or incorrect environmental variable setup

• incorrect path in $PROMAX_HOME/etc/config_file to yourAccount file. Specifically, theaar_log:<PROMAX_HOME>/etc/Account stanza

• accounting:t not turned on in your$PROMAX_HOME/etc/config_file

Note: Although this might not be the config_file youspecify in your environment, you still need to edit it.

• incorrect /etc/inetd.conf syntax

5. Once ProMAX is running, create the area Example, theline Standard, and the flow ShotProc. Insert the followingprocesses in this flow: Synthetic Trace Generation,Automatic Gain Control, and Trace Display.

6. Exit ProMAX and save your changes.

7. In the Templates window, click Reload. You may have touse Tools ➛ Server first to define the server environment.Reload replaces the word parameter with Synthetic TrcGeneration, Automatic Gain Control and a TraceDisplay.

8. Highlight and click on Automatic Gain Control to seethat the agclen parameter is checked. The value for thisparameter is provided with the example.

9. Click on the Status icon. The Status window should belabeled Status (AREA= Example LINE=Standard. Select thecell under the ShotProc column for line A92-398-50100.Click MB3 on the inactive box and select Edit ➛ Release.



Click MB3 and select Edit ➛ Active. The field highlightsto blue displaying active. Click MB3 on active, and selectbuild. Select your host/environment, and fg for queue,and click OK.

10. To change your host, click the ENV icon. Also, check theAuto-refresh box in the Status window.

Note: Auto-refresh does not work on IBM machines. Usethe QC button instead.

Your job status should go from pending to build. If not,check the console window for error details. Click MB3 andselect submit. Once you select your <server:alias>, thestatus should change to submit, and Trace Displaylaunches. Select File ➛ Exit- Continue Flow and theShotProc status should update to execute and thengood.

If your status does not update, highlight the job and clickQC. If status updates:

• the problem may be forgetting to check auto-refresh, orimproper configuration of your pmgrserver.

If the QC button does not work, check the console windowfor error messages. If you receive the following message:

Dispatch remote method qc complete.

3:41 PM> Opening connection fromzeus.advance.com/192.156.212.164:36917.

3:41 PM> zeus.advance.com QC begins.

3:41 PM> zeus.advance.com AAR ProMAX is running and the log file is

/release/1998.6/ProMAX/etc/Account

3:41 PM> zeus.advance.com JobId 1 qc skipped. Log file size hasn'tchanged.

3:41 PM> zeus.advance.com QC ends.

the size of your Account log has changed.

This change can be caused by the wrong account logbeing updated. Make sure the $PROMAX_HOME part ofyour path in /etc/inetd.conf matches the $PROMAX_HOMEpart of aar_log: path in the config_file. Once this is fixed,validate your accounting updates (after submitting a jobin ProMANAGER) by typing:

tail -f $PROMAX_HOME/etc/Account



• Your queue file can be out of date. If you are using lpqueues, $PROMAX_HOME/sys/exe/lpd/quefilter mustbe identical to /etc/lp/interfaces/sml (or whateverqueues you have). If it is not identical, set this interfacefile using the lpadmin command. As root, run lpadmin -psml -i quefilter to update it.

• Your Account log is not updating properly. To check, runtail -f on the Account file you point to in your config_fileaar_log: path. After running a job, run tail -f on this fileagain.

If you still cannot get the Status window to update, doublecheck your aar_promax configuration. See Configuringaar_promax and the Service Port for more information.

If Auto-refresh stops working or the next job in the queuenever starts, look in the /tmp directory where ProManageris running. In the job, promanager.<pid>, pid is theprocessing id of your job. This pid changes to aarid,account id, when the job starts execution. The pid on thisfile should match the pid in your Account log for the jobstatus to change or other jobs to be executed. If it doesnot, there is probably something wrong with your queues.

The following is an example of promanager.aarid:

(lager) >cat /tmp/promanager.27155

#/tmp/promanager.27155

#Mon Jan 15 15:39:56 MST 2001

elapsed=5

pid=27140

db.user=sue

db.url=jdbc\:mysql\://sparky/suemjdb

db.passwd=suepw

cpu=2

db.driver=org.gjt.mm.mysql.Driver

The following is the corresponding Account log:

27155 0 15/Jan/2001 22:39:39

27155 7 lager 344

/network/sparky/swill/data/sdwpromj/seg1/segyextrac0005/27140/

t65022 /cm/installs/promax/2003.0/SUNSV/ProMAX/sys/exe/exec.exe



27140

27155 4 ALONE 1.50

27155 5 ALONE 0 5

The pid of promanager.27155 matches the pid listed at theend of line 3: 27140.

• If the status windows still do not change from submit toexecute when running jobs, ensure that you have aProMAX_RMI_log in your $PROMAX_HOME/etc directory.The directory should have r-w permissions for user,group, and world, and owned by root.


ProMANAGER Service Port Problems76 ProMANAGER User Guide

ProMANAGER Service Port Problems

aar_promax

If aar_promax does not start, look at the system log in/var/adm for error messages. Double check the entry in/etc/inetd.conf for tabs rather than spaces and that thepaths are correct. Check the config_file in$PROMAX_HOME/etc to see that the aar_log stanza points toan output file in a valid directory.

Potential pitfalls with aar_promax

• On machines running NIS, the file: /etc/nsswitch.conf deter-mines where the OS looks for information on services.For Solaris, the default stanza:

rpc: nis [NOTFOUND=return] files

tells the OS to look only at the definition on the NISserver and not find locally configured /etc/inetd.conf and/etc/rpc services. To use local files after NIS, change thestanza to the following:

rpc: nis files

• You must run only one copy of aar_promax on a computehost. This is because it locks the config_file and outputAccount file to prevent multiple concurrent writes. Dueto potential problems locking files on remote filesystems,we recommend that the $PROMAX_HOME/etc directoryis local to the service port, even if the remainder of theProMAX installation is NFS mounted from elsewhere onthe network.

• inetd services are designed to time-out after a designatedidle time and restart when next requested. This does notwork as intended on Solaris 2.6. (Sun plans to provide abug fix.) If a job submission appears to hang, check forthe presence of the aar_promax process with ps -ef | grepaar and its entry in rpcinfo -p. If either of these is missing,kill any aar processes and re-initialize inetd as above.

After successfully starting aar_promax, you can define acron entry to keep it active. Execute crontab -e and add thefollowing line:

0 0,5,10,15,20 * * * rpcinfo -t spitfire aar_promax 2 > /73/advance/etc/aar_log 2>&1



where spitfire to the hostname and the output is sent to a filein your $PROMAX_HOME/etc directory.

Port conflicts

The following message indicates a conflict on your systemwith another service port or one that did not completely diebefore your attempt to restart it.

******Rmiregistry (and associated services) already running on port <port>******Please kill the existing processes before re-starting rmi"*****OR edit $PROMAX_HOME/etc/startrmi and specify a separate port number.

You can run multiple service ports as long as each uses adifferent port number. This is useful in conjunction with adistributed tape configuration.

Unsuccessful MySQL Database Connection

If you do not get a successful MySQL database connection,these additional steps could help:

1. cd to your mysql installation location

2. Get into mysql by typing:bin/mysql -u root mysql

3. Set roots password: For example:> mysql> update user set Password = password ('rootpw')

where User = 'root';

Note: MySQL users, passwords and root password shouldnot be related to UNIX host users and passwords. Aseparate entry must be made for local host and for eachhost from which each database user will connect, such as,localhost, dbusr1 and vail, dbusr1.

4. Add hosts IP address into MySQL user table. For example,insert into the user values:

> mysql> insert into user values/('192.156.212.23','root',password('rootpw'),'Y','Y','Y','Y','Y','Y','N',/'N','N','Y','N','N','Y','Y');

5. Exit out of mysql:> mysql> quit

6. Stop and then restart the mysql server as root toincorporate the changes:

su root





7. cd to $PROMAX_HOME/port/bin/MySQLAdminTool.

8. Edit the MySQLAdminTool script to incorporate the rootpassword and your IP address. For example:

#! /bin/ksh

.ijava_env

java MySQLAdminTool 192.156.212.23 mysql root rootpw

9. Restart MySQLAdminTool. You should get a 'successfulconnection' message.

MySQL database access error

An error like the following indicates a problem connecting tothe SQL database.

SQLException. View console for details.

java.sql.SQLException: General Error: Connection refusedat org.gjt.mm.mysql.Connection.<init>(Connection.java)at org.gjt.mm.mysql.Driver.connect(Driver.java)at java.sql.DriverManager.getConnection(DriverManager.java:91)at java.sql.DriverManager.getConnection(DriverManager.java:134)at com.lgc.ProMAX.ProManager.ProManagerButton.openConnection(...)at com.lgc.ProMAX.ProManager.Navigator.run(Navigator.java)at java.lang.Thread.run(Thread.java:474)

After confirming that the SQL database is running, check theuser, password, database URL and access driver informationdefined in your Resources.lax file(s). If that is all correct,there could be problems with the specific host-usercombination with which you are trying to connect. Seeconfiguration information for your particular database underSetting Up the MySQL Database.


Replicating a ProMAX Flow79 ProMANAGER User Guide

Replicating a ProMAX Flow

Select substitute parameters

The following is a check list if the flow processes do nottransfer to the template:

• Check the ProManager Service Port environment

Are your environment variables defined for the correcthost and alias? Click the Env icon to display theEnvironmental variables. Look at the list of host:aliaspairs on left hand side of the Environment work window.Are your current environmental variables defined for thecorrect host:alias pair? Are your environmental variablescorrect?

Are the paths in the environment variables full paths?For example, is XFILESEARCHPATH defined as your fullpath? In our case:

/clientdata/73alpha/ProMAX/port/lib/X11/%T/%N%S

You cannot make substitutions. For example: $PROMAX_HOME/port/lib/X11/%T/%N%S

Did you press Enter/Return after entering eachvariable? If not, you did not write the variable to thedatabase.

Do you have all required variables?

• Check your .promax.proloop file. The critical entries arerestart_position and restart_active.

(quote( (:restart_position "area" "P" "line" "" )(:area_alphabetic t )(:line_alphabetic t )(:flow_alphabetic t )(:dataset_alphabetic t )(:parameter_alphabetic t )(:header_alphabetic t )(:batch_priority 10 )(:job_output_versions 5 )(:restart_active t )(:help_sticky t ) ) )


Replicating a ProMAX Flow80 ProMANAGER User Guide

• Check that you are using the correct ProManager ServicePort by clicking Utility ➛ ProManager Service Port inthe work area of the Template window.


Building Jobs81 ProMANAGER User Guide

Building Jobs

Good Build

The output lines echoed to the UNIX window from which youstarted ProMANAGER (or the HotJava Console) play a vitalrole in diagnosing problems in job building. A successful jobbuild for a given replica and template produces the followingoutput (without the section headers):

Section 1

Starting dispatch remote method build in the background.build started on ProManager Service Port.Dispatch remote method build complete.Spawning connection to a new incoming socket 7[7]:stargazer:rel1998.5 Attempting to initialize user "promgr".incoming> Spawning new connection to an incoming socket.[7]:stargazer:rel1998.5 Retrieving environments for subprocesses fromdatabase.[7]:stargazer:rel1998.5 DISPLAY=tag:0.0[7]:stargazer:rel1998.5XFILESEARCHPATH=/release/1998.5/ProMAX/port/lib/X11/%T/%N%S[7]:stargazer:rel1998.5LM_LICENSE_FILE=/network/enterprise/usr/flexlm/license.dat[7]:stargazer:rel1998.5PROMAX_DOT_PROMAX_HOME=/network/tag/disk1/promanager/promgr/.promax.proloop[7]:stargazer:rel1998.5PROMAX_SCRATCH_HOME=/network/stargazer/export/star8/scratch[7]:stargazer:rel1998.5PROMAX_ETC_CONFIG_FILE_HOME=/release/permanent/etc/promgr_config_file[7]:stargazer:rel1998.5PROMAX_DATA_HOME=/network/stargazer/export/data4/amelia[7]:stargazer:rel1998.5 PROMAX_HOME=/release/1998.5/ProMAX[7]:stargazer:rel1998.5 HOME=/network/tag/disk1/promanager/promgr

Section 2

[7]:stargazer:rel1998.5 Setting flow for JobId = 149[7]:stargazer:rel1998.5 (setq flo(flow "Marine3D" "SailLineMaster""StackDisplay"))[7]:stargazer:rel1998.5 (setq exec (process flo "executive" 1))[7]:stargazer:rel1998.5 (setq parm (parameter exec "area"))[7]:stargazer:rel1998.5 (dp_adjust_value parm "Marine3D")[7]:stargazer:rel1998.5 (setq parm (parameter exec "line"))[7]:stargazer:rel1998.5 (dp_adjust_value parm "Sw4L1")[7]:stargazer:rel1998.5 (setq parm (parameter exec "flow"))[7]:stargazer:rel1998.5 (dp_adjust_value parm "StackDispl0019")



[7]:stargazer:rel1998.5 (setq parm( parameter(process flo "diskread2" 1) "label"))[7]:stargazer:rel1998.5 (dp_adjust_value parm "Brute Stack")[7]:stargazer:rel1998.5 (setq parm( parameter(process flo "stand_alone" 1)"xserver"))[7]:stargazer:rel1998.5 (dp_adjust_value parm "tag:0.1")[7]:stargazer:rel1998.5 (submit flo nil)[7]:stargazer:rel1998.5 (exit)

Section 3

[7]:stargazer:rel1998.5 Using temporary file/network/stargazer/export/star8/scratch/tmp.383099 for proloop lisp commands.incoming> Marine3D&SailLineMaster&149&build[7]:stargazer:rel1998.5 ProMAX 1998.2 ProLoop(73.5): Copyright 1989-99Landmark Graphics Co.[7]:stargazer:rel1998.5 ctrl-c, Q<return> or (exit)<return> to exit[7]:stargazer:rel1998.5 Usage : /release/1998.5/ProMAX/sys/bin/proloop { -h } | {-f { filename } }[7]:stargazer:rel1998.5 Saved - marine3d/sw4l1/stackdispl0019[7]:stargazer:rel1998.5 Build good[7]:stargazer:rel1998.5 <EOF>[7]:stargazer:rel1998.5 <EOF> found: exiting stdout loop.[7]:stargazer:rel1998.5 stderr buffer = true[7]:stargazer:rel1998.5 (stderr) No function associated with first argument in[7]:stargazer:rel1998.5 BYEClosing Console[7]

In this example, the service port is stargazer; userProMANAGER’s environment alias is rel1998.5; the templateis StackDisplay in area Marine3D, line SailLineMaster; thereplica being built is Sw4L1. Section 1 opens a connectionto the service port as the user with a defined environment.Section 2 defines input and output flow names and sets thetemplate parameters for substitutions. Section 3 saves thecreated flow and returns its status to the user interface. Youcan diagnose problems by comparing the output from a goodbuild to output from a build with errors.

Bad Builds

When the status in your JobStatus display changes to activeor build bad rather than build or submit and your UNIXwindow output is different, you may have encountered thefollowing problem:

No apparent reason

If many cells have been selected for build or submit, one canbuild bad for no apparent reason. Select and build or submitthe specific cell to see if a real problem exists.



Display Tools and Execution Hosts

Templates containing display tools fail to build/submit if thedisplay is defaulted to This Screen. You will get the followingoutput to your UNIX window:

[2]:stargazer:rel1998.5 (stderr) Ensure assertion failed (ret), file"/73/advance/port/src/lib/uiutils/string.c", line 112[2]:stargazer:rel1998.5 (stderr) This program has encountered a significantinternal error and cannot continue.[2]:stargazer:rel1998.5 (stderr) The error results from a situation that was notanticipated by the developer.[2]:stargazer:rel1998.5 (stderr) One possible cause of this error is insufficientvirtual memory.[2]:stargazer:rel1998.5 (stderr) /bin/sh[41]: 373400 Abort

Set the template itself or the substitution for the xservermenu parameter to :0.0 (or :0.1 for second screen) to displayon the service port or to <hostname>:0.0 to send the displayelsewhere. A process requiring a hostname for parallel orSMP execution will fail to build with the same error message.The ProMAX menus are edited to set the hostname to ‘ ‘(single space). If the problem flow contains a process with themenu entry, Enter name of host, check that you have notinadvertently erased the space.

Undefined datasets or tables

If you set up a template with no specified datasets and tablesand fail to define them for substitution, the following erroraccompanies a build bad status:

[2]:stargazer:rel1998.5 (stderr) Error >> Requested dataset not available or onrequisite media <<

Missing datasets or tables

When you build a flow with nonexisting input datasets andtables, ProMANAGER creates empty datasets and tablesusing the names you defined. The flow will fail if executed.However, you can submit the flow after the input exists.

Incomplete substitution definition

If you select a menu parameter for substitution and do notdefine the substitution location, your job build will abort atthe problem parameter. The job status is shown as pending.Check for template substitution errors in the last line before



the JAVA error. Look for template fields or replica values of ?or blank. For example:

[10]:stargazer:rel1998.5 (setq parm(parameter(process flo "diskread2" 1)"label"))[10]:java.lang.reflect.InvocationTargetException[10]: atcom.lgc.ProMAX.ProManager.ThreadedPromaxTaskHandler.run(ThreadedPromaxTaskHandler.java)

This example error indicates that the DiskDataInput datasetname was left undefined.

Pending Job Status prevents build

If a job build aborts, leaving a pending status, refresh theJobStatus display by turning on and off Auto-refresh beforerebuilding the job.


Miscellaneous85 ProMANAGER User Guide

Miscellaneous

Error copying a line from one ProMANAGER session to another

To copy a line from one ProMANAGER session to another,highlight the line to copy; drag/drop to the other. Check theUNIX window, in which you started ProMANAGER, for thefollowing phrase:

Drop Standtest successful.

This means the copy has completed. Check to make sure theentire contents of your line was copied successfully. If it wasnot, scroll up the console window to look for the messagewith a JAVA access denied error.

This error message indicates that the sql database of the lineyou copied has hostname and password problems. Edit thesql database of the original line you copied. For example:

• ProMANAGER session one has sql database on willy

• ProMANAGER session two has sql database on martin

You receive the Java.sql.SQLException error message whilecopying a line from willy to a UI running on martin. To fix thisproblem, cd to your mysql database for willy and enter sqlsession as root:

cd /clientdata/73alpha/mysql

bin/mysql -u root -ppromanager mysql

To add willy as hostname, sue as user, and the same passwordas sue on willy which is also the same password as sue’sResources.lax file on willy:

Insert into user values(‘martin’,’sue’,password(‘suespw’),

‘Y’,’Y’,’Y’,’Y’,’Y’,’Y’,’N’,’N’,’N’,’Y’,’N’,’N’,’Y’,’Y’);

You can also enter the same command with a fully qualifieddomain name. In this example, substitutemartin.advance.com for martin.

As root, stop and start Martin’s sql database:./support-files/mysql.server stop


In the ProMANAGER session on willy, remove the line thatwas unsuccessfully copied to willy by highlighting the line



and clicking Edit➛ Delete. Now go to the ProMANAGERsession on martin and highlight the line to copy anddrag/drop to willy.

Importing large files

You can encounter a problem when importing a large text fileto a ProMANAGER replica table, if you are using a MySqldatabase for ProMANAGER on a Sun or SGI database server,It appears to be related to the way MySql handles manysequential table open/close commands. After a certainnumber of lines, the import aborts with, “too many files open”errors. The following are workarounds for this error:

• If you do not normally import large files, use the follow-ing one time occurrence workaround:

Set the maximum number of file descriptors to 1024 in aUNIX shell before starting ProMANAGER:

limit de 1024

• If you will import large files on a regular occurrence, youmust make a permanent change to the MySql database.

create file called /etc/my.cnf on mysql database server,containing following text:

# mysql config file.

# server configuration parameters:

[mysqld]

set-variable = table_cache=256

stop and restart the mysql server.

We successfully imported a replica table of over 2000 lineswith this setting.

Allowing multiple search paths

ProManager, in using the proloop executable to build andmore particularly to execute flows inherits that programsenvironment variable handling. proloop like the ProMAX UI,loads on top of any explicitly defined or defaulted variablesfrom the calling environment the information defined in theusers ~/.promax file :product stanza if one is presented or theetc/product file if not.



Therefore to have ProManager and the ProMAX UI search thesame suite of locations for executables the ~/.promax fileshould contain a stanza for the ProMAX product and the exesection of the stanza needs to contain a colon delimited list ofpaths to search and where any relative pathnames are withrespect to the current PROMAX_SYS_EXE_HOME or itsdefault.

For Example:

(:product

("P" "ProMAX 2D" "~/promax/main/solaris/exe:."

"~/promax/main/port/menu/promax2d:promax"

"~/promax/main/port/menu/promax/Processes" "promax" "" "" t )

)

Would cause the ProMAX UI to search the users homedirectory via ~/promax/main/solaris/exe and then '.' IE thesupplied or defaulted PROMAX_SYS_EXE_HOME forexecutable files, the directories~/promax/main/port/menu/promax2d and the promax directory inPROMAX_PORT_MENU_HOME for menus and would use the~/promax/main/port/menu/promax/Processes file for the menu list.

In order for proloop to use these same paths the .promaxcontaining this product stanza element must be visible. InProManager this is accomplished by adding aPROMAX_DOT_PROMAX_HOME variable to the environmentcatalog to use that points at the modified .promax.

While this can be the same .promax as used by foreground UIcalls there are occasionally reasons why this may bedifferent. For example the foreground and queue flowpriorities can be adjusted in the .promax passed by theProManager environment catalog if desired.

Sending Error Reports to Support

Some problems are reproducible and can be sent to supportfor problem-solving. To do this, stop ProMANAGER and startit again, directing your console output to a file using thefollowing command:$PROMAX_HOME/port/bin/ProManager | & tee <pathname to logfile>

The logfile and problem description can then be sent tosupport.



File Permissions

The files created in ProMANAGER and from running flowsfrom ProManager inherit their file permissions from theenvironment in which the ProManager script is started.

In a UNIX or Linux environment, your umask (permissions)value is passed to the ProManager server. To change thecurrent umask, add a umask to the ProManager script or tothe java call for the ProManager Client tool. For example:

java -D"umask=000" com.lgc.ProMAX.ProManager.Client

This sets the file permissions wide open.

In a Windows environment, this property must be used. If itis not present the umask defaults to 022.



Glossary

Term Definition

aar_promax ProMAX accounting

API Application Protocol Interface

flow replication process of creating multiple flows, using a template ormaster flow and a set of substitution parameters fordifferent replicas

follow-on switch to indicate a job which may be automaticallysubmitted, upon successful completion of itspredecessor

hold switch indicating a job is not yet ready for submission

jar tar of java binaries

JDBC Java DataBase Connection

JDK Java Development Kit (JRE plus development libraries)

JRE Java Runtime Environment

proloop ProMAX binary which creates new packet files withcommands built by ProMANAGER

regular expression combination of test strings and database variables usedfor parameter substitution



replica a subset of the project data processed through one set offlows. For a large 2D project, a replica is a single 2Dline. For a 3D survey, it could be an individual marinesail line or land acquisition swath during thepreprocessing phase, then a swath, inline range or offsetvolume for further processing.

RMI Remote Method Invocation, used for communicationbetween the Compute and Database Servers

SQL Structured Query Language, a database standard

swing graphics tool kit used by java applets

template master flow into which dataset-dependent parametersare substituted during flow replication

Web browser user interface which displays HTML files

Web server computer configured to host web sites

Term Definition



Appendix A: SQL Commands

This section describes the SQL commands used in MySQLinstallation. For more detailed information, see MySQLdocumentation available in the installation directory. Linksto several tutorials are available from the MySQL homepage.

SQL commands are entered in the following form: bin/mysql [OPTIONS] database_name

• bin/mysql -h: gives commands from outside of theMySQL editor at the UNIX prompt

• bin/mysql followed by a return gets you into the editor

Inside the MySQL editor you will have the mysql> prompt.Enter h or ? to get the commands applicable inside the sqleditor.

• mysql> show tables: you should get a response like:

mysql> show tables;+-----------------+| Tables in mysql |+-----------------+| columns_priv || db || func || host || tables_priv || user |+-----------------+6 rows in set (0.02 sec)

If you make a mistake while typing the input into the sqldatabase you can type a \e to manipulate the commandwithin a vi editor. You can change the command in vi, savethe file and resubmit the command using a semicolon (;),bringing back the last command.

• mysql> select * from user: gives you the contents in theuser table

• mysql> select * from db: allows you to view your data-base

• mysql> select * from hosts: allows you to view yourHost tables



• mysql/support-files/mysql.server stop: stops the sqlserver

• mysql/support-files/mysql.server start: starts the sqlserver

• mysql> quit: exits the mysql> editor

See the following MySQL helpfiles for more information.These files come with the installation in the MySQL directory:

• manual.html

• manual.txt

• manual_toc.html

• mysql-for-dummies



Appendix B: Optional MySQLDatabase Administration

The optional facility exists to set permissions on differentdatabases for different users from different machines.

This is accomplished by adding entries to the host and dbtables

You can use the$PROMAX_HOME/port/bin/MySQLAdminTool to add theseentries if you want to.

This chapter is not intended to be a user guide to MySQL.Here we will only present the tool and it’s usage. It is up tothe user to decide how to make the entries to best provide thedesired database access behavior


Adding Host and Database Entries94 ProMANAGER User Guide

Adding Host and Database Entries

The MySQLAdmin tool in ProMAX

You can use the MySQLAdmin tool in ProMAX to view andedit the contents of the user, host, database tables. After theMySQL database is installed and started, perform thefollowing steps to run the MySQLAdminTool:

1. Set the PROMAX_HOME environment variable.

2. Edit the $PROMAX_HOME/port/bin/MySQLAdminToolscript. You may need to change permissions to edit thisscript. Change the last line in the script from this:

java MySQLAdminTool localhost mysql root

tojava MySQLAdminTool localhost mysql root <rootpw>

Where <rootpw> is your MySQL root password.

You may have to try a few different combinations oflocalhost and the real host name before you get asuccessful connection

java MySQLAdminTool <hostname> mysql root <rootpw>

3. Start the MySQLAdminTool interface:$PROMAX_HOME/port/bin/MySQLAdminTool &



The following interface displays:

If you see these messages in the lower left panel of theinterface "Connection successful""root logged into mysql",proceed to "Single user configuration" step below.

If you see these messages"Connection unsuccessful""java.sql.SQLException: Invalid ... ... (Using password:YES)",you have set a password for root in the previous sectionstep 4, but you misspelled or failed to put this passwordin the MySQLAdminTool script in step 2 above. Revisitthose steps, correct the condition and repeat this step.

If you see these messages"Connection unsuccessful""java.sql.SQLException: Invalid ... ... (Using password:NO)",you did not set a password for root in the previous sectionstep 4, but you did put a password in theMySQLAdminTool script in step 2 above. Revisit thosesteps, correct the condition and repeat this step.

Ifyouseethesemessagesinthelowerleftpane"Connection unsuccessful""java.sql.SQLException: Server configuration denies access to data source",you should exit MySQLAdminTool and follow theseremedial steps:



• cd to your mysql installation location: /usr/bin forLinux, /usr/local/mysql for UNIX.

• Initiate mysql command line access by entering:./mysql -u root -p<root password> mysql

This will give you the mysql prompt: mysql>

• Add the localhost IP address (127.0.0.1) to the MySQLuser table:

mysql> insert into user values \('127.0.0.1','root',password('rootpw'),'y','y','y','y','y','y','n’, \'n','n','y','n','n','y','y');

Note that this is all entered as a single line and you mustinclude the semicolon (;) at the end of the string.Backslashes shown here should not be entered.

• Exit from mysql:mysql> quit

4. As root, stop and restart the service port to make theseusers and databases available. Change the directory toyour MySQL database location and type:

UNIX:./support-files/mysql.server stop


Linux:service mysqld restart



A successful login will show the following display::

You can use the Host and Database table and this GUI toadd entries to set additional permissions that can restrictcertain users from having access to certain databases whenaccess is requested from certain machines

The database access can be summarized as follows:

• The user table fields determine whether to allow or rejectincoming connections. For allowed connections, anyprivileges granted in the user table indicate the user’sprivileges. These privileges apply to all databases on theserver.

The db and host tables are used together:

• The db table fields determine which users can accesswhich databases from which hosts. The privilege fieldsdetermine which operations are allowed.

• The host table is used as an extension of the db tablewhen you want a given db table entry to apply to severalhosts. For example, if you want a user to be able to use adatabase from several hosts in your network, leave theHost value empty in the user’s db table entry, then pop-ulate the host table with an entry for each of those hosts.



NOTE: when using this tool, to enter a blank into a file usethe syntax ’ ’ (two single quotes with a blank in between,


ProMANAGERUser Guide Index

A➲ aar_promax

➲ defined➲ server problems

➲ API, defined➲ Area Parameters icon➲ areas

➲ creating identical structure➲ editing

➲ ASCII file, importing➲ Auto-refresh option

B➲ build

➲ example of good➲ problems➲ troubleshooting

➲ Build icon

C➲ cells

➲ activating in flows➲ editing➲ killing

➲ Common ProMAX database checkbox➲ compute server

➲ configuring➲ configuration

➲ compute server

D➲ data, importing and exporting➲ database

➲ initializing➲ viewing

➲ database server➲ initializing

➲ DBTools icon

Other Docs

E➲ Environment parameters icon➲ environment, setting up➲ error messages

➲ copying a line➲ Explorer

➲ icon➲ exporting data

F➲ File Permissions➲ files, problems importing➲ flow replication, defined➲ flows

➲ building➲ creating identical structure➲ job status setting➲ QCing➲ replicating➲ resubmitting➲ submitting➲ viewing and editing

➲ follow-on, defined

H➲ hold, defined

I➲ icons

➲ navigation window➲ Work window

➲ importing data➲ importing files, problems

J➲ jar, defined➲ JDBC

Known Problems

Index100 ProMANAGER User Guide

10

➲ defined➲ JDK➲ Job Status

➲ icon➲ job.output file, viewing➲ jobs, building➲ JRE

K➲ Kill icon

L➲ lines

➲ creating identical structure➲ editing

➲ Location window➲ menubar

M➲ menubars

➲ Location window➲ navigation window➲ Parameter window➲ ProMAX Explorer Window➲ Status window

➲ monitor aborts➲ MySQL

➲ SQL commands➲ starting on boot

N➲ navigation window➲ newlink default➲ newlink param➲ NT, starting ProMANAGER on

P➲ parameters

➲ substitutingsyntax for multiple fields

➲ substituting in flow template➲ troubleshooting

➲ port conflicts➲ proloop, defined➲ promanager_install, running➲ ProMAX Explorer window

➲ menubar➲ ProMAX UI icon

Q➲ QC

➲ description

R➲ regular expression

➲ defined➲ replica, defined➲ replicating a flow➲ Replication parameters icon➲ Resubmit icon➲ RMI

➲ defined➲ server problems

S➲ server problems➲ SQL commands➲ SQL database

➲ access error➲ configuring➲ installing

➲ SQL, defined➲ String Fill Popup menu➲ Structured Query Language➲ Submit icon➲ substitute parameters

➲ defaulting➲ selecting in flow template➲ troubleshooting

➲ Swing X error➲ swing, defined

T➲ template

➲ build problems

Exit WindowOther Docs Known Problems

Index101 ProMANAGER User Guide

10

➲ building➲ defined➲ editing

➲ template names➲ defined➲ syntax

➲ Template Table icon

U➲ user interface

➲ graphic➲ menubars and icons

W➲ Web browser

➲ defined➲ Web server

➲ defined➲ Windows, starting ProMANAGER on➲ Work window

➲ icons➲ opening

Exit WindowOther Docs Known Problems

Promanager.book

Documents

Transcript of Promanager.book