Completed successfully, but with additional information
HBR_CC_ERROR (8)
Did not complete successfully, due to an application error
HBR_CC_SEVERE (12)
Did not complete successfully, due to a system error
Reason codes
HBR_RC_NONE (0)
Severity - HBR_CC_OK
Explanation - The call completed normally.
Response - None
HBR_RC_UNEXPECTED (2195)
Severity - HBR_CC_SEVERE
Explanation - An error occurred.
Response - Contact your IBM Support Center.
HBR_RC_ERROR_HBRBCON (3001)
Severity - HBR_CC_SEVERE
Explanation - Unable to load the load modules for ODM for z/OS.
Response - Ensure that the JOBLIB and STEPLIB DD statements are correctly specified.
HBR_RC_ERROR_HBRCCON (3002)
Severity - HBR_CC_SEVERE
Explanation - Unable to load the load modules for ODM for z/OS.
Response - Ensure that the JOBLIB and STEPLIB DD statements are correctly specified.
HBR_RC_ERROR_HBRBDSC (3003)
Severity - HBR_CC_SEVERE
Explanation - Unable to load the load modules for ODM for z/OS.
Response - Ensure that the JOBLIB and STEPLIB DD statements are correctly specified.
HBR_RC_ERROR_HBRCDSC (3004)
Severity - HBR_CC_SEVERE
Explanation - Unable to load the load modules for ODM for z/OS.
Response - Ensure that the JOBLIB and STEPLIB DD statements are correctly specified.
HBR_RC_SERVER_NOT_DEFINED (3005)
Severity - HBR_CC_SEVERE
Explanation - The subsystem specified by the HBRSSID variable in the HBRENVPR DD statement data set is not defined to z/OS.
Response - Ensure that the subsystem ID is correct.
HBR_RC_SERVER_NOT_ACTIVE (3006)
Severity - HBR_CC_ERROR
Explanation - The subsystem specified by the HBRSSID variable in the HBRENVPR DD statement data set is not active.
Response - Start the subsystem or change HBRSSID to specify an active subsystem.
HBR_RC_INVALID_NUMBER_PARMS (3007)
Severity - HBR_CC_ERROR
Explanation - A parameter is incorrectly specified in the HBRA-RA-PARMS structure in the HBRA-CONN-AREA data area. The number of the invalid parameter is returned in the HBRA-RESPONSE-MESSAGE field of the HBRA-CONN-AREA data area.
Response - Ensure that you specified a parameter name, and either a parameter address or length.
HBR_RC_SERVER_ID_INVALID (3008)
Severity - HBR_CC_ERROR
Explanation - The subsystem specified by the HBRSSID variable in the HBRENVPR DD statement data set is already in use.
Response - Ensure that the subsystem ID is correct.
HBR_RC_NOT_ACCEPTING_WORK (3009)
Severity - HBR_CC_ERROR
Explanation - The server cannot accept work because it is either paused or not in RULE mode.
Response - Issue the RESUME command to enable the server to accept work or restart the server in RULE mode.
HBR_RC_ERROR_INVALID_CICS (3010)
Severity - HBR_CC_SEVERE
Explanation - An unsupported version of CICS attempted to connect to the server. Please use a supported version.
Response - Use a supported CICS version.
HBR_RC_INVALID_JVMS_RELEASE (3011)
Severity - HBR_CC_SEVERE
Explanation - The version of CICS used with HBRTARGETRES=LCICSJVM is unsupported. HBRTARGETRES=LCICSJVM requires a supported version of CICS TS.
Response - Use a supported version CICS TS for the local JVM Server or make this region an application-owning region.
HBR_RC_ERROR_STORAGE_FAIL (3012)
Severity - HBR_CC_SEVERE
Explanation - Storage could not be obtained. There is insufficient storage available to complete the request.
Response - Check the system configuration to ensure sufficient storage is available to complete the request.
HBR_RC_CICS_NO_JVMSERVER (3013)
Severity - HBR_CC_ERROR
Explanation - The connection to JVM server HBRJVM failed because the JVM server is not installed.
Response - Ensure that JVM server HBRJVM is installed and attempt the connection again.
HBR_RC_CICS_NOTENABLED_JVMS (3014)
Severity - HBR_CC_ERROR
Explanation - The connection to JVM server HBRJVM failed because the JVM server is not enabled.
Response - Determine why the JVM server HBRJVM is not enabled and attempt the connection again.
HBR_RC_ERROR_HBRICON (3015)
Severity - HBR_CC_SEVERE
Explanation - Unable to load the load modules for ODM for z/OS.
Response - Ensure that the JOBLIB and STEPLIB DD statements are correctly specified.
HBR_RC_ERROR_HBRIDSC (3016)
Severity - HBR_CC_SEVERE
Explanation - Unable to load the load modules for ODM for z/OS.
Response - Ensure that the JOBLIB and STEPLIB DD statements are correctly specified.
HBR_RC_ERROR_INVALID_CCSID (3017)
Severity - HBR_CC_ERROR
Explanation - The code page specified in HBRA_CONN_RULE_CCSID is invalid.
Response - Use a supported code page.
HBR_RC_MISSING_HBRSSIDLIST (3018)
Severity - HBR_CC_ERROR
Explanation - An HBRSSIDLIST value is missing in a dataset specified by the HBRENVPR DD statement.
Response - Define a valid HBRSSIDLIST value in the data set.
HBR_RC_INVALID_HBRSSIDLIST (3019)
Severity - HBR_CC_ERROR
Explanation - The HBRSSIDLIST value is incorrect. Provide a comma separated list of one to 32 SSIDs of 4 characters. For example: HBR1,HBR2,HBR3
Response - Define a valid HBRSSIDLIST value in the HBRENVPR DD statement data set.
HBR_RC_NO_SUCCESSFUL_CONN (3020)
Severity - HBR_CC_ERROR
Explanation - No active zRule Execution Server was found in the HBRSSIDLIST property.
Response - The HBRA-RESPONSE-MESSAGE field contains a message listing the completion codes from each zRule Execution Server.
HBR_RC_SOME_SUCCESSFUL_CONN (3021)
Severity - HBR_CC_WARNING
Explanation - One or more of the zRule Execution Servers in the HBRSSIDLIST property is not active and could not be connected to.
Response - Rules can still execute against the successfully connected zRule Execution Servers. See the HBRA-RESPONSE-MESSAGE field for the completion codes for each zRules Execution Server. In CICS, to retry the connection you will need to disconnect first by running the HBRD transaction.
HBR_RC_NO_SERVER_AVAILABLE (3022)
Severity - HBR_CC_ERROR
Explanation - No active zRule Execution Server was available to execute the rule request.
Response - A connection has previously been made to one or more zRule Execution Servers which are now unavailable. Either start or resume the zRule Execution Servers to continue rule executions.
HBR_RC_INVALID_CICS_ENV_DD (3023)
Severity - HBR_CC_ERROR
Explanation - Could not open the data set that is defined in the HBRENVPR DD statement in the CICS JCL.
Response - Check that the HBRENVPR DD statement and configuration parameters are correctly defined.
HBR_RC_CICS_IS_CONNECTED (3024)
Severity - HBR_CC_WARNING
Explanation - The CICS region is already connected because you ran the HBRC transaction.
Response - Run the HBRD transaction to disconnect from the CICS region before re-running the HBRC transaction.
HBR_RC_RCICSJVM_UNAVAILABLE (3025)
Severity - HBR_CC_ERROR
Explanation - The remote CICS JVM Server system is not available. The distributed program link returned a SYSIDERR.
Response - The link to the remote system is out of service, busy, not defined or cannot queue the request. Check the following: the remote system is available and has a sufficient QUEUELIMIT, IRC is enabled and open on both regions, the connection can queue requests.
HBR_RC_RCICSJVM_ABEND (3026)
Severity - HBR_CC_ERROR
Explanation - The remote rule program abends or the session with the server fails. The distributed program link returned a TERMERR.
Response - Check the remote CICS JVM Server logs for error messages. Test that rule execution on the CICS rule-owning region is working. If it is, debug your IRC setup.
HBR_RC_RCICSJVM_UNKNOWN (3027)
Severity - HBR_CC_ERROR
Explanation - An invalid request or response was detected from the DPL to the CICS rule-owning region
Response - Verify that the CICS rule-owning region is working and test rule execution on this region. If the problem persists check the remote CICS JVM Server setup and the logs.
HBR_RC_HBRTARGETRES_INVALID (3028)
Severity - HBR_CC_ERROR
Explanation - The HBRTARGETRES parameter was not recognised.
Response - Ensure that HBRTARGETRES is set to a recognised value.
HBR_RC_MODE_IS_CONSOLE (3029)
Severity - HBR_CC_ERROR
Explanation - The zRule Execution Server is currently running in CONSOLE mode.
Response - If the server is intended to run as a console, remove its name from the list in HBRSSIDLIST. Otherwise, set HBRMODE for the server to RULE.
HBR_RC_CICSJVM_PROG_ERR (3030)
Severity - HBR_CC_ERROR
Explanation - CICS returned PGMIDERR whilst attempting to call the program HBRCJVMS.
Response - Verify the program definition for HBRCJVMS is correct. If this is a CICS application-owning region, ensure that the HBRCJVMS program definition contains valid remote attributes.
HBR_RC_EMBED_JVM_ERR (3031)
Severity - HBR_CC_ERROR
Explanation - The embedded zRule Execution Server for z/OS encountered a JVM error.
Response - Review the batch job output in SDSF and the ++HBRWORKPATH++/logs directory for further information.
HBR_RC_HBRTARGETRES_MISSING (3032)
Severity - HBR_CC_ERROR
Explanation - The HBRTARGETRES parameter was not specified.
Response - Ensure that HBRTARGETRES parameter is specified in a dataset in the HBRENVPR DD statement.
HBR_RC_CICS_ROR_UNAVAILABLE (3033)
Severity - HBR_CC_ERROR
Explanation - The CICS rule-owning region is not available to process requests.
Response - Run the HBRC transaction on the CICS rule-owning region.
HBR_RC_RULE_TIMEOUT (3034)
Severity - HBR_CC_ERROR
Explanation - The rule execution took longer than the value specified in the HBRTIMEOUT property.
Response - Review the zRule Execution Server logs to diagnose the reason for the timeout.
HBR_RC_TIMEOUT_PROP_ERR (3035)
Severity - HBR_CC_ERROR
Explanation - The value specified in the HBRTIMEOUT property is not valid.
Response - Ensure that a valid value is specified in the HBRTIMEOUT property.
HBR_RC_CICS_L2L_NOT_READY (3036)
Severity - HBR_CC_ERROR
Explanation - The CICS Liberty JVM server is enabled but not ready to process the request.
Response - Wait for the CICS Liberty JVM server to become ready and try running the transaction again. If the problem persists, review the CICS MSGUSR log.
HBR_RC_CICS_L2L_PGM_ERROR (3037)
Severity - HBR_CC_ERROR
Explanation - The LINK to the CICS Liberty JVM server failed for an unknown reason.
Response - Review the CICS MSGUSR log for further information.
HBR_RC_HBRCTIMEOUT_PROP_ERR (3038)
Severity - HBR_CC_ERROR
Explanation - The value specified in the HBRCTIMEOUT property is not valid.
Response - Ensure that a valid value is specified for the HBRCTIMEOUT property.
HBR_RC_CICS_L2L_SIT_PROHIBIT (3039)
Severity - HBR_CC_WARNING
Explanation - Cannot connect to a CICSJVM RES during CICS initialization.
Response - No action is required, HBRC will be automatically rerun after system initialization.
HBR_RC_CICS_L2L_RETRY (3040)
Severity - HBR_CC_WARNING
Explanation - The CICS Liberty JVM server is not ready to process the request, a retry will be attempted.
Response - No action is required, a further connection attempt will be made.
HBR_RC_CICS_L2L_SCHED_ERROR (3041)
Severity - HBR_CC_ERROR
Explanation - Attempt to schedule HBRC for after system initialization failed.
Response - Manually issue HBRC from a CICS terminal. Review CICS output for details of the failure.
HBR_RC_HBRCRETRY_PROP_ERR (3042)
Severity - HBR_CC_ERROR
Explanation - The value specified in the HBRCRETRY property is not valid.
Response - Ensure that a valid value is specified for the HBRCRETRY property.
HBR_RC_CICS_L2L_SIT_NORETRY (3043)
Severity - HBR_CC_WARNING
Explanation - CICS PLT entry HBRCCON is present, but HBRCRETRY=NO. HBRC connection not attempted.
Response - To connect to zRule Execution Server, running in CICS, at startup you must specify the HBRCRETRY=YES property.
HBR_RC_WOLA_BATCHING_REQUEST (3044)
Severity - HBR_CC_ERROR
Explanation - Rule execution through WOLA does not support batched rule requests.
Response - Do not make requests through WOLA using the batching api (HBRPUTN and HBRPUTP in your COBOL program).
HBR_RC_CICS_L2L_PGMID_ERROR (3045)
Severity - HBR_CC_ERROR
Explanation - LINK to the CICS Liberty JVM server - PGMIDERR error.
Response - Review the CICS MSGUSR log for further information.
HBR_RC_CICS_L2L_PGMID_TOUT (3046)
Severity - HBR_CC_ERROR
Explanation - LINK to the CICS Liberty JVM server - PGMIDERR TIMEOUT error.
Response - Review the CICS MSGUSR log for further information.
HBR_RC_ONLY_MISMATCHED (3047)
Severity - HBR_CC_ERROR
Explanation - Only Servers offering mismatched Decision execution were available
Response - Ensure you have zRES servers started in a mode matching the exection type required (ODM/ADS/DMOE)
HBR_RC_ADS_NO_INPUT_LENGTH (3049)
Severity - HBR_CC_ERROR
Explanation - HBRADSX call made without an InputObj Length provided, cannot continue
Response - Ensure you provide a value for HBRADS-INPUTOBJ-LENGTH
HBR_RC_ADS_NO_INPUT_ADDRESS (3050)
Severity - HBR_CC_ERROR
Explanation - HBRADSX call made without an InputObj Address provided, cannot continue
Response - Ensure you provide a value for HBRADS-INPUTOBJ-ADDRESS
HBR_RC_ADS_NO_RESULT_LENGTH (3051)
Severity - HBR_CC_ERROR
Explanation - HBRADSX call made without a Result Length provided, cannot continue
Response - Ensure you provide a value for HBRADS-RESULT-LENGTH
HBR_RC_ADS_NO_RESULT_ADDRESS (3052)
Severity - HBR_CC_ERROR
Explanation - HBRADSX call made without a Result Address provided, cannot continue
Response - Ensure you provide a value for HBRADS-RESULT-ADDRESS
HBR_RC_ADS_NO_ID (3053)
Severity - HBR_CC_ERROR
Explanation - HBRADSX call made without a Decision Service ID, cannot continue
Response - Ensure you provide a value for HBRADS-HBRADS-DECISION-SERVICE-ID
HBR_RC_ADS_NO_OPERATION (3054)
Severity - HBR_CC_ERROR
Explanation - HBRADSX call made without a Decision Operation, cannot continue
Response - Ensure you provide a value for HBRADS-DECISION-OPERATION
HBR_RC_ADS_AND_ODM_PARMS (3055)
Severity - HBR_CC_ERROR
Explanation - Both ADS and ODM Parameters were provided, cannot continue
Response - Ensure you zero HBRA-RA-PARMETERS and HBRADS-API, and only provide one set of parameters.
HBR_RC_ERROR_TOONEW_FAIL (3056)
Severity - HBR_CC_SEVERE
Explanation - Connection failed because client application is at a newer version of ODM than the zRES server.
Response - You must upgrade your zRES Server, before upgrading client applications.
HBR_RC_ERROR_AUTHEXTR_CICS (3057)
Severity - HBR_CC_SEVERE
Explanation - task user is not authorized to issue EXTRACT EXIT
Response - Check permissions of CICS user
HBR_RC_ERROR_PCMISMATCH_FAIL (3058)
Severity - HBR_CC_SEVERE
Explanation - Connection failed because client application pc call structure doesn't match the server one.
Response - Your client application and server application must use the same product version.
HBR_RC_ERROR_CLMISMATCH_FAIL (3059)
Severity - HBR_CC_SEVERE
Explanation - Connection failed because client application and server are at different versions.
Response - Your client application and server application must use matching SHBRLOAD and SHBRAUTH versions.
HBR_RC_CONN_NOT_AUTH (4035)
Severity - HBR_CC_ERROR
Explanation - The user ID of the application issuing the HBRCONN API call is not authorized to connect to the server.
Response - See "Managing connection security" in the zRule Execution Server for z/OS documentation.
HBR_RC_MISSING_RA_NAME (4084)
Severity - HBR_CC_ERROR
Explanation - Missing RuleApp name.
Response - The RuleApp name was not specified. Provide a valid RuleApp name.
HBR_RC_INVALID_RA_NAME (4085)
Severity - HBR_CC_ERROR
Explanation - Invalid RuleApp name.
Response - The supplied RuleApp name is invalid. Correct the RuleApp name.
HBR_RC_CONN_NOT_SETUP (4086)
Severity - HBR_CC_ERROR
Explanation - The connection to the zRule Execution Server for z/OS has not been setup.
Response - The connection to the zRule Execution Server for z/OS is setup by running the HBRC transaction. If the HBRC transaction failed, look up the return code and reason in the information center. If the HBRC return code is zero but the problem persists, restart the region and retry.
HBR_RC_INVALID_HBRC (4087)
Severity - HBR_CC_ERROR
Explanation - The HBRC structure in the HBRA-CONN-AREA data area passed either to the HBRCONN API or the HBRRULE API is invalid or contains invalid data.
Response - Review and correct the HBRC structure.
HBR_RC_ALREADY_CONNECTED (4088)
Severity - HBR_CC_WARNING
Explanation - The user ID is already connected to the server. The user ID is passed back in the HBRA-RESPONSE-MESSAGE field of the HBRA-CONN-AREA data area.
Response - Remove the extra call to the HBRCONN API from your application.
HBR_RC_MISSING_HBRSSID (4089)
Severity - HBR_CC_ERROR
Explanation - An HBRSSID value is missing in a dataset specified by the HBRENVPR DD statement data set.
Response - Define a valid HBRSSID value in the data set.
HBR_RC_NOT_CONNECTED (4090)
Severity - HBR_CC_ERROR
Explanation - The application is not connected to the server.
Response - Ensure that the HBRCONN API is called before the HBRRULE or HBRDISC API are called.
HBR_RC_IMS_CONN_NOT_SETUP (4091)
Severity - HBR_CC_ERROR
Explanation - The connection to the zRule Execution Server for z/OS has not been setup.
Response - The connection to the zRule Execution Server for z/OS is setup by the IMS Initialization routine. If the IMS Initialization routine failed, look up the return code and reason in the information center. If the IMS Initialization routine return code is zero but the problem persists, restart the IMS region and retry.
HBR_RC_HBRC_WORKPATH_BAD (4092)
Severity - HBR_CC_ERROR
Explanation - The HBRWORKPATH supplied does not exist.
Response - Ensure that the HBRWORKPATH supplied by the HBRCICSJ member is correct.
HBR_RC_INVALID_PARAMETER (4093)
Severity - HBR_CC_ERROR
Explanation - A parameter supplied to HBRPUTP had a length greater than 48
Response - Ensure that parameter names have a maximum length of 48
HBR_RC_HBRPUTP_WITH_NO_PUTN (4094)
Severity - HBR_CC_ERROR
Explanation - A call to HBRPUTP was made without a preceding call to HBRPUTN
Response - Ensure that HBRPUTN is called to start a new rule request before HBRPUTP is called
HBR_RC_HBRGETP_NO_PARAMETER (4095)
Severity - HBR_CC_ERROR
Explanation - The parameter name passed to HBRGETP could not be found
Response - Ensure that the parameter name is correct and matches one passed to HBRPUTP
HBR_RC_HBRGETN_TOO_MANY (4096)
Severity - HBR_CC_ERROR
Explanation - HBRGETN has been called more times than HBRPUTP was
Response - Ensure that the number of calls to HBRGET matches the number of calls to HBRPUTP
HBR_RC_JRULES_UNEXPECTED (5000)
Severity - HBR_CC_SEVERE
Explanation - An exception occurred in the JRules engine.
Response - Check the HBRA-RESPONSE-MESSAGE field of the HBRA-CONN-AREA error code and look up the cause and action. Otherwise review the server logs in the HBR CICS work path for more information.
HBR_RC_JRULES_EXCEPTION (5001)
Severity - HBR_CC_ERROR
Explanation - An exception occurred in the JRules engine.
Response - Check the HBRA-RESPONSE-MESSAGE field of the HBRA-CONN-AREA error code and look up the cause and action. Otherwise review the server logs in the HBR CICS work path for more information.
HBR_RC_RAW_DATA_EXCEPTION (5002)
Severity - HBR_CC_ERROR
Explanation - An exception occurred while converting the parameter data.
Response - Review the server logs for more information.
HBR_RC_ILR_FORMAT_EXCEPTION (5003)
Severity - HBR_CC_ERROR
Explanation - An exception occurred while parsing the rule application path.
Response - Review the server logs for more information.
HBR_RC_WOLA_LOAD (6000)
Severity - HBR_CC_SEVERE
Explanation - Unable to load the WOLA load modules.
Response - Validate the application STEPLIB DD statements.
HBR_RC_WOLA_BAD_DAEMON_GROUP (6001)
Severity - HBR_CC_SEVERE
Explanation - The WebSphere Application Server for z/OS instance specified by HBRWOLASERVER cannot be located.
Response - Ensure WebSphere Application Server for z/OS is started and WOLA support is active.
HBR_RC_WOLA_BAD_CELL_OR_NODE (6002)
Severity - HBR_CC_SEVERE
Explanation - The node name or server name cannot be found.
Response - Ensure that HBRWOLANODE and HBRWOLACELL are set correctly.
HBR_RC_WOLA_WAS_ERROR (6003)
Severity - HBR_CC_SEVERE
Explanation - Unable to connect to WebSphere Application Server for z/OS.
Response - Try restarting WebSphere Application Server for z/OS.
HBR_RC_WOLA_EJB_NOT_FOUND (6004)
Severity - HBR_CC_SEVERE
Explanation - The WOLA EJB could not be found.
Response - Ensure that the WOLA EJB EAR file is installed on WebSphere Application Server for z/OS and that the server is active.
HBR_RC_WOLA_NOT_ENABLED (6005)
Severity - HBR_CC_SEVERE
Explanation - WOLA is not enabled on WebSphere Application Server for z/OS.
Response - Enable the server environment to use WOLA.