PxPlus 2022 Update 1 is now available.  This update includes a number of minor correction and provides the following language enhancements:

New/Enhanced Features

• Added 'OnDoubleClick property to multi_line inputs
• Webster+ Desktop interface presents Webster pages in Windows window
• Added hdrclass=xxx option to define Webster grid header
• Numerous improvements to the File Maintenance generator
• Enhanced WEB IDE capabilities

---

Additional information can be found at https://manual.pvxplus.com/?/pxplus/vers1910.htm
Product downloads available at https://home.pvxplus.com/pgsrvr.pvp?pg=dl_pxp1910

PxPlus 2021 Update 2 is an update release that includes the enhancements below and a number of small fixes that have been developed since the initial update of PxPlus 2021.

Enhancements

• Added support to the *BROWSER object to enable a "Find" hot-key that will open a Find dialog to search text on the displayed Web page
  • Also added a new Find button to the Enhanced IDE for searching text on the displayed IDE Web page
• Ability to access the PVX Plus Helpdesk Support system from the menu in the Windows-based and Web-based IDE
• New parameter for the *TOOLS/MAKEQRCODE utility to indicate the quality of the QR code to be returned
• New allowScripts property added to the TinyMCE® object to allow editing of HTML with JavaScript
• Improved the performance of the *plus/web/request when host returns "chunked" data
• Addressed numeric overflows in the "*winapi;getdiskfreespace" routine on large drives
• Resolved issue with spinner control when application clears input queue
• Corrected OPEN TIM= setting on TCP connections to properly adhere to timeout value specified

Downloads are now available at https://home.pvxplus.com/pgsrvr.pvp?pg=dl_pxp1820

PxPlus 2021 Update 1 is an update release that includes the enhancements below and a number of small fixes that have been developed since the initial release of PxPlus 2021.

Enhancements

• Webster+ Enhancements
  • New program and HTML editor through the Inspector interface
    
  • Added support for Drop style queries
    
  • New Run-time Report Writer filters
    
• Enhanced Auto Advance folder option
  
• New directory copy utility
  
• Improved screen copy functionality to suppress trailing CR/LF
  

Downloads are now available at https://home.pvxplus.com/pgsrvr.pvp?pg=dl_pxp1810

Unfortunately due to an issue at the hosting service we use for this forum it's database had to be restored to the backup from last night (March 31st at 2AM).

As a result of this, postings made between 2AM and 4PM March 31 have been lost.

For PxPlus 2020 we are looking to eliminate some of the older Linux builds while we add new ones such as Redhat/Centos 8.

Please take a moment to indicate in this poll which of these legacy systems you still actively sell/install and that may require PxPlus 2020.
Indicate None of the above if you don't use any of these versions so we can get a idea of how many people actually voted.

Note that most of these are no longer supported by their respective manufacturer and on some there are limitations as to what we can both provide and support.

As always we strongly encourage clients to stay current both with PxPlus and your respective Operating Systems.

If you need one machine to run PxPlus with multiple licenses, it’s actually quite easy to setup. 

Here's a typical scenario:

A company has purchased licenses for its two branch operation; a ten user license for the system in Montreal and a twenty user license for the system in Toronto.  Management now decides that instead of having two servers they want to consolidate the branch operation onto a single server in the cloud.

Technically you can simply install two copies of PxPlus in separate locations and run them on different ports and this is the preferred and most straightforward approach. 

This does however mean that when upgrading the software you would have to upgrade both instances.  If you wish to share a single install between multiple license, the following technique can be used to accomplish this.

This technique involves having multiple license files on the system and pointing different instances of PxPlus to the different license files by setting the PVXKEY environment variable prior to running PxPlus or any of its utility programs, such as product registration.

---

Unix/Linux Setup

Here is a small Linux shell script that can be used to make it simple to accomplish this:

• #!/bin/bash
  lic=$PWD/lic_$1
  [ ! -d "lic_$1" ] && mkdir "$lic"
  export PVXKEY=$lic
  shift
  $@

Take the above script and place it in your PxPlus install directory in a file called 'usekey', then set execute permission on this file using the following command:

• chmod a+x ./usekey

What this script does is allow you to specify the license to use when launching pxplus or the registration program pxpreg.  It creates a sub-directory "lic_XXXX" to hold the license if it doesn't already exist, then sets the PVXKEY environment variable to point to that directory.

So taking our example, to enter the activation key for Montreal we could enter the following:

• ./usekey MTL ./pxpreg

This would create a sub-directory called lic_MTL and run ./pxpreg against it allowing you to enter the license keys.

For Toronto you could enter:

• ./usekey TOR ./pxpreg

To run the online registration the commands would be:

• ./usekey MTL ./pxplus "*plus/reg/net"
• ./usekey TOR ./pxplus "*plus/reg/net"

Once you have the keys setup you can use the same script to run the Simple CS interface for each of the branches:

