Another method of changing logging on a database

Hi All, Just a curious question .... Many of us run very large batch programs (mostly DML Statements) against some of our databases. The problem is that I want the programmers to be able to switch from logging to non-logging for their particular database without running the ontape and modifying the TAPEDEV parameter which would be set to a tape device and need to be modified to /dev/null to ensure that they were not performing a level 0 archive on the system to tape when they change their logging mode on their database back and forth (from logging to non-logging and vice-versa). I know that you can change the logging mode using SQL with a logging database from buffered to unbuffered logging using the SET LOG command but this I am sure (based on the SQL Syntax Guide pdf) does not change from a logging to a non-logging database and vice-versa. In order for you to properly do this (change logging on and off) .. you must use the ontape utility ... right? ... and each time you do this requires a system archive on the server ... right? I have done this many times... Is there any easier way that the programmers can make this modification without going through all these steps outlined above to change thier logging methods on their databases? Has anyone run into this situation and if so ... what did you do to make things more convenient for the user? Any help appreciated. For the record I am using 7.30 UC5 on LINUX 5.2 (Redhat). TIA, Lloyd AJ Wilson.

Write them a script that modifies the ONCONFIG, runs the archive to set the logging status, runs their script, runs the archive to restore the logging status, and repairs the ONCONFIG. Art S. Kagel Lloyd AJ Wilson wrote: > > Hi All, > > Just a curious question .... > > Many of us run very large batch programs (mostly DML Statements) against > some of our databases. The problem is that I want the programmers to be > able to switch from logging to non-logging for their particular database > without running the ontape and modifying the TAPEDEV parameter which would > be set to a tape device and need to be modified to /dev/null to ensure that > they were not performing a level 0 archive on the system to tape when they > change their logging mode on their database back and forth (from logging to > non-logging and vice-versa). > > I know that you can change the logging mode using SQL with a logging > database from buffered to unbuffered logging using the SET LOG command but > this I am sure (based on the SQL Syntax Guide pdf) does not change from a > logging to a non-logging database and vice-versa. > > In order for you to properly do this (change logging on and off) .. you must > use the ontape utility ... right? ... and each time you do this requires a > system archive on the server ... right? I have done this many times... > > Is there any easier way that the programmers can make this modification > without going through all these steps outlined above to change thier logging > methods on their databases? Has anyone run into this situation and if so > ... what did you do to make things more convenient for the user? > > Any help appreciated. For the record I am using 7.30 UC5 on LINUX 5.2 > (Redhat). > > TIA, > > Lloyd AJ Wilson.

In article <37E91B18.561E6B61@bloomberg.net>, kagel@bloomberg.net wrote: >Write them a script that modifies the ONCONFIG, runs the archive to set >the logging status, runs their script, runs the archive to restore the >logging status, and repairs the ONCONFIG. > >Art S. Kagel > Don't Level 0 archives need to be performed in between? -Peter