BPA0016E DB2 UTILITY APPLICATION INCOMPLETE Reason Code 00E40070 executing Database Management Solutions Post install Create Required Db2 Objects task
search cancel

BPA0016E DB2 UTILITY APPLICATION INCOMPLETE Reason Code 00E40070 executing Database Management Solutions Post install Create Required Db2 Objects task

book

Article ID: 93024

calendar_today

Updated On: 03-28-2025

Products

Database Management for DB2 for z/OS - Administration Suite Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Utilities Suite DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS Batch Processor

Issue/Introduction

When executing the Post Install Create Required Db2 Objects job (ssid0001) after upgrading the Database Management Solutions to the r20 release,
the following error was encountered during a Load utility::

DSNU037I 109 11:12:42.23 DSNUGSDA - RECFM=U FOR DDNAME PTILOAD
DSNU016I 109 11:12:42.24 DSNUGBAC - UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X'00E40070'
BPA0016E: DB2 UTILITY APPLICATION - INCOMPLETE. 
.FREE FI(SYSIN) .FREE FI(SYSPRINT) RETCODE = 16

Resolution

This error can occur when the unload step fails with:
DSNU185I  -ssid 088 09:21:19.51 DSNUGSRI - THE VSAM DATA SET DOES NOT EXIST FOR
            TABLESPACE PTDB.TSNAME

If the tablespace is created with DEFINE NO, the underlying VSAM LDS is not created until data is inserted. The Load fails because there is no data written to the unload file.


                                          
As there is no data to unload or load there are two ways to circumvent the problem:
 
1. Restart the ssid0001 job in step EXECRBP2 at the NEXT Sync point after the Db2 Load. 

Restart step EXECRBP2 via .RESTART SYNC ###:
.RESTART SYNC nnnn 
.CONNECT ssid

 

2. Edit the hlq.CDBASAMP(ssidDDL) and specify DUMMY for the PTILOAD allocation for the failed table load: 

.ALLOC FI(PTILOAD) + 
DUMMY

Additional Information

- If the problem occurred processing a utility (Load, Unload, Reorg etc...) terminate the UTILID shown in the output prior to restarting.
- If a COPY was being processed, delete the allocated copy dataset prior to restarting.

See also: RC/Migrator : Restart of a Utility Execution during an execution of Batch Processor code.