I may have posted something on this subject before but it started rearing its ugly head again....We periodically get this type of failure...In most cases we can rename the .failed file and when doing so, the file will always load successfully (at least up till now)...Our issue is, we still have reports coming from the mainframe to CMOD which use OS/390...When this type of file fails, the mainframe job itself has to be rerun manually. We risk the possibility of losing data in the event the job runs multiple times and data from failed job gets overwritten. Our engineering group contacted ECS storage...here was their response:
"This represents a failure rate of 0.02 for clip writes and 0.01 for blob writes
We generally advertise ECS availability of 99.9% which you are well within
There is no concern here. The application will automatically retry these failures which will succeed upon retry".
The main issue here is, ERR doesn't support automatic retry...Our options are to manually rename .failed file or manually re-run mainframe job.
Anyone else using ECS storage having any issues?
Appreciate any feedback
Dave