The following CAISDI/med PRODUCT and EVENT initialization statements define the interaction between CAISDI and CA MIM Resource Sharing to generate CA Service Desk tickets for CA MIM Resource Sharing abends:
/*==================================================================*/
/* Unicenter CA-MIM Product Interface Definitions */
/* */
/* Define Unicenter CA-MIM 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-MIM, /* Product name */+
EVENT=ABEND, /* Event qualifier */+
JOBNAME=MIMGR, /* Product started task name */+
AFFECTED_END_USER=System_MIM_User, /* Affected End User */+
REPORTED_BY=System_MIM_User, /* Reported By for tickets */+
ASSIGNEE=System_MIM_User, /* Assigned contact name */+
PRIORITY=2, /* Priority for tickets */+
/* TEMPLATE='CA-MIM,Low Priority', /* Service Desk template */+
SERVER=USDSRV01 /* Direct request to this server */
EVENT ABEND, /* Capture ABEND events */+
PRODUCT=CA-MIM, /* Associated product statement */+
COMPONENT='MiMgr*', /*Unicenter CA-MIM component (mixed case) */+
JOBNAME=MIMGR, /* Product started task name */+
EXCLUDE=((0051,0000), /* Internal entry to VCF recovery */+
(0051,X'10')) /* Normal MIGRATE CTC to DASD */
This 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.
Beginning with the EVENT statement, the crucial specification provided is the COMPONENT parameter, MiMgr.
Note: The specification is made with uppercase and lowercase letters.
CA MIM Resource Sharing recovery routines always place the character string, MiMgr, in the SDWACID field for all CA MIM Resource Sharing abend events. Therefore, 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 MiMgr. 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 several abend code/reason code combinations for CA MIM Resource Sharing that are to be ignored for problem reporting. These abends are used in normal CA MIM Resource Sharing operation for Virtual Control File processing and should not be reported as errors.
The JOBNAME parameter of the EVENT statement names the job, MIMGR. The JOBNAME parameter is useful if more than one copy of CA MIM Resource Sharing is operating in a single z/OS operating system image. For example, perhaps the CA MII Data Sharing facility executes with a job name of CAMII while the CA MIA Tape Sharing facility executes with a job name of CAMIA. In this case, multiple EVENT statements with separate JOBNAME parameter specifications could be used to uniquely direct and categorize CA Service Desk tickets from each respective CA MIM Resource Sharing component address space.
Finally, the PRODUCT parameter defines the CAISDI/med 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/med PRODUCT initialization statement.
The preceding PRODUCT statement defines the CA‑MIM product as referenced in the PRODUCT= parameter of the EVENT statement. Again, the JOBNAME parameter defines the job name of MIMGR as the qualifier to which CA MIM Resource Sharing address space this PRODUCT statement applies. As discussed earlier, the JOBNAME parameter is useful when the various CA MIM Resource Sharing facilities are operated in separate z/OS address spaces.
The PRODUCT statement EVENT parameter qualifies that the product events associated with this product definition are abend events.
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 ensure that tickets generated by CAISDI/med 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.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |