APAR status
Closed as documentation error.
Error description
Rational Business Developer V7.5.1.5: Documentation changes for the EGL COBOL support are needed to document the following information. An ELAX abend or message ELA09974P is received running IBM Rational Business Developer generated COBOL programs on CICS, using the IBM Rational COBOL Runtime for zSeries, when an error occurs in the program and the exception is not handled by the program. When the ELAX abend occurs, the following is an example of the messages that are written to the ELAD queue: ELA00093I An error occurred in program P0000000, function MAIN ELA09974P Unhandled exception occurred. EGL line: 000019 ELA09973I Condition code: 9981 ELA09965P Runtime exception ELA00001I An error occurred in program P0000000, function MAIN. An error occurred in program P0000000 on ELA00001I statement number 19. Condition code: 00027 ERROR CODE=00000000. Runtime exception. If the V60ExceptionCompatibility program property is set to YES, instead of the ELAX abend, the ELAM02 panel is displayed with the above messages. An example of when this problem occurs is when assigning a string that contains invalid data to a numeric field. The following is an example of an assignment statement that causes this problem: n3 decimal(7, 2) = "1234.5"; In this example, the failure occurs with the following settings: - In the build part, the following build descriptor options are set: - decimalSymbol = , (comma) - separatorSymbol = . (period) - In the ELARIccc (where ccc is the language code), language-dependent options module. the following are set: - decimal point set to a , (comma) - numeric separator set to . (period) Based on the settings above, a period in the string is not a valid decimal point character. Prior to Rational Business Developer 7.5.1.5, this scenario was not handled as an error and resulted in unexpected results in the numeric field. In the example provided, the results were 12345,00. In comparison, the EGL Debugger displays error message EGL0102E for the same scenario. With the 7.5.1.5 fix pack, the EGL COBOL support was changed to be consistent with the EGL Debugger in handling this as an error. As mentioned earlier, this problem only occurs if the EGL program does not handle the exception using a TRY block. Some options for resolving or handling the error situation are: - Correct the problem causing the exception. In the example provided, change the period to a comma in the assignment string, or change the decimal point and numeric separator settings to match the data. - Add a TRY block to handle the error. One example of handling the error is to display an informative message to the end user.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Change in COBOL gen behavior was not reflected in the documentation
Problem conclusion
Made the following doc changes in version 8.0.1 1) removed the note about different behavior from regl_core_compat 2) added a note to the decimalSymbol docs about the possible error message 3) added a "Compatibility" note to the V60ExceptionCompatibility topic
Temporary fix
Comments
APAR Information
APAR number
PM17330
Reported component name
RBD EGL FOR COB
Reported component ID
5724S5001
Reported release
751
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-25
Closed date
2010-12-07
Last modified date
2010-12-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMQ79","label":"Rational Business Developer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
07 December 2010