Search

Monday, October 1, 2012

DB2 Abends while loading unloading tables


Here are some common abends faced while running DB2 load unload.

Issue: The error shows input field is not matching the data or vice versa. Key word here is 'INPUT FIELD 'ACCT_3' NOT ENTIRELY WITHIN INPUT RECORD'


DSNURWI - TABLE SPACE DatabaseName.tablespace WILL REMAIN IN BASIC ROW FORMAT DUE TO 
SPRMRRF=DISABLE
DSNURRST - EXISTING RECORDS DELETED FROM TABLESPACE                            
DSNURWBG - INPUT FIELD 'ACCT_3' NOT ENTIRELY WITHIN INPUT RECORD          
DSNURWBF - (RE)LOAD PHASE STATISTICS - NUMBER OF INPUT RECORDS PROCESSED=1     
GBAC - UTILITY DATA BASE SERVICES MEMORY EXECUTION ABENDED, REASON=X'00E40323' 



Reason: Developer needs to rule out following  causes: 
1.Check the SYSPUNCH for the table if it is correct. 
2.Confirm that table layout has not changed.
3.Check if the table used to unload in the JCL and the corresponding UNLOAD file is correct. Same for the load.

Issue: The error shows job cannot restart. Key word here is 'JOB IS NOT RESTARTABLE DUE TO -START DATABASE ACCESS FORCE COMMAND'


OB61261.D0000101.?,2012.275,07:29:21:62       <FILE                            
SNUGUTC - OUTPUT START FOR UTILITY, UTILID = ID.Jobname                 
SNUGTIS - PROCESSING SYSIN AS EBCDIC                                           
43 DSNUGASU - JOB IS NOT RESTARTABLE DUE TO -START DATABASE ACCESS FORCE COMMAND
SNUGBAC - UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X'00E40018'    


Reason: Developer needs to rule out following  causes 

1.Never do Stop/Start with ACCESS(FORCE) in DB2 Commands
2.Check if the job has abend earlier and utility is terminated.
3.Check if the table is in RW mode and with normal Start.




1 comment:

  1. Why exactly ACCESS(FORCE) creates issue while loading/unloading?

    Sreenivas
    Clearmainframeinterview.blogspot.com

    ReplyDelete