My apologies, I am on digest, but if you want to monitor DELETE.FILE, put a wrapper on it.
:CT VOC DELETE.FILE VOC: DELETE.FILE: S DELETE.FILE.WRAP :CT VOC DELETE.FILE.WRAP VOC: DELETE.FILE.WRAP: C /TESTPLACE/TEST.PROGRAMS/SOME.BP/_DELETE.FILE.WRAP (or globally catalog it) :ED SOME.BP DELETE.FILE.WRAP Top of "DELETE.FILE.WRAP" in "SOME.BP", nnn lines, nnnn characters. 001: * DELETE.FILE.WRAP 002: * Simulate the DELETE.FILE command to track to a file. This is on UniData, but you get the general idea. Be careful to account for saved lists. I am curious though, how it is that you restore the file and if it's restored, why the voc pointer to the voc file would be missing from the restored file... Shaun Ferguson Master Data Systems Analyst/Global Business Applications Wolseley North American Division- 12500 Jefferson Avenue - Newport News - VA - 23602-4314 T: (757) 989-2916 - F: (757) 989-2801 - E: [email protected] www.wolseley.com <file:///C:/Documents%20and%20Settings/SFERGUS1/Application%20Data/Micro soft/Signatures/www.wolseley.com> ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
