If table names, physical paths, or other attributes in a job are specified as parameters
and those parameters resolve to literal values that contain
characters other than letters, numeric digits (such as 0 through 9), or underscores,
then code generation for the job might fail.
If code generation for a parameterized job fails, check the log for an error message
that says:
NOTE:
Special characters encountered; References may require: %unquote(&<name>);
If you see this message,
use the %unquote(&<name>); syntax to resolve the parameter value correctly during execution of the generated
code. For example, suppose that the metadata for an external file specified its physical
path as the parameter &srcpath. When code is generated for the external file, the
&srcpath parameter expands to a string that included slashes and the job fails.
To enable the job to run, open the properties window for the external file, go to
the field where the
&srcpath parameter is specified, and enter the following string:
%unquote(&srcpath);
After this change, the
resolution of the parameter value for the generated code can handle
special characters, and the path no longer causes an error.