PxPlus User Forum

Twitter Twitter Twitter

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - bmohrhardt

Pages: 1 [2]
16
Hello Forum :

           We have some really elderly providex.dde and providex.ddf files, containing a lot
of our Data Defnitions. When I move these files to the backup server that I am testing
Pxplus V. 1510 on, and attempt to go to Dictionary Maintenance, it comes up with an
error, no doubt due to the fact that the format of the .dde & .ddf files has changed.

            Is there a utility or a command that will bring the many records up to the new
format? I have all of my old Mailing List emails on another machine, and I am sure that
the answer is in there!

            Thanks,
            Bill.

17
Thanks, EVa.  ;D The issue was the iptables settings.

One question though, when we are at a 1} prompt in Windx, how
can we quickly execute Shell Commands? In the old character-based
world, it was with a " followed by the command? Do we have to create
our own shortcuts?

18
Hello Forum :

      My apologies if this sounds like a newbie question. I am attempting to setup our backup servers for developing GUI versions of our character-based programs. I have modified the iptables on the CentOS server to accept tcp port 4093, and I have issued the command /0/pxp15/pxplus "*plus/cs/host" -arg "4093;recon=300" and the server answers back : Awaiting connect ... When I issue the lsof -i:4093 command, it shows the process listening. Both the server and the client machine are on the same node, so no firewall is blocking the attempt, and we are not using SSL.

[root@ecoback ~]# lsof -i:4093
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
pxplus  12481 root    5u  IPv4 816627      0t0  TCP *:4093 (LISTEN)
[root@ecoback ~]# iptables -L | grep 4093
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:4093

Then, I attempt to connect from an Ubuntu 16.04 workstation running Wine, from a command window, using :

"/home/prog/.wine/drive_c/PVX Plus Technologies/Windx Plugin 2018 Upd 1/pxplus.exe" *plus/cs/client -arg 192.168.150.6;4093

After a brief pause, the message box comes back stating that it cannot connect to 192.168.150.6 on port 4093, and offers to test
connectivity by browsing th http://192.168.150.6:4093. That does not connect either, but we have never allowed http traffic into
the backup server.  Do I have to specify a startup program? If so, does that program need to be resident on the server, or on the client?

Thanks,
Bill.

19
Programming / Firewall changes to allow Port 4093
« on: March 26, 2019, 06:40:52 PM »
Hello Forum :

        In order to allow remote access to Simple Client/Server, do we have to open up both TCP Port 4093 and UDP Port 4093?
        Also, will the firewall have to forward the connections to the inside server that has the Simple C/S daemon waiting?
        Our set-up is Pxplus 15.10 running on CentOS Linux 5.10.

       Thanks,
       Bill.

20
Programming / Windx screen size.
« on: February 19, 2019, 07:02:11 PM »
Hello Forum :

         With Providex Plus version 15.10 running on our CentOS Linux servers, now
we want to start modifying our character-based programs to GUI. When we install
and run the Windx plugin, version 15.10, and we run it, either on Windows, or on
Linux via Wine, the initial screen size is very small. Is there a parameter somewhere
that allows us to have Windx Connect and use more of the available monitor space?

         For example, my desktop monitor is a widescreen 22" model, and my resolution
is set to 1920 x 1080. When I Maximize the Windx window, the portion of the window
containing the telnet session remains the same. Even if I RUN "*nomads", the GUI window
comes up fine, but remains at the very small size relative to the available space on the monitor.
Is there some setting in an .INI file? The edges of the telnet window do not allow clicking and
dragging.

          Thanks,
          Bill.

21
Programming / Re: ESC key behaviour Providex Plus 15.
« on: February 19, 2019, 06:47:30 PM »
Thanks Eric!

22
Programming / ESC key behaviour Providex Plus 15.
« on: February 14, 2019, 04:52:21 PM »
Hello Forum :

         We have recently installed Pxplus 15 on our CentOS Linux servers.
         All of our programs (still all character-based) are executing properly, so far.
         One odd behaviour is that if a program is sitting at an INPUT statement,
         or even just at a Pxplus prompt, pressing the ESC key, after a brief pause,
         behaves the same as if the user had pressed <Enter>. The program proceeds
         and a CTL value of zero is returned. This did not work exactly the same way in
         Providex 9.10. I checked the manual for System Parameters, but none were 
         specifically related to the ESC key. The keypress does still generate a hex $1B$.

         Is there a way to switch this off? Or is the ESC key needed to exit some GUI routines?

        Thanks,
        Bill.

23
Hello Forum :

After replacing a dedicated Point-to-Point circuit with an ipsec site-to-site route, our RPC files spontaneously close if the user does not touch their Providex session for an hour.
The new connection is using Cisco ASA firewalls, and raw ftp or rsync commands work much faster, as the new connection uses whatever bandwidth is available. However, any files OPENed via the PROCESS SERVER directive still read and write fairly slowly. This likely has to do with the fact that we are still on Providex 9.10. I will execute the same routines on a backup server, where I am testing our code on Providex Plus 14.10. I am certain that improvements were made to Remote Process Control between the 2 versions.

My question is this : Can Providex (or Providex Plus) be configured to allow the RPC OPENed files to remain open? If a user leaves his or her session untouched for a period of time? It almost seems as if the PROCESS SERVER command is getting severed, as any RPC OPENed files will no longer be open, but any local files remain open indefinitely.

Thanks,
Bill.

Pages: 1 [2]