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.
Pages: [1]
1
Language / Can a PostgreSQL file be opened directly in PxPlus?
« on: February 13, 2020, 02:04:27 PM »
Hello Forum :
If a PostgreSQL file cannot be OPENed directly, are there any plans to add the possibility?
Thanks,
Bill.
If a PostgreSQL file cannot be OPENed directly, are there any plans to add the possibility?
Thanks,
Bill.
2
Programming / Can a Query write its output to a *memory* file?
« on: October 28, 2019, 11:43:22 AM »
Hello Forum :
We are starting to get some of our major files properly defined in the PxPlus Data Dictionary. In so doing, we are beginning to see how powerful and quick that defined Queries can be. Can a defined Query have its output sent to a *memory* file? Thanks, Bill.
We are starting to get some of our major files properly defined in the PxPlus Data Dictionary. In so doing, we are beginning to see how powerful and quick that defined Queries can be. Can a defined Query have its output sent to a *memory* file? Thanks, Bill.
3
Programming / Can a MSGBOX be made to display larger?
« on: September 06, 2019, 12:51:34 PM »
Hello List :
We are moving forward, and testing some NOMADS panels. We use CALLs to the MSGBOX program for a variety of messages. Is there any way to modify the size of the MSGBOX display? We tried padding out the message with spaces, and that does modify the width slightly, until it wraps! It just seems that the MSGBOX displayed is disproportionately small, especially given the typical display size.
Also, the (ahem) aging eyesight of some of us programmers could really use a larger display! We are running Windx 15.10 on Ubuntu 14.04 via Wine.
Thanks,
Bill.
We are moving forward, and testing some NOMADS panels. We use CALLs to the MSGBOX program for a variety of messages. Is there any way to modify the size of the MSGBOX display? We tried padding out the message with spaces, and that does modify the width slightly, until it wraps! It just seems that the MSGBOX displayed is disproportionately small, especially given the typical display size.
Also, the (ahem) aging eyesight of some of us programmers could really use a larger display! We are running Windx 15.10 on Ubuntu 14.04 via Wine.
Thanks,
Bill.
4
Programming / Providex Plus Button return to Nomads panel after CALL directive.
« on: July 29, 2019, 04:17:49 PM »
Hello Forum :
We have a Nomads panel with several buttons. As shown in the attached Button Properties, the button makes a CALL to a program that generates a .pdf of a Packing Slip. When we click on the button, the pdf does get created, but when the program hits the EXIT directive, it does not return to the original panel. Is there a better method to execute a program, and return focus to the original panel?
Thanks,
Bill.
We have a Nomads panel with several buttons. As shown in the attached Button Properties, the button makes a CALL to a program that generates a .pdf of a Packing Slip. When we click on the button, the pdf does get created, but when the program hits the EXIT directive, it does not return to the original panel. Is there a better method to execute a program, and return focus to the original panel?
Thanks,
Bill.
5
Programming / Can the Providex Plus manual be downloaded?
« on: June 12, 2019, 06:43:04 PM »
Hello Forum :
I did a search, but I did not see this question.
Is there a way to download the Providex Plus manual as a pdf?
Thanks,
Bill.
I did a search, but I did not see this question.
Is there a way to download the Providex Plus manual as a pdf?
Thanks,
Bill.
6
Programming / Data Dictionary conversion from old Providex version to Pxplus 15.10
« on: April 19, 2019, 03:34:49 PM »
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.
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.
7
Thin Client/WindX / Is a start-up program required for Simple Client Server?
« on: April 15, 2019, 06:33:51 PM »
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.
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.
8
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.
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.
9
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.
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.
10
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.
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.
11
Programming / rpc dropping connection after dedicated point-to-point replaced.
« on: September 14, 2018, 11:43:23 AM »
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.
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]