Return Codes That Do Not Reach the Application - Call-Level Interface Version 2

Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Call-Level Interface Version 2
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-06-12
dita:mapPath
zws1641280432166.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
B035-2418
Product Category
Teradata Tools and Utilities

Some return codes do not reach the application. For example, EM_BUFSIZE (203) is detected and corrected by CLI without the application’s intervention. Or again, the EM_NODATA (211) and EM_DATAHERE (212) return codes are alternates, but CLI filters out EM_DATAHERE; the application must therefore test for EM_DATAHERE by testing for the absence of EM_NODATA.

At times, application programs may print, to stderr, messages that have the word net/oserr and a number code. The code shown is generated by MOSI and the message is formatted by MTDP.