You can extend and customize CICSĀ® Configuration Manager server processing by attaching your own CICS programs to the following user exit points:
You can write user exit programs to perform the following tasks:
You can use this exit point to enforce site standards upon resource definition names and attributes. For example, when a user edits and then attempts to save a resource definition, your user exit program can check the resource definition name and attributes, and then disallow the update, or allow the update as requested, or allow the update with some attribute values updated to match site standards.
You can use these exit points to augment change package workflow. For example:
For the change package pre-processing exit point, you can write user exit programs to disallow or allow the API command.
If a change package API command updates resource attributes, then the command triggers the following exits:
You can write user exit programs in any language supported by CICS.
For additional information on these exit points, view the online help for the CICS Configuration Manager ISPF dialog interface: go to option 1.6 Exit Points, and then press the Help key (F1).
The following figure shows the user exit points, their names, and where they occur in a typical change package workflow.