%META:TOPICINFO{author="ChrisBartram" date="1170469005" format="1.1" version="1.2"}%
%META:TOPICPARENT{name="Hp3000ImageSql"}%
---+ Setup hints and common problems with !ImageSQL access on the HP3000

There have been so many requests for help about IMAGE/SQL lately, that I hope this might be some help: 

1) Creating the DBE. Because this may be made up of a number of different files, you can never be absolutely certain that there will not be a name clash with a file you have already created. So I find that the easiest way to avoid clashes is simply to put your DBE into a group of its own, and not put anything else there at all. Some people prefer to let IMAGESQL create the DBE for them automatically, rather than doing it explicitly with ISQL. There are two drawbacks to this. The first is that the default SYSTEM filespace is not very big, and may very well be inadequate to accomodate sorts etc. The second is that the log files are not very big, and you may find you cannot execute an IMAGESQL "detach", without first deleting all the users one by one. 

2) Maintenance words and access. When you create an IMAGESQL DBE (though I admit here that I'm just assuming it's the same as ALLBASE), it is released. So there is no MPE security on the DBE. Since you may want to attach Turbodb's from a number of different accounts, you may not be able to be logged in as the creator of both the DBE and the Turbodb. This is where maintenance words are useful, and if you are in this situation it will give much more flexibility if you set maintenance words on both the Turbodb and the DBE. 

3) Set DDL off Once you have finished all the configuration via IMAGESQL, you can use SQLUTIL to switch off DDL (data definition language). This allows ALLBASE to assume that the system tables will not be changed when it opens the DBE, and keep them loaded in memory, which should give better response times. 

  --[[MartinKnapp]]

Please note that a PC Socket error 10054 is returned to PC API when users do not have write access to !HPDAARLG.PUB.SYS. Please ensure that you have placed any ACD's on this file. 

Try releasing !HPDAARLG.PUB.SYS at least temporarily to test. If you have a very secure system, apply the following ACD to the log file: 

@.@ = R,X,A,L 

  --[[PeggyLacy]]


-- Main.ChrisBartram - 18 May 2006