:BEGIN_EXT_INTERPRETERS... :END_EXT_INTERPRETERS

Script Statements: They are used to mark the beginning and end of the external interpreter's script in the Process page of Windows and UNIX Job objects . They depend on the system variables UC_EXT_INTERPRETERS_WIN and UC_EXT_INTERPRETERS_UNIX respectively.

Syntax

:BEGIN_EXT_INT[ERPRETERS]Key
External Interpreter Script
:END_EXT_INT[EPRETERS]Key

Value	Description/Format
Key	Interpreter key as defined in UC_EXT_INTERPRETERS_WINDOWS or UC_EXT_INTERPRETERS_UNIX. For more information, see UC_EXT_INTERPRETERS_* - Register External Interpreters.
External Interpreter Script	Contains the script to be used for the external interpreter. The script format is entirely dependent on the external interpreter called.

Warning! You can use more than one external interpreter with this script statement. In that case, use them sequentially. Several external interpreter scripts (of the same or a different external interpreter type) may not cascade or overlap.

Warning! Scripts used in the Process page of a Job object (JOBS) will be overridden by the respective script entries in the parent Workflow object, in case the Job object is part of a workflow.

Tip: Use the :REGISTER_VARIABLE script statement to store return values or data in user defined variables.

Examples

The following example shows a Perl script, which will not only print all file names, the number of all files and the number of all text files, but also store these values in the variables defined with :REGISTER_VARIABLE.

! Transfer resource file (Perl library) from DB to agent
:ATTACH_RES "STORE_LIB", "FUNC1", C

! Prepare resource file path string
:SET &cachepath# = STR_SUB("&$AGENT_RESOURCES_CLIENT#", "\", "\\")
:SET &funcfile# = STR_CAT(&cachepath#,"func.pl")

:BEGIN_EXT_INTERPRETERS perl

# include transferred file
require "&funcfile#";

# Call function "myadd" of library file and print out result
my $val1 = 10;
my $val2 = myadd($val1);
print "calculated via lib function = $val2";

:END_EXT_INTERPRETERS perl