My company has been using CMOD to load very large accounting reports to mainframe CMOD. We are now in the process to migrate from the mainframe CMOD to AIX CMOD. Numerically speaking, I have moved 90% of the data for about about 80% of the necessary reports. Along the way, I ran into ARS024 object recovery errors for a few reasons.
The data migration method is an "arsdoc get" from mainframe CMOD followed by an arsload to AIX CMOD.
It turns out some ARS024 errors would eventually return all a report's document objects intact, sometimes failing at different points along retrieval, but subsequent reads of data in OAM progressed further and further, until completely successful. This was observed in the output logs.
I have a more persistent error, with very large reports failing perhaps in DB2 buffering, with the report being unable to be uploaded, then transferred to the intermediate Windows retrieval server. Which is never out of space. These reports are 40,000 to 50,000 pages of line data. In one load sequence, with multiple reads per object, only one report loaded out of 21 attempted. This particular report is in 500 page blocks, and with a page range value. There may be from 70-100 index lines for the report, but due to page range, the report is viewed as a single object in the arsdoc get retrieval .
I am out of support with z/OS CMOD 9.04.
Any ideas out there ? Or is this report stuck on z/OS CMOD forever ?
Larry Wagner