How to Set the Dynamic Library Path when Exporting Quality Profiling Projects to Batch (UNIX) - trillium_discovery - trillium_quality - 17.2

Trillium DQ Repository Administrator Guide

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Quality
Trillium > Trillium Discovery
Version
17.2
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium DQ Repository Administrator Guide
First publish date
2008
Last updated
2024-07-01
Published on
2024-07-01T08:53:20.448228

Before you run a batch script for an exported project that contains Trillium Quality profiling processes, you must set the dynamic library path to point to your system's libcore library directory.

This procedure applies to exported Trillium Quality projects that contain one or more of the following profiling processes:

  • Business Rules

  • Dependencies

  • Keys

  • Load

Note: For more information about exporting projects that contain profiling processes, see the Profiling Processes topic in the Trillium Control Center Help.

Note the following:

  • This information applies to Trillium on UNIX systems only.

  • You must be a Trillium repository or systems administrator to complete this procedure.

  • Set the environment variable at any time before you export the project and run it in batch.

  • This procedure permanently sets the dynamic library path in your environment so that you do not have to set it each time you start a session.

To set the dynamic library path on UNIX

  1. Open the settings file, located in your home directory, as shown in the example below.

    Figure 1. .cshrc File Example
  2. Add the dynamic library path to the variable list.

  3. Set it to point to Software/bin directory of your Trillium installation. This is used as the libcore library directory. For example:

    setenv LD_LIBRARY_PATH /.../Linux/17/Software/bin
  4. Save the file.

  5. Source the file, as shown in the following command example:

    source .cshrc