15.10 - Using-data-count - 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

Using‑data‑count is a four byte field that when not zero indicates Using‑data‑pointer‑vector addresses a vector of pointers to areas containing data that is associated with the USING clause in the request string. The number of pointers in the vector is the value of Using‑data‑count. If Variable‑length‑request is not specified, Using‑data‑length‑vector addresses a vector of four byte values containing the length of each area of using‑data. If Variable‑length‑request is specified, Using‑data‑length‑vector is unused.

A Using‑data‑count of one (along with the associated data and length) is functionally equivalent to the existing Using‑data‑pointer (along with the associated length). A Using‑data‑count greater than one will be rejected if the server does not support Array Operations. The DBCHQE Array‑operations query may be used to ascertain whether the server supports this feature.

Using‑data‑count 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, Using‑data‑count is ignored.

 

In this language...

The variable name for Using‑data‑count is...

COBOL

DBRIUDC

PL/I

DBRIUDC

C

dbriUDC

IBM Assembler

DBRIUDC

 

This routine...

Does this for Using‑data‑count...

DBCHINI

writes

DBCHCL

reads (RSUP; IWPF; IRQ)

 

Using‑data‑count is used by...

To...

applications

write

Before calling DBCHCL for the Initiate Request function when the request contains a USING modifier, the application must provide the associated using‑data. Variable Length Request applies as follows:

 

When Variable Length Request is set to this value...

Then...

Y

Using‑data‑length‑vector is ignored and each data area addressed by Using‑data‑pointer‑vector must point to the two‑byte area containing the length of using‑data, which is followed by the actual using‑data.

N

the entries of Using‑data‑length‑vector specify the length for each area.

See “Variable Length Request” on page 197.

Since CLIv2 does not parse the request string, it is the application's responsibility to set any using‑data appropriately.