It is a long time since I had to deal with configuring image 
logging but let me see if I understand user logging properly.

1.	A user log file must reside in the same account as the image 
databases to which it is assigned.

2.	A user log file must be created only in the logon group of the 
logid creator.

3.	An auto-incrementing log file can only be obtained by providing 
the logid with a file name ending in 001.

4.	If a file ending in a number one greater than that used by the 
current active log process exists in the the same group and 
account, otherwise having the form of that used by the logid, then 
a CHANGELOG will fail (presumably as will an auto increment roll-
over).

5.	Despite these requirements however, a user logid creator cannot 
actually start their own logging process! Unless, of course, they 
are given permission to use the LOG command via the ALLOW command.

Why this division of responsibilities, the user who can enable 
logging cannot set up the infastructure and the user who sets up 
the logging infrastructure cannot enable logging?  For that matter, 
is there any good reason why the system manager should not be able 
to control all logging processes on the system?  Is there a 
technical reason why there is no provision in user logging to roll 
over intervening files; is this a sop to IMAGE DBMS recovery 
limitations?  Why cannot one start a userlog process with any 
arbitrary numbered file?  How does one control the rollover point?

These questions have never troubled me before because other than 
complete system upgrades I never had cause to move our operational 
system from one box to another.  But now I am arriving at the 
conclusion that it will be impossible to have an identical RESTORE 
and go box at our DR site, mainly because of image logging.  I will 
have to provide an alternative disc file nomenclature for the user 
logid on the DR box to avoid a namespace conflict.

> :getlog haldblog;log=halog071,disc;auto
>                                    ^
> Logfile must end with "001" to use AUTO. (CIERR 3751)

";AUTO" has to be among the most useless options ever provided for 
a utility, since if one gives GETLOG a file name ending in 001 then 
auto is assumed and if one does not then it generates an error.  On 
the other hand, I suppose ;NOAUTO does something useful in some 
obscure corner case where one actually wants to halt processing 
when a log file ending in 001 fills.

Shaking my head...

Regards,
Jim

--   
     *** e-mail is not a secure channel ***
mailto:byrnejb.<token>@harte-lyne.ca
James B. Byrne                Harte & Lyne Limited
vox: +1 905 561 1241          9 Brockley Drive
fax: +1 905 561 0757          Hamilton, Ontario
<token> = hal                 Canada L8E 3C3

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