PxPlus User Forum

Twitter Twitter Twitter

Recent Posts

Pages: [1] 2 3 ... 10
Programming / Re: PXPlus crashing after error 61
« Last post by Mike King on February 21, 2024, 07:48:30 PM »
Glad its been resolved. 

Over the years I have seen a variety of weird OS compatibility issues so I always suggest you run a version of PxPlus compiled and tested AFTER the release date of any OS.  In your case, while v12.50 may have started and appeared to run on Redhat 7, it was compiled and tested on Redhat 6.
Programming / Re: PXPlus crashing after error 61
« Last post by Loren Doornek on February 21, 2024, 07:08:30 PM »
As a followup, updating the client to PXPlus version 17 resolved the issue - we haven't seen any crashes since the update. 

Thanks, Mike, for your detailed explanation of the versions available for the OS release, and thanks to James and Jason for the debugging suggestions!
Programming / Re: Sign XML Documents with Digital Signatures
« Last post by Loren Doornek on February 21, 2024, 07:03:17 PM »
Here's a simple example of creating a signature hash for an XML document, based on a Wikipedia example.  But, this only creates the signature and does not encrypt the signature data using RSA, which is what the XML signing requires.  To complete the process, you would need to finish building the required XML (most of which was included in your example in the <Signature> segment), and then create an RSA-encrypted signature value for that segment.  I don't know of any method of using RSA encryption directly within PXPlus, but maybe Mike can comment on that.  Mikes suggestion of using the XMLSEC utility might be the only method of handling the RSA part.

0010 BEGIN
0020 LET inv$=XML(ADD "Marge Simpson" TO inv$,KEY="Client")
0030 LET inv$=XML(ADD "847.63" TO inv$,KEY="Amount")
0040 LET inv$=XML(ADD inv$ TO $$,KEY="Invoice")
0050 LET sig$=CVS(HSH(inv$,256),"ASCII:BASE64")
0060 LET xml$=XML(ADD sig$ TO inv$,KEY="Signature",OPT="xmlns=""http://www.w3.org/2000/09/xmldsig#""")
0070 PRINT xml$

 <Client>Marge Simpson</Client>
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">G9Q1/Lu96dgOVNd3ZChqZLCBUDgIPuAivTwVIngey2U=</Signature>
ODBC / Re: ODBC output from UPS Worldship
« Last post by Devon Austen on February 21, 2024, 10:30:45 AM »
I am not sure what application you are using that is interfacing with the PxPlus ODBC driver, so I can only make guesses.

It seems it is generating a insert with parameters to allow users to specify the insert values.

I don't know if that is supported for insert and update.

I tested a similar INSERT here with a newer version and I get a parameter missing error or a parameter not supported error when I try it not the errors you report.

Maybe prevent the ODBC client application from using parameters for this insert and have it specify the values if possible.

ODBC / Re: Serius I complete missing undesrtand odbc
« Last post by Mike King on February 21, 2024, 08:00:11 AM »
Edias is correct.  This appears to be the ProvideX ODBC driver as sold and supported by Sage with their MAS90 accounting package. 

If the issues you are having are relative accessing MAS90 data you should contact Sage for assistance as their ODBC driver is different than the drivers for PxPlus.
ODBC / Re: Serius I complete missing undesrtand odbc
« Last post by EVa on February 21, 2024, 03:06:40 AM »
For starters, you could enable debugging to see if there's a difference the 1st and 2nd time you connect.  Also, this appears to be a rather old version of the ODBC driver as it says 'ProvideX' in the title bar ?
ODBC / ODBC output from UPS Worldship
« Last post by dalem on February 20, 2024, 05:16:49 PM »
Any help or insight into this is appreciated!
on the off-chance the ( ?, ?, ?, ?, ?, ?, ?) in the error refers to UPS not being able to find it's own fields linked to ours in a writable PX+ file, I went in and re-did the mapping to make sure.

using 32 byte version of both ups & px+ odbc 5.2. Since the only similar error was responded with "why such an old version", its more of a decision above me.

This is the px+ driver log from the ODbc. The attached picture is what the UPS software and/or driver pops up with.
\\mcvan-app01\E\Share\CSV_FILES\UPS_EXPORT\UPS_EXPORT.ini , available 3 table(s)
ISAMCloseTable: Closing table UPS_EXPORT1 - 0 file reads, 0 re-reads, 0 writes, 0 removes
     CACHE STATS - 0 reads, size 9216 estimated, 0 used
Driver version: 5.20.0000
ISAMOpen: UserID='cai-support', length=11
ISAMOpen: Trying to access the server using UserID='cai-support', Company=''

ISAMClose: <3> S0000 S0000 [PxPlus][ODBC Driver][FILEIO]Not supported
Programming / Re: Sign XML Documents with Digital Signatures
« Last post by HendersonS on February 20, 2024, 04:47:02 PM »
Thanks Mike for your instructions.

If I understood correctly, you mean that I can invoke this tool from pxplus? And just in case I take another route to do it with pxplus, is there any utility to extract the private key from a .pem?
ODBC / Re: slowing down an ODBC query
« Last post by Jeffrey Ferreira on February 20, 2024, 04:22:11 PM »
Thank you Devon. i will ask the customer if they would be partial to the Dirty Read.
ODBC / Re: slowing down an ODBC query
« Last post by Devon Austen on February 20, 2024, 03:29:31 PM »
The PxPlus SQL ODBC driver has some options that may help.

Goto the Options tab of the DSN setup page for the PxPlus ODBC client install. There you will find two options that may help.

Dirty Read - Check box for Dirty Read mode of operation to skip the normal file consistency checks.

                   Dirty reads can speed file processing by reducing the number of locks issued against a file. However, this may result in inconsistent data should the file be updated while being read by
                   the PxPlus SQL ODBC Driver.

Burst mode - Check box to enable Burst mode. This helps reduce some of the overhead created by temporary locks.

                      With Burst mode set, the PxPlus SQL ODBC Driver locks the file header for either 50 file operations or three-tenths of a second, whichever occurs first. This decreases the number of
                      times the file must be locked and the number of times that internal buffers may need to be reloaded. Refer to the next paragraph below for an explanation on the effect of temporary

I suspect dirty reads may be of the most help to you.
Pages: [1] 2 3 ... 10