HP 3000 Manuals HP 3000 Manuals
User Logging Cycles
After Silhouette is installed, and logging established, it is necessary
to periodically start a new log cycle on the primary system. When the
Silhouette system is in operation, the SAVE file on the secondary system
must be kept synchronized with the logfile on the primary system.
Creating a New User Logging Cycle
To create a new log cycle perform the following steps:
1. Notify all active users to log off the primary system database.
2. On the primary system ensure that databases are synchronized by
issuing a >STATUS command. The report generated should show equal
values for LOGFILE record # = on both the primary system and the
secondary system. When the value of DATABASE opens = 0 and
outstanding = 0, indicating no users are accessing the secondary
system, issue a >STOP command:
:RUN SILMP.PUB.SYS
>STATUS configfile
<< Report Generated >>
>STOP
3. On the primary system issue the DBUTIL DISABLE command to disallow
user access to each database in the configuration:
:RUN DBUTIL.PUB.SYS
>>DISABLE dbname FOR ACCESS
>>EXIT
4. On the secondary system, store the database to tape as a backup
procedure. Do not store the SAVE file or the logfile to tape:
:FILE T;DEV=TAPE
:STORE dbname.group.account;*T;SHOW
5. On the secondary system purge the SAVE file specified in the
configuration file:
:PURGE savefile
6. On the secondary system purge and rebuild the logfile:
:PURGE logfile name
:BUILD logfl.group.account;CODE=LOG;DISC=10000,10,10
:GETLOG logproc;LOG=logfl.group.account,DISC
The parameters specified for the DISC= keyword of the :BUILD
command vary by system. The values specified depend upon the rate
at which transactions are applied to the database and the
frequency of log cycles. Using the :GETLOG command is a
procedural recommendation which may not be necessary on your
system.
7. On the primary system stop logging:
:LOG logid, STOP
8. On the primary system purge the logfile, then build a new one if
you are not currently logging:
:PURGE logfile
Then:
:BUILD logfl.group.account;CODE=LOG;DISC=10000,10,10
If you are logging and a CHANGELOG occurred, issue:
:ALTLOG logid; LOG=logfl001, DISC
The parameters specified for the DISC= keyword of the :BUILD
command vary by system. The values specified depend upon the rate
at which transactions are applied to the database and the
frequency of log cycles.
9. On the primary system start logging:
:LOG logid, START
10. On the primary system enable the database for access:
:RUN DBUTIL.PUB.SYS
>>ENABLE dbname FOR ACCESS
>>EXIT
11. Notify users they may resume accessing the database on the primary
system.
12. Start Silhouette:
>START configfile
If You Are Using Automatic CHANGELOG
The following describes the procedures to follow if automatic CHANGELOG
is used:
1. On the primary system notify all active users to log off the
database.
2. On the primary system issue the MPE :CHANGELOG command to create a
new current logfile for user access:
:CHANGELOG logid
3. On the primary system stop Silhouette:
:RUN SILMP.PUB.SYS
>STOP configfile
4. On the primary system ensure that databases are synchronized by
issuing a >STATUS command. The report generated should show equal
values for LOGFILE record # = on both the primary system and the
secondary system. When DATABASE opens = 0 and outstanding = 0 no
users are accessing the secondary system.
5. Notify all users they may resume accessing the database on the
primary system.
6. Store the database, logfile, and SAVE file on the secondary system
to tape.
:FILE T;DEV=TAPE
:STORE dbname,savefile.group.account;*T;SHOW
When using AUTOCHANGELOG, store the SAVE file in case of a
secondary system failure.
7. Restart Silhouette:
>RESUME