Getting Started with TRANSACT (32247-90007)

Chapter 9 169
Creating Custom Applications
Adding, Deleting, and Changing Elements
Figure 9-24. Compiling Transact Program to Resolve Data Changes
DICTDBU and DICTDBL cannot handle all types of element changes. For example,
cust-no was changed from a 9(4) definition to an I+(4) definition in this example because
these utilities will not convert a numeric ASCII element properly. This is because Image
does not have a data type corresponding to numeric ASCII. DICTDBC creates an element
defined as numeric ASCII as an alphanumeric element of type X. Thus, if cust-no were
being changed from 9(4) to 9(6), DICTDBU would unload it as X(4). DICTDBL would
reload it as X(6) causing the new field to be left justified with two spaces inserted on the
right. Transact would no longer be able to interpret the field as numeric.
Thus, when writing a custom application, avoid using data type 9 or write a utility to
convert data after DICTDBU has run and before DICTDBL has run.
run trancomp.pub.sys
TRANSACT/3000 COMPILER HP32247A.02.02 - (C) Hewlett-Packard Co. 1984
SOURCE FILE> custup
LIST FILE>
CONTROL> dBlist
TRANSACT/3000 COMPILER A.02.02 : TUE, MAY 14, 1985, 9:32 AM COMPILED
LISTING OF FILE CUSTUP.CUSTOMIZ.MILLER PAGE 1
COMPILING WITH OPTIONS: CODE,DICT,ERRS
CODE FILE STATUS: REPLACED
0 COMPILATION ERRORS
PROCESSOR TIME=00:00:08
END OF PROGRAM
: