Downloads
Product availability Matrix (PAM)
Downloads of this patch are available from the
Rocket Customer Support Portal.
Further explanation can be found
here.
Currencies
- Add support for PGS 15 (U1.7) on RedHat, CentOs and Oracle Linux (LIE, LIF, LIG)
|
Fixes
| UNI-32984 | Settings in .ini files that have a value with a length that exceeds 1K don't work properly. |
| UNI-32856 | The Boolean values 0/1 cause structToJson to crash |
| UNI-32647 | Compilation of signature or component might fail when entity/occurrence parameters are used |
| UNI-32467 | When using sql/data or sql/print in combination with one of the UDT drivers PGS, MQL, SLE, DB2 or MSS a crash may occur. |
| UNI-32426 | DB2: Type P tables not selected by IDE Load Definitions. |
| UNI-31656 | OpenSSL cannot create private keys without a configuration file. |
| UNI-6776 | Structtojson crashes when a numeric structmember holds a string value |
| UNI-6625 | Misleading message in URouter log when using $USE_PMQ |
UNI-32984 - Settings in .ini files that have a value with a length that exceeds 1K don't work properly.
Solution available in patch(es): 10.4.02-021
Description:
Settings in .ini files that have a value with a length that exceeds 1K don't work properly. This problem is caused by the size of internally used String buffers.
Environment:
+ Uniface version: 10.x
+ Platform: ALL
Workaround:
None.
Notes:
Values of .ini file settings can now be up to 3K in size.
UNI-32856 - The Boolean values 0/1 cause structToJson to crash
Solution available in patch(es): 10.4.02-021
Description:
The Boolean values 0/1 cause the ProcScript statement structToJson to crash.
The problem occurs when (e.g.) a Boolean variable with the value 0 or 1, or the Boolean return value of a local ProcScript module (returns Boolean) is assigned to a Struct. Converting the Struct to Json will cause a crash.
Consider the following example:
bValue = 1 ; Boolean
struct1->Root->Element1 = bValue
structtojson vJson, struct1
Result: Uniface will crash
->jsonDataType = "boolean"
Environment:
+Uniface: Version 10
+Operating System: OS independent
+Database: DBMS independent
Workaround:
1. Assign the value "T" to the Boolean variable instead of 1
bValue = "T"
struct1->Root->Element1 = b_action
2. Use $typed when assigning the Boolean value to the Struct
bValue = 1
struct1->Root->Element1 = $typed("$boolean(%%bValue)")
3. Add the tag jsonDataType = "boolean"
bValue = 1
struct1->Root->Element1 = bValue
struct1->Root->Element1->$tags
Notes:
This problem is solved.
UNI-32647 - Compilation of signature or component might fail when entity/occurrence parameters are used
Solution available in patch(es): 10.4.02-021
Description:
The compilation of a signature or component might fail when it includes operations that use entity or occurrence parameters and the entities in question have not been analysed before (i.e. no entity descriptors exist).
When compiling such a signature and no entity descriptors exist before the compilation then the following error can be seen:
===
Compile Signature: 'CPT1'
Analyze entity: ENT1.MOD1
error: 1031 - Cannot find entity descriptor for parameter ENT1.MOD1 of "CPT1".OPER1().
[info 0, warnings 0, errors 1]{noformat}
===
When compiling a component then the output is as follows:
===
Compile Service: 'CPT1'
Phase 2: Model definitions
Phase 3: Prep. structure
Phase 4: Form definitions
Phase 5: Background text
Phase 6: Component variables
Phase 7: Procs compilation
info: 1134 - Subsetting of ENT1 includes: PK, FLD1, FLD2
Phase 8: Structure tables
info: 6921 - Entity used for referential integrity.
info: 6921 - Entity ENT1 used for referential integrity.
Phase 9: Descriptor
info: 1122 - Generating and storing descriptor for entity ENT1.MOD1....
info: 1110 - Generating and compiling signature for CPT1....
warning: 1111 - Generated signature for CPT1 could not be compiled.
phase completed with error-code -1031
1114 - ****** NO NEW COMPONENT CREATED *******
[info 6, warnings 1, errors 1]
===
The error-code -1031 refers to the error 1031 (Cannot find entity descriptor) that can be seen above in the output of the signature compilation.
Environment:
+Uniface: Version 10
+Operating System: OS independent
+Database: DBMS independent
Workaround:
Make sure that the sub-folder \edc exists in the resources output directory (set with $RESOURCES_OUTPUT) before compiling signatures or components.
Notes:
This problem is solved.
UNI-32467 - When using sql/data or sql/print in combination with one of the UDT drivers PGS, MQL, SLE, DB2 or MSS a crash may occur.
Solution available in patch(es): 10.4.02-021
Description:
When using sql/data or sql/print in combination with one of the UDT drivers PGS, MQL, SLE, DB2 or MSS a crash may occur, either immediately or later on when closing the application. This happens if the query running for sql/data or sql/print results in a record that is larger then Uniface's internal buffer of 32K.
Environment:
+ Uniface version: 10.x
+ Platform: ALL
Workaround:
None.
Notes:
This problem has been resolved.
UNI-32426 - DB2: Type P tables not selected by IDE Load Definitions.
Solution available in patch(es): 10.4.02-021
Description:
Type P tables are not shown in the Tables tab because the query used by Load Definitions in Uniface 10 does not select this type of tables.
Environment:
+ Uniface version: 10.x
+ Platform: WIN
+ Database: DB2
Workaround:
None.
Notes:
This problem has been solved.
UNI-31656 - OpenSSL cannot create private keys without a configuration file.
Solution available in patch(es): 10.4.02-021
Description:
A template OpenSSL configuration file is now shipped with Uniface, that can be adapted to the user's requirements.
Environment:
Uniface version: 10.4.02
OS: Windows
Workaround:
None.
Notes:
The new file will be located in \common\bin\openssl.cnf.
It can be used with -config=filePath or by setting the environment variable OPENSSL_CONF=filePath.
UNI-6776 - Structtojson crashes when a numeric structmember holds a string value
Solution available in patch(es): 10.4.02-021
Description:
The conversion cannot handle the mismatch between data type and value and, although this is not very useful in a read application, it is for Uniface a valid situation and it needs to be robust for it.
Environment:
+ Uniface version: 10.x
+ Platform: ALL
Workaround:
None.
Notes:
This problem is solved.
UNI-6625 - Misleading message in URouter log when using $USE_PMQ
Solution available in patch(es): 10.4.02-021
Description:
When using the URouter setting $USE_PMQ and a postmessage queue (PMQ) is closed/cleaned up then the following message is added to the URouter log file:
cleaned up peer PMQ but thread exists t=0, chn=0
This message is misleading and incorrect since there actually is no thread (since t=0) and this message therefore should not be logged.
Environment:
+Uniface: Version 10
+Operating System: OS independent
+Database: DBMS independent
Workaround:
None.
Notes:
This problem is solved.