Recent content by George Potemkin

Can you post the timing per phases (dump, idxbuild, load)?

OpenEdge Release 10.2B06 as of Mon Mar 19 19:14:30 EDT 2012 OpenEdge Release 10.2B07 as of Fri Sep 7 02:16:34 EDT 2012 OpenEdge Release 10.2B08 as of Tue Nov 12 19:06:41 EST 2013 OpenEdge Release 10.2B0848 as of Tue Nov 10 05:16:39 EST 2015 OpenEdge Release 11.0 as of Fri Dec 2 19:00:19 EST 2011...

-z (since V11.1?) adds a few extra messages: Thread memory usage #threads: %d Required: %J Limit: %J In use: %J %B %s: numEntries: %i Threads requested: Data scan: %d, sort: %d, merge: %d, sort groups %d *** Used %l in-memory sort buffers out of %l (%j MB out of %j MB)

My 2 cents: you can use 'proutil <db> -C viewB2 [-csoutput -verbose]' to check the locations of the objects per areas. Size of Aries.d1 is 3 GB. It means the objects are in Schema Area.

I'm wary of ProExec simply because it was created for a product whose support is currently limited and whose future is uncertain. I'm a newbie to this topic, so I'm looking for pros & cons, as well as for best practices.

We are forced to adapt the Progress code between the process architecture supported by Progress. Is it a Progress bug?

Finally (I hope), the input parameters of the CreateProcessA procedure get NULL value with just a few exceptions. Type change seems to be required only for two parameters: lpStartupInfo and lpProcessInformation.

Would it be wrong to use INT64 on PROCESS-ARCHITECTURE 32?

Bingo! Can I tell whether an OE installation is 32-bit or 64-bit without PROCESS-ARCHITECTURE? https://community.progress.com/s/article/can-i-tell-whether-an-oe-installation-is-32-bit-or-64-bit-without-process-architecture "Can be used in OE versions prior to 11.3, when the PROCESS-ARCHITECTURE...

Thanks, Stefan. The article says "Change parameter from LONG to INT64" but it does not say which one - some or all? "Technically, hMonitor should also be an INT64 in 64-bit processes but Windows allows you to use 32-bit values for handles." Readprobe -> lib/windows.i PROCEDURE CreateProcessA...

ProTop and Readprobe use CreateProcessA procedure to create new processes on Windows. But the programs use the following construction to define the types of CreateProcessA procedure's parameters as well as for the functions used to read the memory structures: &IF...

Patrick, Why did you choose to use ProExec? It's a Progress .dll written to support Report Engine. It uses WinExec and WaitForSingleObject from kernel32.dll - the ancient (10/03/97) kbase article # 16735 was titled "Report Engine - WinExec errors in ProExec.dll". If you need to create the...

My goal is to copy all parameters of the current session (connected databases, session's parameters) and to launch new sessions with the same parameters. Almost as Patcick does in his example above. The parameter values may also contain the spaces. So it's better to quote them also. The extra...

Workaround for OS-COMMAND is found: the extra quotation marks around the whole command: DEFINE VARIABLE vCommand AS CHARACTER NO-UNDO. ASSIGN vCommand = SEARCH("_progres.exe"). OS-COMMAND VALUE('"' + QUOTER(vCommand) + ' -param "a b""'). It's still a mystery.

4 days ago Tom Bascom wrote: https://community.progress.com/s/question/0D5Pb00003uKdhKKAS/pro2-replproc-logging "I wouldn't be using PROWIN.EXE for a background service. That is the job of _PROGRES.EXE" Progress community appears to be divided into parties - the supporters of prowin and the...