Hi all,
I've worked with Uniface for many years and have never come across this one, so I'm curious whether anyone recognises it.
In a Uniface 10.4 environment [exacte versie/patch + server-OS invullen], many userver logs show $ioprint=21075 in the [startup] header. It only happens with userver processes acting in the Data Server role (the good old PolyServer). Uniface Servers in other roles start with the $ioprint value we expect.
21075 is not a value anyone here configured:
- Binary it is 1 + 2 + 16 + 64 + 512 + 4096 + 16384. Bits 512, 4096 and 16384 are not documented as I/O message levels.
- In hex it is 0x5253, which happens to be ASCII "RS". That may be a coincidence, but it looks more like something being read as a number than a deliberate setting.
What I've ruled out:
- $IOPRINT in [SETTINGS] of the userver assignment file, including included files and usys.asn
- /pri in the UST definitions in the [SERVERS] section of urouter.asn, and the command line in general
- Settings changed via the Uniface Router Monitor
- Environment variables and startup scripts
- Application code: $ioprint is only ever set explicitly to 0
Questions:
- Has anyone seen this value, or other "odd" $ioprint values, in Data Server userver logs?
- Are bits 512, 4096 and 16384 used internally by Uniface?
- Does a Data Server userver derive its initial $ioprint from somewhere other than the asn and /pri, for example the router or the client request that starts it?
I'm happy to share a sanitised log header or asn excerpt if that helps.
Thanks in advance!
