Problem Note 35599: Metadata functions generate an incorrect return code when run on a metadata server that is configured to use non-standard session encoding
If you have configured your SAS® Metadata Server to run with an alternate session encoding such as W3, and you execute a DATA step that uses metadata functions such as METADATA_RESOLVE or METADATA_GETNASN to retrieve objects from the metadata repository, the functions will fail to locate objects that do exist. Consequently, the resulting return codes and output parameter values are incorrect.
You can circumvent the problem by using the KCVT function to transcode the object uri in the metadata function into the corresponding session encoding format used on the metadata server.
For example, instead of this syntax...
object_found=metadata_resolve("omsobj:PhysicalTable?@Id='A5OX3LOE.B6000001'",'PhysicalTable',tableURI);
use this syntax:
object_found=metadata_resolve(kcvt("omsobj:PhysicalTable?@Id='A5OX3LOE.B6000001'",'ebcdic1141'),'PhysicalTable',tableURI);
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Metadata Server | z/OS | 9.2 TS2M0 | 9.2 TS2M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Metadata functions like METADATA_RESOLVE and METADATA_GETNASN fail to locate existing metadata objects when run on MVS with session encoding enabled.
Type: | Problem Note |
Priority: | high |
Topic: | Data Management ==> Data Sources ==> Metadata System Administration ==> Installation ==> NLS (National Language Support) System Administration ==> Servers ==> Metadata
|
Date Modified: | 2009-09-09 12:38:49 |
Date Created: | 2009-04-16 15:18:53 |