At http://www.robelle.com/tips/image.html I read this:

<--- snip
Therefore:

a. Logging Identifiers retain the copy number on the CLST tape in the
case of an UPDATE or UPDATE CONFIG.

b. Logging Identifiers on the system retain the NEXT log file they
need to CHANGELOG to.

So if one needs to use a CLST to load and you're using Image Logging,
remember to use it just after you create it, or make sure no
CHANGELOGs occurred since it was made.

This may effect some sites as they may believe their CPU is a static
configuration and only do a CSLT once a month or once a week. In the
case of an emergency tape load, to save some heartache rebuilding
image log files, they may need to do a CSLT every day.
<--- snip


Is there no way around this?  Really? One must create a CSLT every day
just to be able to to use image logging in recovery with ones nightly
DBSTOR?

I was going to ask how to set the next logfile number for the image
logging id but I guess this passage answers that.  However, is that
the only way?


-- 
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrne                mailto:[log in to unmask]
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

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