I am trying to load very high number of records into a table. Due to the enormous input, the sort dataset (SYSUT1 and SORTOUT) became full and the job went down with SB37.
To avoid this condition, i defined the sort dataset on CART and submitted the job again (after terminating the utility and correcting the Recover pending status on indices). It ran fine and completed successfully.
I, then extended the same method (of creating sort dataset on CART) for loading another table of equal size. But this time it abended with S7FA code. The Output message showed that the
I tried submitting the job again but was of no use.
Did you made sure that, Tablespace and indexspace was not in restricted state when the LAOD job failed for the first time. But i do wonder how it ran second time when you defined on disk volume.
You can always use the SORTKEYS & SORTDEVT options to get rid of SYSUT1 & SORTOUT work datasets. These parameters adds to performance as well. It will avoid lot of I/O's especially when you have more indexes and more data on the table. I hope you are in the DB2 V7 or Higher level. Thanks
I will try and see if SORTKEYS and SORTDEVT can help me. At the same time i am curious to know the reason behind the abend. The problem seems to be with CART.A Search on '07FA' the reason code suggests some MQ object being already open.It would be wonderfull if that error mesasage could be understood .
PS: I had made sure that the DATABASE and all the related Indices were not in restricted state or any other abended state.