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 and 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 */
This example shows how the PRODUCT and the EVENT statement are used to activate the capture of abend events for a named product 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 used for both abend events that CAISDI capture and PROBLEM events that CA OPS/MVS Event Management and Automation generates.
Defines the product, in this case CA OPS/MVS Event Management and Automation.
Indicates that the product events associated with this PRODUCT definition are abend events.
Defines the job names to which this product statement applies. In the preceding sample, all jobs beginning with “RMO*” would qualify for the processes that are defined for this product statement.
Defines the contact name that appears in the Affected End User field of the ticket.
Defines the contact name that appears in the Reported By field of the ticket.
Defines the contact name that appears in the Assignee field of the ticket.
Defines the Priority of the ticket.
Defines the CA Service Desk TEMPLATE name. The proper use of predefined CA Service Desk templates ensures that tickets, generated by CAISDI/med on behalf of the named product, are properly categorized, prioritized, and assigned.
Refers to the SERVER statement that defines the CA Service Desk server that receives tickets that are associated with this product definition.
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. The internal tickets that are 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.
Contains the crucial COMPONENT operand OPS.
Defines the CAISDI product name to associate with abend events captured due to a matching COMPONENT specification. This PRODUCT name specification that makes the connection to a specific CAISDI PRODUCT initialization statement.
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. This COMPONENT specification indicates that CAISDI abend event intercept captures 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.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|