Search results

So it sounds to me like you need to convince SonarCloud to support OpenEdge (good luck with that!) Or not use SonarCloud since they don’t support OpenEdge.

Does CABL not "prepare a report"?

I suggest that you use CABL. You are never going to see support for OpenEdge in SonarCloud.

No need for symlinks. To preserve your scripts, the only part of the database that must be in /db/env is the .db file. All of the rest of it can be moved elsewhere. You will need to modify the .st file to reflect new extent locations and then either restore a backup to those new locations, or...

Of course not. That is just how one would print on Linux. Replace “output through…” with whatever it is that you are already doing to print on windows. Make sure to parameterize it so that you can easily support multiple destinations.

There is nothing built-in to the language that will simultaneously send the same output to two destinations. Frankly I would be surprised if any language has such a feature built in. The closest thing that springs to mind is the UNIX "tee" command. Working within the 4gl I would simply...

So I was right about LOAD and mistaken about SAVE, that is actually PUT-KEY-VALUE, I could almost be a Windows programmer :)

Not that I am a Windows kind of guy but aren't there some statements to LOAD and SAVE INI files? Is it possible that some code is allowing users to save settings somehow and that that is rewriting the INI file?

Are you hoping to find a way to multi-thread the 4gl?

Usually you would do this by sending large enough jobs that the first ones are still printing while you start the 2nd, 3rd, 4th etc...

ProTop also contains lots of code that will give you better insight into your database performance plus a ton of documentation explaining what those metrics mean. And you can easily entice us to talk about it by asking questions ;)

The values that you are seeing are just dumped directly from the VSTs (Virtual System Tables). Those are documented here: https://docs.progress.com/bundle/openedge-database-management-117/page/Virtual-system-table-summaries.html

BTW, 97.6% is not "very close to 100%". 97.6% is actually pretty crappy for a hit%. Using the example above if we assume a blazingly fast SAN with 2ms read repsonse time reading 100 records will take roughly 10.0001ms. Of that 10ms is waiting on disk, the 0.0001ms portion is operations in...

The hit% is the percentage of "db access" operations that do NOT result in a "db read". IOW, what percentage of logical activity is performed in memory? If you read 100 records, you have probably done about 210 "db access" operations (100 record block reads and a few more than 100 index entry...

There are many numbers in your post. Which ones do you think ought to be the same? Just guessing but a common misperception is that "db reads" are record reads. They are not. "db reads" is better read as "disk reads". A "db read" occurs when the database reads a block from disk. Which it will...

You should ensure that your database has been started with a non-zero value for -usernotifytime. This controls how frequently clients will check for schema updates. If the value is zero and a client is just sitting around doing nothing with the database (maybe the user went home for the weekend...

Progress 8.3 dates from the 90s. There were *ports* to many different platforms - HPUX, AIX, SunOS, Windows, etc but they are not binary compatible. As I recall the first Linux release was for 8.3e. And that required a SCO emulation package which has not been available with Linux for a very...

You have received a promotion!