Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

UNIX

FACT(s) (Environment):

Actuate

SYMPTOM(s):

Actuate Date Problem

Dates are displayed with the wrong values (e.g. 31 March 1996 displays as 03 July 1998)

OIBroker running on Unix server

FIX:

Workaround:

The Progress OIB and OID processes which Actuate uses to connect to
Progress databases use the default Progress startup parameter file
("$DLC/startup.pf"). If this file contains the "-d" or "-E" para
meters (which set date format and European numeric format) Actuate
not function correctly. In particular, dates may be displayed with
the wrong values (e.g. 31 March 1996 displays as 03 July 1998).

It is not acceptable simply to modify the "startup.pf" file, since
this is used by all Progress processes on a system. However, there is
an environment variable "PROSTARTUP" which can be used to redefine the
startup parameter file. The simplest solution is to modify the
"prooibrk" and "prooidrv" shell scripts (in the $DLC/bin directory) by
adding the following line immediately before the final line of each
script:

PROSTARTUP=$DLC/startup_oib.pf ; export PROSTARTUP

Now (in the $DLC directory) copy "startup.pf" to "startup_oib.pf" and
remove or comment out any uses of "-d" and "-E" from "startup_oib.pf".

Make sure that you kill and re-start any Progress OIB processes
which are running using PROSHUT -SV -S servicename for the broker
then exit and restart all Actuate sessions. (BEWARE that on win95
PROSHUT -SV -S servicename causes a gpf (known bug, also reported to
Actuate) and therefore needs to be killed by hand.)

The Progress OIB and OID processes will now be using the modified
startup parameter file which does not contain the problem parameters.
Thus Actuate will function correctly.