Configuring CA Products for CAISDI › CA Products That Support CA Service Desk Integration › CA OPS/MVS Event Management and Automation

CA OPS/MVS Event Management and Automation

The following CAISDI/med PRODUCT and EVENT initialization statements define the interaction between CAISDI and CA OPS/MVS Event Management and Automation to generate CA Service Desk tickets for CA OPS/MVS Event Management and Automation product abends as well as internally detected PROBLEMs:

/*==================================================================*/
/*    Unicenter CA-OPS/MVS Product Interface Definitions            */
/*                                                                  */
/*    Define Unicenter CA-OPS/MVS product ABEND and PROBLEM         */
/*    events that are to be captured by CAISDI/med, and how         */
/*    that information is to be presented in the request ticket     */
/*    to CA Service Desk.                                                    */
/*                                                                  */
/*   Required customization:                                        */
/*                                                                  */
/*      SERVER  CAISDI/med name for Service Desk Server             */
/*                                                                  */
/*   NOTE:  Sample values for AFFECTED_END_USER, REPORTED_BY,       */
/*          ASSIGNEE, and TEMPLATE are valid, provided the          */
/*          CA Service Desk Administrator loads predefined   */
/*          templates and contacts.  Otherwise, customize these     */
/*          parameters as directed by the Unicenter Service         */
/*          Desk Administrator.                                     */
/*                                                                  */
/*==================================================================*/

PRODUCT CA-OPS/MVS,               /* Define product name            */+
        EVENT=(ABEND,PROBLEM),    /* Event qualifiers               */+
        JOBNAME=OPSMAIN,          /* Product started task name      */+
        AFFECTED_END_USER=System_OPSMVS_User,   /*Affected End User */+
        REPORTED_BY=System_OPSMVS_User,  /* Reported By for tickets */+
        ASSIGNEE=System_OPSMVS_User, /*Assigned contact name        */+
        PRIORITY=2,               /* Priority for tickets           */+
     /* TEMPLATE='CA-OPSMVS,Priority unassigned',  /* Template      */+
        SERVER=USDSRV01           /* Direct request to this server  */

EVENT ABEND,                   /* Capture ABEND events              */+
      COMPONENT='OPS*',        /* Unicenter CA-OPS/MVS component ID */+
      PRODUCT=CA-OPS/MVS       /* Associated product statement      */  

The preceding example shows how the PRODUCT and the EVENT statement are used to activate the capture of a named product's abend events and to define the associated CA Service Desk attributes to be associated with tickets that are opened as a result of the abend event. The PRODUCT statement EVENT parameter operands indicate that the product definition is to be used for both abend events captured by CAISDI as well as PROBLEM events generated by CA OPS/MVS Event Management and Automation itself.

Beginning with the EVENT statement, the crucial specification is the COMPONENT operand, OPS. CA OPS/MVS Event Management and Automation recovery routines always place the character string, OPS, in the SDWACID field for all CA OPS/MVS Event Management and Automation abend events. Therefore, this COMPONENT specification indicates that CAISDI abend event intercept should capture any detected abend event where the concatenation of the SDWACID and SDWASC fields begins with the characters OPS. The asterisk (*) in the sample initialization statement is a wild card and indicates that any subsequent characters are considered a match condition.

The PRODUCT parameter, CA‑OPS/MVS, defines the CAISDI product name to associate with abend events captured due to a matching COMPONENT specification. It is this PRODUCT name specification that makes the connection to a specific CAISDI PRODUCT initialization statement.

The preceding PRODUCT statement defines CA OPS/MVS Event Management and Automation as referenced in the PRODUCT= parameter of the EVENT statement. The PRODUCT statement EVENT parameter qualifies that the product events associated with this product definition are abend events, and PROBLEM events. CA OPS/MVS Event Management and Automation can report on internally detected problems using a proprietary interface to CAISDI. Internal tickets generated using this interface specify a product name of “CA OPS/MVS Event Management and Automation” and an event type qualifier of “PROBLEM.” Therefore, a single CAISDI PRODUCT name of CA OPS/MVS Event Management and Automation with an event list of abend and PROBLEM are used to assign CA Service Desk tickets.

The SERVER parameter refers to the SERVER statement that defines the CA Service Desk server that is to receive tickets associated with this product definition.

The remaining parameters define the names of predefined CA Service Desk specific entities that are to be assigned to any generated tickets. These named entities should be predefined by the CA Service Desk administrator on the target CA Service Desk server.

The most important predefined entity is the CA Service Desk TEMPLATE name. The proper use of predefined CA Service Desk templates ensures that tickets generated by CAISDI on behalf of the named product are properly categorized, prioritized, and assigned.

The AFFECTED_END_USER parameter is used to define the contact name that appears in the Affected End User field of the ticket.

The REPORTED_BY parameter is used to define the contact name that appears in the Reported By field of the ticket.

The PRIORITY parameter defines the Priority of the ticket.

The ASSIGNEE parameter is used to define the contact name that appears in the Assignee field of the ticket.

For detailed information on these parameters, see Running CAISDI.