| Table of Contents |

Installing, licensing and configuring OmniMark Professional Batch Compiler on UNIX

Install OmniMark Professional Batch Compiler by untarring the files into a suitable directory. Once OmniMark Professional Batch Compiler is installed, you must license it.

To license your copy of OmniMark Professional Batch Compiler you must request a license key from Stilo.

To receive and install your license key

STEP 1

Run OmniMark Professional Batch Compiler and issue the -reqkeygen command, saving the output to a file, with the following arguments:

1. The serial number you received when you purchased Professional.
2. The email address you want the license key sent to.
3. A string of your choice that will let you identify the license key you will receive. This is useful if you are licensing several copies of OmniMark Professional Batch Compiler at once.

Here is a sample command line, where SN-Yy3X-ptdi-gpa-u[4 is your serial number and you have saved the contents of the line in the file "req.txt":

ompbc -reqkeygen "SN-Yy3X-ptdi-gpa-u[4" [email protected] "Machine Sol23" > req.txt

OmniMark Professional Batch Compiler will generate a request key and write it to the specified file.

STEP 2

Email the content of the request key file to [email protected]. You will receive a license key by return email.

STEP 3

Create an environment variable called OMNIMARK_INFO and give it the value "AUTH:" followed by your license key. For example: for Bourne shells (sh, ksh, bash and variants):

export OMNIMARK_INFO="AUTH:AU-tuRo-mXA#-+pXV-3rd#-mKfv-Jtnj-4+Q"

If you already have an OMNIMARK_INFO environment variable, you can add your new key to the end of the existing key using a semi-colon as a separator:

export OMNIMARK_INFO="AUTH:fjeie89erhjefiou39;AUTH:AU-tuRo-mXA#-+pXV-3rd#-mKfv-Jtnj-4+Q"

In C shells (csh , tcsh and variants):

setenv OMNIMARK_INFO "AUTH:AU-tuRo-mXA#-+pXV-3rd#-mKfv-Jtnj-4+Q"

or for more than one environment variable

setenv OMNIMARK_INFO "AUTH:fjeie89erhjefiou39;AUTH:AU-tuRo-mXA#-+pXV-3rd#-mKfv-Jtnj-4+Q"

Configure the search paths for OmniMark Professional Batch Compiler

OmniMark Professional Batch Compiler ships with a number of include files, with names ending in ".xin". Your OmniMark scripts can call functions in these libraries. You can also write your own include files or obtain libraries from third parties.

You must configure your system so that OmniMark Professional Batch Compiler can find the include files you install. When you install OmniMark Professional Batch Compiler on a UNIX system, directories containing the include files are not located automatically. You must do one of the following:

• set the OMNIMARK_INCLUDE environment variable (recommended)
• use the -i command-line options

When setting the OMNIMARK_INCLUDE variable under UNIX, paths should be separated by a colon. For example:

OMNIMARK_INCLUDE = /bin/omnimark/lib/:/bin/mystuff/lib/

If you want a specific OmniMark script to use a different set of include files, you can specify their location on the command line using the -i command line option. You can prevent OmniMark Professional Batch Compiler from searching the directories named in the environment or the registry using the -noenvarg or -noea command line option.

When searching for include files, OmniMark Professional Batch Compiler searches in the following order:

1. the current directory
2. paths specified on the OmniMark Professional Batch Compiler command line
3. paths specified in environment variables

  OmniMark 7.1
  EUM105-0204, generated: March 17, 2004 at 02:51:51 pm
  If you have any comments about this section of the documentation, send email to [email protected]