I've also seen it done by accident. Part of the
production run deletes and redefines a dataset
(IEFBR14). Next, program 1 updates it, then program 2
reads it. One day, program 2 got the previous day's
data. User tried again with same result. As it turned
out, there was only the one area available to reallocate
the dataset - right where it was, before. Program 1 had no
data for that dataset, so it never opened and closed it, so
there was no EOF written. Program 2 read the old data.
You could consider this to be a flaw in program 1. If it has no data to
output, it should still open and close the output file to indicate this.
--
Bruce Black
Senior Software Developer
Innovation Data Processing
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
