HP3000-L Archives

March 1998, Week 1

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:
Tony Furnivall <[log in to unmask]>
Reply To:
Tony Furnivall <[log in to unmask]>
Date:
Mon, 2 Mar 1998 10:48:51 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (53 lines)
Hi there folks!

Thanks for the responses suggesting MPEX's LISTF <fileset>,DB. I'm going to
use that for now, even though it doesn't meet my underlying need (which is
to create a set of db grooming tools).

However, I have found another goody!

Logged on as MANAGER.SYS I have the authority to examine the maintenance
word for any IMAGE/SQL database on the system. On a couple of databases when
I do this (did this, no longer possible for reasons described below!), I
would get a string which said:

  MAINTENANCE WORD:

and then did not supply one. Being a not-dumb person, I repeated the attempt
with Display Functions enabled, and also redirecting output to a file. In
every instance, the received maintenance word was a 0 length string. This is
different, however, from a database where there IS no maintennce word. For
this case, DBUTIL returns the value:

  Maintenance word is not present.

Now, with my former claim to greatness still in effect, I can see that these
two strings are different. So what's going on in DBUTIL? It seems that one
part of the program is detecting that there is a maintenance word, and
retrieving it, but sort of overlooking the fact that it has a length of 0!
The part of DBUTIL responsible for printing the darn thing just accepts this
0 length string and "prints" it.

Do we think this is reasonable?

The reason I'm doing this is to build a list of all Image/SQL <==>
Allbase/SQL relationships on the system. And here is where the second gotcha
rears its ugly little head.

As MANAGER.SYS I can interrogate an Image/SQL database and find out how
many, if any, Allbase/SQl DBEs it is attached to:

  DISPLAY SQLDBES FOR <database>,MAINT=<maintword>

Now, if there IS no maintenance word, IMAGESQL (the program, not the
capabilityset!) refuses to allow me to specify ",MAINT=" and claims that I
made a syntax error (ACTERR 32435). HOwever, if I don't even try to specify
the maintenance word, I'm told that I jolly well ought to! (ACTERR 32403).

My question is, if I choose to leave my databases unprotected by maintenance
words, how can I use IMAGESQL as MANAGER.SYS to look at them?

Any ideas, scars from discovering this earlier, or whatever?

Tony "Rapidly losing hair from frustrated scratching" Furnivall

ATOM RSS1 RSS2