| This table lists the enhancements and fixes in fix pack version 2.1.2. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 83134 | JR23179 | Hexadecimal EBCDIC values need to be printed to the trace file. |
| Symptom: When AS/400 values are converted into Java Object form, users are not able to find the corresponding Hexadecimal values. |
| Resolution: The adapter traces the Hexadecimal and EBCDIC values. |
|
| 2 | 83135 | JR23178 | The iSeries Adapter is unable to parse the PackedDecimal Parameter accurately |
| Symptom: The iSeries Adapter is unable to parse the parameter accurately and pass it. It reports a VerbProcessingFailedException. |
| Resolution: The adapter correctly parses the parameter and traces bytes accordingly. |
|
| 3 | 83086 | JR23114 | Error in parameter count for multi-record business objects |
| Symptom: The adapter reported an incorrect parameter count for multi-record business objects. |
| Resolution: The count is corrected now for multi-record business objects. |
|
| 4 | 74170 | JR226721 | Support for single sign-on to avoid tracing of password. |
| Symptom: iSeries Adapter traces the connection business object which also contains the password to the iSeries machine. This is a security leak. |
| Resolution: The login information provided in the connection business object could not be encrypted due to ADK limitations.
The users now have two options : 1. Use the conventional business object which will trace the password.
2.Use the new configuration template with boolean USE_DEFAULT_CONNECTION_INFO and three new encryptable configuration properties for hostname, login user name and password
(DEFAULT_CONN_PASSWORD, DEFAULT_CONN_HOSTNAME, DEFAULT_CONN_USERNAME). These will override the information in the connection business object if the USE_DEFUALT_CONNECTION_INFO is set to 'true'. |
|
| 5 | 83984 | JR23671 | The iSeries Adapter ObjectEventID value grows longer for each polled business object. |
| Symptom: The ObjectEventID was appended to the adapter name each time an event was polled and sent to the broker. |
| Resolution: The ObjectEventID is no longer appended to the adapter name. |
|
| 6 | 83331 | JR23590 | ODA for iSeries - names must not start with #. |
| Symptom: Normally, the ODA will set the exact IFS file name (without extension) as the business object name, even if they have some special characters. This led to some errors because of some special characters in the filename. |
| Resolution: The ODA removes any special characters in the filename string while setting the business object name. |
|
| 7 | 85973 | JR25295 | When reading the keyed data queue, the error "No Message Found" was logged. |
| Symptom: The maximum length of the KeyedDataQueue (KDQ) entry and the CCSID for the key should be matched. The adapter included the key length incorrectly as part of the KDQ entry. |
| Resolution:
The adapter now uses the correct length for the KDQ entry and also uses the given CCSID in the attribute's ASI. Based on this length, the adapter extracts the key part of KDQ into the business object 'QKeyAttribute' and extracts the remaining data of KDQ into the business object 'QNonKeyPart'. |
|
| 8 | 86591 | JR25209 | The iSeries ODA does not create the business object correctly for the KeyedDataQueue (KDQ) entry. The maximum length of the NonKey attribute is incorrect. |
| Symptom: The ODA did not create the business object 'QNonKeyPart' with the correct length. The ODA was subtracting the key length from the KDQ maximum length. |
| Resolution: The ODA now creates the business object 'QNonKeyPart' with the correct length. |
|