Business logic interface responses

Attention: This topic contains Product-sensitive Programming Interface and Associated Guidance Information.

One of the following values is returned in wbbl_response. These values correspond to the intended HTTP responses to be sent to an HTTP client.

400
One of the converter functions returned a URP_EXCEPTION response with a reason URP_CORRUPT_CLIENT_DATA. The business logic interface writes an exception trace entry (trace point 4556) and issues a message (DFHWB0120).
403
A LINK command to the program specified in wbbl_server_program_name received a NOTAUTH response. The business logic interface writes an exception trace entry (trace point 4556) and issues a message (DFHWB0120).
404
A LINK command to the program specified in wbbl_server_program_name received a PGMIDERR response. The business logic interface writes an exception trace entry (trace point 4556) and issues a message (DFHWB0120).
500
One of the following occurred:
  • The business logic interface detected an abend. A message that depends on the program that abended is issued. For the program specified in wbbl_server_program_name, the message is DFHWB0125. For the Encode function of the converter, the message is DFHWB0126. For the Decode function of the converter, the message is DFHWB0127. For any other program, the message is DFHWB0128. In any case an exception trace entry (trace point 4557) is written.
  • A LINK command to the program specified in wbbl_server_program_name received an INVREQ or a LENGERR or an unexpected response. The business logic interface writes an exception trace entry (trace point 4556) and issues a message (DFHWB0120).
501
One of the following occurred:
  • Decode returned a response of URP_EXCEPTION with an undefined reason code. The business logic interface writes an exception trace entry (trace point 455B) and issues a message (DFHWB0121).
  • Decode returned a response of URP_INVALID. The business logic interface writes an exception trace entry (trace point 455C) and issues a message (DFHWB0121).
  • Decode returned a response of URP_DISASTER. The business logic interface writes an exception trace entry (trace point 455D) and issues a message (DFHWB0121).
  • Decode returned an undefined response. The business logic interface writes an exception trace entry (trace point 455E) and issues a message (DFHWB0121).
  • Encode returned a response of URP_EXCEPTION with an undefined reason code. The business logic interface writes an exception trace entry (trace point 455B) and issues a message (DFHWB0122).
  • Encode returned a response of URP_INVALID. The business logic interface writes an exception trace entry (trace point 455C) and issues a message (DFHWB0122).
  • Encode returned a response of URP_DISASTER. The business logic interface writes an exception trace entry (trace point 455D) and issues a message (DFHWB0122).
  • Encode returned an undefined response. The business logic interface writes an exception trace entry (trace point 455E) and issues a message (DFHWB0122).
503
One of the following occurred:
  • A LINK command to the program specified in wbbl_server_program_name received a TERMERR response. The business logic interface writes an exception trace entry (trace point 4555) and issues a message (DFHWB0120).
  • A LINK command to the program specified in wbbl_server_program_name received a SYSIDERR or ROLLEDBACK response. The business logic interface writes an exception trace entry (trace point 4556) and issues a message (DFHWB0120).