|
|
|
The CAISDI/med PRODUCT and EVENT initialization statements are used to define the interaction between CAISDI and CA Spool Enterprise Print Management to generate CA Service Desk tickets for CA Spool Enterprise Print Management abends events. The following sample shows the addition of an Abend event definition to the Message Events defined in the preceding sample.
/*==================================================================*/
/* Unicenter CA-Spool Product Interface Definitions */
/* */
/* Define Unicenter CA-Spool product ABEND and message 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-SPOOL, /* Product name */+
EVENT=(%ESF886), /* Event qualifier */+
AFFECTED_END_USER=System_Spool_User, /* Affected End User */+
REPORTED_BY=System_Spool_User, /* Reported by for tickets */+
ASSIGNEE=System_Spool_User, /* Assigned contact name */+
PRIORITY=2, /* Priority for tickets */+
/* TEMPLATE='CA-Spool,Priority unassigned', /* template name */+
SERVER=USDSRV01 /* Direct requests to this server */
PRODUCT CA-SPOOL, /* Product name */+
EVENT=(ABEND,%ESF*), /* Event qualifier */+
AFFECTED_END_USER=System_Spool_User, /* Affected End User */+
REPORTED_BY=System_Spool_User, /* Reported by for tickets */+
ASSIGNEE=System_Spool_User, /* Assigned contact name */+
PRIORITY=3, /* Priority for tickets */+
/* TEMPLATE='CA-Spool,Priority unassigned', /* template name */+
SERVER=USDSRV01 /* Direct requests to this server */
EVENT ABEND, /* Capture ABEND events */+
PRODUCT=CA-SPOOL, /* Associated Product */+
COMPONENT='SPOOL-Main*', /*Unicenter CA-Spool */+
JOBNAME=ESF* /* Product JOB names */
This sample shows two PRODUCT statements that are used to activate the capture of message, and an EVENT ABEND statement that defines CA Spool Enterprise Print Management abend events to be captured by CAIDSI.
The PRODUCT statement defines the product, the event, the name of the CA CAISDI/med server that will process this event, and the CA Service Desk attributes to be associated with the tickets that are opened as a result of the defined event.
The EVENT parameter indicates the events associated with this PRODUCT definition. In addition to the message event IDs that were discussed previously, the second PRODUCT statement also has defined an event named ABEND. This event matches up with the EVENT ABEND statement that is discussed later in this section. To completely eliminate the message event, you would only need to code EVENT=ABEND on the PRODUCT statement.
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 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 CA Service Desk TEMPLATE name. The proper use of predefined CA Service Desk templates ensure that tickets generated by CAISDI/med on behalf of CA Spool Enterprise Print Management 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 Spool Enterprise Print Management, this is set to a value of “SPOOL-Main.” This operand must be entered exactly as it is coded in this example. Note that case is significant for this value.
CA Spool Enterprise Print Management recovery routines place the character string “SPOOL-Main” in the SDWACID field for all CA Spool Enterprise Print Management 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 “SPOOL-Main”.
The EXCLUDE parameter of the EVENT statement can be used to list abend/reason code combinations for CA Spool Enterprise Print Management that should be ignored for problem reporting. We recommend that all abends be reported.
The JOBNAME parameter of the EVENT statement defines the jobs where the abend event may occur. In the sample, ESF* is coded to specify that we want to create a ticket for abend events for task names beginning with ESF. The JOBNAME parameter can be used to restrict the event to a specific job or task, or masked to handle a range of jobs or tasks. The JOBNAME parameter is also useful if multiple copies of CA Spool Enterprise Print Management are operating in a single z/OS operating system image. In this situation, separate JOBNAME parameters can direct and categorize CA Service Desk tickets from each CA Spool Enterprise Print Management address space.
The PRODUCT parameter on the EVENT statement defines the CAISDI/med product associated with the abend events captured. This PRODUCT name specification makes the connection back to the CAISDI/med PRODUCT initialization statement.
For detailed information on these parameters, see Running CAISDI.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |