Search results

The -n parameter doesn't affect how many users you can define, if by "define" you mean "create". The -n parameter determines how many users can connect to the database at the same time. You can see how many users were purchased for each of the product licenses that are installed on the server...

Of course. Every setting has a limit. The -n parameter determines how many database connections you can have concurrently. It includes all types of connections (4GL clients, SQL clients, utilities, helper processes, etc.), except for servers and brokers. The question shouldn't be about the...

Correct. The AND AVAILABLE ttcbc is equivalent to AND TRUE (unless you were doing something like releasing the ttcbc buffer prior to the if available, which you are not). It doesn't accomplish anything. Why do you think it is required? Original: Revised: Why did you add the qualification of...

A modern Linux machine very likely isn't going to run an old Progress version like 9.1D; it won't have the required libraries. But if you have source code for your application then you can compile it under a modern release of OpenEdge and run that on Linux. The current release is 12.8. If you...

You cannot back up and restore databases across different operating systems. You must dump and load the databases. What release of Progress do you have for Linux?

The license model (e.g. Named User, Concurrent User, Registered Device, Access Agent, etc.) is a property of an OpenEdge product license. The license has other properties, such as product code (e.g. Enterprise RDBMS, Client Networking, etc.), platform (e.g. Windows, Linux), architecture (e.g...

Any "what can OpenEdge do" question is entirely dependent on which OpenEdge release you are using. We don't know that.

Yes, -Mm affects remote 4GL client connections. In 11.x the default value is 1024 which is quite low, and inadequate for most applications. Try 8192. You can specify it on the database login broker, and you don't have to specify it on the client (App Server) side.

You're welcome. :) The client OpenEdge release may be at or above the database release, up to one major-version different (e.g. 12.x client connecting to 11.x database), provided that the database connection is via TCP and not shared memory. The database release cannot be above the client release.

You and I may have differing opinions on "legitimacy", which is a value judgement, but this is a common and very acceptable configuration. At this point -N exists for backward compatibility. It doesn't hurt but it doesn't help. There is only one supported network protocol which is tcp...

The watchdog only operates on servers and self-service connections. It only intervenes and removes a connection if it detects a variance between the processes listed in the user connection table (_Connect) and the OS process list. For example, if _Connect shows user 123, type Self/4GL, PID...

Exactly. Or the user could run applicationstartprocedure.p, which is the name of the procedure that everyone runs, except that unbeknownst to you their copy is modified to do something different. And the modified copy can be replaced before you get a chance to check it. It sounds like the...

Who needs fonts? Make it CHUI. :D

This sounds awfully familiar. There was a similar discussion recently, here: https://www.progresstalk.com/threads/progress-editor.202254/ Your options are going to depend on your OpenEdge release, which you haven't mentioned.

Procedure Editor unsaved buffers are transient by design. And even if you could get .ped files to stick around, they are files in the user's file system that they have permission to delete, so it still wouldn't fulfill any meaningful audit requirement. So it seems your real requirement is that...

Here is a little more material for your upcoming discussion. OpenEdge 11.7 will be retired in a little over a year from now, in April 2025. https://docs.progress.com/bundle/openedge-life-cycle/page/OpenEdge-Life-Cycle.html Progress has moved OpenEdge to a long-term support (LTS) model, where...

I don't think you have described your database structure in detail yet, e.g. whether your application data is in Type 1 or Type 2 storage areas. This is relevant for this discussion, as they do space management differently. What is the issue that makes you set on freeing space for growth...

Your table and LOB data lives in record blocks (sometimes called "RM blocks"). Once a block is formatted as a record block, it remains a record block. Even if you delete all the record fragments it contains, while the the record block is in a sense logically empty, its block type does not...

For future reference, in Windows the services file is %windir%\System32\drivers\etc\services. In Unix systems it is /etc/services. It is a mapping of service names to TCP or UDP port numbers. The -S parameter, when used on a database broker, is what makes it a login broker. The broker binds...