× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello Rob,

You wrote:
>Forgive me for digging up the dead, (but still warm).  Just got back.

Grave robbing vs. Cradle snatching -- which is worse :)

>Granted changing FRCRATIO can be a performance pig.  But, what about a DR
>situation?  Wouldn't you want all records written to dasd in case of
>abnormal termination?  If I trip on the power cord and it gets yanked,
>what happens to these records?

That's what journalling is for!

However, journalling does not affect the number of records in the program buffer
and those are the only records that would be lost in the event of a power
failure.  The system guarantees that records are written to the journal before
they are written to the file.  However, the records it writes are only those 
that
are in main storage.  If you use blocking in your programs (as you should for
best performance) then you could lose records that are changed but still in the
program buffer.  Records are moved from the program buffer to main storage when
the buffer is full so a large blocking factor will increase the potential number
of records that could be lost.  FRCRATIO(1) will save you from this possibility
but at a serious performance impact.  Journalling is better for performance
because a journal write is a sequential operation -- especially if the receiver
can be isolated to a private disk unit (aka ASP).

If you are concerned about disaster recovery then you must:

        o Use journalling
        o Use commitment control
        o Use a UPS

and possibly:

        o install a generator
        o install a second system

thus you keep your data integrity and you get good performance.  I guess on a
fast system you could run with FRCRATIO(1) but I suspect you would soon reach
saturation on disk arm utilisation because every output operation becomes
synchronous and the queueing multiplier effect will cripple your system.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.