Recent posts
#1
Language / Re: DEF ENV and BEGIN
Last post by James Zukowski - May 01, 2026, 05:07:25 PMThat's a good news/bad news situation...
Great that you found it and could fix it. Unfortunately, our company policy it to stay 1 major release back, so we won't be able to use that until next year at the earliest (unless you folks provide another interim release for v22...days before your v23 release...).
Great that you found it and could fix it. Unfortunately, our company policy it to stay 1 major release back, so we won't be able to use that until next year at the earliest (unless you folks provide another interim release for v22...days before your v23 release...).
#2
Language / Re: DEF ENV and BEGIN
Last post by Devon Austen - May 01, 2026, 11:02:09 AMI was able to reproduce the issue on a RHEL9 pxplus running locally (i.e. no windx).
With that I was able to find and fix the issue. The issue only affected linux/unix.
PxPlus 2026 should include the fix.
With that I was able to find and fix the issue. The issue only affected linux/unix.
PxPlus 2026 should include the fix.
#3
General Announcements / PVX Plus April 2026 Update
Last post by PxPlus - April 30, 2026, 03:59:16 PMKeep up to date with what's happening at PVX Plus. Please see our latest newsletter.
April 2026 Newsletter
April 2026 Newsletter
#4
Language / Re: DEF ENV and BEGIN
Last post by James Zukowski - April 30, 2026, 03:03:04 PMThese parameters are set in START_UP and our lead program sequence:
There is no server-side pxplus.ini in use. The Windows-side pxplus.ini file contains:
After exiting to command mode, I entered the statements shown in the previous example.
The PxPlus version has been upgraded to 22.01 and it still produces the same results.
The server is running RHEL 9.7
Client is Windows 11 Enterprise 10.0.26100 Build 26100
Many aspects of the PC are managed by the company. Would there be any restrictions on this behavior coming from there? Would there be any sort of "memory protection" prohibiting this?
Code Select
SET_PARAM 'KF'=2
SET_PARAM '+A'=12
SET_PARAM 'BY'=0
SET_PARAM -'D0'
SET_PARAM 'FF'=3
SET_PARAM 'OP'
SET_PARAM 'XT'=0
SET_PARAM 'F,'
SET_PARAM 'XF'
SET_PARAM 'NE'
SET_PARAM '+M'
SET_PARAM -'SB'
SET_PARAM 'PQ'=PRM('PQ')
EXECUTE "[WDX]SET_PARAM 'TC'=3"
SET_PARAM 'TC'=3
There is no server-side pxplus.ini in use. The Windows-side pxplus.ini file contains:
Code Select
[Font]
Points=19
Charset=0
Name=Lucida Console
[WindowFrame]
TypeSizeLoc=1,902,594,200,131After exiting to command mode, I entered the statements shown in the previous example.
The PxPlus version has been upgraded to 22.01 and it still produces the same results.
The server is running RHEL 9.7
Client is Windows 11 Enterprise 10.0.26100 Build 26100
Many aspects of the PC are managed by the company. Would there be any restrictions on this behavior coming from there? Would there be any sort of "memory protection" prohibiting this?
#5
Language / Re: DEF ENV and BEGIN
Last post by Devon Austen - April 30, 2026, 12:03:31 PMThe code didn't change for this between those versions and I tested with version 22.00.0002 here and the begin did not clear env vars for me.
This means likely there is something in your START_UP or INI file that is different between your test and mine.
What WindX type are you using Simple CS? What host OS are you using?
This means likely there is something in your START_UP or INI file that is different between your test and mine.
What WindX type are you using Simple CS? What host OS are you using?
#6
Language / Re: DEF ENV and BEGIN
Last post by James Zukowski - April 30, 2026, 10:30:37 AMThe screen snip I included is exactly the process I went through. There were no other actions between the steps. This is being launched out of Connection Manager. The v22.01 version should be installed in the next couple of days, so I'll re-test it when it gets here.
#7
Language / Re: DEF ENV and BEGIN
Last post by Devon Austen - April 30, 2026, 10:19:25 AMI just tested in that version via local/windx and win/linux and it never clears it either.
Do you have something in your START_UP that could be causing issues?
From our side we are calling a OS system call to set the env var and only ever call that when DEF ENV() is used. The only way to unset it is to call DEF ENV() again for the same name and with no value. That or close the process.
Maybe some how your system is closing the process?
Do you have something in your START_UP that could be causing issues?
From our side we are calling a OS system call to set the env var and only ever call that when DEF ENV() is used. The only way to unset it is to call DEF ENV() again for the same name and with no value. That or close the process.
Maybe some how your system is closing the process?
#8
Language / Re: DEF ENV and BEGIN
Last post by James Zukowski - April 30, 2026, 10:03:08 AMTested using v22.00.0002
We'll be updating to 22.01 shortly.
We'll be updating to 22.01 shortly.
#9
Language / Re: DEF ENV and BEGIN
Last post by Devon Austen - April 30, 2026, 09:59:45 AMI just tried locally from Windows and Linux and then via WindX to a Windows and Linux server. All maintained the env var after the begin.
I was testing in PxPlus 2025 Update 1.
What version are you running?
I was testing in PxPlus 2025 Update 1.
What version are you running?
#10
Language / Re: DEF ENV and BEGIN
Last post by James Zukowski - April 30, 2026, 09:06:58 AMCould it be a difference between Linux-based and Windows-based systems? I attached what I got with your test.