Teradata Preprocessor2 for Embedded SQL. Programmer Guide

Transcription

1 Teradata Preprocessor2 for Embedded SQL Programmer Guide Release B A February 2009

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc. EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of GoldenGate Software, Inc. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, DB2, MVS, RACF, Tivoli, and VM are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI and Engenio are registered trademarks of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. QLogic and SANbox trademarks or registered trademarks of QLogic Corporation. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademarks of SPARC International, Inc. Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a collective membership mark and a service mark of Unicode, Inc. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please teradata-books@lists.teradata.com Any comments or materials (collectively referred to as Feedback ) sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright by Teradata Corporation. All Rights Reserved.

3 Preface Purpose This book provides information about Teradata Preprocessor2 for Embedded SQL, which is a Teradata Tools and Utilities product. Teradata Tools and Utilities is a group of products designed to work with Teradata Database. PP2 is used to incorporate Structured Query Language (SQL) statements into application programs that access data in a Teradata Database. Audience This book is intended for use by application programmers who must incorporate Teradata SQL statements into COBOL, C, or PL/I application programs to access data stored in a Teradata Database. Supported Releases This book supports the following releases: Teradata Database 12.0 Teradata Tools and Utilities Teradata Preprocessor2 for Embedded SQL Note: See Release Number Information on page 26 to verify the Teradata Preprocessor2 for Embedded SQL version number. To locate detailed supported-release information: 1 Go to 2 Navigate to General Search>Publication Product ID. 3 Enter Open the version of the Teradata Tools and Utilities ##.##.## Supported Versions spreadsheet associated with this release. The spreadsheet includes supported Teradata Database versions, platforms, and product release numbers. Teradata Preprocessor2 for Embedded SQL Programmer Guide 3

4 Preface Prerequisites Prerequisites The following prerequisite knowledge is required for this product: Basic computer technology Developing application programs in PL/I, C, or COBOL SQL Teradata Database Changes to This Book The following changes were made to this book in support of the current release. Changes are marked with change bars. For a complete list of changes to the product, see the Release Definition associated with this release. Date and Release July Description Added DML array support for the following platforms: Network Cobol Mainframe C Mainframe Cobol Mainframe PL/I Support for online archive logging was added. Changed application linking instructions for: C on UNIX Micro Focus COBOL on UNIX LPI COBOL on MP-RAS Added support for extended ANSI-compliant Unicode delimited identifiers and character string literals. Added support for query banding. Removed limitation regarding compiling a 32-bit application on a 64-bit Windows EM64T machine. Added Microsoft Windows Vista support. Clarified that, in a mainframe environment, a TDP module must be started prior to precompiling. Additional Information Additional information that supports this product and Teradata Tools and Utilities is available at the web sites listed in the table that follows. In the table, mmyx represents the publication date of a manual, where mm is the month, y is the last digit of the year, and x is an internal 4 Teradata Preprocessor2 for Embedded SQL Programmer Guide

5 Preface Additional Information publication code. Match the mmy of a related publication to the date on the cover of this book. This ensures that the publication selected supports the same release. Type of Information Description Access to Information Release overview Late information Additional product information CD-ROM images Use the Release Definition for the following information: Overview of all of the products in the release Information received too late to be included in the manuals Operating systems and Teradata Database versions that are certified to work with each product Version numbers of each product and the documentation for each product Information about available training and the support center Use the Teradata Information Products Publishing Library site to view or download specific manuals that supply related or additional information to this manual. Access a link to a downloadable CD-ROM image of all customer documentation for this release. Customers are authorized to create CD-ROMs for their use from this image. 1 Go to 2 Select the General Search check box. 3 In the Publication Product ID box, type Click Search. 5 Select the appropriate Release Definition from the search results. 1 Go to 2 Select the Teradata Data Warehousing check box. 3 Do one of the following: For a list of Teradata Tools and Utilities documents, click Teradata Tools and Utilities and then select a release or a specific title. Select a link to any of the data warehousing publications categories listed. Specific books related to Teradata Preprocessor2 for Embedded SQL are as follows: Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems B mmyx SQL Reference: Data Definition Statements B mmyx SQL Reference: Fundamentals B mmyx SQL Reference: Stored Procedures and Embedded SQL B mmyx Teradata Director Program Reference B mmyx 1 Go to 2 Select the General Search check box. 3 In the Title or Keyword box, type CD-ROM. 4 Click Search. Teradata Preprocessor2 for Embedded SQL Programmer Guide 5

