HP3000-L Archives

February 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
B T Vikram Kumar <[log in to unmask]>
Reply To:
B T Vikram Kumar <[log in to unmask]>
Date:
Mon, 14 Feb 2000 08:46:27 +0530
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
Thanks Glen for pointing this out. In fact, I satand corrected on length
of 24 char dbaname. In fact the problem is when the length is exactly 24
char. In this case one of the routines used to SCAN the dbname buffer
fails to find a whitespace. This is being fixed.

Regards,
Vikram

Glenn Cole wrote:

> 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

ATOM RSS1 RSS2