Previous Topic: CAISDI/soap API Return Codes

Next Topic: CAISDI/els API Abend Codes

CAISDI/els API Return Codes

Various CA products use the CAISDI/els component to open CA Service Desk request tickets. In the event of failure, those products may display the return code, reason code, and information code that was passed back by CSDEOPRQ, the CAISDI/els Interface API module, through a call using the CSDEREQ macro. The API itself will issue message CASD560E for CAISDI/els API Return Codes of 12 or higher. This table details the meaning of the CAISDI/els API Return Codes.

Return Code

Reason Code

Information Code

Description

0

0

N/A

The USD request was opened. EPLRESP contains the USD request ticket number, left justified and blank filled.

4

1

N/A

The USD request was not opened because of MINTIME.

4

2

N/A

The USD request was not opened because of MAXCOUNT.

4

3

N/A

The USD request was not opened because the interface for this particular product is currently disabled.

8

0

N/A

The CAISDI/els interface module, CSDEOPRQ, was not found.

8

1

N/A

The CAISDI/els interface was found, but the interface has not been initialized. (The Event Control Structure was not found in this environment.)

8

2

N/A

The CAISDI/els interface module and the Event Control Structure was found, but this product is not defined to the interface. The CAISDI/els startup control member, ELSSTART, does not contain a DEFINE command for this product.

8

3

N/A

The CAISDI/els interface module and the Event Control Structure was found. This product is defined to the interface, but this particular event was not found. There was no event member for this product in the CAI.CAIEVENT library for this event.

8

4

N/A

The CA Common Services SOAP API module, CAS0PCLI, was not found.

12

rc

drc

The call to the CA Common Services SOAP API module, CAS0PCLI, failed. The "rc" value is the CAISDI/soap API return code and "drc" is the CAISDI/soap API detailed return code. See the CAISDI/soap API Return Code table for a detailed explanation.

16

1

N/A

Not enough storage to begin processing, increase REGION size.

16

2

N/A

Internal storage shortage while acquiring buffers, increase REGION size.

20

1

N/A

The Event Parameter List is invalid: Eye catcher is missing.

20

2

N/A

The Event Parameter List is invalid: Length is inconsistent with the parameters.

20

3

N/A

The Event Parameter List is invalid: Product name or event name is missing.

20

4

N/A

The CA Service Desk request ticket was opened, but the request number was not found in the response packet. This should not occur, but it could happen if the format of the XML reply packet was changed, or if the XML packet was incorrectly altered somewhere in the network path.

20

5

n

Error creating summary text, "n" is the return code from EDIT. This should not occur, but could if the Event Control Structure has been corrupted (overlaid).

20

6

n

Error creating description text, "n" is the return code from EDIT. This should not occur, but could if the Event Control Structure has been corrupted (overlaid).

20

7

N/A

Error generating XML. This should not occur, but it could happen if the CSDEOPRQ module itself was partially corrupted.

24

4

N/A

An invalid attempt occurred to update the Event Control Structure. This should not occur, but could if the Event Control Structure has been corrupted (overlaid).

24

5

N/A

The Product Event Table update was aborted because the table entry was below the table boundary. This should not occur, but could if the Event Control Structure has been corrupted (overlaid).

24

6

N/A

The Product Event Table update was aborted because the table entry was above the table boundary. This should not occur, but could if the Event Control Structure has been corrupted (overlaid).

24

8

N/A

The Product Event Table PC update routine has been removed. This should not occur, but could if the Event Control structure has been corrupted (overlaid).

28

n

N/A

The CAISDI/els interface module, CSDEOPRQ, has abended. The “n” value is the abend code given to the ESTAEX routine. This should not occur, but could if the Event Control Structure has been corrupted (overlaid), or if a calling program has passed an invalid parameter. An invalid parameter would most likely cause a S0C4 abend.