PH59026: BLOCKBASE GENERATION OPTION COMMIT=YES INOPERATIVE

APAR status

• Closed as fixed if next.

Error description

• In RPP documentation, option COMMIT=YES generates a COMMIT
  after a DROP.
  So, in the same flow of commands, it is possible do delete and
  then recreate the same object.
  However, despite COMMIT=YES is specified in -GO, no COMMIT is
  generated after a DROP.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All the RPP users who generate relational database blocks.   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The COMMIT option, which generates a COMMIT WORK after each  *
  * DROP line when COMMIT=YES is set on -GO of the relational    *
  * database block is not taken into account in RPP.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels