Jump to content


Member Since 08 Jul 2004
Offline Last Active Jan 13 2011 03:39 AM

Posts I've Made

In Topic: Converting Code from 5.5 to 6.1

10 March 2009 - 07:22 PM

We already migrate our system from PROIV 5.5 to PRO 6.1, we exported everything and then reimported to 6.1, after that we were requiere to regen all the system. After it was done, the system was working fine, we did not have any issues.

I don't think it's posible to ISIN from 5.5 to 6.1

Probably not want you want to hear but I would not short cut the upgrade, follow the route Northgate advise and support.

Although I think for you it's just an easy ISIN the newer version VIP and regen the system.

However, we have been thinking about attempting to install some of our smaller projects straight from our VIP 5.5932 into 6.1 to reduce some overhead (do not ask me why we do not just upgrade our VIP environment to 5.5932 or higher, I would, but I don't make that call).

Still it is tempting to go with the short cut and if you have issues where Northgate suggest going back to the original codebase and redo the upgrade, you can do a nice "I told you so" to whom ever does make the call :) .

Of course it might all be fine.

In Topic: Problem accesing read only CISAM files

10 March 2009 - 07:15 PM

Actually the owner and group are not the same for user thats trying to view the content of the files, but that's the requirement, the problem here is that with the same file permission I'm able to view the content of the proisam file and it's not doing the same for the Cisam file. Here is the ls -l :

-rwxrwxr-x 1 root root 1024 Mar 9 17:02 PRUEBA_CISAM.dat
-rwxrwxr-x 1 root root 3072 Mar 9 17:02 PRUEBA_CISAM.idx
-rwxrwxr-x 1 root root 1024 Mar 9 17:04 prueba_pro.pro

User running proiv is pro61 and the group is pro61.

Sounds like file ownership issue to me.
Try doing a CHOWN on the file.

Make sure the owners are all in the same group nd have access permissions.

In Topic: Licence Server Error on 6.1

10 June 2008 - 02:29 AM


After working with PRO-IV support we were able to found the following in the file
wrapper.log, it had a warning regarding a 32 bit version of java (the server we are using it's a 64 bit server). So in the wrapper.conf we changed the following line:
wrapper.java.command=/opt/java1.5/jre/bin/java for wrapper.java.command=/opt/java1.5/jre/bin/IA64W/java which is the 64 bit version of java. Rebooted the server and it worked.

Thank you.

In Topic: Parent function of Global Window

20 June 2006 - 05:36 AM

Try @CURFUNCT, it used to work in PRO-IV 4.6, I don't know if it's going to work with PRO-IV 5.5

In Topic: SQL and C-ISAM access

14 May 2006 - 08:41 PM

Have you try set linux environment variables insted of declare them in the pro4.ini file?

$export PROPATH=/home/proiv/dev/prg
$export PRODATA=/home/proiv/dev/data
$export PROTEMP=/home/proiv/install/temp
$export INFORMIXDIR=/home/proiv/install/gls
$export PROTERM=DECVT100