One "easy" way is for the daily job to process all generations of the
dataset, then delete them when it's captured the data.
There are variations on that theme using that would involve copying the
FTP generations to a "workday" generation if you need to keep the input.
One thing I've learned, you can't trust "somewhere", they will send
yesterdays data again, then send today's, send todays twice, send
nothing, have a transmit problem, or something to ruin your sleep....
Frank Swarbrick wrote:
Consider the following...
A file is received (via FTP) 7 days a week from somewhere. The FTP writes to
generation +1.
Problem: The program that uses the file(s) runs only every business day. On
a regular Tuesday-Friday it needs to only read the most recent generation
(0). But on Monday it needs to read (0), (-1) and (-2). And of course there
are holidays to consider.
Thoughts on how this can be addressed?
Thanks,
Frank
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
