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 WebSphere® Message Broker.
When the <node schema> is the only schema referenced, the broker XML message does not include the extra features contained in WebSphere Message Broker V6.0.
Brokers in previous versions of WebSphere Message Broker do not support multiple schemas, for example, subroutine libraries for reuse. To deploy to a broker 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 V6.0 ESQL syntax in content assist and source code validation. When generating broker ESQL code, the Eclipse tooling can generate V2.1 style code for compatibility with earlier versions.
Without the presence of any of the preceding items, the Eclipse tooling generates broker ESQL without module and funtion Main wrappers. This style is accepted by both V2.1 and V5.0 brokers. However, if you use a V2.1 broker, you cannot use any V5.0 or V6.0 syntax in the code, for example, namespace.
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 ....