Special Usage Considerations › Integration with CA Service Desk

Integration with CA Service Desk

In the unlikely event of an abnormal termination, CA JARS can open requests in CA Service Desk. To use this feature, you must do all of the following:

• Install CA Service Desk on an appropriate platform. See the CA Service Desk documentation for supported operating platforms and other information about CA Service Desk.
• Install and configure the CA Service Desk interface on a mainframe system. In addition, the CA Common Services SOAP client must be installed and active on the system where CA JARS is running or on a system reachable via CCI. For more information on the SOAP client, see the CA Common Services documentation and visit http://www.w3.org/2000/xp/Group.
• Configure CCI to allow for communication with the SOAP client if CA JARS is not going to be run on the same z/OS image as the SOAP client. The API that CA JARS will use to send messages to the SOAP client can find the SOAP client via CCI as long as it is set up. There is no setup needed in CA JARS to define a CCI pathway to the SOAP client.

CA JARS will open a request for all abend conditions encountered that appear to be a product failure. Conditions such as invalid input data or resource shortages will not cause CA Service Desk requests to be opened. The following z/OS abnormal completion codes will not generate a CA Service Desk request:

• 0C7
• 0C9
• *22
• *37

Note that CA JARS does not terminate if an 0C7 or 0C9 abend occurs. These are almost always caused by data errors in the input SMF data, and CA JARS recovers from the condition and continues normal operation. If this error does occur, the record is snapped to print (provided the snap limit has not been reached).

If an asterisk is part of the completion code, CA JARS will not open a request regardless of the code.