Why does RC/Migrator strategy analysis end when a return code 4 is issued
search cancel

Why does RC/Migrator strategy analysis end when a return code 4 is issued

book

Article ID: 230618

calendar_today

Updated On:

Products

RC/Migrator for DB2 for z/OS Batch Processor

Issue/Introduction

Why does the RC/Migrator for Db2 for z/OS (RCM) analysis of a strategy end when no error has occurred.
The analysis issued a return code 4 (warning).

Resolution

Batch Processor (RBP) issues the following warning message to indicate that a utility issued a warning message with a return code 4.

BPA0046W: UTILITY WARNING MESSAGE(S) ISSUED. UTILITY RETURN CODE = 4.

With .OPTION NOERRORS specified, RBP stops processing as a non-zero return code has been returned.

.OPTION NOERRORS NOSQLERRORS RETRY(96) BINDERRORS

Review the utility messages for any messages that have resulted in a return code 4.

To allow RBP to continue processing when it receives a warning message with a severity of 4,  .OPTION ERRORS needs to be specified. RBP will then stop processing
if return codes 8, 12, and 16 are generated for non-SQL errors.

Note the ERRORS/NOERRORS option is controlled by the CONTINUE IF WARNING processing option.

Other than specifying .OPTION ERRORS to allow RBP to continue when a warning message is issued, one other suggestion could be to add the
utility message to the BATPROC Parmlib member.

/*  BPUTILM:       SPECIFIES UTILITY MESSAGES AND THE      
/*  WAY THEY SHOULD BE INTERPRETED BY BP.                  
/*                                                         
/*      BPUTILM IS A SET OF PAIRS - (MSGID,X) WHERE MSGID  
/*      IS THE MESSAGE IDENTIFIER, AND X IS EITHER O -     
/*      MEANING THE UTILITY WARNING MESSAGE IS OK, OR      
/*      B - MEANING THE UTILITY WARNING MESSAGE IS BAD.    

For example, adding the following to the BATPROC Parmlib member

(DSNU1166I,O) would be interpreted as the message is OK and the execution of the script will continue.