Technical data

Figure 7–7 Split Screen After FETCH 2 WITHIN PART_SUPPLY
maintainedCURRENTLegend: POSITION null
ZK−6074−GE
SUPPLY
PART
PART_SUPPLY VENDOR_SUPPLY
%DBM − I − CURDISPLA, Currency for run unit is 3:2:2
%DBM − I − CURDISPLA, Currency for PART_SUPPLY set type is 3:2:2
%DBM − I − CURDISPLA, Currency for VENDOR_SUPPLY set type is 3:2:2
%DBM − I − CURDISPLA, Currency for SUPPLY record type is 3:2:2
SUP_RATING = 0
SUP_TYPE = WSUP
SUP_LAG_TIME = 1−2 WEEKS
%DBM − I − CURDISPLA, Currency for MARKETS realm is 3:2:2
VENDOR
7.3 Program Map Listings on Alpha or VAX
Listings are different on OpenVMS Alpha and OpenVMS I64 systems than they
are on OpenVMS VAX systems. This section shows two listings on Alpha and I64
and two on VAX.
7.3.1 Listings on Alpha and I64
This section shows two compiler listing examples for OpenVMS Alpha and
OpenVMS I64.
PARTSS1 Program Map Listing (Alpha, I64)
PARTSS1-PROGRAM in Example 7–3 includes the Oracle CODASYL DBMS
data-names of the PARTSS1 subschema. The complete subschema can be
obtained from the Oracle CDD/Repository DICTIONARY utility, using the
following commands (refer to the Oracle CDD/Repository documentation):
$ DICTIONARY OPERATOR
CDO> SET OUTPUT filename.extension
CDO> SHO GENERIC CDD$DATABASE/FULL database-name
(The logical CDD$DEFAULT must have been previously defined.)
7–10 Debugging and Testing HP COBOL DML Programs