Leonard notes:

> The problem with using Adager for this purpose (dataset
> filenames) is that Adager by default does a lot of up front
> work , including consistency checking and checking TPI
> before it is ready for a command. I understand that there is
> a way to inhibit these functions, and interested parties can
> get information from Adager.

:SETJCW  SKIPADAGERCONSISTENCY 1
:SETJCW  FORBIDTPIMAINT 1

Will cause Adager to skip the normal consistency check.
forbidTPImaint does what you would expect...   ** BUT **:
Note if set the above JCW as shown, when you run Adager
after entering the Database name you will see:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NOTE: JCW "SkipAdagerConsistency" is NOT ZERO.  So, I will skip
Adager's normal consistency checking.  You are fully responsible...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

All please note and remember those last words:  YOU ARE
FULLY RESPONSIBLE !!!....   The thing you want to be *real*
careful about is setting the above "just to get the filenames" or
etc.;  then going off and doing something else and forgetting
they are set;  then running Adager again to do something
where you definitely do NOT want it to skip consistency check;
and then ignoring the above warning NOTE....  but hopefully any
of y'all that run Adager on your production databases always
pay attention to what it tells you in the dialogue....    :-)

Ken Sletten