Jump to content

Chris Mackenzie

Member Since 11 Oct 2001
Offline Last Active Oct 24 2017 12:02 PM

Posts I've Made

In Topic: How do you create a memory file?

22 January 2016 - 07:57 PM

I looked at ProIV's documentation regarding creating memory files (topic ID 720293) and it has left me more confused than enlightened.

I took the simple approach of changing the file type of one of our existing "working files" and regenning all functions that reference it. It seems to have made no difference at all in execution speed of the report I was testing. The documentation also mentions adding an entry to pro4v7.ini which I did but it still makes no difference. 


Chaging to mem  file is quite simple - sounds like you did it correctly.  with modern file systems there is a lot of caching going on - if this was a pro-isam or c-isam file originally then converting to mem file may not give as much advantage as you might think - replacing a database table based workfile can give huge performance advantages.  Perhaps theres is something else slowing your report?  What sort of volume of data were you processing using this memory workfile?  I'm quite sure if you really pump up the volume you will see a difference.

In Topic: Cannot open function "Unknown Control ID!"

21 January 2015 - 10:02 PM

what versions - kernel, client & proivDeveloper?

In Topic: Batch Update and Windows Environment

16 July 2014 - 01:00 PM

? why not refactor -   set @LFUNCT FNEXIT and then re-enter to where you were in your main function after calling your update..

In Topic: Batch Update and Windows Environment

12 July 2014 - 12:08 AM

Batch ID can only be used for non global functions. We tried. I know PROIV Developer saves logics behind the scene. Anyone know how they do it?


why is that a problem?   you wrap the required globals in a non-global Update and set that to run in batch.


BTW - what reason were you given for batch queue not working in Windows?


Someone suggested

In Topic: capture crash on windows server

27 June 2014 - 08:22 AM

that's quite similar to how our job runs.  The logfile though doesn't help as the kernel has crashed.  There is activity on the Windows server from proivsrv.exe and p4wks.exe.  on linux there is strace - has anyone used "stracent" ? If I can catch that info then I have something useful to give pro-iv support.


 we could start the server with "c:> stracent -- proivsrv.exe" or suchlike but how would that work for a gateway call?