|
Control Functions Gain Capabilities as Release 7.44i of Unibase by DMAC gives over thirty control functions new features and compatibility. As part of implementing the channel designation described in the Fall, 1994 issue of "The Unibase Technical Review," a better paradigm became available and the result was spread to all control functions which could use the new approach. Every control function which has or could have an integer quantity as part of the function can now accept an integer or a variable as the integer. Channel Access is Easier The following control functions can now be used to reference a channel (channel 0 is the workfile) in either a move or output statement. As an example as to what is acceptable in the AID language: move 3 to variable.Many Functions Reference Channel These control functions can now behave as above: <iname>, < flag>, <verified>, <corrects>, <fileedit>, <fieldedit>, <status>, <records>, <job>, <cdate>, <cdate4>, <eoper>, <eetime>, <lmode>, <recfmts>, <voper>, <vtime>, <ientry>, <ipath>, <ipathidx>, <isource>, <itype>, and <icount>. In addition to retaining the old method using the at sign (@), the following control functions now can be used as shown above: <fmt>, <file>, and <length>. Few Functions Reference Numbers These control functions can now behave as above which means they can now use a variable or a number to represent the second datum: <rec>, <hex>, and <blk>. Others Contain Two Variables These control functions have two datum where each now can be a variable or number: <outdev channum;port>, <ilist channum;item>, and <accum channum;accumulatornumber>.
|