6 Preface Additional Information Type of Information Description Access to Information Ordering information for manuals General information about Teradata Use the Teradata Information Products Publishing Library site to order printed versions of manuals. The Teradata home page provides links to numerous sources of information about Teradata. Links include: Executive reports, case studies of customer experiences with Teradata, and thought leadership Technical information, solutions, and expert advice Press releases, mentions, and media resources 1 Go to 2 Select the How to Order check box under Print & CD Publications. 3 Follow the ordering instructions. 1 Go to Teradata.com. 2 Select a link. 6 Teradata Preprocessor2 for Embedded SQL Programmer Guide

7 Table of Contents Preface Purpose Audience Supported Releases Prerequisites Changes to This Book Additional Information Chapter 1: Introduction PP2 Processes Using Static and Dynamic SQL Upgrading PP2 and CLIv Mainframe and Windows Platforms UNIX/LINUX Platforms Supported Operating Systems and Host Programming Languages PP2 Input PP2 Output Contents of PP2 Output Listing Release Number Information OPTIONS, SOURCE, and XREF Sections PRINT Option Diagnostic Messages Client Language Source Code Server Failure and Recovery PP2 Behavior Application Behavior Query Banding Finding Information Teradata Preprocessor2 for Embedded SQL Programmer Guide 7

8 Table of Contents Chapter 2: Connecting to the Database and Invoking PP Connecting to the Teradata Database PP2 Connection Runtime Execution Connection Explicit Connection Implicit Connection Invoking PP IBM Mainframe Environment: z/os and z/vm CMS Network-Attached Environments PP2 Options How to Read the Option Syntax APOST QUOTE -a -q APOSTSQL QUOTESQL -as -qs CHARSET(charset) -cs charset CURPREFIX(prefix) -c prefix DATABASE(dbname) -db dbname DATE(D E I J U) -d D E I J U DYNPREFIX (prefix) -dp prefix FLAG(I W E S) -f I W E S INPUT(file spec) -i filespec ld logdata LINECOUNT(integer) -lc integer lm logmech MARGINS(m,n[,c]) -m m,n[,c] NULLSCAN NONULLSCAN -ns -nns OPTIONS NOOPTIONS -lo -nlo PRINT[(file spec)] NOPRINT -l [filespec] -nl Teradata Preprocessor2 for Embedded SQL Programmer Guide

9 Table of Contents PUNCH[(file spec)] NOPUNCH -o [filespec] -no SOURCE NOSOURCE -ls -nls SQLCHECK(FULL NOSYNTAX) -sc FULL NOSYNTAX SQLFLAGGER (NONE ENTRY INTERMEDIATE) -sf (NONE ENTRY INTERMEDIATE) TDPID(tdpid network group name) -t tdpid network group name TERM[(file spec)] NOTERM -e [filespec] -ne TRANSACT(ANSI BTET COMMIT 2PC) -tr ANSI BTET COMMIT USERID(userid[,password[,accountid]]) -u userid[,password[,accountid]] VERSION(COBOL COBOLII COBOL3) -v MF1 MF2 LPI XREF NOXREF -lx -nlx Chapter 3: Writing Embedded SQL Applications in C C Language Support Program Status Information Teradata Mode Communications Area ANSI-Compatible Mode Communications Variables BIGINT Support C Coding Considerations Embedded SQL Statement Format Array Support Comments Continuation for SQL Statements Dynamic SQL Including Code Margins Sequence Numbers SQL Strings Statement Labels String Delimiters User Defined Functions Multi-Session Programming Considerations Teradata Preprocessor2 for Embedded SQL Programmer Guide 9

