There is a Response Center Engineering Note that should be accessible via
ITRC that fully describes the likely causesof this problem. Here's a brief
excerpt from that regarding the two common causes:

-------------------------

1.  Not enough disc space.

    Use DISCFREE to verify there is adequate disc space on the system
    to build a new DBE.  [ and more on how to verify/remedy ].

2.  Duplicate filename.

    When IMAGE/SQL creates a new DBE, it builds a DBCon file, a DBEFile,
    a logfile, and an IMAGE/SQL configuration file.

    For a DBE called TESTDBE, the following files are created:

    TESTDBE    - DBCon file
    TESTDBFL   - DBEFile0
    TESTDBLG   - Logfile
    TESTDBCR   - IMAGE/SQL configuration file

    The convention followed is the first six characters of the DBE name
    followed by the appropriate extensions.  Check to see if a file with
    one of these names already exists that might conflict
    with what IMAGE/SQL is trying to build.

-------------------------

HTH,

Bill
HP/CSY

> Hi all. I'm trying to create a new image database. I've already got a
> turbo database. I'm trying to attach these two database. I can go into
> imagesql and set the turbodb just fine. When I try to set the sqldbe i
> get an error that says ALLBASE/SQL RELEASE command failed (ATCERR
> 32352).
>   ALLBASE/SQL not running.  (DBERR 2100)
> Anybody know why this is happening? TIA.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *