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.
31
Thin Client/WindX / Re: WindX auto-download and Application Server
« on: December 03, 2020, 04:12:16 AM »
Are you talking about the 'dynamic downloads' (parameter '+U') or the 'static downloads' (sync.conf file) ? I've set up an application server (*appserv/config) and tried both, and they both work.
-Eric-
-Eric-
32
Thin Client/WindX / Re: Can't get Simple CS to work on a new Redhat server
« on: October 13, 2020, 05:09:52 AM »
Loren,
With your OPEN (1)"[tcp];1234;SECURE=/usr/common/cert.cer" & OPEN (2)"[tcp]localhost;1234;SECURE" test, PRINT MSG(-1) when you get an error on the second open. That should tell you why the open isn't working.
-Eric-
With your OPEN (1)"[tcp];1234;SECURE=/usr/common/cert.cer" & OPEN (2)"[tcp]localhost;1234;SECURE" test, PRINT MSG(-1) when you get an error on the second open. That should tell you why the open isn't working.
-Eric-
33
Programming / Re: Question on key padding
« on: September 17, 2020, 03:37:52 AM »
-:/
0010 BEGIN ; LET z$="D:/tmp/eraseme.dat"; ERASE z$,ERR=*NEXT
0020 DIM cfibrec$::"RecordCnt:C(3),Name:C(6),Format:C(1),ExternalKey:C(1),MaxRe
0020:cs:C(3),RecordSize:C(2),KeyedFileFlg:C(1),threshold:C(1),FileType:C(1),Ext
0020:ernalHandle:C(1),Unusedfields:C(4),Path:C(60),KeySegments:C(384)"
0030 KEYED z$,[1:1:4:"K:7F"],0,-256 ! or [1:1:4:"N:xx"]
0040 LET wrk=1; OPEN INPUT (wrk)z$
0050 LET cfibrec$=FIB(wrk); CLOSE (wrk)
0060 PRINT HTA(cfibrec::keysegments$(8,1))
-:run
7F
PxPlus stores what you call the 'null character' for K and N key attributes in that byte.
-Eric-
0010 BEGIN ; LET z$="D:/tmp/eraseme.dat"; ERASE z$,ERR=*NEXT
0020 DIM cfibrec$::"RecordCnt:C(3),Name:C(6),Format:C(1),ExternalKey:C(1),MaxRe
0020:cs:C(3),RecordSize:C(2),KeyedFileFlg:C(1),threshold:C(1),FileType:C(1),Ext
0020:ernalHandle:C(1),Unusedfields:C(4),Path:C(60),KeySegments:C(384)"
0030 KEYED z$,[1:1:4:"K:7F"],0,-256 ! or [1:1:4:"N:xx"]
0040 LET wrk=1; OPEN INPUT (wrk)z$
0050 LET cfibrec$=FIB(wrk); CLOSE (wrk)
0060 PRINT HTA(cfibrec::keysegments$(8,1))
-:run
7F
PxPlus stores what you call the 'null character' for K and N key attributes in that byte.
-Eric-
34
Programming / Re: Question on a structure string
« on: September 17, 2020, 03:21:55 AM »
What do you mean by "This does not work" - are you getting an error or does cfibrec$ remain empty or ... ?
-Eric-
-Eric-
35
Nomads / Re: Determine previous control that had focus?
« on: September 16, 2020, 11:01:45 AM »
You can make that button a 'signal only' button so the focus doesn't change. And you can check MSE - position 25,2 contains the object that lost focus.
-Eric-
-Eric-
36
Nomads / Re: h-scrollbar in listbox
« on: May 07, 2020, 03:12:43 AM »
Thomas,
As far as I know, a standard listbox doesn't have that capability. When you create a window with scrollbars and you use the scrollbar(s), all controls with 'scrolling enabled' will also move - that's what the 'enable scrolling' setting does.
-Eric-
As far as I know, a standard listbox doesn't have that capability. When you create a window with scrollbars and you use the scrollbar(s), all controls with 'scrolling enabled' will also move - that's what the 'enable scrolling' setting does.
-Eric-
37
Thin Client/WindX / Re: Does ObjectID user object function over WindX?
« on: May 06, 2020, 05:30:44 AM »
Jeff,
It will probably work when your custom object exists on the WindX PC (or is accessible from the WindX PC) and you change line 40 to:
LET O=NEW("[LCL]{path}myGrid",X)
where {path} is optional (and a true path).
-Eric-
It will probably work when your custom object exists on the WindX PC (or is accessible from the WindX PC) and you change line 40 to:
LET O=NEW("[LCL]{path}myGrid",X)
where {path} is optional (and a true path).
-Eric-
38
Thin Client/WindX / Re: pxp 1600 and Windx Licensing
« on: May 16, 2019, 04:23:27 AM »
There's something not quite right - I installed the Plugin v16 and connected through SSH with our server. I can start pxplus as xterm without a problem, but when using ansi or winterm, this happens (I added SETTRACE RECORD PGN to ansi/winterm/tty and start.up and created a pvxtrace.log prior to starting PxPlus):
export TERM=ansi
`pwd`/pxplus console.pgm
console.pgm executes this code:
0010 ! console.pgm
0020 SETTRACE RECORD PGN
0030 SET_PARAM 'XT'=0
0040 PRINT "In console mode"
0050 STOP
WindX simply disappears and pvxtrace.log then contains this:
[admin@mail pxplus]$ cat pvxtrace.log
May 16 10:14 [*dev/ansi:25] /apps/pxplus/lib/_dev/ansi
May 16 10:14 [*dev/winterm:15] /apps/pxplus/lib/_dev/winterm
May 16 10:14 [*start.up:25] /apps/pxplus/lib/_start.up
May 16 10:14 [console.pgm:20] /apps/pxplus/console.pgm
May 16 10:14 [console.pgm:40] Sighup received
May 16 10:14 [console.pgm:40] Sighup received - Forcing Auto exit
May 16 10:14 [console.pgm:40] Post SIGHUP read error: count=1
May 16 10:14 [console.pgm:40] Read stdin error count exceeded - Forcing Auto exit
May 16 10:14 [console.pgm:40] Post SIGHUP read error: count=2
May 16 10:14 [console.pgm:40] Read stdin error count exceeded - Forcing Auto exit
May 16 10:14 [<noprog>:65000] Post SIGHUP read error: count=3
May 16 10:14 [<noprog>:65000] Read stdin error count exceeded - Forcing Auto exit
May 16 10:14 [<noprog>:65000] Post SIGHUP read error: count=4
May 16 10:14 [<noprog>:65000] Read stdin error count exceeded - Forcing Auto exit
export TERM=ansi
`pwd`/pxplus console.pgm
console.pgm executes this code:
0010 ! console.pgm
0020 SETTRACE RECORD PGN
0030 SET_PARAM 'XT'=0
0040 PRINT "In console mode"
0050 STOP
WindX simply disappears and pvxtrace.log then contains this:
[admin@mail pxplus]$ cat pvxtrace.log
May 16 10:14 [*dev/ansi:25] /apps/pxplus/lib/_dev/ansi
May 16 10:14 [*dev/winterm:15] /apps/pxplus/lib/_dev/winterm
May 16 10:14 [*start.up:25] /apps/pxplus/lib/_start.up
May 16 10:14 [console.pgm:20] /apps/pxplus/console.pgm
May 16 10:14 [console.pgm:40] Sighup received
May 16 10:14 [console.pgm:40] Sighup received - Forcing Auto exit
May 16 10:14 [console.pgm:40] Post SIGHUP read error: count=1
May 16 10:14 [console.pgm:40] Read stdin error count exceeded - Forcing Auto exit
May 16 10:14 [console.pgm:40] Post SIGHUP read error: count=2
May 16 10:14 [console.pgm:40] Read stdin error count exceeded - Forcing Auto exit
May 16 10:14 [<noprog>:65000] Post SIGHUP read error: count=3
May 16 10:14 [<noprog>:65000] Read stdin error count exceeded - Forcing Auto exit
May 16 10:14 [<noprog>:65000] Post SIGHUP read error: count=4
May 16 10:14 [<noprog>:65000] Read stdin error count exceeded - Forcing Auto exit
39
Web Services / Re: *web/email not working with PxPlus Webserver
« on: April 25, 2019, 09:13:47 AM »
The error message indicates that a simple open of "[tcp]unc-address;25" doesn't work (or "[tcp]unc-address;25;secure" if you specified -secure) and results in an error 0. Can you create a simple web program that tries to do that open ?
40
Programming / Re: error 0 while applying journal files
« on: April 24, 2019, 03:43:51 AM »
Can you check if TCB(87) contains any valid information when the error 0 happens ?
41
Thin Client/WindX / Re: Is a start-up program required for Simple Client Server?
« on: April 19, 2019, 05:35:31 AM »
ls should work in console mode (at the -} prompt) without the need for " as it's a user command (stored in lib/_cmd{/system}).
If you need other ones, this logic should work:
0010 OPEN INPUT (1)"<command" ! for example "<ps -ax"
0020 WHILE 1; READ (1,ERR=*BREAK)O$; PRINT O$; WEND
0030 CLOSE (1)
You can create a user command to execute shell commands, for example:
0010 ! do - execute Linux commands
0020 ENTER COMMAND$,ERR=*NEXT
0030 LET COMMAND$=STP(COMMAND$,2); IF COMMAND$="" THEN EXIT
0040 LET CHAN=UNT; OPEN INPUT (CHAN)"<"+COMMAND$
0050 WHILE 1; READ (CHAN,ERR=*BREAK)OUT$; PRINT OUT$; WEND
0060 CLOSE (CHAN); EXIT
-;save"*cmd/do"
/pxplus/lib/_cmd/do
-}do ps ax|grep pxp
3351 ? Ss 0:00 /pxplus/pxplus /pxplus/pxplus.ini -id=T0 -port=4093 *plus/cs/host;ChkRun;2019-02-28 07:46;56 -arg 4093 /pxplus/web/check.pxp
3420 ? S 0:00 /bin/sh -c ps ax|grep pxp
3422 ? S 0:00 grep pxp
-}
If you need other ones, this logic should work:
0010 OPEN INPUT (1)"<command" ! for example "<ps -ax"
0020 WHILE 1; READ (1,ERR=*BREAK)O$; PRINT O$; WEND
0030 CLOSE (1)
You can create a user command to execute shell commands, for example:
0010 ! do - execute Linux commands
0020 ENTER COMMAND$,ERR=*NEXT
0030 LET COMMAND$=STP(COMMAND$,2); IF COMMAND$="" THEN EXIT
0040 LET CHAN=UNT; OPEN INPUT (CHAN)"<"+COMMAND$
0050 WHILE 1; READ (CHAN,ERR=*BREAK)OUT$; PRINT OUT$; WEND
0060 CLOSE (CHAN); EXIT
-;save"*cmd/do"
/pxplus/lib/_cmd/do
-}do ps ax|grep pxp
3351 ? Ss 0:00 /pxplus/pxplus /pxplus/pxplus.ini -id=T0 -port=4093 *plus/cs/host;ChkRun;2019-02-28 07:46;56 -arg 4093 /pxplus/web/check.pxp
3420 ? S 0:00 /bin/sh -c ps ax|grep pxp
3422 ? S 0:00 grep pxp
-}
42
Thin Client/WindX / Re: Is a start-up program required for Simple Client Server?
« on: April 16, 2019, 03:32:11 AM »
You don't need a start-up program for the Simple Client/Server. When testing the connection with a browser, this should appear:
PxPlus CS Host server active
Please connect to this port using CS Client
Your workstation address is ::ffff:xxx.xxx.xxx.xxx
Server has been up since YYYY-MM-DD HH:mm and processed x requests
If that doesn't appear, the host isn't started correctly or the client is unable to reach the host. In your case, I would simply start PxPlus as 'root' on the host and in console mode, enter RUN "*plus/cs/host". The 'Awaiting connect' message should appear. You can test if the host is started correctly by connecting with a browser on the host machine (http://127.0.0.1:4093).
Then try a browser on the client machine (http://host_ip:4093). This must work before trying to connect with *plus/cs/client.
PxPlus CS Host server active
Please connect to this port using CS Client
Your workstation address is ::ffff:xxx.xxx.xxx.xxx
Server has been up since YYYY-MM-DD HH:mm and processed x requests
If that doesn't appear, the host isn't started correctly or the client is unable to reach the host. In your case, I would simply start PxPlus as 'root' on the host and in console mode, enter RUN "*plus/cs/host". The 'Awaiting connect' message should appear. You can test if the host is started correctly by connecting with a browser on the host machine (http://127.0.0.1:4093).
Then try a browser on the client machine (http://host_ip:4093). This must work before trying to connect with *plus/cs/client.
43
Programming / Re: Program Caching
« on: April 16, 2019, 03:23:24 AM »
Don't ADDR programs that you are going to edit ?
44
Language / Re: 'CURSOR' Unchanged
« on: April 03, 2019, 05:39:35 AM »
Have you set parameter IM ? If you did, disable it: SET_PARAM 'IM'=0 .
45
Web Services / Re: pxplus webserver automatically start
« on: March 21, 2019, 05:01:40 AM »
It's a Microsoft group in the Microsoft Start menu. When running Windows 10, I believe it's located here: C:\Users\{Username}\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup .