Skip to main content

Patch 10.4.02-025

Downloads

Product availability Matrix (PAM)
Downloads of this patch are available from the Rocket Customer Support Portal.
Further explanation can be found here.

New Feature(s)

  • Add user-configurable keyboard shortcut functions to Windows GUI applications.

Currencies

  • Xerces updated to version 3.2.4 on iSeries to improve security. Note that XML validation messages in $procerrorcontext might change due to updates in Xerces.

  • Add support for IBMi 7.5 (AS7)

Fixes

UNI-33661UServer may hang indefinitely on shutdown if there is a license related message
UNI-33609Executing pseudo SQL can cause error when using PostgreSQL
UNI-33550Function used in Global ProcScript gives compile error
UNI-32631Overlaid weboperation with Javascript function causes compile error
UNI-32614IDE: Window Properties of modeled component lost when changing split bar on derived component
UNI-3192764-bit Uniface 10.4.02: Closing Message Frame Window with Esc can cause crash
UNI-29313After changing the implementation type of a component the signature is not changed
UNI-28434Global object might not be found on subsequent calls when using remote resources



UNI-33661  -  UServer may hang indefinitely on shutdown if there is a license related message

Solution available in patch(es):      10.4.02-025

Description:

When the licensing system issues a message that a license is due to expire in a number of days it sends that message to the transcript window. However, UServers do not have a transcript window so that message will never be displayed. But when the userver eventually shuts down it thinks there is a transcript window and keeps waiting for it to be closed, and that never happens.

Environment:

+Uniface: Version 10.4.02.023
+Operating System: Windows
+Database: DBMS independent

Workaround:

You can set option LM_TRANSCRIPT=Off in $license_options in the UServer assignment file.

Notes:

This problem is solved.

Back to top



UNI-33609  -  Executing pseudo SQL can cause error when using PostgreSQL

Solution available in patch(es):      10.4.02-025

Description:

Executing the following sql/data statement against PostgreSQL (using the PGS driver) will return an error:

sql/data "SELECT 'a', 'b', 'c', 'd', 'e'", "DATA"
putmess $result; $result = ""
putmess $status; $status = -31

"The DML statement of the sql instruction exceeds 32 KB."

When running the above sql statement against Orace, SQLite, or MSS will not return an error and as result the Uniface list "a;b;c;d;e" is returned.

It seems that the PGS driver will allocate for each pseudo column 8KB and when specifying more than 4 columns then this will exceed the current limit of 32 KB.

Environment:

+ Uniface version: 10.x
+ Platform: ALL

Workaround:

None.

Notes:

This problem has been resolved.

Back to top



UNI-33550  -  Function used in Global ProcScript gives compile error

Solution available in patch(es):      10.4.02-025

Description:

When a Global ProcScript contains a function module, the compiler produces an error message stating that the preceding module should end with an "end" statement, even if the preceding module ends with an explicit "end" statement.

Environment:

+ Uniface version 10.4.02.016 and higher
+ Platform: ALL

Workaround:

None.

Notes:

This problem has been solved.

Back to top



UNI-32631  -  Overlaid weboperation with Javascript function causes compile error

Solution available in patch(es):      10.4.02-025

Description:

When a weboperation or webtrigger that contains a JavaScript function is overlaid or undeclared, the compiler issues error messages. The compiler mistakes the JavaScript function to be a ProcScript function.

Environment:

+ Uniface version 10.4.02.016 and higher
+ Platform: ALL

Workaround:

None.

Notes:

This problem has been solved.

Back to top



UNI-32614  -  IDE: Window Properties of modeled component lost when changing split bar on derived component

Solution available in patch(es):      10.4.02-025

Description:

The Window Properties of a modeled components are overwritten (not inherited) by the IDE Component Editor when a Split Bar is added to the derived component or in case the position of an existing split bar (inherited from the modeled component) is changed. After a split bar is added or changed on the derived component then the Window Properties only include the Split Bar (SPLIT) properties. This means that all other Window Properties will get their default value.

For example: the Modality property will have the value Modal (regardless of what was defined in the modeled component; other properties such as background image or color will be emptied.

Environment:

+Uniface: Version 10
+Operating System: OS independent
+Database: DBMS independent

Workaround:

None

Notes:

This problem is solved.

Back to top



UNI-31927  -  64-bit Uniface 10.4.02: Closing Message Frame Window with Esc can cause crash

Solution available in patch(es):      10.4.02-025

Description:

A crash can occur when using 64-bit Uniface 10.4.02-000 (or higher) and the Message Frame Window is closed with the Esc key. The problem can (e.g.) be seen when opening the Message Frame from a More Editor of the IDE (e.g. Signature Editor).

Environment:

+Uniface: Version 10.4.02
+Operating System: OS independent
+Database: DBMS independent

Workaround:

None.

Notes:

This problem is solved.

Back to top



UNI-29313  -  After changing the implementation type of a component the signature is not changed

Solution available in patch(es):      10.4.02-025

Description:

When the implementation of a component is changed (by changing the Component Type property) then recompiling the component will not recreate an existing signature correctly. As a result, when calling an operation of the converted component then this will fail with the error -50 (Signature descriptor for the current component not found or when it is found then an interface is missing or invalid).

Consider the following scenario:

+ the form component CPT1 is created with the operation MYOPER1
+ CPT1 is compiled and a test is done to call MYOPER1 of CPT1

=> the test will be successful

+ Now the form component is converted into a service by changing the Component Type property from 0 (Form) to 1 (Service)
+ CPT1 is recompiled and another test is done to call MYOPER1 of CPT1

=> this test will fail with the error -50 ($status & $procerror = -50; UACTERR_NO_SIGNATURE)

Environment:

+Uniface: Version 10
+Operating System: OS independent
+Database: DBMS independent

Workaround:

Manually delete the signature before recompiling the component.

Notes:

This problem is solved.

(Note that in case you have an existing signature with an incorrect default implementation the compiler will not detect this. You can manually delete the signature to resolve this.)

Back to top



UNI-28434  -  Global object might not be found on subsequent calls when using remote resources

Solution available in patch(es):      10.4.02-025

Description:

When using remote resources then global objects might not be found anymore when accessed/called for the second or subsequent time. The problem occurs when using patch 10.3.02.061 (or higher) and the remote resources are directly addressed. E.g. 

[RESOURCES]
$REMOTE:.\resources

Consider the following scenario:

The form FRM1 features two buttons that show the glyphs GLY1 and GLY2
FRM1 starts the form FRM2 that features three buttons that show the glyphs GLY1,  GLY2, and GLY3
When starting FRM2 for the first time then all glyphs are shown as expected
After closing and reopening FRM2 the glyph GLY3 is not shown anymore when using remote resources that are directly addressed (see details above)

Environment:

+Uniface: Version 10.3.02-061 (and higher), 10.4.01 (and higher)
+Operating System: OS independent
+Database: DBMS independent

Workaround:

In case the search of the remote resources is delegated to the server (new functionality that was introduced with patch 10.3.02.061) then the problem does not occur. E.g. 

; client asn
[RESOURCES]
$REMOTE:

; server asn
[RESOURCES]
.\resources

Notes:

This problem is solved.

Back to top



Be the first to reply!
Terms & ConditionsAccessibility statement