Positioning‑statement‑number specifies the statement number from which the Fetch is to be performed when Positioning‑action indicates other than Next‑parcel.
A request can consist of multiple statements, each of which contributes to the response. The first statement is numbered one and any subsequent statements are assigned subsequent ascending integers.
Successful response parcels for each statement begin with either a Success, OK, or StatementStatus parcel and end with an EndStatement parcel, both of which contain the statement number. For unsuccessful statements, the Error, StatementError, or Failure parcel contains the statement number.
|
In this language... |
The variable name for Positioning‑statement‑number is... |
|
COBOL |
STATEMENT‑POSITION |
|
PL/I |
STATEMENT_POSITION |
|
C |
statementPosition |
|
IBM Assembler |
DBFISPOS |
|
This routine... |
Does this for Positioning‑statement‑number... |
|
DBCHINI |
writes |
|
DBCHCL |
reads (FET) |
|
Positioning‑statement‑number is used by... |
To... |
|
applications |
write |
Use of this setting does not require use of Change‑option. That is, honoring Positioning‑statement‑number depends only upon the setting of Positioning‑action, not Change‑option.
The following field, which served the same purpose, but was only 2 bytes long, is now deprecated. For compatibility, it will be used if the field contains a non-zero value. To use the new 4 byte field described above, zero the deprecated field:
|
In this language... |
The variable name for Positioning‑statement‑number is... |
|
COBOL |
DBFIPSNM |
|
PL/I |
DBFIPSNM |
|
C |
dbfiPSNm |
|
IBM Assembler |
DBFIPSNM |