> 3.  Use two forms files as source and have a single target fast
forms
> file using the new VMERGE utility available on the the latest VPLUS
> patch on both MPE/V and MPE/iX.  This utility takes advantage of the
> fact that you can fit a lot more forms into a fast forms file
> than into a regular forms file.
>
> This solution would require the ongoing use of two regular forms
files
> for development, but the applications could continue to use only the
> single merged fast forms file.  The VMERGE utility is
> documented in the MPE/iX 5.0 and MPE/V 3P Communicators.

Reminder for sites using this technique: if you also use DICTIONARY/V
(if you don't: why not??), DICTVPD *only* the fast form files (file
code VFAST), not the form source files (code VFORM). In fact, if you
use only VFAST files in your SYSTEM statements (or whatever that
"other" language uses to declare files), there's generally no value to
having your VFORM files in the dictionary at all.

Steve