At 09:56 AM 3/2/98 -0800, Gavin asked:
>Is this reproducible in DBUTIL manually, or does it only happen whn you
>are running it with $STDIN redirected (or whatever method you are using
>to feed it the info from the MPEX run)?

So I thought, Hm, I wonder, and tried:

HP30391C.06.20 etc

SHOW ADFDB.DATABASE.DDP CAPACITY

<good results, just what I want>

SHOW DA.DATABASE.DDP  <a database that I know to exist>

NON-EXISTENT ACCOUNT (FSERR 50)
DAMBASE     M  3  <a line of valid output!>

So, it looks like the second attempt fails. What happens if I go back to the
original database again?

SHOW ADFDB.DATABASE.DDP CAPACITY

<clear as a bell!>

Alright - problems on the second, right? Might be a dud database? But no, if
you try this on any two databases (call them DB1 and DB2):

SHOW DB1 CAPACITY
<works OK>

SHOW DB2 CAPACITY
<Flying fecal matter>

exit from DBUTIL and try again

SHOW DB2 CAPACITY
<works well>
SHOW DB1 CAPACITY
<duck!>

So it seems that the SECOND and/or subsequent attempts to refeence a
different database are doomed to failure. This happens whether it is
"directly interactive" or with CIOR.

Hmm, this is getting curiouser and curiouser!

Tony "Bring on the ROgaine" Furnivall