Path variables in upgrade scripts

Previous Next

In upgrade scripts, path variables are allowed in:

INVOKE XML.EXPORT

INVOKE XML.IMPORT

INVOKE USXSL.APPLY2FILE

A path variable must occur at the beginning of the file path:

$$release\custom\myfile.xml

 

 

Path variables in upgrade scripts are resolved when you have the script checked (press the Check button in the Upgrade Scripts box). You can inspect the result in the Output Statement tab (on the right hand side) of the Parameters box.

 

Example 1: XML.EXPORT, path variable

INVOKE XML.EXPORT WITH SELECT

         '$$release\custom\myfile.xml' WriteOutputTo

,        *

FROM     mytable

 

The WriteOutputTo element is required. Otherwise, you can use any SQL including joins and subqueries, but GROUP BY and ORDER BY clauses in the top-level SELECT statement are not allowed.

 

Example 2: XML.IMPORT, path variable

INVOKE XML.IMPORT WITH SELECT

         '$$release\custom\myfile.xml' 

 

 

Example 3: USXSL.APPLY2FILE, path variables

INVOKE USXSL.APPLY2FILE WITH SELECT

         '$$stash\temp\temp1.xml'

,        '$$stash\transformation.xsl'

,        'c:\temp\output.xml'

 

Each of the three elements of the SELECT output list must be string values, as shown, as opposed to column names or expressions with SQL functions. Each element may or may not start with a path variable. For the second element, you are allowed to use the $$xsl placeholder.

 

See Also

Path variables in task step parameters of type SQL Command

Path variables