10.12.2012 Views

Oracle C++ Call Interface Programmer's Guide

Oracle C++ Call Interface Programmer's Guide

Oracle C++ Call Interface Programmer's Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

OTT Utility Reference<br />

CONFIG Parameter<br />

This parameter specifies the name of the OTT configuration file to be used. The<br />

configuration file lists commonly used parameter specifications. Parameter<br />

specifications are also read from a system configuration file found in an operating<br />

system-dependent location. All remaining parameter specifications must appear<br />

either on the command line or in the INTYPE file.<br />

CONFIG=filename<br />

Note: The CONFIG parameter can only be specified on the OTT<br />

command line. It is not allowed in the CONFIG file.<br />

CPPFILE Parameter<br />

For <strong>C++</strong> only. This parameter specifies the name of the <strong>C++</strong> source file that will<br />

contain the method implementations generated by the OTT utility.<br />

This parameter is required under the following conditions:<br />

■ A type not mentioned in the INTYPE file must be generated and two or more<br />

CPPFILEs are being generated. In this case, the unmentioned type goes in the<br />

CPPFILE specified on the command line.<br />

■ The INTYPE parameter is not specified, and you want the OTT utility to<br />

translate all the types in the schema.<br />

The restrictions to this are similar to that of the existing HFILE parameter<br />

restrictions already in place for Pro*C/<strong>C++</strong> and OCI. This parameter is optional<br />

when the CPPFILE is specified for individual types in the INTYPE file.<br />

CPPFILE=filename<br />

ERRTYPE Parameter<br />

If you supply this parameter, then a listing of the INTYPE file is written to the<br />

ERRTYPE file, along with all information and error messages. Information and error<br />

messages are sent to the standard output whether or not the ERRTYPE parameter is<br />

specified.<br />

Essentially, the ERRTYPE file is a copy of the INTYPE file with error messages<br />

added. In most cases, an error message will include a pointer to the text that caused<br />

the error.<br />

How to Use the Object Type Translator Utility 7-121

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!