10 Table of Contents Special Considerations Host Variables Using C Structures as Output Host Variables Using C Structures as Input Host Variables Example Overview Requirements for Host Variables C Language and Host Variables SQL and Host Variables Indicator Variables PP2 Issues Host Variable Declaration Host Variable Values Server to Host Assignment Conversion Rules Byte String Assignment Character Assignment Single Character Data Varying Character Data Character String Data Character String Padding Character Truncation Numeric Value Assignment Date Assignment Host to Server Assignment Assignment Rules Host Variable Declaration Indicator Variables Rules for Indicator Variables Indicator Variables and Input Indicator Variables and Output Indicator Variables and Structures SQL Error Return ANSI Mode SQLCODE Variable SQLSTATE Variable Using PPRTEXT to Retrieve Return Codes SQL Error Return Teradata Mode SQLCODE Field Using PPRTEXT to Retrieve Return Codes Exception Conditions: WHENEVER Exception Conditions WHENEVER Is Declarative Rules for Using WHENEVER Teradata Preprocessor2 for Embedded SQL Programmer Guide

11 Table of Contents Dynamic Statement Example A Caution When Using Dynamic SQL Include SQLDA Example Multi-Session Programming Online Archive Performing a Stored Procedure Using Stored Procedure Dynamic Result Sets Using UPSERT in Embedded SQL Chapter 4: Writing Embedded SQL Applications in COBOL COBOL Language Support COBOL Application Requirements Program Status Information Teradata Mode Communications Area ANSI-Compatible Mode Communications Variables BIGINT Support Large Decimal Support COBOL Coding Considerations Array Support Embedded SQL Statement Format Comments Continuation for SQL Statements Dynamic SQL Including Code Margins Paragraph Names Sequence Numbers SQL Strings String Delimiters APOSTSQL Example QUOTESQL Example User Defined Functions Multisession Programming Considerations Special Considerations Host Variables Using COBOL Structures as Output Host Variables Using COBOL Structures as Input Host Variables Example Overview Teradata Preprocessor2 for Embedded SQL Programmer Guide 11

12 Table of Contents Requirements for Host Variables COBOL and Host Variables SQL and Host Variables PP2 Issues Host Variable Values Server to Host Assignment Host to Server Assignment Host Variable Declaration Indicator Variables Rules for Indicator Variables Indicator Variables and Input Indicator Variables and Output Indicator Variables and Structures SQL Error Return ANSI Mode SQLCODE Variable SQLSTATE Variable Using PPRTEXT to Retrieve Return Codes SQL Error Return Teradata Mode SQLCODE Field Using PPRTEXT to Retrieve Return Codes Exception Conditions: WHENEVER Exception Conditions WHENEVER Is Declarative Rules for Using WHENEVER Dynamic Statement Example Online Archive Chapter 5: Writing Embedded SQL Applications in PL/I PL/I Language Support PL/I Application Requirements Program Status Information Teradata Mode Communications Area ANSI-Compatible Mode Communications Variables BIGINT Support Large Decimal Support PL/I Coding Considerations Array Support Embedded SQL Statement Format Teradata Preprocessor2 for Embedded SQL Programmer Guide

13 Table of Contents Comments Continuation for SQL Statements Dynamic SQL Including Code Macro Processor Margins Sequence Numbers SQL Strings Statement Labels String Delimiters Multi-Session Programming Considerations Special Considerations Host Variables Using PL/I Structures as Output Host Variables Using PL/I Structures as Input Host Variables Example Overview Requirements for PL/I Host Variables Server to Host Assignment Conversion Rules Byte String Assignment Character String Assignment String Truncation Numeric Value Assignment Date Assignment Host to Server Assignment Graphic Literals for Multibyte Characters Host Variable Declaration Indicator Variables Rules for Indicator Variables Indicator Variables and Input Indicator Variables and Output Indicator Variables and Structures SQL Error Return ANSI Mode SQLCODE Variable SQLSTATE Variable Using PPRTEXT to Retrieve Return Codes SQL Error Return Teradata Mode SQLCODE Field Using PPRTEXT to Retrieve Return Codes Exception Conditions: WHENEVER Exception Conditions WHENEVER Is Declarative Teradata Preprocessor2 for Embedded SQL Programmer Guide 13

