Multi-statement-errors - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

Product
Call-Level Interface Version 2
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

Multi‑statement‑errors is a one byte EBCDIC field that indicates whether each statement in a multi‑statement request may reflect an error for certain limited conditions using the StatementError parcel.

 

In this language...

The variable name for Column‑info is...

COBOL

MULTI‑STATEMENT‑ERRORS

PL/I

MULTI_STATEMENT_ERRORS

C

multiStatementErrors

IBM Assembler

DBRIMSE

 

This routine...

Does this for Multi‑statement‑errors...

DBCHINI

writes

DBCHCL

reads (RSUP; IRQ; IWPF)

 

Multi‑statement‑errors is used by...

To...

applications

write

One of the following values may be set before initiating a request:

  • 'N' (DBRIMSEN for Assembler, DBC_MultiStmtErrsNo for C, DBC‑NO for COBOL, DBC_MULTI_STMT_ERRS_NO for PL/I), indicates that a problem with any statement in a multi-statement request ends processing of that request.
  • 'Y' (DBRIMSEY for Assembler, DBC_MultiStmtErrsYes for C, DBC‑YES for COBOL, DBC_MULTI_STMT_ERRS_YES for PL/I) indicates that certain problems with a statement in a multi-statement request allows other statements to be processed.
  • The default setting is 'N'.

    With Multi‑statement‑errors=N, a problem with any statement in a multi-statement request results in a single Failure parcel indicating which statement had the problem; none of the statements were executed. With Multi‑statement‑errors=Y, processing is the same unless all errors are of certain limited types, in which case the response to statements having those problems is a StatementError parcel; the response to all other statements are the usual Success, OK, or StatementStatus parcels.