Re: Speaking of APIs ....

I'm an outsider, so Bruce will know this better. But it seems that the setting
is not about reads, it is about writes (updates) to disk. To me this is similar
to FRCRATIO(1) on a PF - this can slow things down some. If you do asynchronous
writes to disk, you go faster. The data is still available as being in the PF
(or index?) but you have a very small window of vulnerability in the case of a
power failure. With user indexes, this is probably not so critical as with data
in files.

I ramble - but I see forcing to aux storage (disk) as ensuring no loss of data
- asynchronous writes have a microscopic chance of losing something.

To clarify, the data IS in memory and associated with the object at hand - so
any other app has access to it, even if it is not written to aux storage yet.

HTH
Vern

-------------- Original message --------------
From: AGlauser@xxxxxxxxxxxx

Thanks Vern and Bruce.

Vern Hamberg wrote on 01/05/2007 21:26:31:

Auxiliary storage means DASD - disk. Synchronously means it is done
right away, as Bruce said.

So, does that mean that the option for immediate update (or not) does not
affect the retrieval of user index entries (short of power failures or
other problems with main memory)?

Attention:

The information contained in this message and or attachments is
intended only for the person or entity to which it is addressed and may
contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received this message in error, please contact the sender
and
delete the material from any system and destroy any copies. Thank you for
your
time and consideration.

Attention:

Le contenu de ce message et(ou) les fichiers ci-joints s?adressent
exclusivement à la personne ou -entité à laquelle ils sont destinés. Ils
peuvent
contenir de l?information confidentielle, protégée et(ou) classifiée. Il est
strictement interdit à toute personne ou entité autre que le(la) destinataire
prévu(e) de ce message d?examiner, de réviser, de retransmettre ou de
diffuser
cette information, de prendre une quelconque action en fonction ou sur la
base
de celle-ci, ou d?en faire tout autre usage. Si vous avez reçu ce message par
erreur, veuillez communiquer avec l?expéditeur(trice), supprimer ce message
et
les fichiers ci-inclus de tout système, et en détruire toutes copies,
qu?elles
soient électroniques ou imprimées. Nous vous remercions de votre entière
collaboration.