The following CAISDI/med PRODUCT and EVENT initialization statements define the interaction between CAISDI and CA Dispatch to generate CA Service Desk tickets for CA Dispatch abends:
/*==================================================================*/
/* Unicenter CA-Dispatch Product Interface Definitions */
/* */
/* Define Unicenter CA-Dispatch product ABEND events that are to be */
/* captured by CAISDI/med, and how that information is to be */
/* presented in the 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-DISPATCH, /* Product name */+
EVENT=ABEND, /* Event qualifier */+
JOBNAME=*, /* Product JOB names */+
AFFECTED_END_USER=System_Dispatch_User, /* Affected End User*/+
REPORTED_BY=System_Dispatch_User, /* Reported by */+
ASSIGNEE=System_Dispatch_User, /* Assigned contact name */+
PRIORITY=3, /* Priority for tickets */+
/* TEMPLATE='Dispatch,Priority unassigned', /* template name */+
SERVER=USDSRV01 /* Direct requests to this server */
EVENT ABEND, /* Capture ABEND events */+
PRODUCT=CA-DISPATCH, /* Associated Product */+
COMPONENT='CADD CADDSPL R11 *', /* Unicenter CA-Dispatch */+
JOBNAME=*, /* Product JOB names */+
EXCLUDE=(X'122',X'222',X'522') /* Ignore x22 abends */
This example shows how the PRODUCT and EVENT statements are used to activate the capture of abend events for CA Dispatch. These statements also define the CA Service Desk attributes to be associated with the tickets that are opened as a result of the abend event.
The parameters define the names of predefined CA Service Desk specific entities that are assigned to any generated tickets. The CA Service Desk administrator predefines these named entities on the target CA Service Desk server.
Defines the product, in this case CA Dispatch.
Indicates that the 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.
Contains the crucial COMPONENT operand that is used to match this event statement with the actual event. For CA Dispatch, this is set to a value of “CADD CADDSPL R11 *”. This operand must be entered exactly as it is coded in this example.
Note: The spaces between words are significant.
Defines the CAISDI/med product that is associated with the abend events captured. This PRODUCT name specification that makes the connection back to the CAISDI/med PRODUCT initialization statement.
CA Dispatch recovery routines place the character string “CADD CADDSPL R11” in the SDWACID field for all CA Dispatch abend events. This COMPONENT specification indicates that CAISDI/med abend event intercept captures any detected abend event where the concatenation of the SDWACID and SDWASC fields begins with the characters “CADD CADDSPL R11”. The asterisk (*) in the sample initialization statement is a wild card, and indicates that any subsequent characters are considered a match condition.
Defines the job names to which this product statement applies. The sample has coded '*' so that all CA Dispatch-intercepted abends are processed by this EVENT statement in any address space including customer address space with intercepted reports. The JOBNAME parameter could be used to restrict the event to a specific JOB, or leave it as it is to handle all of them. The JOBNAME parameter is also useful if more than one copy of CA Dispatch is operating in a single z/OS operating system image. For example, separate JOBNAME parameter operand specifications could be used to uniquely direct and categorize CA Service Desk tickets from each respective CA Dispatch component address space.
Lists abend/reason code combinations for CA Dispatch that are ignored for problem reporting. (In the sample all *22 abends are eliminated.)
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|