Upgrade from Database Management r19 to r20.0 and RC/Migrator Job finished with RC=04 instead of RC=00

Products

• RC/Migrator for DB2 for z/OS
• RC Compare for DB2 for z/OS

Issue/Introduction

With RC/Migrator for Db2 for z/OS (RCM) r19 there was a call to .CALL LOADDEL program, data sets were not allocated or cataloged and
the job issued BPA0085I message, the RC/Migrator job finished with RC=00.
 
.CALL LOADDEL
BPA0085I: BATCH PROCESSOR WAS UNABLE TO DELETE THE FOLLOWING DSN:
'xxxx.xxxx.xxxx'.

RETCODE = 0


With RCM r2 the same call to .CALL LOADDEL program and data sets were not allocated or cataloged, now BPA0085W message was
issued and RC/Migrator job finished with RC=04.
 
CALL LOADDEL
BPA0085W: BATCH PROCESSOR WAS UNABLE TO DELETE THE FOLLOWING DSN:
'xxxx.xxxx.xxxx'.

RETCODE = 4

Resolution

This behavior was changed by RC/Migrator 20.0 IR5 PTF SO04470 Item 40.

Copied here the text of Item 40:
>>>
RBP CANNOT DELETE FILES, BUT STILL GIVES RETCODE = 0

PROBLEM DESCRIPTION:
The return code is set to zero (0) by the Batch Processor interface component
(RBP) of the CA Database Management Solutions for DB2 for z/OS,even when it
cannot delete files during the LOADDEL phase of execution.

SYMPTOMS:
The Batch Processor job executes with RC = 0, even when there is a problem
with deleting the files.

IMPACT:
Subsequent jobs abend because the files are not deleted in the previous jobs.

CIRCUMVENTION:
None.

PRODUCT(S) AFFECTED:
Batch Processor Interface Release : 19.0
Batch Processor Interface Release : 20.0
<<<

The PTF for Release 19.0 was SO03652, with this PTF applied over Release 19.0 RC/Migrator job should have finished with RC=04 as well.