Common request processing reason codes

Edit online

Certain common error conditions can be encountered during the processing of many of the operations of the API. When they are encountered they are reported using the same HTTP status and reason code by any operation of the API that may encounter them.

These common request processing reason codes are listed in the following table:

HTTP status code Reason code Description
500 (Server Error) 0 - 39 An internal processing error has occurred and no additional details are documented.
41191 The BCPii transport rejected the particular request. Activate CTRACE with CTRACE option "ALL" and reissue the request. If the request fails again, turn off CTRACE, collect the SVCDUMP, and contact your next level of support.
41301 The support element failed to return the required information needed for BCPii address space to come up.
Action:
  1. If this error occurs during BCPii initialization, restart BCPii manually (S HWISTART).
  2. If restarting BCPii manually fails, perform the following steps to re-drive the SE recovery process to return the required information:
    1. Issue the command VARY CN(*),ACTIVATE from Operating System Messages
    2. Issue a command (any command) from Operating System Messages
    3. Manually restart BCPII (S HWISTART)
  3. If the above suggested actions still fail, IPL is required to restart BCPii.
42081 The support element rejected the particular request. This could occur for any number of reasons including: the SE is busy, the SE is rebooting, etc. Consider retrying the request one or more times. If the problem persists, activate CTRACE with CTRACE option "ALL" and reissue the request. Then turn off CTRACE, collect the SVCDUMP, and contact your next level of support.
4209- 42111 The SEND BCPii permission was not granted to The LPAR on this support element, contact your next level of support.
42121 The support element rejected communication from BCPii, likely for one of the following reasons: the SEND BCPii permission was not granted to the LPAR on this support element or the SE/HMC is missing the required MCL. Contact your next level of support.
43131 C®/ASM applications: the length of the data area provided for the response body is not large enough to contain the response from the SE. Increase the data area size to the recommended amount and re-issue the request. REXX applications: the size of the response exceeds the support 2.5 MB response body limit for this environment, consider using C or ASM to re-issue the request with the recommended data area size.
4xxx1 An internal error occurred processing the request, contact your next level of support.
503 (Service Unavailable) 1 The request could not be processed because the HMC is not currently communicating with an SE needed to perform the requested operation.
3 This request would exceed the limit on the number of concurrent API requests allowed.
4 The limit of concurrent requests has been reached for a specific BCPii source partition.
5 This request would exceed the limit on the number of concurrent Server-Sent Events streams allowed for a session.
504 (Gateway Timeout) 0 The address for the specified target was unable to be determined.
1 The targeted API server was unable to be reached.
2 The targeted API server was reached and a request was successfully submitted but the response did not arrive in a timely enough manner to satisfy the time out specified by the client.
3 The targeted API server was reached and a request was successfully submitted but the response did not arrive in a reasonable amount of time.
42241 No response was received from the support element, after waiting the amount of time specified by the timeout request parameter, and BCPii timed out the request. Contact your next level of support to check if connectivity to the support element is still there.
1This reason code is only applicable to operations initiated through the BCPii interface.