Skip to main content

Patch 10.4.02-031

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)

  • Code and Layout editors in the IDE now support Uppercase and Lowercase functions.
    Note:
    Installation using the edist will add a [userkeys] section to your usys.ini file. If you overlay using the patch zip file, you need to manually add to your usys.ini:
    [userkeys]
    code.uppercase=Ctrl+U
    code.lowercase=Ctrl+Shift+U
    Or use the Context Menu options only.

Fixes

UNI-34738 Project Editor Resource Browser menu's throw exception
UNI-34708 IDE Resource Browser U-Bar: letters a or c can not be entered anymore
UNI-34581 State project file misc/usysstat.xml only contains service.
UNI-34332 In some circumstances a deadlock can occur on Linux after some time.
UNI-33918 On Solaris, the 'sleep' proc statement can not sleep for more than four minutes and already returns after on average two minutes.



UNI-34738  -  Project Editor Resource Browser menu's throw exception

Solution available in patch(es):      10.4.02-031

Description:

Project Editor Resource Browser menu's throw exception, in Templates, Model and Objects tabs this can be seen. As a result the menu is not started.

Environment:

+ Uniface version: 10.4.xx
+ Platform: WIN
+ Database: ALL

Workaround:

You can use the popup menu in the structure view in most cases.

Notes:

This problem is solved.

Back to top



UNI-34708  -  IDE Resource Browser U-Bar: letters a or c can not be entered anymore

Solution available in patch(es):      10.4.02-031

Description:

Since patch 10.4.02.030 letters a and c are setting the U-Bar into display only mode and as a result there is no results retrieved.

Environment:

+ Uniface version: 10.4.02.030
+ Platform: WIN
+ Database: ALL

Workaround:

If looking for just a or c there is no workaround, if looking for a string starting with, or containing, a or c, continue typing that word.

Notes:

This problem is solved.

Back to top



UNI-34581  -  State project file misc/usysstat.xml only contains service.

Solution available in patch(es):      10.4.02-031

Description:

The state project file usysstat.xml, only delivers the state service, the ustate entity and project definition were missing since patch 10.4.02.029.

Environment:

+ Uniface version: 10.4.02.029
+ Platform: WIN
+ Database: ALL

Workaround:

Import from an older patch.

Notes:

This problem is solved.

Back to top



UNI-34332  -  In some circumstances a deadlock can occur on Linux after some time.

Solution available in patch(es):      10.4.02-031

Description:

When using Sentinel a SIGALRM signal is send every four minutes. In the signal handler a semaphore function is used that is not async safe. If the same thread was doing the same thing for some other reason, for example, TCP/IP operations, then this may cause the handler to try and lock a semaphore that is already locked by the same thread and thus block the whole thread.

Environment:

+Uniface: Version 10.4.02.026 and higher
+Operating System: Linux
+Database: DBMS independent
+Licensing System: Sentinel

Workaround:

There is no workaround for this problem, except using a version prior to patch 026.

Notes:

This problem is solved.

Back to top



UNI-33918  -  On Solaris, the 'sleep' proc statement can not sleep for more than four minutes and already returns after on average two minutes.

Solution available in patch(es):      10.4.02-031

Description:

On Solaris, when a sleep is interrupted by a SIGALRM signal, it will always stop sleeping. On other platforms sleep this is not the case, sleep can resume their sleep after this signal.
The Sentinel licensing software sends a SIGALRM signal every four minutes to signal the refresh of license features. This is the way it implements the equivalent of DLM's 'heartbeat'.

Environment:

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

Workaround:

In your proc code you can get the current time, then do the sleep, and when that returns check that the required period has indeed elapsed. If not, you do the sleep again for the remainder of the time.

Notes:

This problem has been solved.

Back to top



Be the first to reply!