We experienced problems on our backleveled CMOD (AIX, DB2, TSM) which we are planning to upgrade soon. This ultimately was due to the TSM database filling up and saturating at 100% utilization. As part of the resolution process, we recycled the production server.
Since that time, as long as ARSLOAD is successful it works normally. However, for the small percentage of files that need to fail, it puts the standard 88 message in the syslog, then the process hangs and must be manually killed.
Only then does it react as it used to, appending the back input file name as .FAILED and continuing onto the next file to load. No obvious syslog error messages.
Not sure if related, but we have another process which is also hanging. If we run ARSMAINT w/o specifying a Application Group, it hangs. We had a scheduled process to reduce it to the standard 80% once nightly. If we run ARSMAINT vs an application group or groups, it works for the most part. Although we seen to have lost link to DB2 occasionally and had to recycle that connection.
It seems that may be due to the dreaded "broken links in cache" issue, which doesn't seem to have a well documented solution.