15.10 - Use-default-conn - Call-Level Interface Version 2

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

prodname
Call-Level Interface Version 2
vrm_release
15.10
category
Programming Reference
featnum
B035-2417-035K

Use‑default‑conn is a one byte EBCDIC field that indicates whether a connection being established by an External Stored Procedure calling CLIv2 and executing in the Teradata Database is a new connection or the connection used by the application to call the procedure.

Use‑default‑conn exists only when DBCHINI had been called for a DBCAREA with Total‑length set to at least 640 (that is, the returned DBCAREA Level value is at least 1). For a smaller DBCAREA, Use‑default‑conn is ignored.

 

In this language...

The variable name for Use‑default‑conn is...

COBOL

USE‑DEFAULT‑CONN

PL/I

USE_DEFAULT_CONN

C

useDefaultConn

IBM Assembler

DBCNIDC

 

This routine...

Does this for...

DBCHINI

writes

DBCHCL

reads (CON; IRQ; IWPF)

 

Use‑default‑conn is used by...

To..

applications

write

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

 

If...

Then set Connect Type to...

'N', indicates that a new connection is established.

  • DBCNIDCN for Assembler
  • DBC_DfltConnNo for C
  • DBC‑NO for COBO
  • DBC_DFLT_CONN_NO for PL/I)
  • 'Y', indicates that the connection used to call the procedure is used.

  • DBCNIDCY for Assembler
  • DBC_DfltConnYes for C
  • DBC‑YES for COBOL,
  • DBC_DFLT_CONN_YES for PL/I
  • If not specified 'N' is assumed.

    If Use‑default‑conn is set to 'Y', since a new connection is not being established, the following DBCAREA settings that would normally apply to the Connect function are ignored: Connect‑type, Delegate‑user‑identity, input‑TDP‑pat, Logon‑length, Logon‑pointer, Mechanism‑data‑encoding, Mechanism‑data‑len, Mechanism‑data‑ptr, Mechanism‑name, Run‑length, and Run‑pointer.

    If Use‑default‑conn is set to 'Y' since session-wide settings from the existing connection are used, the following DBCAREA options that would normally apply to the Connect function are ignored: Date‑form, Language‑conformance, Statement‑status, Transaction‑semantics, and 2PC.

    For details on External Stored Procedures, refer to Chapter 17: “Stored Procedures.”