I have some programs which convert massive amounts (3M RECORD SETS) of data from flat ascii files into various related FP tables. In an attempt to improve performance I liberally used the SP3 command, INDEXSEEK as opposed to SEEk. I found that this function exhibits a nasty memory leak when used in a high volume repetitive loop and have since converted back to SEEK.
Has anyone else experienced a problem with INDEXSEEK?
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only