14 Table of Contents Rules for Using WHENEVER Dynamic Statement Example Online Archive Appendix A: SQL Data Type Codes Data Type Codes Unused/Internal Data Type Codes Appendix B: Sample Application Linkage Procedure Overview Bit Platform Linking Concerns Application Linking for z/os Application Linking for CICS Application Linking for IMS Application Linking for z/vm CMS Application Linking for C on UNIX Linkage Script for a 64-Bit Application on AIX Linkage Script for a 64- Bit Application on Itanium HP-UX Linkage Script for a 64-Bit Application on 64-Bit Itanium RH Linkage Script for a 32-Bit Application on Opteron Solaris Linkage Script for a 64-Bit Application on Opteron Solaris Application Linking for Micro Focus COBOL on UNIX Linkage Script for a 64-Bit Application on AIX Script Notes Application Linking for LPI COBOL on MP-RAS Application Linking for Visual C++ on Windows Appendix C: Embedded SQL Examples About the Examples LAB Files Setting Up the Examples Teradata Preprocessor2 for Embedded SQL Programmer Guide

15 Table of Contents Procedure Overview z/os Operating Systems Where to Find Source Code and LAB Files Which Setup Files to Use z/os JCL Network-Attached Operating Systems Where to Find Source Code and LAB Files Which Setup Files to Use z/vm Operating Systems Where to Find Source Code and LAB Files Which Setup Files to Use z/vm EXEC Operator Messages EMPLOYEE Table Source Code LAB6 and LAB7 Macros Source Code EMPLOYEE Table Glossary Index Teradata Preprocessor2 for Embedded SQL Programmer Guide 15

16 Table of Contents 16 Teradata Preprocessor2 for Embedded SQL Programmer Guide

17 List of Figures Figure 1: PP2 Operation Teradata Preprocessor2 for Embedded SQL Programmer Guide 17

18 List of Figures 18 Teradata Preprocessor2 for Embedded SQL Programmer Guide

19 List of Tables Table 1: Upgrading PP2 and CLIv2 on UNIX and LINUX Table 2: Supported Host Programming Languages Listed by Operating System Table 3: OPTIONS, SOURCE, and XREF Section Information Table 4: Teradata-Defined Character Sets for Mainframe Environments Table 5: Site-Defined Character Sets for Mainframe Environments Table 6: Teradata-Defined Character Sets for Network-Attached Environments Table 7: Site-Defined Character Sets for Network-Attached Environments Table 8: C Definitions for Teradata Database Data Types Table 9: COBOL Definitions for Teradata Database Data Types Table 10: PL/I Definitions for Teradata Database Data Types Table 11: SQL Data Type Codes Teradata Preprocessor2 for Embedded SQL Programmer Guide 19

20 List of Tables 20 Teradata Preprocessor2 for Embedded SQL Programmer Guide

21 CHAPTER 1 Introduction Teradata Preprocessor2 for Embedded SQL, PP2, provides an easy-to-use method of accessing data stored in the Teradata Database. PP2 does this by interpreting and expanding Teradata SQL statements that have been embedded in an application program. Interpretation of the statements allows the program to perform tasks supported by Teradata SQL, such as data retrieval. The application program is called an embedded SQL host program. The language in which the host program is written is called the host programming language. Therefore, the host program consists of Teradata SQL code that provides the database interface, plus the host programming language, which provides remaining instructions for application execution. Review the next sections in this chapter for information on: PP2 Processes Using Static and Dynamic SQL Upgrading PP2 and CLIv2 Supported Operating Systems and Host Programming Languages PP2 Input PP2 Output Contents of PP2 Output Listing Diagnostic Messages Client Language Source Code Server Failure and Recovery Finding Information PP2 Processes PP2 includes a precompiler as well as the services that execute, or provide runtime support for a compiled application. A precompiler is necessary to interpret the embedded SQL statements in the host program. Regardless of the host language, PP2 operation consists of two stages: 1 The precompile phase, which precedes application compilation and linking. 2 Execution, or runtime support, of the application. During precompilation, PP2 reads and replaces all the SQL statements embedded in the host program with CLIv2 calls that are acceptable to the native compiler for the host language. The host programming language syntax remains unchanged. Teradata Preprocessor2 for Embedded SQL Programmer Guide 21

