The PATH clause specifies a list of additional schemas to be searched when matching function and procedure calls to their implementations. The schema in which the call lies is implicitly included in the PATH clause.
The PATH clause is used to resolve unqualified function and procedure names in the tools according to the following algorithm.
When you start a function or procedure, the name that you use must be qualified by the schema name. The behavior depends on the circumstances:
If a matching function exists in one schema, it is used. A compile-time error occurs if a matching function exists in more than one schema. If there is no matching function, then the schema SQL is searched.
This rule and the preceding rule imply that a local module routine takes priority over a built-in routine of the same name.
If a matching function exists in one schema, it is used. A compile-time error occurs if a matching function exists in more than one schema. If there is no matching function, the schema SQL is searched.
This rule and the preceding rule imply that a local schema routine takes priority over a built-in routine of the same name.
The <node schema> is defined as the schema containing the node's message flow.
The <node schema> is specified in this manner to provide compatibility with earlier versions of IBM® Integration Bus.
When the <node schema> is the only schema referenced, the integration node XML message does not include the extra features contained in WebSphere® Message Broker Version 6.1.
Integration nodes in previous versions of IBM Integration Bus do not support multiple schemas, for example, subroutine libraries for reuse. To deploy to an integration node in a previous version of the product, put all of the ESQL subroutines into the same schema as the message flow and node that start the ESQL subroutines.
Eclipse tooling uses WebSphere Message Broker Version 6.1 ESQL syntax in content assist and source code validation.
Without the presence of any of the preceding items, the Eclipse tooling generates integration node ESQL without module and funtion Main wrappers.
Function and procedure names must be unique within their schema or module.
BROKER SCHEMA CommonUtils
PATH SpecialUtils;
MODULE ....
The next example adds a path to the default
schema:PATH CommonUtils, SpecialUtils;
MODULE ....