POLITE REQUEST FOR HELP: Why "onbar -b -L 1" sometimes runs level 0 backups?

Hello, I apologise for taking bandwidth with my question. I tried to search for a solution on my own, even asked some Informix administrators, but still no answer. I am a Unix system admin and cannot call myself a DBA. Recently, I wrote a new Bourne Shell script to automate Informix backups. STATUS: Server: Solaris 2.6 Informix Version: Informix Dynamic Server Version 7.31.UD2XA NetBackup Version: 3.4GA The Shell script executes "onbar -b -L 0" or "onbar -b -L 1", depending on the day of the week, as scheduled throyh cron(1). Other parts of the script are static (environment variables and so on). The script checks number of things, like: Ensures that used "informix" runs it exclusively; Ensures that environment variables are set correctly; Ensures that previous onbar backups are completed (checks the lock file and process status); Ensures that only numerical values 0 and 1 are provided when defining backup level; Calculates total backup times and summarises information on tablespaces; Remote tape library is used through NetBackup. The Shell script is called through cron as: /informix/XXX/bin/onbar_backup.sh -l 0 or /informix/XXX/bin/onbar_backup.sh -l 1 ... which, in turn, executes "onbar -b -L 0", and "onbar -b -L 1", respectivelly. PROBLEM: On occasion, although the script initiates "onbar -b -L 1", the Informix log shows that level 0 backup was run!? The file that reports this is /tmp/bar-act.log. How can this happen? Is there something that I am doing wrong, or is some unusual database feature responsible for this? I welcome any comments. Regards, Dusan, Amateur Radio VK2COT from "down-under" (Australia)