The CICS asynchronous API provides a simple, supported way to improve efficiency and reduce response times via asynchronous processing. For system administrators, the API affords a great opportunity to improve performance, and using CICS policy, you can gain even finer control over the the parent and child tasks in your system.
CICS policy provides a set of rules which monitor and control user tasks. Defined via CICS Explorer, they set limits which, if met or exceeded, result in the affected CICS regions automatically taking some action. CICS policy is defined in a CICS bundle, and can be scoped to a CICS region, CICS application, or a CICS platform.
Async requests rule type
To help control parent tasks, and the asynchronous workload started by
EXEC CICS RUN TRANSID commands, a new policy rule type has been introduced:
Async requests. Using the
Async requests rule type, you can choose a threshold for how many
RUN TRANSID commands can be issued before the policy action is initiated.
In this example, the async_over_3 rule specifies that if a task issues more than three
RUN TRANSID commands, CICS will issue message
DFHMP3001 to let you know:
The async_over_1k rule, on the other hand, will abend a task if it issues more than a thousand
RUN TRANSID commands. A
DFHMP3002 message will be issued, along with the abend code
AMPB. Abends caused as a result of policy rules can be handled just like any other abend.
Using CICS policy you can govern tasks in a CICS region in a simple and unobtrusive way, keeping your applications under control. For more details about defining and using CICS policy, see Creating policies in the IBM Knowledge Center.