22 Chapter 1: Introduction PP2 Processes At runtime, the inserted syntax runs in conjunction with Call-Level Interface version 2 (CLIv2) and Teradata Director Program (TDP) modules to provide an efficient, convenient interface between the application program and the Teradata Database. Note: In a mainframe environment, a TDP module must be started prior to PP2 performing the precompile step, even if no data access is required (that is, using NOSYNTAX). The following example uses a COBOL program to show the operations PP2 performs, from logging on to the Teradata Database through precompilation. The process is similar for other languages: 1 Logs a session onto the Teradata Database and determines whether it is to be a Teradata mode or ANSI-compatible mode session. 2 Checks the syntax of SQL statements in the host language source program, validating database objects against the entries in the Data Dictionary. 3 Builds code in the DATA division for the data elements. 4 Builds code in the PROCEDURE division to handle SQL statement passing to the Teradata Database. 5 Comments out the SQL source code. 6 Produces COBOL source for input to the COBOL compiler. Figure 1 gives a high-level view of starting with a PL/I embedded SQL program as the source input file, then precompiling, compiling, linking, and finally, running the PL/I program. Figure 1: PP2 Operation PL/I PP2 PL/I embedded SQL programs CICS precompiler In CICS environment precompiler Translates embedded SQL into appropriate host language COMPILE LOAD/LINK (For CICS, use Teradata CICS libraries) EXECUTION Execute program with communication to Teradata RDBMS 2446B Teradata Preprocessor2 for Embedded SQL Programmer Guide

23 Chapter 1: Introduction Using Static and Dynamic SQL Using Static and Dynamic SQL Both static and dynamic SQL statements are allowed in the embedded SQL host program. Static SQL statements, as the name implies, remain static each time the program is run. Dynamic SQL statements are built at runtime. To use static SQL statements in a host program, be sure to know the SQL statement type, plus database table and column names when the program is written. Only the specific data values the statement is looking for are unknown. Use host language variables to represent those unknown values. For example, use a static SQL statement to enter an order, and a host language variable to represent the quantity of an item in the order. Because static SQL statements are hard-coded into the program, the statements require parsing, and so forth, only once. Therefore, using static SQL tends to result in faster processing. Dynamic SQL is useful for programs where the content of a SQL statement is un-known at the time the program is written. For example, an interactive application that prompts the user for a table name, would be a good situation in which to use dynamic SQL. Each host programming language handles dynamic SQL statements differently. Refer to Writing Embedded SQL Applications in C, Writing Embedded SQL Applications in COBOL, Writing Embedded SQL Applications in PL/I, and Embedded SQL Examples for more information. Upgrading PP2 and CLIv2 Mainframe and Windows Platforms When upgrading to a newer version of the Teradata Database, install the latest versions of Teradata Preprocessor2 for Embedded SQL and CLIv2.When you upgrade to a newer version of Teradata Warehouse, install the latest versions of PP2 and CLIv2. UNIX/LINUX Platforms If you have not made changes to the source code in your existing application programs, execute your programs using the latest versions of PP2 and CLIv2. It is not necessary to precompile, compile, and link the existing applications again. If you have made changes to the source code in the existing application programs, run the PP2 precompiler, compile, then link the applications. When you upgrade to a newer version of Teradata Warehouse, install the latest versions of PP2 and CLIv2. Refer to Table 1 for instructions on whether or not it is necessary to precompile, compile, and link existing applications before executing them with the new PP2 and CLIv2 versions. Teradata Preprocessor2 for Embedded SQL Programmer Guide 23

24 Chapter 1: Introduction Supported Operating Systems and Host Programming Languages Table 1: Upgrading PP2 and CLIv2 on UNIX and LINUX Have you made changes to the source code in your existing application program? 32-Bit Platforms 64-Bit Platforms no Relink the application with the latest PP2 runtime library. If the application was last precompiled with TTU 8.2 PP2, relink the application with the latest PP2 runtime library. If the application was last precompiled with a version of PP2 earlier than TTU 8.2 PP2: precompile, compile, then link the application again. yes Precompile, compile, then link the application again. Supported Operating Systems and Host Programming Languages PP2 operates with host programming languages in several environments: Table 2: Supported Host Programming Languages Listed by Operating System Operating System HP-UX 11.0, 11.11, and 11i (PA-RISC 2) (32- bit) HP-UX 11.0, 11.11, and 11i (PA-RISC 2) (64- bit) HP-UX and (Itanium) (64-bit) IBM AIX 5.1 (32-bit) IBM AIX 5.2 (64-bit) IBM AIX 5.1 (64-bit) IBM AIX 5.2 (32-bit) IBM AIX 5.3 (32-bit) IBM AIX 5.3 (64-bit) IBM z/os (MVS) Note: USS is not supported. IBM z/vm Microsoft Windows bit SP4 Host Programming Language C and Micro Focus COBOL (32-bit) C (32-bit or 64-bit) C (64-bit) C and Micro Focus COBOL (32-bit) C (32-bit and 64-bit) C (32-bit and 64-bit) C and Micro Focus COBOL (32-bit) C and Micro Focus COBOL (32-bit) C and Micro Focus COBOL (64-bit) SAS/C, IBM COBOL, IBM PL/I (32-bit) SAS/C, IBM COBOL, IBM PL/I (32-bit) C (32-bit) 24 Teradata Preprocessor2 for Embedded SQL Programmer Guide

