S04E Abend with REASON=X'00E40347'

krithikaj · New User Joined: 10 Aug 2008 Posts: 45 Location: India

Hi,

I am trying to load data into a table that is partitioned using IBM LOAD and my job is ending up with S04E Abend. Please find the joblog below.

************************************************************************************
RESOURCE UNAVAILABLE
REASON 00D70014
TYPE 00000220
NAME DDZI.DSNDBC.DTVIPC.STVIPC0.I0001.A087
UTILITY DATA BASE SERVICES MEMORY EXECUTION ABENDED, REASON=X'00E40318' CAUSE=X'00C9000A'
UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X'00E40347'
************************************************************************************

Can somebody help me what is the problem and what can be done to solve this issue.

Thanks,
KJ

vishal_arora · New User Joined: 20 May 2005 Posts: 16

Hi ,

Well just this much of information is not enough to resolve your issue. Need some more details like :

1) Did you get this error on first partition itself or some records got loaded to partition then abended.
2) Need to look at load card.

Alternatively you can try :

1) See if there is UTIL id clash or some database backup jobs are running and the tablespace is in UT mode.
2) May be the partition you are trying to load is full . You need to terminate the load utility and then alter the partition key.
3) what operation used ? Load Replace or Resume . In my opinion first partition should be replace then resume otherwise if replace is used for all the partition then the tablespace gets deleted everytime.

krithikaj · New User Joined: 10 Aug 2008 Posts: 45 Location: India

Thanks for your reply.

I did not get this error for the first time. Actually my table has 545 partitions each having a capacity to hold about 25million rows. I got this abend while I was trying to load Part 87.

Please check the Control card
LOAD DATA LOG NO RESUME YES NOCOPYPEND
SORTNUM 128
SORTKEYS 1600000000
SORTDEVT SYSDA
INTO TABLE DBNAME.TABLENAME PART 0087 REPLACE REUSE INDDN(SYSREC)

The tablespace is in RW when I tried submitting the job.

Thanks,
KJ

vishal_arora · New User Joined: 20 May 2005 Posts: 16

Hi ,

I am doubting this as a SPACE issue as the Reason code and Resource type is pointing this only.

I think the VSAM datasets which is corresponds to your tablespace partition 87 reached max extents .

123 - is max extents for single volume VSAM dataset
255 - is Max extents for Multivolume datasets

Please use ISPF 3.4 option , to the check the max extents of the VSAM datasets for the tablespace . You can get the name of the datset from the joblog of your job .

If that's the case then you need to contact your DBA for a Alter Tablespace and increasing the PRIQTY and SECQTY or require a REORG.

Thanks

krithikaj · New User Joined: 10 Aug 2008 Posts: 45 Location: India

What you mentioned is true.

Thank You so much for your reply.
KJ