Jump to content

Clarence Owens

Member Since 01 Feb 2000
Offline Last Active Dec 22 2005 06:16 PM

Posts I've Made

In Topic: When a function was last run?

04 December 2003 - 01:19 PM

Don't know whether you are a Glovia user, but in Glovia 5.4 the Superlayer language processor adds calls to the Pro-IV code that track the last 40 executions of each function in the file SLTRNHIS. Well, it tracks *most* functions anyway and it's been quite handy at times. I wrote a screen to display a portion of the file and a report to display all 40 entries for the selected function. The SLTRNHIS file def may only have been present in Pro-IV and if so I migrated it to Superlayer.

In Topic: How to prevent users from shelling out using '!'

16 December 2002 - 05:42 PM

I see that your version of Pro-IV is pretty old, but in our Glovia 5.4 system, Pro-IV v4.6 there is a function called 'OP_SYS Execute Operating System Command' that controls the shelling out. In our system its source is there. If your version uses it it'd be easy to restrict access to OP_SYS by setting its security category or by adding coding to it to qualify the operator.

In Topic: PRO-IV ISAM conversion to Oracle Database

28 February 2002 - 02:28 PM

Well, it depends somewhat on your environment, but in general you can start by copying the original Pro-ISAM file def to a new one and renaming the pro-ISAM (xxxx.pro) file to match the new def. Then you can change the original file def to have the external variable names and format specs you want for the Oracle table columns. Then you can create the Oracle table and primary key and alternate key indexes. Last, write a small update to copy the contents of the renamed Pro-ISAM file to the original (now Oracle) file.

If you have a Glovia system, they provide a suite of utilities written in Superlayer to do most of the detail work.

If you are converting from an old version of Pro-IV and have the extended Pro-IV kernal that allows Pro-ISAM files of 'unlimited' size, you will have to split any oversized old Pro-ISAM files into chunks that will be acceptable to the new kernel.

My experiences have been with Glovia/Superlayer migrations, but I believe the basic concepts are the same for any Pro-IV environment; just the tools available will be different.

In Topic: @DATE is sometimes blank...

08 May 2001 - 10:50 AM

Isn't @DATE one of the System variables that you can write to? Not that you'd want to... I don't want to try it since we only have two environments at the moment and both are in use. If it is one that can be written to, perhaps there's a global logic call or an LSCALL that is returning data to it.


In Topic: Writing to flat file

12 July 2000 - 03:16 PM

They're standard and supported, as per the 'Native Pro-IV Version 4 Developer's Guide Document No. 100709 Revision B'. I just was searching for info on the new file modes X, M and R and ran into the info on accessing the environment variables on page 5-12 of my manual.

I never did find anything about file mode 'X' in the Pro-IV book but it looks like that's Superlayer's version of the Pro-IV file mode 'R'. Ya gotta love it...