25 Chapter 1: Introduction Supported Operating Systems and Host Programming Languages Table 2: Supported Host Programming Languages Listed by Operating System (continued) Operating System Microsoft Windows.NET Server 2003 (32-bit or 64-bit) Microsoft Windows Server 2003, Standard Edition/Enterprise Edition on Intel EM64T Microsoft Windows Vista Microsoft Windows XP Professional (32-bit or 64-bit) Microsoft Windows XP Professional on Intel EM64T Novell SUSE Linux Enterprise 9 on 32-bit Intel x86 Novell SUSE Linux Enterprise 9 on Intel EM64T Novell SUSE Linux Enterprise 9 and 10 on 64-bit AMD Opteron RedHat Enterprise Linux Advanced Server 4.0 on AMD Opteron Red Hat Linux Advanced Server 2.1 and 3.0 (32-bit) RedHat Linux Advanced Server 4.0 on 32-bit Intel x86 RedHat Linux Advanced Server 4.0 on Intel EM64T Red Hat Linux Advanced Server 4.0 and above on 64-bit AMD Opteron Red Hat Linux Itanium 64-bit Advanced Server 3.0 SUN Solaris 8 and 9 SPARC (32-bit) SUN Solaris 8 and 9 SPARC (64-bit) SUN Solaris 10 on 64-bit AMD Opteron Host Programming Language C (32-bit and 64-bit) C (32-bit and 64-bit) C (32-bit and 64-bit) C (32-bit and 64-bit) C (32-bit and 64-bit) C (32-bit) C (32-bit and 64-bit) C (32-bit and 64-bit) C (32-bit and 64-bit) C (32-bit) C (32-bit) C (32-bit and 64-bit) C (32-bit and 64-bit) C (64-bit) C (32-bit) C (32-bit and 64-bit) C (32-bit and 64-bit) UNIX MP-RAS C, Micro Focus COBOL and LPI COBOL (32- bit) Note: The IBM mainframes are channel-attached to the NCR hardware platform running the Teradata Database. Other environments are referred to as network-attached systems. Teradata Preprocessor2 for Embedded SQL Programmer Guide 25

26 Chapter 1: Introduction PP2 Input PP2 Input The PP2 input file is the embedded SQL host program (also called the source input file). Depending on the program environment, one or more additional files are required in addition to the PP2 input file if when using an SQL INCLUDE statement.the PP2 input file is the embedded SQL host program (also called the source input file). Depending on the program environment, one or more additional files are required in addition to the PP2 input file if you use a SQL INCLUDE statement. PP2 Output The source output program is the source input program as modified by PP2. Modifications to the program include: Inclusion of host language comments that identify the program as output from PP2 and that provide the date and time of precompilation. These comments are inserted near the beginning. Conversion of all embedded Teradata SQL statements to host language comments. Insertion of host data variable declarations and procedural statements to implement the embedded Teradata SQL statements. Contents of PP2 Output Listing The output listing is headed by release number and date and time information (see Release Number Information on page 26). The next three sections of the listing are based on the OPTIONS, SOURCE, and XREF PP2 options (see OPTIONS, SOURCE, and XREF Sections on page 27). The line-by-line listing of the input program is augmented by: An analysis of the PP2 options specified and defaulted Input line numbers assigned by PP2 PP2 diagnostics Cross-references of host variables, cursor, and dynamic statement names A summary of diagnostics A summary of input and output file record counts Release Number Information The first block of the PP2 output listing indicates the date and time of compilation, the PP2 release number, and, if known, the Teradata Database release number. When precompiling using the NOSYNTAX option or if the Teradata Database level is earlier than V2R6.2, the 26 Teradata Preprocessor2 for Embedded SQL Programmer Guide

