Etapa de seguimiento

The following items can be configured:

Usage of a template for launch script generation [New in v2.2]

configuration file line : SCRIPT_TEMPLATE | <template file path>

command line argument : -script <template file path>

default value : no script template

<template file path> is the path of a template file containing keywords that are replaced

by the solver manager with the launch parameters received from the GUI. The filled template is then executed by the solver manager. If no template file is specified, the solver manager uses its own built-in template (same behavior than previous versions). This option is available on Unix/Linux systems only.

See Defining a Template File for the Launch Script, below, for more details about defining a template file.

PRODUCT START UP Solver Manager Configuration Command used to launch a calculation in "batch" mode

configuration file line : BATCH_COMMAND | <batch cmd>

command line argument : -batchcmd <batch cmd>

default value : batch

<batch cmd> is the name of the command used in batch mode to launch the solver.

Name of the linked library path environment variable on Unix/Linux systems configuration file line : LIBRARY_VARIABLE | <lib var>

command line argument : -libvariable <lib var>

default value : DEFAULT

<lib var> can be an environment variable name (LD_LIBRARY_PATH for example) or a keyword:

DEFAULT : the environment variable name depends on the operating system: - IRIX : LD_LIBRARY_PATH

- HPUX : SHLIB_PATH and LD_LIBRARY_PATH are both set - SOLARIS : LD_LIBRARY_PATH

- AIX : LIBPATH and LD_LIBRARY_PATH are both set - DIGITAL : LD_LIBRARY_PATH

Automatic setting of the linked library path environment variable on Unix/Linux systems

configuration file line : LIBRARY_PATH | <lib path>

command line argument : -libpath <lib path>

default value : NONE

<lib path> can be a standard path (/usr/lib for example) or a keyword: NONE : do not set the library path environment variable SOLVER_DIRECTORY : set the library path environment variable as the solver

directory path

Automatic setting of the multi-processor environment variable configuration file line : MP_VARIABLE | <mp var>

command line argument : -mpvariable <mp var>

default value : NONE

<mp var> can be an environment variable name or a keyword:

PRODUCT START UP Solver Manager Configuration

DEFAULT : set an environment variable whose name depends on the operating system: - IRIX : MP_SET_NUMTHREADS - HPUX : MP_NUMBER_OF_THREADS - SOLARIS : PARALLEL - AIX : XLSMPOPTS='parthds... - DIGITAL : MP_STACK_SIZE

Path and name of the solver manager log file

configuration file line : SERVER_LOG_FILE | <log file>

command line argument : -output <log file>

default value : blank (no file)

<log file> is the full name of the log file (eg: /usr/tmp/solvermanager.log) Port number on which the solver manager listens to requests

configuration file line : SERVER_PORT | <port id>

command line argument : -port <port id>

default value : 1201

<port id> is the port number on which the solver manager listens to the requests.

Version of the communication with the GUIs protocol

configuration file line : SERVER_PROTOCOL_VERSION | <version>

command line argument : not available by command line

default value : depends on the version of the solver manager (2 for v2.2)

<version> is a number from 1 to n.

Note:

· A GUI and a solver manager can always communicate whatever their version is

(full compatibility). The user should never need to modify this option.

Path of the temporary directory

configuration file line : TEMP_DIRECTORY | <tmp dir>

command line argument : -tmpdir <tmp dir>

default value : /usr/tmp

<tmp dir> is the path of the directory where the solver manager will write launch

PRODUCT START UP Solver Manager Configuration Save the launch script generated by the solver manager

configuration file line : SAVE_LAUNCH_SCRIPT | YES / NO command line argument : -savelaunchscript

default value : NO

When this option is enabled, the launch script generated by the solver manager in its temporary directory is not deleted once the solver is launched but renamed to

smgr_launch_script. This allows for example to check / modify this script and restart it in a console to track a launch problem. Note that all scripts are renamed to the same name; it is advised to work with a copy of smgr_launch_script which will be overwritten by subsequent launches.

Enable the sourcing of profiles files (sh and ksh environments)

configuration file line : SOURCE_PROFILE | YES / NO command line argument : -nosourceprofile

default value : YES

When this option is disabled, the launch script generated by the solver manager will not include execution of /etc/.profile and $HOME/.profile files. This can be useful

if these files contain instructions that make the launch fail.

Force automount before entering directories [New in v2.2]

configuration file line : FORCE_AUTOMOUNT | YES / NO command line argument : -forceautomount

default value : NO

When this option is enabled, the solver manager calls some “list directory” commands to trigger automount of some directories before trying to enter them (just entering a directory might not trigger automount on old systems). This option should not be activated if no problem occurs with automount.

Delay before deleting scripts [New in v2.2]

configuration file line : SCRIPT_CLEANUP_DELAY | <delay>

command line argument : -scriptcleanupdelay <delay>

default value : 5 (seconds)

This option allows defining the delay (in seconds) before the solver manager deletes a script it has just launched.

PRODUCT START UP Solver Manager Configuration

Defining a Template File for the Launch Script