committment control and file changes

Physical file changes under commitment control can be rolled back for errors.

Do Logical files behave the same way ie the underlying PF would roll back the same way that direct PF updates would? Or are there some restrictions on LF's that would cause programmers to use the LF to read the PF by primary key and update the PF directly?

Do OPNQRYF's behave the same way as PF's also? Ie will the based-on PF roll back on an error while under commitment control?

Does the file output method matter? Ie if a file is opened as OUTPUT vs UPDATE would both of these behave the same ? ie rollback on error under CC?

Some pgmrs here claim that PF updates roll back nicely, whereas LF updates do NOT roll back. Is this possible? (assuming all files are journalled properly and such)

Thanks!





______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________