Policy actions

CICS® monitors task resource utilization and if any thresholds, as defined by any deployed policies, are exceeded, CICS performs the specified action. The actions that can be performed when a threshold is exceeded are:

• Issue the message DFHMP3001, which is the default policy action. This message is issued so that the system programmer can take the appropriate action.
• Abend the task. The task is ended by CICS, message DFHMP3002 is issued, and either the default abend code AMPB or a user-specified abend code is issued. By default a transaction dump is taken for the abend. You can suppress the transaction dump or request a system dump by using the CEMT SET TRDUMPCODE|SYDUMPCODE and EXEC CICS SET TRANDUMPCODE|SYDUMPCODE commands. You can handle the abend by using the EXEC CICS HANDLE ABEND command.
• Emit an event. The user can specify the name of either an EP adapter or EP adapter set. The event has the same behavior as CICS system events, and as with system events, a policy event can be emitted to only an asynchronous and non-transactional EP adapter. The information that is captured in the event is pre-determined and non-customizable. Items that are captured and displayed in the event context are:
  • Policy schema version
  • Policy schema release
  • Event binding name: "CICS Policy Event"
  • Capture spec name: "CICS_Policy_Event_Capture_Spec"
  • Event binding user tag
  • Business event name: "CICS_Policy_Event"
  The following items are captured and displayed in the event data:
  • Policy name
  • Rule name
  • Rule type (for example, "storage")
  • Rule item (for example, "task24")
  • Operator (for example, "GT")
  • Threshold (for example, 2048)
  • Current count (for example, 2200)
  • Platform name
  • Application name
  • Application version (major.minor.micro)
  • Operation
  • Bundle name which contains the policy
  • Bundle version (major.minor.micro)
  • Bundle ID
  • Date
  • Task ID
  • Transaction ID
  • Program name
  • Policy usertag