NOBUF

NOBUF

Top  Previous  Next

 

The NOBUF statement turns off buffering for a record opened using OPENSEQ.

 

 

Format

 

NOBUF file.var

{THEN statement(s)}

{ELSE statement(s)}

 

where

 

file.varis the file variable associated with the record by a previous OPENSEQ statement.

 

statement(s)are statement(s) to be executed depending on the outcome of the NOBUF statement.

 

At least one of the THEN and ELSE clauses must be present.

 

Normally, QM buffers data for records opened using OPENSEQ. The NOBUF statement turns off this buffering such that READBLK will read the exact number of bytes specified and READSEQ will read byte by byte until a line feed character is found. WRITEBLK, WRITESEQ and WRITESEQF will write data without intermediate buffering.

 

Using unbuffered processing will result in lower performance than normal operation but may be useful, for example, when the item opened using OPENSEQ is actually a device or a pipe rather than a file system data record.

 

 

See also:

CLOSESEQ, CREATE, OPENSEQ, READBLK, READCSV, READSEQ, SEEK, WEOFSEQ, WRITEBLK, WRITECSV, WRITESEQ, WRITESEQF