Starting Your Product › How to Configure Without CA MSM › Update CAISDI Parameters › Configuring CAISDI for CA Dispatch

Configuring CAISDI for CA Dispatch

The following CAISDI/med PRODUCT and EVENT initialization statements define the interaction between CAISDI and CA Dispatch to generate Service Desk tickets for CA Dispatch abends:

/*======================================================================*/

/* CA Dispatch Product Interface Definitions 		  	          */
/* 									  */
/* Define 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 CA 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 *', 		           /* 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 PRODUCT statement defines the product, in this case CA Dispatch.
• The JOBNAME parameter 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.

• The EVENT parameter indicates that the events associated with this PRODUCT definition are abend events.
• The SERVER parameter refers to the SERVER statement that defines the Service Desk server that is to receive tickets associated with this product definition.

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

• The most important predefined entity is the Service Desk TEMPLATE name. The proper use of predefined Service Desk templates ensure that tickets generated by CAISDI/med on behalf of CA Dispatch 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.
• The EVENT statement 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 that the spaces between words are significant.

  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 should capture 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.

• The EXCLUDE parameter of the EVENT statement lists abend/reason code combinations for CA Dispatch that should be ignored for problem reporting. (In the sample all *22 abends are eliminated.) The JOBNAME parameter of the EVENT statement defines the jobs where the abend event may occur. In the sample, * is 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 can be used to restrict the event to a specific JOB, or masked to handle a range of jobs. The JOBNAME parameter is also useful if multiple copies of CA Dispatch are operating in a single z/OS operating system image. In this situation separate JOBNAME parameters can direct and categorize Service Desk tickets from each CA Dispatch address space.

The PRODUCT parameter on the EVENT statement defines the CAISDI/med product associated with the abend events captured. It is this PRODUCT name specification that makes the connection back to the CAISDI/med PRODUCT initialization statement.

Note: For more information about these parameters, see the chapter, "Running CAISDI." in the CA Common Services for z/OS CA Service Desk Integration Guide.