Skip to main content

Patch 10.4.02-024

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 Sybase (SAP ASE) 16 on Windows Server 2019 (64bit)

  • Xerces updated to version 3.2.4 on Windows, Linux and Unix to improve security and schema validation. Note that XML validation messages in $procerrorcontext might change due to updates in Xerces.

Fixes

UNI-33522A few Sentinel 10 libraries are missing from the IBM iSeries (AS/400) Uniface distributions
UNI-33114Multiple SIGPIPE signals from UServers can cause URouter to unexpectedly exit.
UNI-10961IDE: Navigation from CMI window to entry included by #entry/#function fails
UNI-8531A read u_where with a non-existent field incorrectly returns status -20 (urouter error)



UNI-33522  -  A few Sentinel 10 libraries are missing from the IBM iSeries (AS/400) Uniface distributions

Solution available in patch(es):      10.4.02-024

Description:

Sentinel 10 libraries needed for ulic /prep and ulic /repair are missing from the IBM iSeries (AS/400) Uniface distributions.

Environment:

+Uniface: Version 10
+Operating System: IBM iSeries (AS400)
+Database: DBMS independent

Workaround:

None.

Notes:

This problem is solved.

Back to top



UNI-33114  -  Multiple SIGPIPE signals from UServers can cause URouter to unexpectedly exit.

Solution available in patch(es):      10.4.02-024

Description:

Multiple SIGPIPE signals thrown by a number of UServer processes to URouter can cause the URouter to unexpectedly exit. Problem seen on very fast Solaris system, however not a Solaris specific problem.

Environment:

+Uniface: Version 10
+Operating System: Linux / Solaris
+Database: DBMS independent
+Browsers: Browser independent

Workaround:

None.

Notes:

This problem is solved.

Back to top



UNI-10961  -  IDE: Navigation from CMI window to entry included by #entry/#function fails

Solution available in patch(es):      10.4.02-024

Description:

Using the #entry(/#function) pre-compiler directive, allows you to compile a global procscript's content into a component. When using #entry(/#function), the definition of the Global Proc entry is resolved at compile time; a call to the entry(/function) is no longer dependent on availability of the compiled Global Proc as a separate runtime object.

The CMI that is generated by the compiler is not correct for #entry(/#function):

The reference to the entry(/function) having the name of the global procscript points to the position of the #entry(/#function) statement in a ProcScript container
The reference to additional entries contained in a global procscript that is 'included' via #entry(/#function) take the 'line number' from the Global ProcScript container, but point to the container that contains the #entry(/#function) statement.

Environment:

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

Workaround:

None.

Notes:

This problem is solved.

Back to top



UNI-8531  -  A read u_where with a non-existent field incorrectly returns status -20 (urouter error)

Solution available in patch(es):      10.4.02-024

Description:

read u_where using a nonexistent field returns status -20.

This is documented as: -20: UNETERR_MAX_CLIENTS; Router could not accept new client, $MAX_CLIENTS exceeded.

And this is also returned in $procerrorcontext:

ERROR=-20;MNEM=<UNETERR_MAX_CLIENTS>;DESCRIPTION=URouter cannot accept more clients, maximum is reached; COMPONENT=F75403;PROCNAME=7&#92;READ;TRIGGER=READ;LINE=1

This is incorrect and the read u_where should actually return: -403: <UMISERR_UWHERE>; Nonexistent field in a u_where clause..

Compiling the form in question would have generated a warning

Phase 7: Procs compilation
(7&#92;READ) 1 read u_where foobar = "blabla"
(7&#92;READ) warning: 1000 - Field 'FOOBAR' not found

but this is easy to miss and the component is created anyway.

Environment:

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

Workaround:

None.

Notes:

This problem is solved.

Back to top



Be the first to reply!
Terms & ConditionsAccessibility statement