I saw this once in the old days when ATCINFO was called ATCINFO when we had
2 DBE's in the same group so you could not create a new ATCINFO.

Is LPRDBE something new?

Could it be possible that there is a LPRDBECR in that group which does not
belong to the DBE??

Ken Vickers

LINKWAY Development and Support
__________________________________
Computing Solutions Limited

Tel. +44 1905 794400
Fax. +44 1905 794464
mailto:[log in to unmask]
http://www.csllink.com
__________________________________


-----Original Message-----
From: Glenn Cole <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: 11 February 2000 17:10
Subject: Re: IMAGE/SQL QUESTION


>Peter Chong writes:
>
>> I got a error message on IMAGESQL
>>
>> IMAGESQL
>> HP36385B B G2.11  Image/SQL Utility
>>
>> >>set sqldbe Iprdbe
>> >>Set turbodb wdsshp
>> >>ATTACH
>> Cannot open ATCINFO file(ATCERR 32411, FSERR -247).
>
>
>then B T Vikram:
>
>> Please check, whether the fully qualified dbname (i.e.,
>> wdsshp.groupname.accountname) is more than 24 characters. If it is
>> more than 24 characters, the error reported is a known problem
>[snip]
>
>I was not aware of that caveat, but that cannot be the problem in
>Peter's case, since
>
>   wdsshp.groupname.accountname
>      6 +1+ max 8 +1+ max 8     = 24
>
>Since 24 is not greater than 24, it must be something else.
>
>(Hmmmm.  In fact, since the Image database name can NEVER be more than
>6 chars, how could this total EVER be more than 24??)
>
>--Glenn
>