The FSETMODE intrinsic activates or deactivates the access mode option that permits critical output verification. This means that all output must be verified as physically complete before control returns from an output intrinsic (FWRITE,FUPDATE, or FREMOVE) to your program.
The access mode established by the FSETMODE intrinsic remains in effect until another FSETMODE call is issued or until the file is closed.
USING FSETMODE |
 |
When FSETMODE is executed with the modeflags parameter equal to 2 (bit 14=1), then each logical record written by an output intrinsic is physically transferred to the file immediately. Control is not returned to the user program until the transfer has been made. At that time a CCE condition code is returned to the program.
When FSETMODE is executed with the modeflags parameter equal to zero (bit 14=0), output is treated in the standard manner. That is, when an output intrinsic writes a logical record, the record is physically transferred to the file only when the entire physical record (block) of which it is a part is transferred. (Calls to FWRITE, FUPDATE, and FREMOVE send output to the KSAM file.)
For example, the following intrinsic call activates critical output verification:
If you want to return to normal output mode, you can use the call:
When the file is first opened and when it is opened subsequently following an FCLOSE call, the critical output verification mode is deactivated.
