Re: Ontape Error

Cosmo Lee wrote: > > Mark D. Stock wrote: > > > You can change the tape parameters using tbmonitor/onmonitor, without > > bouncing OnLine. If you make ANY changes to parameters in your > > tbconfig/onconfig file, you must bounce OnLine before they become > > effective. > > > > I'm not sure if I'm reading the above right, but you *can* change the > TAPEDEV & LTAPEDEV and SIZE parameters in the ONCONFIG file, and they *will* > take effect the next time you run `ontape`. > > However, beware a bug: If you change the TAPEDEV or LTAPEDEV parameter to > "/dev/null" in the ONCONFIG, then run `ontape`, then change the TAPEDEV > parameter back to a real device, the next time you try to run `ontape`, it > will keep telling you that you may not archive to "nul", even though your > TAPEDEV is pointed to a perfectly legitimate path. The problem is that the > Reserve Pages do not get properly rewritten. To get back to archiving to a > real device, w/o bouncing the engine, you must run `onmonitor` to change the > tape parameters. This is only a problem for LTAPEDEV. Ontape does read the TAPEDEV and TAPESIZE parameters from the ONCONFIG for archives but for logical log backups only the reserved page version of LTAPEDEV and LTAPESIZE are used. Onmonitor modifies both the ONCONFIG and the reserved pages as Cosmo states. Art S. Kagel