Change package pre- and post-processing exit points

Start of change Change package exit points occur before and after processing an API command for a change package: Approve, Backout, Create, Delete, Disapprove, Discard, Import, Install, Migrate, Newcopy, Ready, Unready, and Update.End of change The pre-processing exit points occur after any security checks.

You can use these exit points to augment change package workflow. For example:

For the pre-processing exit points, you can write user exit programs to disallow or allow the action.

Table 1. Change package exit points
API command Pre-processing exit point name Post-processing exit point name
Approve CPPRAP01 CPPOAP01
Backout CPPRBO01 CPPOBO01
Start of changeCreate, Update, Start of changeor DeleteEnd of change  1 End of change Start of changeCPPRED01End of change Start of changeCPPOED01End of change
Disapprove CPPRDA01 CPPODA01
Start of changeDiscardEnd of change Start of changeCPPRDI01End of change Start of changeCPPODI01End of change
Import CPPRIM01 CPPOIM01
Install CPPRIN01 CPPOIN01
Migrate CPPRMG01 CPPOMG01
Newcopy CPPRNC01 CPPONC01
Ready CPPRRD01 CPPORD01
Unready CPPRUR01 CPPOUR01
Start of change 1 End of change
Start of changeThe Edit exit point is executed for the API commands Create, Update, and Delete. An Update command for a change package causes its attributes, such as description or external reference, to change. In the following situations, the Edit exit point does not execute:
  • When resource definitions or commands are added to or removed from a change package
  • When the attributes of a change package are set by another API command, such as when the status of a change package is set by the Ready API command
End of change