Technical data

GET
7. If a database exception condition occurs during the execution of a GET
statement, the DBCS places a database exception condition code in the
special register DB-CONDITION (see Technical Note). This code identifies
the condition.
Technical Note
GET statement execution can result in these DB-CONDITION database exception
condition codes:
DBM$_CRUN_NULL The currency indicator for the run unit is null.
DBM$_CRUN_POS The currency indicator for the run unit points to a
vacated position in the database.
DBM$_WRONGRTYP The record type for record-name is not identical to the
current record type, or a record-item is not a group or
elementary item in the current record.
DBM$_CONVERR A data conversion error occurred in the GET operation.
DBM$_ILLNCHAR An invalid character was found in a numeric field.
DBM$_NONDIGIT A nonnumeric character was found in a numeric field.
DBM$_OVERFLOW A data overflow error occurred in the GET operation.
DBM$_TRUNCATION A data truncation error occurred in the GET operation.
DBM$_UNDERFLOW A data underflow error occurred in the GET operation.
Additional References
• Section 2.2, on reserved words (database special registers)
• HP COBOL Reference Manual, Chapter 6, section on scope of statements
• Section 4.8.1, on database On Error condition
• USE statement
Examples
1. This example gets the current record of the run unit:
GET.
2. This example gets a PART record only if it is the current record of the run
unit:
GET PART.
3. This example gets these items only if they are part of the current record of
the run unit:
GET PART_ID, PART_DESC.
4–42 Procedure Division