The logid and log password is stored in label zero of the Image root file.
The definition is documented in the blue Image3000 handbook.
01 !1-LABEL-ZERO.
05 !1-LZ-ROOT-MODE-FLAG PIC X(02).
05 !1-LZ-DATE-CREATED PIC 9(04) COMP.
05 !1-LZ-TIME-CREATED PIC S9(09) COMP.
05 !1-LZ-NO-LONGER-USED PIC X(02).
05 !1-LZ-COLD-LOAD-ID PIC S9(04) COMP.
05 !1-LZ-CURRENT-ACCESSORS PIC S9(04) COMP.
05 !1-LZ-DST-NUMBER PIC S9(04) COMP.
05 !1-LZ-LOG-ID PIC X(08).
05 !1-LZ-LOG-PASSWORD PIC X(08).
05 !1-LZ-FLAGS PIC X(02).
05 !1-LZ-LAST-DBSTORE-DATE PIC 9(04) COMP.
05 !1-LZ-LAST-DBSTORE-TIME PIC S9(09) COMP.
05 !1-LZ-MAX-USER-COUNT PIC S9(04) COMP.
05 !1-LZ-LAST-ILR-LOG-CREATE-DATE PIC 9(04) COMP.
05 !1-LZ-LAST-ILR-LOG-CREATE-TIME PIC S9(09) COMP.
05 !1-LZ-LAST-ILR-LASTLOG-AC-DATE PIC 9(04) COMP.
05 !1-LZ-LAST-ILR-LASTLOG-AC-TIME PIC S9(09) COMP.
05 !1-LZ-LAST-PREV-ROLLBACK-DATE PIC 9(04) COMP.
05 !1-LZ-LAST-PREV-ROLLBACK-TIME PIC S9(09) COMP.
05 !1-LZ-LAST-ROLLBACK-DATE PIC 9(04) COMP.
05 !1-LZ-LAST-ROLLBACK-TIME PIC S9(09) COMP.
05 !1-LZ-LANGUAGE-ID PIC X(22).
05 !1-LZ-RESERVED-FOR-DBCONV PIC X(02).
05 !1-LZ-FILLER-38 PIC X(38).
05 !1-LZ-MAINTENANCE-WORD PIC X(08).
05 !1-LZ-BUFFSPEC-TABLE.
10 !1-LZ-BUFFSPEC-ARRAY OCCURS 120.
15 !1-LZ-BUFFSPEC-USER PIC X(01).
Brian.
On Thu, 19 Jun 2008 16:55:02 -0400, Simpkins, Terry
<[log in to unmask]> wrote:
>I need a command file that will create LOGIDs, build the logfile and
>then increment the logfile number assigned to the LOGID until it reaches
>the desired number.
>Anyone ever created one of these? I'll write it if I have to (it's been
>a long time since I wrote command files), but I'd much rather leverage
>someone else's work if possible.
>
>What I am trying to do is move a series of IMAGE databases from one
>machine to another, and retain the logfile sequence from the old machine
>to the new machine.
>
>These are the assumptions I am working under. If I've got something
>wrong, please enlighten me.
>
>1) the LOGIDs and the 'current' logfile are stored somewhere in the
>OPSYS, not in the IMAGE rootfile
>2) the fact that logging is enabled and the LOGID being used is stored
>in the IMAGE rootfile
>3) when I restore the files to the new machine, the IMAGE DBs will know
>they are enabled for logging, and what LOGID to use
>4) the new machine has no knowledge of the LOGIDs and they must be
>defined using GETLOG and the approriate parameters
>5) when you create a LOGID and want it set to AUTO, you must start with
>logfile '001', then issue the required number of CHANGELOG commands to
>get the file incremented to the correct number.
>
>Because we do a CHANGELOG every night on about 50 LOGIDs, we quickly get
>to some fairly large logfile numbers (ie logid685). I'd really rather
>not have to sit and do this manually. So I am thinking about a command
>file that will prompt for the LOGID and the logfile sequence # required.
>Then issue the GETLOG command, the BUILD command for the '001' logfile
>and then use a WHILE loop to increment (CHANGELOG) the logfile # until
>it reaches the desired number.
>
>I can't believe it's this tedious and that someone hasn't already
>invented a way to do this.
>
>*****************************
>Terry W. Simpkins
>Director ISIT
>Measurement Specialties
>757-766-4278
>http://www.arcticride.com
>[log in to unmask] <mailto:[log in to unmask]>
>*****************************
>
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