27 Chapter 1: Introduction Contents of PP2 Output Listing Teradata Database release number does not display. Here is an example where the Teradata Database release number is not known: /* THIS PROGRAM WAS PREPROCESSED ON JAN 30, 2006 AT 12:08:48 BY THE C PREPROCESSOR2 PREPROCESSOR SOFTWARE RELEASE: PP DBS N/A */ OPTIONS, SOURCE, and XREF Sections Table 3: OPTIONS, SOURCE, and XREF Section Information Section The section contains: Output/suppression of this section is controlled by this option: Other information OPTIONS PP2 options that have been specified at invocation options used by PP2 option errors detected by PP2 OPTIONS/NOOPTIONS This section does not contain specified userid. SOURCE the same source that is input to PP2. The section format depends on the host language and includes line numbers known to PP2 and any included lines brought in via EXEC SQL INCLUDE statements. source errors detected by PP2 SOURCE/NOSOURCE - XREF host variable, cursor, and dynamic statement declarations and usages summary of input/output records summary of the warnings and errors detected by PP2 XREF/NOXREF Asterisks in the variable declaration type field indicate that the size of the field exceeds the capability of the cross reference. However, this variable remains valid for use in SQL requests. Teradata Preprocessor2 for Embedded SQL Programmer Guide 27

28 Chapter 1: Introduction Diagnostic Messages PRINT Option The PRINT option must be in effect for the output listing to be produced. The listing is placed in the file specified or defaulted for the PRINT option. No listing is produced if the NOPRINT PP2 option is specified. Diagnostic Messages Message Form Diagnostic messages returned by PP2 occupy two lines and take the following form: SPPnnnn <severity>, at line nnn, column nn: <diagnostic message text> where <severity> is one of the following: Warning SQL Flagger Warning Error Severe Error Fatal Error SPPnnnn is an identifying value unique to PP2. The qualifying phrases at line nnn and column nn vary to suit conditions. If the diagnostic originates with the Teradata Database, the message begins with a four digit Teradata error code. See Messages. Client Language Source Code PP2 produces client language source code as a result of the precompilation. Code generation is enabled or suppressed via the PUNCH/NOPUNCH option. The code is placed in the file specified or is defaulted for the PUNCH option. No code is produced if the NOPUNCH PP2 option is specified. C and COBOL code generation is also suppressed if an error is encountered during the precompilation phase. Server Failure and Recovery This section describes the behavior of PP2 and Teradata Database-generated applications when they encounter a node reset. 28 Teradata Preprocessor2 for Embedded SQL Programmer Guide

29 Chapter 1: Introduction Server Failure and Recovery PP2 Behavior If Teradata Preprocessor2 for Embedded SQL is running on a Resetting node Non-Resetting node LAN-attached client Channel-attached client Then it aborts. Preprocessing must be restarted after the node resets. This is equivalent to the situation where a utility or application is initiated on an external client that fails. reconnects its session (if connected to a server) and the current SQL statement undergoing a syntax check returns an error. Restart preprocessing to ensure complete syntax checking. Application Behavior The behavior of Teradata Database-generated applications in the event of a node resetting depends on the: Crash notification setting Type of node on which PP2 is running Application Behavior on a Resetting Node IF a PP2-generated application is running on a Resetting node THEN it aborts. Restart the application after the node resets. This is equivalent to the situation where a utility or application is initiated on an external client that fails. Setting Crash Notification Specify crash notification behavior with the SET CRASH statement, which sets the following wait_across_crash (WAC) and tell_about _crash (TAC) options: IF specified... THEN WAC is set to... AND TAC is set to... WAIT_NOTELL Y N NOWAIT_TELL N Y The default settings for these options are: wait_across_crash (WAC) = Y tell_about_crash (TAC) = N Teradata Preprocessor2 for Embedded SQL Programmer Guide 29