Implementing Processes › Generic Processes Using Resource Variables

Generic Processes Using Resource Variables

You can define generic processes that perform functions that are dependent on how they are initiated by using resource variables. These variables contain information about a resource that is defined to the knowledge base. They are useful for building automated paging, standardized startup for CICS regions, and many other tasks where a uniform solution is required. Using a generic process reduces any overhead associated with building individual processes for individual resources.

Note: For information about knowledge base variables, see the Reference Guide.

Example: Use Process to Page Support

Service level agreements require that appropriate support personnel are pageable if any production CICS region is under stress. CA Automation Point is available at your site to monitor the condition and provide the paging function. Different CICS regions have different support personnel assigned.

You implement the following method in the CICS resource definitions:

1. Specify details of the support personnel.
2. Identify and specify the message to trigger automated paging.
3. Specify an event-related action for this message using the following generic process:

    |                     Condition                                               |
    |      StepName   Step/RC  Opr RC    Macro    Description                     |
    |      S1                            WTOR     WTOR TO L1 SUPPORT              |
    |      S2         S1       EQ  32    WTOR     TIMED OUT - CALL L2             |
    |      S1OK       S1       EQ  0     SETSTATE L1 RESPONDED - SET EXT. DISPLAY |
    |      S2OK       S2       EQ  0     SETSTATE L2 RESPONDED - SET EXT. DISPLAY |
    |      S3         S2       NE  0     GENALERT NO SUPPORT - RAISE ALERT        |
    |      S4         S2       NE  0     SETSTATE NO SUPPORT - SET EXT. DISPLAY   |
   

   1. At Step S1, the resource sends a WTOR message, using knowledge base variables (for example, &ZRMDBREOPAG1 that contains the pager number) to provide details of the support personnel responsible for the failing resource.

      CA Automation Point or by an operator intercepts the WTOR message, and the indicated first-level support person is paged. Response to the message indicates the success or failure of paging.

   2. If paging of the first-level person is successful, Step S1OK sets the extended display of the resource to indicate that the support person has acknowledged the paging.

      If no reply is received within a specified period, Step S2 sends another WTOR message to invoke paging of the second-level support person.

   3. If paging of the second-level person is successful, Step S2OK sets the extended display of the resource to indicate that the support person has acknowledged the paging.

      If paging fails, Step S3 raises an alert and Step S4 sets the extended display of the resource to indicate that no support personnel have responded.