We load AFP documents from a windows box to CMOD on z/os. ARSLOAD is running as a service on the windows box. Twice now the security was removed that provided delete authority from the id that runs the ARSLOAD service. The load works fine but the file is not deleted. What this means is that the same set of 10 files were loaded thousands of times, spawning many new DB2 tables. We noticed it days later when the folder query response went to hell doing a union on 82 tables.
CMOD support says not their issue. I am fighting this because it’s a documented feature to delete the file, and minimally I believe a syslog record should be cut because the delete failed. However, they are not budging.
What I did was write a program that runs hourly and looks back 3 hours in the system load table to ensure no duplicate file names in the input_file_name column. While this catches the issue much quicker, we still have the potential to have many hundreds of loads to remove.
Any ideas on a more proactive approach? I am at wits end on this one.
Is there a way to read the security on the windows box, or a log to see that it was changed? Being windows server illiterate, I am unsure where to start.
