The ANALYZE statement requires a connection to the Teradata Database when object names are specified in internal RDBMS hexadecimal format (’<...>’XN) on the input statement, because Teradata ARC cannot normally accept object names in internal RDBMS format. Although the ANALYZE statement does not typically require a connection to the Teradata Database, under this circumstance the object names in internal hexadecimal must be translated by the Teradata Database into the external client format (X’...’) to be used by the ARCMAIN program. This connection is done by the LOGON statement.
Failure to make a connection to the Teradata Database results in the object name being skipped by the ANALYZE operation, which produces the following warning message:
ARC0711 DBS connection required to interpret object name. %s skipped.
In addition, when the HEX runtime parameter is executed, the HEX display of object names from the ANALYZE statement is in the external client format (X’...’). This is because object names in ANALYZE statements may contain “hybrid” EBCDIC and kanji EUC, or EBCDIC and kanjiShiftJIS single byte and multibyte characters, which cannot be translated into internal RDBMS format, but can be translated into external client format.
Hybrid object names result when an object is archived that was created:
- In the KANJIEUC or KANJISJIS character set from a KANJIEBCDIC mainframe client
- The hexadecimal representation of the object being archived is not used
In such a circumstance, the Teradata Database cannot properly translate the character set and produces a hybrid object name composed of single byte characters from the EBCDIC character set and multibyte characters from the creating character set (UNIX OS or DOS/V). The hybrid object name cannot be understood by the Teradata Database.