HP 3000 Manuals HP 3000 Manuals
CANCEL COMMANDS
Cancels all changes entered in the change file since the last BASE
command.
Syntax
CA[NCEL] COM[MANDS]
Description
Use this command to cancel all changes entered since the last BASE
command. After issuing CANCEL COMMANDS, the change file returns to the
state it was in just after the most recent BASE command. To continue
using the DBCPLUS program after issuing CANCEL COMMANDS, you must issue a
new BASE command.
Example
>add item ship-cost j 4 (/12,13,14,18)
Addition of data item accepted.
>add field sales ship-cost
Addition of field accepted.
>cancel commands
Completed CANCEL COMMANDS, existing change file is intact.
>base orders
>
In this example, some restructuring commands are canceled and the DBCPLUS
program returns the change file to the state it was in when the BASE
command was issued.
Before issuing the restructuring commands to the ORDERS change file, the
ITEMS part of the schema and the SALES data entry in the schema look like
this:
ITEMS:
ACCOUNT , I4(0,11,12,13,14,18/);
BINNUM , Z2(/13);
CITY , X12(12,13,14/11);
CREDIT-RATING , R2(/14);
DATE , X6(11,12,13,14,18/);
DELIV-DATE , X6(/14);
DESCRIPTION , X20(0,11,12,13,14,18/);
FIRST-NAME , X10(14/11);
INITIAL , U2(14/11);
LAST-NAME , X16(14/11);
LASTSHIPDATE , X6(12/);
ONHANDQTY , J2(14/12);
PRICE , J2(14/);
PURCH-DATE , X6(11/14);
QUANTITY , I1(/14);
STATE , X2(12,13,14/11);
STOCK# , U8(0,11,12,14,18/);
STREET-ADD , X26(12,13,14/11);
SUPPLIER , X16(12,13/);
TAX , J2(14/);
TOTAL , J2(11,14/);
UNIT-COST , P8(/12);
ZIP , X6(12,13,14/11);
SETS:
:
NAME: SALES ,D(11/14,18);
ENTRY: ACCOUNT ( CUSTOMER (PURCH-DATE )),
STOCK# (!PRODUCT ),
QUANTITY ,
PRICE ,
TAX ,
TOTAL ,
PURCH-DATE ( DATE-MASTER ),
DELIV-DATE ( DATE-MASTER );
CAPACITY: 500(10);
Before canceling the restructuring commands, the ITEMS part of the schema
and the SALES data set entry in the schema look like this:
ITEMS:
ACCOUNT , I4(0,11,12,13,14,18/);
BINNUM , Z2(/13);
CITY , X12(12,13,14/11);
CREDIT-RATING , R2(/14);
DATE , X6(11,12,13,14,18/);
DELIV-DATE , X6(/14);
DESCRIPTION , X20(0,11,12,13,14,18/);
FIRST-NAME , X10(14/11);
INITIAL , U2(14/11);
LAST-NAME , X16(14/11);
LASTSHIPDATE , X6(12/);
ONHANDQTY , J2(14/12);
PRICE , J2(14/);
PURCH-DATE , X6(11/14);
QUANTITY , I1(/14);
STATE , X2(12,13,14/11);
STOCK# , U8(0,11,12,14,18/);
STREET-ADD , X26(12,13,14/11);
SUPPLIER , X16(12,13/);
TAX , J2(14/);
TOTAL , J2(11,14/);
UNIT-COST , P8(/12);
ZIP , X6(12,13,14/11);
SHIP-COST , J4(/12,13,14,18); <---- data item added
SETS:
:
NAME: SALES ,D(11/14,18);
ENTRY: ACCOUNT ( CUSTOMER (PURCH-DATE )),
STOCK# (!PRODUCT ),
QUANTITY ,
PRICE ,
TAX ,
TOTAL ,
PURCH-DATE ( DATE-MASTER ),
DELIV-DATE ( DATE-MASTER ),
SHIP-COST ; <---- field added
After canceling the restructuring commands, the ITEMS part of the schema
and the SALES data set entry in the schema look like this:
ITEMS:
ACCOUNT , I4(0,11,12,13,14,18/);
BINNUM , Z2(/13);
CITY , X12(12,13,14/11);
CREDIT-RATING , R2(/14);
DATE , X6(11,12,13,14,18/);
DELIV-DATE , X6(/14);
DESCRIPTION , X20(0,11,12,13,14,18/);
FIRST-NAME , X10(14/11);
INITIAL , U2(14/11);
LAST-NAME , X16(14/11);
LASTSHIPDATE , X6(12/);
ONHANDQTY , J2(14/12);
PRICE , J2(14/);
PURCH-DATE , X6(11/14);
QUANTITY , I1(/14);
STATE , X2(12,13,14/11);
STOCK# , U8(0,11,12,14,18/);
STREET-ADD , X26(12,13,14/11);
SUPPLIER , X16(12,13/);
TAX , J2(14/);
TOTAL , J2(11,14/);
UNIT-COST , P8(/12);
ZIP , X6(12,13,14/11); <---- 1
SETS:
:
NAME: SALES ,D(11/14,18);
ENTRY: ACCOUNT ( CUSTOMER (PURCH-DATE )),
STOCK# (!PRODUCT ),
QUANTITY ,
PRICE ,
TAX ,
TOTAL ,
PURCH-DATE ( DATE-MASTER ),
DELIV-DATE ( DATE-MASTER );
<---- 2
CAPACITY: 500(10);
1 data item addition canceled
2 field addition canceled