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.
1
Language / 'picutre' mnemonic
« on: August 09, 2023, 03:12:45 PM »
Assuming a command like this: print 'picture'(10,10,200,200,"myfile.jpg")
Is there a way to have the image reside on the Windx client? I have tried prefix the file name with windx and a full path - [wdx]c:\images\myfile.jpg, but to no avail. Thanks!
Is there a way to have the image reside on the Windx client? I have tried prefix the file name with windx and a full path - [wdx]c:\images\myfile.jpg, but to no avail. Thanks!
2
Thin Client/WindX / Re: Server to Windx failure
« on: July 31, 2023, 02:53:06 PM »
A final note here. I have no idea why this works, but if I adjust the block size down to 256 bytes when I am transferring from Linux to windows it all works. I had cut down to 1024, and then 512. Both of those failed, so I stopped. Go figure.
3
Thin Client/WindX / Re: Server to Windx failure
« on: July 17, 2023, 03:27:16 PM »
Mike,
I think we got off a little bit. I am trying to read data from a linux file and write it to a local file. I open the linux source; I create and open the windows target. I read the linux file with a block. When I issue the write to the local windows file, it PxPlus dies. The customer provided this grid:
IP OS PVX VERSION
LIVE SERVER 192.168.101.6 Red Hat Enterprise 5.7 514(32 bit)
TEST SERVER 192.168.101.66 Centos 7 771(64 bit)
TEST CLIENT 192.168.101.161 Windows 10 Home 771(64 bit)
What is odd is that if the test client is pointed over to the Centos Server the failure does not occur.
I think we got off a little bit. I am trying to read data from a linux file and write it to a local file. I open the linux source; I create and open the windows target. I read the linux file with a block. When I issue the write to the local windows file, it PxPlus dies. The customer provided this grid:
IP OS PVX VERSION
LIVE SERVER 192.168.101.6 Red Hat Enterprise 5.7 514(32 bit)
TEST SERVER 192.168.101.66 Centos 7 771(64 bit)
TEST CLIENT 192.168.101.161 Windows 10 Home 771(64 bit)
What is odd is that if the test client is pointed over to the Centos Server the failure does not occur.
4
Thin Client/WindX / Windx on a MAC
« on: July 14, 2023, 09:25:19 AM »
Customer wishing to access their PxPlus application running on a windows server from their Mac. Any ideas on solutions here.
5
Thin Client/WindX / Re: Server to Windx failure
« on: July 07, 2023, 10:16:53 AM »
James, Yes, empty file. Mike, I will check on the AV issue; if I can create the file (which I can) doesn't that prove that the directory is writeable?
6
Thin Client/WindX / Re: Server to Windx failure
« on: July 05, 2023, 02:17:43 PM »
I added the error branch on the write record. Providex still dropped out on the write record. So, to be clear, I can create the serial file on the Windx Client machine; I can open the file. As soon as I try a write record of any size (I did create a file and do a write record of the word "test" with no issue) providex exits.
7
Thin Client/WindX / Re: Server to Windx failure
« on: July 05, 2023, 10:22:51 AM »
I verified that the Windx version matches the version of Providex. The instruction that fails is he write record. When I step through that command providex drops. I am trying to re-connect with the customer and see if an error branch will trap an error (I doubt it, but I'm going to try).
8
Thin Client/WindX / Re: Server to Windx failure
« on: July 03, 2023, 04:26:36 PM »
Mike, I *think* you missed the substring on the "this_File$" in the execute command.
9
Thin Client/WindX / Server to Windx failure
« on: June 30, 2023, 10:56:28 AM »
I'm almost embarassed to post this as we are talking pvx 7.7, but here goes. I customer is replacing their Redhat 5.7 server with a new Centos 7 server. PVX seems to run fine, but any time it tries to do certain things via Windx, the session drops. So, this program will cause the issue on the write record:
0010 open (hfn,isz=-1)"/tmp/4586-1.out"; let IN=lfo
0015 let THIS_FILE$="[wdx]c:\infor\jmg.pdf"
0020 execute "[wdx]serial "+$22$+THIS_FILE$(6)+$22$
0025 open lock (hfn,isz=-1)THIS_FILE$; let OUT=lfo
0030 read record (IN,siz=512)XX$
0035 write record (OUT)XX$
If I change the IP address that the Windx client is using to be the old server, everything works. Any insight here would be appreciated.
Thanks! Michael
0010 open (hfn,isz=-1)"/tmp/4586-1.out"; let IN=lfo
0015 let THIS_FILE$="[wdx]c:\infor\jmg.pdf"
0020 execute "[wdx]serial "+$22$+THIS_FILE$(6)+$22$
0025 open lock (hfn,isz=-1)THIS_FILE$; let OUT=lfo
0030 read record (IN,siz=512)XX$
0035 write record (OUT)XX$
If I change the IP address that the Windx client is using to be the old server, everything works. Any insight here would be appreciated.
Thanks! Michael
10
ODBC / Re: ODBC on Redhat
« on: June 09, 2023, 03:17:59 PM »
You are correct sir. Long week I guess. Thanks.
11
ODBC / Re: ODBC on Redhat
« on: June 09, 2023, 03:04:43 PM »
Devon, That was just me being sloppy. /facts93 is a symbolic link to /facts/facts93. In order to eliminate that as the issue I changed everything to be /facts/facts93 in odbc.ini. If I issue the command with -d /facts/facts93 you see the success on the first and a fail on the second.
12
ODBC / ODBC on Redhat
« on: June 09, 2023, 01:19:07 PM »
This is configured for 64 bit on RH 7.9. unixODBC is installed. If I do this:
[root@rhlinux etc]# /usr/pxpsqlodbc/pxpsql -d /facts93 LIST |grep AR_CUST
AR_CUST_BY_ALPHA
AR_CUST_BY_CLASS
AR_CUST_BY_CNTCT
AR_CUST_BY_DOC
AR_CUST_BY_PHONE
AR_CUST_BY_SLSP
AR_CUST_BY_ZIP
AR_CUST_CLASSES
AR_CUST_CLASSES_AKT
AR_CUST_CROSS_REF
AR_CUST_LDGCARDS
AR_CUST_MAST
AR_CUST_PRC_CLS
AR_CUSTOMER_HISTORY
AR_CUSTOMER_NOTES_A
AR_CUSTOMER_NOTES_B
AR_CUSTOMER_NOTES_C
You can see AR_CUST_MAST as a table. Good. Now this:
[root@rhlinux etc]# /usr/pxpsqlodbc/pxpsql -d /facts/facts93 LIST table AR_CUST_MAST
ERROR: Invalid Table Name or No Columns Returned By LIST Columns Command.
Since (think) I know the table name is good, what would cause the column list to fail. Providex.ddf shows the file, and the file has an embedded IO list (as well as an IO program, see attached.
Any insight appreciated. - Michael
[root@rhlinux etc]# /usr/pxpsqlodbc/pxpsql -d /facts93 LIST |grep AR_CUST
AR_CUST_BY_ALPHA
AR_CUST_BY_CLASS
AR_CUST_BY_CNTCT
AR_CUST_BY_DOC
AR_CUST_BY_PHONE
AR_CUST_BY_SLSP
AR_CUST_BY_ZIP
AR_CUST_CLASSES
AR_CUST_CLASSES_AKT
AR_CUST_CROSS_REF
AR_CUST_LDGCARDS
AR_CUST_MAST
AR_CUST_PRC_CLS
AR_CUSTOMER_HISTORY
AR_CUSTOMER_NOTES_A
AR_CUSTOMER_NOTES_B
AR_CUSTOMER_NOTES_C
You can see AR_CUST_MAST as a table. Good. Now this:
[root@rhlinux etc]# /usr/pxpsqlodbc/pxpsql -d /facts/facts93 LIST table AR_CUST_MAST
ERROR: Invalid Table Name or No Columns Returned By LIST Columns Command.
Since (think) I know the table name is good, what would cause the column list to fail. Providex.ddf shows the file, and the file has an embedded IO list (as well as an IO program, see attached.
Any insight appreciated. - Michael
13
Programming / Re: Preview / Viewer Object
« on: April 06, 2023, 04:53:40 PM »
Jeff,
Create a link file using /dev/null on *nix or nul on windows. Use the driver viewer provided with PxPlus.
Michael
Create a link file using /dev/null on *nix or nul on windows. Use the driver viewer provided with PxPlus.
Michael
14
Programming / Strange if then else behavior
« on: March 08, 2023, 09:00:05 AM »
This is an abstraction of a code issue we are seeing:
0005 let mike$="P"
0010 if mike$="P" then {
0015 print "Yes P"
0020 } else if mike$="T" then {
0025 print "Doing T too"
0030 }
If you execute this, you get both outputs when it seems you should not get the "Doing T too". I realize this is not great coding (I didn't write it) but it seems it should work.
0005 let mike$="P"
0010 if mike$="P" then {
0015 print "Yes P"
0020 } else if mike$="T" then {
0025 print "Doing T too"
0030 }
If you execute this, you get both outputs when it seems you should not get the "Doing T too". I realize this is not great coding (I didn't write it) but it seems it should work.
15
Language / TCP/IP address
« on: January 16, 2023, 05:06:04 PM »
Is there anything in the PxPlus environment that stores/returns the IP address of a telnet or raw tcp connection on a *nix box. I can get the value from the telnet login but it is ugly. Same thing with the mac address (parse arp -a).