CA Service Desk Configuration › CAISDI/elmds Backout Procedure › How to Implement Standalone CAISDI/els › Run Standalone CAISDI/els › CAISDI/els Control Statements › Reports › List Reports

List Reports

There are two types of reports that can be obtained with the LIST control statement:

If you omit the REQUESTS keyword, CAISDI/els produces a detailed EVENTS report. This is a list of all defined events and their current status. If you include the PRODUCT parameter, you can report on an event of a single product. Otherwise, all events for all products are reported.

If you include the REQUESTS keyword, CAISDI/els queries the CA Service Desk and produces a REQUESTS report. This is a report of all CA Service Desk tickets in open status that match your other criteria. You can list the open tickets for one product by including the PRODUCT parameter. If you omit the PRODUCT parameter, all tickets for each product that is currently defined are reported, one product at a time. You can specify any one or all of ASSET, REPORTED_BY, AFFECTED_END_USER, and ASSIGNEE as extra selection criteria. Only the tickets where all criteria are true are reported. If you omit all criteria, the AFFECTED_END_USER contact from each product's definition is used as if you had specified the AFFECTED_END_USER parameter.

This example reports the events for one product:

//LIST  JOB  '1234','Systems',CLASS=A
//CASDIELS EXEC PGM=CSDECNTL
//STEPLIB  DD  DSN=CAI.CAW0LOAD,DISP=SHR    
//SYSPRINT DD  SYSOUT=*    
//REPORT   DD  SYSOUT=*
//SYSIN    DD  *
LIST PRODUCT=CA-1

To report on all events for all products using CAISDI/els, omit the PRODUCT parameter:

//LIST  JOB  '1234','Systems',CLASS=A
//CASDIELS EXEC PGM=CSDECNTL
//STEPLIB  DD  DSN=CAI.CAILIB,DISP=SHR    
//SYSPRINT DD  SYSOUT=*    
//REPORT   DD  SYSOUT=*
//SYSIN    DD  *
LIST

The previous example produces a report, which is written to the DD named REPORT. This report lists all events for each product, one product at a time, showing the event counts and the last time the event was triggered.

The following example lists CA Service Desk tickets for one product:

//LIST  JOB  '1234','Systems',CLASS=A
//CASDIELS EXEC PGM=CSDECNTL
//STEPLIB  DD  DSN=CAI.CAW0LOAD,DISP=SHR    
//SYSPRINT DD  SYSOUT=*    
//REPORT   DD  SYSOUT=*
//SYSIN    DD  *
LIST REQUESTS,PRODUCT=CA-1

In this case, the CA Service Desk contact that is identified to CAISDI/els as the AFFECTED_END_USER is used as the selection criteria. Only the tickets that are currently open are reported. The report is written to the DD named REPORT.

In the following example, the user has changed the AFFECTED_END_USER value so that there are tickets still open from two different affected end users. However, this user consistently opened all CA Service Desk tickets using the software asset named “CA 1® Tape Management.”

//LIST  JOB  '1234','Systems',CLASS=A
//CASDIELS EXEC PGM=CSDECNTL
//STEPLIB  DD  DSN=CAI.CAW0LOAD,DISP=SHR    
//SYSPRINT DD  SYSOUT=*    	
//REPORT   DD  SYSOUT=*
//SYSIN    DD  *
LIST REQUESTS,ASSET='CA 1® Tape Management'

The previous example lists all open tickets for the CA 1® Tape Management product and is written to the DD named REPORT. The report shows who is assigned to each ticket, when it was first opened, and when it was last updated.