You could always create a symbolic link to a shorter path. For instance, if /opt/java/jdk does not exist:
# mkdir -p /opt/java
# ln -s /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.382.b05-1.el7_9.x86_64 /opt/java/jdk
Those are the example directories. You do have /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.382.b05-1.el7_9.x86_64 etc. So, as you indicated above, you should change java_env to be:
JDKHOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.382.b05-1.el7_9.x86_64...
The article is saying that you should put your actual path to Java in java_env and providing a simple example.
You must also adjust: "The new value of the JAVA_HOME environment variable in <DLC>/properties/java.properties"
There are some "interesting" patterns with ENCODE(), for instance:
define variable rr as character no-undo.
define variable ii as integer no-undo.
define variable jj as integer no-undo.
do ii = 1 to 10:
rr = "".
do jj = 1 to 16:
rr = rr + chr( random( 32, 126 )).
end.
display...
I wasn't thinking that the plaintext password would be stored, that's a grave sin, but in my mind I was certain that ENCODE() just ignored everything after the 16th character.
I should have tested that :(
Aside from being ancient and supposedly easy to crack, the other reason that the ENCODE function is inadequate is that it only considers the first 16 characters - so your ability to require long passwords is compromised. (strike out for posterity...)
Also "requirements" #1 & #2 are junk...
Sorry, there is no magic pixie dust that will add support for OpenEdge to SonarCloud. (I said as much is the first reply to this thread.)
You might as well ask when Oracle will start supporting OpenEdge.
If you want Sonar style code analysis of OpenEdge, CABL is the solution. I'm terribly...
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.
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...
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?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.