Technical data

Figure 7–3 Split Screen After MODIFY SUP_RATING
maintainedCURRENTLegend: POSITION null
ZK−6069−GE
SUPPLY
PART vendor
PART_SUPPLY VENDOR_SUPPLY
The next statement to test is the FETCH for SUPPLY record’s owner in the
VENDOR_SUPPLY set.
dbq> FETCH OWNER WITHIN VENDOR_SUPPLY
Figure 7–4 Split Screen After FETCH OWNER WITHIN VENDOR_SUPPLY
maintainedCURRENTLegend: POSITION null
ZK−6070−GE
%DBM − I − CURDISPLA, Currency for run unit is 3:5:1
%DBM − I − CURDISPLA, Currency for VENDOR_SUPPLY set type is 3:5:1
%DBM − I − CURDISPLA, Currency for VENDOR record type is 3:5:1
%DBM − I − CURDISPLA, Currency for MARKETS realm is 3:5:1
VEND_ADDRESS = (1) = 132 MAIN ST.
VEND_ID = 02321332
VEND_NAME = U.S. SEALS
VEND_CONTACT = R.R. BINGHAM
VEND_ADDRESS = (2) = MOLINE, ILL.
VEND_ADDRESS = (3) =
VEND_PHONE = 8168845398
SUPPLY
VENDOR_SUPPLY
VENDOR
Assuming the data item MODIFY-COUNT has a value 1, you can test the last
(MODIFY PART) DML statement.
dbq> MODIFY PART_STATUS
PART_STATUS [CHARACTER(1)]= X
dbq> DBM-F-WRONGRTYP, Specified record type not current record type
DBQ generates an error message indicating the MODIFY statement did not
execute because the current of run unit is not a PART record. Comparing the
shading and intensities of the Bachman diagram in Figure 7–4 with the legend
shows the current record is a VENDOR record. Therefore, the diagram indicates
7–6 Debugging and Testing HP COBOL DML Programs