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
Off Topic / Looking for Hardware Support in Reno NV
« on: September 01, 2022, 01:19:08 PM »
Anyone know of of a company in Reno, NV that provides good hardware and network support? I know of a company that is relocating to Reno that is looking for those services. If anyone can recommend someone, please let me know.
2
Programming / Keyed load failure
« on: March 12, 2022, 06:08:38 PM »
I have a 4.5 GB enhanced VLR file that has a corrupt key structure (error 105).
When trying to repair it using the 'keyed load' directive, it fails with this message: "Reception error... Crc Recvd:0FEA... Computed:F3D7". screenshot attached.
I also tried using *UFAR, but the original file says it has 8.8 million records and the restructured file from *UFAR only has 2.4 million records.
This post indicates that *UFAR shouldn't be used on files over 2GB and that *fixvlr should be used instead:
https://forum1.pvxplus.com/index.php?topic=124.new#new
However that utility doesn't exist on my version of PxPlus.
Can the *fixvlr utility be provided to me and if so, will it work on PxPlus 11.65? Is there another way to fix this file?
RHEL 7.6
PxPlus 11.65
Thanks for any help you can provide.
When trying to repair it using the 'keyed load' directive, it fails with this message: "Reception error... Crc Recvd:0FEA... Computed:F3D7". screenshot attached.
I also tried using *UFAR, but the original file says it has 8.8 million records and the restructured file from *UFAR only has 2.4 million records.
This post indicates that *UFAR shouldn't be used on files over 2GB and that *fixvlr should be used instead:
https://forum1.pvxplus.com/index.php?topic=124.new#new
However that utility doesn't exist on my version of PxPlus.
Can the *fixvlr utility be provided to me and if so, will it work on PxPlus 11.65? Is there another way to fix this file?
RHEL 7.6
PxPlus 11.65
Thanks for any help you can provide.
3
Programming / VLR file size limits
« on: February 11, 2021, 07:36:58 PM »
In the manual, both the 'keyed' and 'create table' directives show file size limits for EFF files. Where can I find similar limits for VLR files?
My problem is that I'm getting an error 16 when writing to a VLR file. Current file size is 32 GB and the block size is 4K. I assume 32 GB is the limit for that block size, but would like to confirm that is the problem. I'd also like to know file size limit for different key block sizes so I can pick the right block size for my rebuild.
Pages with file limits for EFF files only (not VLR):
https://manual.pvxplus.com/PXPLUS/directives/keyed.htm
https://manual.pvxplus.com/PXPLUS/directives/create_table.htm
PxPlus 1165 on RHEL 7.6.
My problem is that I'm getting an error 16 when writing to a VLR file. Current file size is 32 GB and the block size is 4K. I assume 32 GB is the limit for that block size, but would like to confirm that is the problem. I'd also like to know file size limit for different key block sizes so I can pick the right block size for my rebuild.
Pages with file limits for EFF files only (not VLR):
https://manual.pvxplus.com/PXPLUS/directives/keyed.htm
https://manual.pvxplus.com/PXPLUS/directives/create_table.htm
PxPlus 1165 on RHEL 7.6.
4
Language / Shared user slots
« on: July 18, 2019, 04:45:34 PM »
From the reference manual, the '1U' parameter says that if the parameter is off, "PxPlus attempts to use shared user slots for the session". Noting the word "attempts", what would prevent PxPlus from being able to share a user slot?
The reason I ask is that I can open 3 code screens and all will be sharing the same user slot.
However, if I try to resize the screens to allow a larger viewable area, they are sometimes assigned a dedicated user slot. It is inconsistent, but happens often enough to cause "User limit exceeded" problems.
Example:
-}?prm('1U')
0
-}?tcb(27)
-17
-}deftty (0)40,15
-}?prm('1U')
1
-}?tcb(27)
10
For some reason, when issuing the deftty directive above, the '1U' parameter gets set and the session is now using a dedicated user slot. Any suggestions on how to prevent this from using a dedicated user slot?
The reason I ask is that I can open 3 code screens and all will be sharing the same user slot.
However, if I try to resize the screens to allow a larger viewable area, they are sometimes assigned a dedicated user slot. It is inconsistent, but happens often enough to cause "User limit exceeded" problems.
Example:
-}?prm('1U')
0
-}?tcb(27)
-17
-}deftty (0)40,15
-}?prm('1U')
1
-}?tcb(27)
10
For some reason, when issuing the deftty directive above, the '1U' parameter gets set and the session is now using a dedicated user slot. Any suggestions on how to prevent this from using a dedicated user slot?
5
ODBC / ODBC Connection string
« on: March 01, 2019, 01:23:53 PM »
I'm trying to create an ODBC connection string that can be used by a third party product to access a couple PxPlus data files.
I have the ODBC server and client setup.
I have been able to successfully extract data from the PXPlus files using Excel with this connection string:
DRIVER={PxPlus® ODBC Driver (32-bit)};Directory=/my_dir/sub_dir/;RemotePVKIOHost=192.168.xxx.xxx
*Note - when using Excel, credentials are tendered in a separate screen, but in the other software, I'm adding ";uid=user" to the connection string (no password).
I also successfully got data using Excel by simply specifying a DSN in the connection string:
DSN=Shipping
However, when using either of the connection strings above in the third party software, it failed.
I have tried variations of the above connection strings with additional keywords, but got similar results... They succeed in Excel, but fail in the other software. They assure me they are simply taking the connection string I provide without any manipulation.
Any ideas why it works with Excel, but not the other software? Is Excel manipulating the connection string I provide?
Server:
RedHat 7.5
PxPlus 11.65
ODBC 5.20
Client
ODBC 5.20
I have the ODBC server and client setup.
I have been able to successfully extract data from the PXPlus files using Excel with this connection string:
DRIVER={PxPlus® ODBC Driver (32-bit)};Directory=/my_dir/sub_dir/;RemotePVKIOHost=192.168.xxx.xxx
*Note - when using Excel, credentials are tendered in a separate screen, but in the other software, I'm adding ";uid=user" to the connection string (no password).
I also successfully got data using Excel by simply specifying a DSN in the connection string:
DSN=Shipping
However, when using either of the connection strings above in the third party software, it failed.
I have tried variations of the above connection strings with additional keywords, but got similar results... They succeed in Excel, but fail in the other software. They assure me they are simply taking the connection string I provide without any manipulation.
Any ideas why it works with Excel, but not the other software? Is Excel manipulating the connection string I provide?
Server:
RedHat 7.5
PxPlus 11.65
ODBC 5.20
Client
ODBC 5.20
Pages: [1]