Please enable JavaScript to view this site.

2021/01/18

 

•Apply Engine (SQDENG): Parser updated to support additional IMS DBD syntax elements defined as metadata for external applications. See the IBM documentation Defining DBD and PSB metadata to the generation utilities

•Apply (SQDENG) and Replicator (SQDRPL) Engines and the sqdutil and sqdmon utilities on Linux making TLS connection to z/OS will fail when the GnuTLS library is not found. They will now report the error and terminate without crashing. A non-standard installation location is the most likely reason the libgnutils.so file cannot be found.
 
The RHEL7 linux distro and default package manager for example, would place it in /usr/lib64:
lrwxrwxrwx  1 root root       20 Jul  8  2020 libgnutls.so -> libgnutls.so.28.43.3
lrwxrwxrwx  1 root root       20 Sep 11  2019 libgnutls.so.28 -> libgnutls.so.28.43.3
-rwxr-xr-x  1 root root  1300504 Mar 14  2019 libgnutls.so.28.43.3
 
In this case the libgnutls.so link is installed in a location included in the 'default library path' : /usr/lib64.
 
If the library has been installed in the wrong location, the following environmental variable can be used but Precisely only recommends doing so in a test environment:
SQDATA_GNUTLS_LIBRARY=<path_To_softlink/>libgnutls.so