A simple available cubpackconv should be sufficient:
icbccnt = 0.
for each ttcbc no-lock:
assign
lv_size = ''
lv_back = ''
lv_cup = ''
.
if item.backsize > '' then do for cupbackconv:
find first cupbackconv no-lock
where cupbackconv.inentity =...
Not sure if this applies to you, but beware that there is a difference between a PASOE dev(elopment) and a PASOE prod(uction) instance.
The dev instance will clean up all sorts of things whereas the prod instance will not, since it starts a singleton - see this article.
Imagine you are able to lock down the .ped files, what are you going to when you find a .ped file with contents:
run mindyourownbusiness.p
Fire the user and hope they did not do anything too malicious?
If you are starting the backup using the Windows Task Scheduler beware that this defaults the task priority to low, killing backup performance even when the system is doing nothing else - see Progress Knowledge Base article P169922
Only SAX supports cdata, see the write-cdata method.
DOM may support cdata, since the create-node method does allow cdata as subtype.
Read-xml and write-xml both do not support cdata, see archived community post, the enhancement request Jens created received four votes and
has status 'Will not...
google:
site:progress.com product availability 9.1e aix
Provides Which versions of OpenEdge are supported against what AIX platform versions, which contains:
I used the OpenSSL manual.
As to which ciphers are actually used when you allow two, I'm not sure if this shows up with logging-level 5.
Maybe this will show in Fiddler.
TLS 1.3 will not work with 11.7.
I think you have two typos in your remaining ciphers:
ECDHE-ECDSA-AES256-GCM-SHA384
ECDHE-ECDSA-AES128-GCM-SHA256
11.7.17 uses OpenSSL 1.1.1q - not sure about 11.7.18 -> proenv
sslc version
You will need to force the Progress client to use these ciphers, the...
You are encoding an unlimited bit length string to a limited bit length space. Why are you surprised? This is a property of all hashes - see Hash collision - Wikipedia - the 16 character length of _password does not help in reducing the chance of hash collision.
It would have been easier if Java 8: Does OpenEdge Support Java8 Runtime for OE11.6? had had a link to How to change the Java version for an OpenEdge installation on Windows.
I've seen this oddity repeated a few times in the knowledge base - it is not true.
Someone seems to have thought that since the format for the _user._password field is x(16), you can only enter a 16 character password. The plain text password is not stored in _password, the encoded password is...
You are aware that OpenEdge 11.7.4 was the first release of 11 for which Windows 2019 server was certified?
You are aware that OpenEdge 11.3 was retired in 2016?
what is in your WebSpeed agent log? I think you will also get an unable to run if for example your code was compiled against a...
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.