This is a "guess" but it might be worth a try.

First my suggestion; then the "why".

Suggestion:
  Do a "LISTF [log in to unmask]@,2"

  If you find a "hit" I would guess that a file (perhaps an ALLBASE DBE?
file) in the group where the DBD?#### file resides is causing the STORE to
croak.  Try excluding that group from your file selection on the STORE and
see if your STORE gets further.

Now the "why"...

Consider yourself "lucky" that the STORE obviously didn't work.  I went
(unaware) for 4 days with "backups" that were NOT USABLE (for RESTOREs)!  In
my case the STORE "seemed" to go fine (listed files, took about the normal
time, etc) but four days later when I tried to RESTORE I got strange errors
and no files were restored!

After a week and a half of sleepless nights (from testing) I discovered that
files in a particular group were rendering the STORE tapes useless.  If I
exclude that group then the STORE goes fine and (so far as I can find out)
files can be restored.

In my case, when STORE had trouble [s]he built two files, of the form:
  DBDC####
  DBDS####
The #### starts at 0000 and increments each time (night) that STORE croaked.
The DBDC#### file is a "PRIV" file.  I didn't snoop at it much.
The DBDS#### file is a ASCII file containing an abort trace from STORE.

As for my system, it is running 5.5 using what came with the "PUSH" release
(no power patch).

Hope that helps.  Lemme know if you have questions re: the above.

Lee Hallin (Systems Programmer, Lane Community College, Eugene, OR)

Disclaimer:
  The above are MY personal views/opinions.