Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp

:

more options
 

hp.com home
End of Jump to page title
PLI - Difference Between FLUSH After A Put And A Write
Jump to content



» 

business support center

Home & Home Office Support:
» HP branded products
» Presario branded products
» Services & Warranties
Small & Medium Business Support:
» Small & Medium Business products
» Small & Medium Business services
Support for IT Professionals:
» Enterprise products (IT Resource Center)
» NonStop enterprise products
» Business & IT Services
Content starts here
Copyright (c) Digital Equipment Corporation 1992. All rights reserved
LAYERED PRODUCT:  VAX PLI                           OP/SYS:  VMS

SOURCE:     Digital Customer Support Center

SYMPTOMS:

The built-in FLUSH subroutine in PL/I doesn't seem to flush the last buffer
when the PUT statement is used but it does when the WRITE statement is used.

ANALYSIS:

This behavior is correct.  For data written with the PUT statement, PL/I
buffers this data in a "stream block".  The $FLUSH system service, called
by the FLUSH() built-in subroutine, flushes only the RMS buffers.  Since
PL/I has not written its stream block using RMS, the missing data is not
in the RMS buffer(s) to be flushed.

In the case of record I/O (WRITE), it manipulates RMS buffers directly and
does not use its own buffering, hence a $FLUSH on a record I/O statement
accurately reflects all I/O done to the file.  This second is more important,
since shared access to files typically happens on record-oriented files (i.e.
relative or indexed sequential) rather than on stream files.




buy online or call 1.800.AT.COMPAQ
privacy statementusing this site means you accept its terms