Jump to content


Member Since 14 Feb 2006
Offline Last Active Dec 10 2015 03:25 PM

Topics I've Started

Secure Connection on Solaris

10 December 2015 - 03:25 PM

We can connect to Linux using the Securt Connection option on the Connection screen of Edit | Session properties. However, when we connect to Solaris the same way, the session does not connect and no error message is given. Any suggestions?

Pro-Isam file locked but not accessed elsewhere

13 June 2013 - 01:21 PM

We are getting a recurring problem at a v5.5 / Windows 2003 customer where a process stops because of a lock on a record in a file but nothing else appears to be accessing the file. Does anyone know of any tools that will help ascertain what is accessing a Pro-Isam file?

Green screen access with v7

29 March 2012 - 04:18 PM

I can't get GUI access to work with our new Linux box so, whilst I'm waiting for ProIV support to support me, I'm trying to get in via green screen to import my functions etc. However, upon entering with PRORUNTYPE=DEV, GUI=N and PROTERM=ANSIMON, I get taken to @PRO4M1 from which option 2, Utility Menu, takes me to a run-time utility menu. Switching with option 3 on @PRO4M1 between Production and Development status doesn't help.

Does anyone know how to get to a development utility screen when in green screen mode, please?

Thanks for any help.

Parsing SQLServer SQL/ENDSQL on v6.2

17 June 2010 - 03:00 PM

There's a bug in the parser for SQL/ENDSQL in 6.2.41 running on Windows against SQLServer.

This will fall over with an SQL error

:$ABC = 'X'

whereas this won't:

(:$ABC = 'X')

and neither will this:

OR :$ABC = 'X'

The problem is the parser effectively produces
OR:$ABC = 'X'
instead of
OR<space>:$ABC = 'X'
when the OR (same for an AND) ends the line and the next line doesn't start with a bracket.

The version that fails on SQLServer works fine on Oracle.

ProIV accept it's a bug and hopefully it will be fixed.

Setting exit for @VIPMENU in v6.2 run-time

17 June 2010 - 11:51 AM

We use the ProIV import for loading patches at the customers' sites.

In v5.5, we set @UM to exit back to our own screen from which the user logs off, thus we can tidy up the 'logged on' records we create when the user logged on.

In v6.2, the import screen appears to be a global function called from @VIPMENU. However, ProIV have removed the ability to set function exit in v6.2, so it looks like our patch install instructions are going to have to tell the users, after they've done the import, to click the 'System & Communications Varaibles' option, take the Link Functions tab and set the Link To function, then exit @VIPMENU. This will have to be done every time, as the values entered in 'System & Communications Varaibles' are lost each time you exit @VIPMENU.

Anyone got a method of setting the exit from @VIPMENU on a permanent basis? :)