The APPX 4.2.4 Patch Release addresses the following items:
- Bug #731: Client Preferences issues
- Bug #996: File Names not available to scan from READ stmt
- Bug #998: GUI destroys field content if multiple '=' characters are contained
- Bug #1023: Spelling mistake in DD
- Bug #1026: Scan fails with seg fault
- Bug #1027: License server off by one
- Bug #1028: Multiple sessions not allowed after registration limit reached
- Bug #1034: Maintenance agreement license server changes
- Bug #1036: Scan on Alternate key returns 1st record
- Bug #1037: Direct Process 1 = > Signal Error
- Bug #1066: Scan doesn't return 1st record when <Enter> is pressed
- Bug #1079: Overriding LOGIC field as BIT field doesn't work
- Bug #1087: 0-apps cursor in wrong place
Bug #731: Client Preferences issues
- There were differences between value and default value for debugNotifyLevel and debugLogLevel caused by one being the token value, the other the token number. Also, widget is misspelled in the description for editorForceSize.
- These have been corrected.
Bug #996 - File Names not available to scan from READ stmt
- When entering a READ statement and scanning to select the file name to be read, only field names were presented, and the 'Select File' option button does not function.
- Corrected as follows: When you scan on an operand that can contain a field name or a file name, you should now be able to scan for either. The scan processor will show you the list of files by default - use option 1 to scan fields instead. The scan processor will remember your scan preference.
Bug #998: GUI destroys field content if multiple '=' characters are contained
- If the content of an alpha field is a series of '=' characters (example '==========') the gui represented its content as NULL (empty). If the record was stored the field content was blanked out. If the alpha field contained a substring of '=====' 's that substring was replaced by blank characters.
- This has been fixed.
Bug #1023 - Spelling mistake in DD
- In the AA popup for Alpha fields, the 'Lowercase OK?' label is misspelled as 'Lowercare'.
- This has been corrected.
Bug #1026 - Scan fails with seg fault
- Invoking scan from within a live application caused a seg fault.
- This has been fixed.
Bug #1027 - License server off by one
-
The Appx license server granted one too many usage rights for any counted feature registrations.
-
This has been corrected.
Bug #1028 - Multiple sessions not allowed after registration limit reached
-
The license server, which allows up to four logins under the same user ID for each usage right, disabled multi-session logins once you reached the maximum number of users allowed by the registration.
-
This has been corrected.
Bug #1034 - Maintenance agreement license server changes
- The Appx license server previously compared the expiration date contained in the APX/MNT feature registration with the compile date of the Appx engine. If the engine was built after the registration expiration date, Appx reported an invalid, missing or expired MNT registration.
- Our new maintenance policy states that a user can run any patches made to a supported version of Appx. In other words, if version 4.2 (a major release) is released while your APX/MNT registration is valid, you should be able to run any 4.2.x release, even if 4.2.x was issued after your APX/MNT registration has expired.
- This feature has been implemented in 4.2.4.
Bug #1036 - Scan on Alternate key returns 1st record
-
When you did a scan on Alternate key and select a record from a list built by that scan, it returned the first record from that list.
-
However, if you scanned on the Primary Key first and changed path to Alternate Key, 'select' works properly.
-
This has been fixed.
Bug #1037 - Direct Process 1 = > Signal Error
-
When user defined a SYSPARM Direct Process 1, users entering appx got => MODULE: BI.C.1727 ; 'An unrecoverable error has occurred (signal), exiting'
-
This has been fixed.
Bug #1066 - Scan doesn't return 1st record when <Enter> is pressed
- When scanning a file, if the desired record is the first one on the screen, a simple return did NOT bring the record back. Only by clicking on the record would it be retrieved.
- This has been fixed.
Bug #1079 - Overriding LOGIC field as BIT field doesn't work
- When overriding the LOGIC fields to BIT data type, a problem is detected with the inputs. The Checkboxes always appeared UNCHECKED (if seen from the Java Client) and when checked the values didn't seem to work properly in SQL Server. Leaving the fields as varchar(1) was the best method to handle this error.
- This has been corrected.
Bug #1087 - 0-apps cursor in wrong place
- When adding records on a scrolling display, when you reached the bottom of the display and added a record, after returning to the scrolling display, the cursor was on the row above the bottom row.
- This has been corrected.
Refer to the APPX 4.2.0 Release Notes for all enhancements and corrections built into this major release. Also refer to the Release Notes for APPX 4.2.1, APPX 4.2.2, and APPX 4.2.3 for items addressed by those patch releases.