For Montreal to allow user to connect to port 4093:

• ./usekey MTL ./pxplus "*plus/cs/host" -arg 4093

For Toronto to allow user to connect to port 10000:

• ./usekey TOR ./pxplus "*plus/cs/host" -arg 10000

This approach can be extended to allow any number of different types of licenses to be run from the same install.

---

Windows Setup

You can setup a similar script on Windows as a .BAT file.  It would look something like this:

• @ECHO OFF
  SETLOCAL
  SET lic=%CD%\lic_%1
  IF NOT EXIST "%lic%" MKDIR "%lic%"
  SET PVXKEY=%lic%
  %2 %3 %4 %5 %6 %7
  

Take the above script and place it in your PxPlus install directory in a file called ‘usekey.bat’.

Now you can use this BAT file to register and launch PxPlus using different licenses on Windows.

To enter the installation key for Montreal (MTL) we could go to the Windows command line, change your directory to where you have your PxPlus installed and enter the following:

• usekey.bat MTL .\pxpwactv

This will run the activation key entry program for PxPlus with the resultant activation key going to the directory lic_MTL in the install directory.

To enter the key for Toronto (TOR) the command would be:

• usekey.bat TOR .\pxpwactv.exe

To run the online registration the commands would be:

• usekey.bat MTL .\pxplus "*plus/reg/net"
• usekey.bat TOR .\pxplus "*plus/reg/net"

In order to run PxPlus using the MTL key you could enter the command:

• usekey.bat MTL .\pxplus.exe "*plus/cs/host" -arg 4093

For Windows you may want to create a desktop shortcut link for this.  Your shortcut would have the command with the starting directory being where PxPlus is installed.

Note: Should you not want the license files in the directory where PxPlus was installed or if you want to run your application in a different directory, you can provide a full pathname to the pxplus.exe and change the usrkey.bat file so that 'lic' points to where you want to save the license file(s).

On Linux, if you are finding you are having trouble connecting to a secure server using TCP, it may be because the system is not able to find the OpenSSL system libraries.  This can manifest itself in having problems running the online registration process, getting updates, or any form of network/internet request using a secure connection.

The easiest way to test if the libraries can be found is to try and open a secure connection to the target system or to any Internet server,   To do this simply issue the following command from the PxPlus command line:

OPEN (1) "[tcp]www.pvxplus.com;443;secure"

If the libraries are not found you will get the following error:

Error #13: File access mode invalid
Last IO to [tcp]www.pvxplus.com;443;secure, channel 1
Unable to locate SSL library (ssleay or libssl) (err/ret=9/9)

This indicates the OpenSSL libraries cannot be found, however on most Linux system they do exist but the OS may not have created the proper linkage to the version of OpenSSL you are running.   The library files often are suffixed with the specific version of OpenSSL being used and for PxPlus to use them, it needs a link to the correct library.

Since we ship a 'generic' version of PxPlus for multiple versions of Linux, we use generic names (without the version number) in the SSL interface. Most Linux systems include these by default, but some don't so you have to define which OpenSSL library version to use. 

NOTE: Because OpenSSL changes regularly many Linux distros already have these generic links defined so they
can change when a new version comes out without having to re-compile all applications.

If the generic link does not exist, you can fix this by first finding the installed SSL libraries (libssl.so and libcrypto.so) on your Linux server.  Generally they will be in one of the following locations:

• 32 bit systems: /lib -or- /usr/lib
• 64 bit systems: /lib64 -or- /usr/lib64
  

To find which libraries are installed you can use the OS 'ls' command as in:

ls -l /usr/lib/libssl*

This will display something like:

-rwxr-xr-x 1 root root 470376 Aug 8 21:38 /usr/lib/libssl.so.1.0.2k

This indicates that you have version 1.0.2k of the OpenSSL libraries installed.

In order for PxPlus to find this library you need to create a symbolic link within the system library files to the .so file.  This can be done as follows:

ln -s /lib/libssl.so.1.0.2k /lib/libssl.so
ln -s /lib/libcrypto.so.1.0.2k /lib/libcrypto.so

To give you an idea of what this will look like, here is the 'ls' of a Centos 7 library directory:

[root@v1153828 ~]# ls -la /usr/lib64/libssl*
-rwxr-xr-x 1 root root 370584 Aug 12 11:55 /usr/lib64/libssl3.so
lrwxrwxrwx 1 root root     16 Sep 18 00:49 /usr/lib64/libssl.so -> libssl.so.1.0.2k
lrwxrwxrwx 1 root root     16 Sep 18 00:47 /usr/lib64/libssl.so.10 -> libssl.so.1.0.2k
-rwxr-xr-x 1 root root 470376 Aug  8 21:38 /usr/lib64/libssl.so.1.0.2k

You can see it is set to use OpenSSL version 1.0.2k