PxPlus User Forum

Twitter Twitter Twitter

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.

Messages - Ned L

Pages: [1] 2
Programming / Re: How to disable blink?
« on: November 21, 2019, 05:48:10 PM »
Thanks, Mike!
(No wonder I couldn't figure out how to do it!)

Programming / How to disable blink?
« on: November 19, 2019, 12:37:35 PM »
My application, written in PxPlus (not Nomads) occasionally uses 'BB' and 'EB' to highlight various fields.
Many, many years ago we set 'BB' to appear in red using
   1118 LET TEMP$(17,8)=$0101010101010101$; REM " 'BB' = Red
so these fields both blinked and appeared with red text.

I have a client who likes the red, but doesn't want the text to blink.
Is there a method to globally turn off the blink, without affecting the color?
I've tried
but those aren't accepted.

I've tried
but that seems to make the text disappear completely.

Maybe this is a matter of modifying the terminal driver in *dev
But, frankly, I'm not sure which terminal driver I'm using.
I'm starting PxPlus with
  "\\spsrds\c$\PVX Plus Technologies\PxPlus 2019 Upd 1\pxplus.exe" -NR -SZ=8000  m:\_QAP\CP\OP4MZA"
running on a Windows server.  What determines which terminal emulation setup routine is used?  If I knew that, would it just be a matter of REM'ing out the

Thanks in advance for any assistance you can provide.

ODBC / Re: Was ODBC included in PxPlus Rev 8 Professional?
« on: October 15, 2019, 10:30:23 AM »
Devon -
Thank you for your prompt reply!

ODBC / Was ODBC included in PxPlus Rev 8 Professional?
« on: October 10, 2019, 02:51:54 PM »
Was support for ODBC included in Rev 8 Professional?

I have a client running PxPlus Rev 8 Professional on a Redhat Linux system
There don't seem to be any pvx OBDC drivers installed, perhaps because they didn't need them when the system was originally installed.
Now I'd like to be able to access their pxplus data files using SQL from windows.
Can this be done?  Or do I need to buy newer pxplus licensed for each Windows user that would want to run SQL?

Thanks in advance for your assistance.

Ned Lee, AMS Software

Language / Re: *VIEWER* with SSH
« on: January 17, 2019, 12:30:08 PM »
Eric -
Thanks for hanging in there with me...
The MSGBOX shows the filename as

When I went to /pxplus/lib/_viewer
I saw that software.prm had a timestamp of January 8th and was owned by the Linux account my clients and I log in with, and permissions -rw-rw-rw-.
I tried renaming the file so that line 642 would get an Error 12 and recreate the file. It did, but I'm still getting an Error 99.

I'm at the point that I need to call PxPlus tech support, and will do so. 
But if you have any further ideas, please let me know.
Thank you for your interest and all your assistance!
- Ned

Language / Re: *VIEWER* with SSH
« on: January 16, 2019, 12:48:31 PM »
Eric -
Thank you for your continuing assistance.
Thanks for suggesting the trace.
The problem seems to be in
in the OnCreate: section:
0611 WEND
0612 CADone:
0616 END DEF
0618 OnCreate:
0619 ENTER _._._.FileName$,ERR=*NEXT
0620 IF _._._.FileName$="" THEN LET _._._.FileName$="*usr/applications.prm"
0622 LET _._._.Channel=HFN
0623 OCRetryOpen:
0624 OPEN OBJECT (_._._.Channel,KEY="*PaRaMTr",ERR=OC_OpenErr)_._._.FileName$
0641 OC_OpenErr:
0642 IF ERR=12 THEN {KEYED _._._.FileName$,[1:1:10:"+"],[2:1:32:"C"]+[3:1:96:"C
0653  }
0656 OnDelete:
0657 IF _._._.Channel THEN CLOSE (_._._.Channel)

(Line 0001 indicates the place our error handler is triggered.)
Does the above trace tell you anything?
- Ned

Language / Re: *VIEWER* with SSH
« on: January 16, 2019, 07:25:12 AM »
Eric -
Sorry for the delay in responding, and thank you for your response.
Here's what I get:
PxPlus Type         = Professional
Expiry Date         = none
User Count          = 40
Version Information = 15000002 / Activation Level 15

*****  Activated Packages  *****
20001  Internet Toolkit                 20003  SSL Support
20004  Multiple Image Type Support      20005  Smart Controls
20006  Chart Control                    20007  Customizer
20008  Views                            20010  BBx Keyed File Read
20011  OLE Server                       20012  Report Writer
20013  Thin Client Plug-in              20014  MySQL
20017  Native Oracle Support            20018  Native DB2 Support
20019  ADO Interface to MS Sql          21020  eSignature

*****  Separately Activated Packages  *****
7587   PxPlus Enabled                 Expiry Date=none

*****  Non-Activated Packages  *****
20002  Web Server                       20009  Application Server
20015  XML                              20020  PxServer
20021  MyTiles

Language / Re: *VIEWER* with SSH
« on: January 14, 2019, 02:15:23 PM »
Mike -
Thank you for your patience and ongoing help.
I am still getting
    0134 LET ParametersSoftware=NEW("*viewer/parameters","*viewer/software.prm")
    Error #99: Feature not supported
    Current program is /pxplus/lib/_dev/preview, line 134
when I try to
    OPEN (7) "*VIEWER*"
I am using
"C:\PVX Plus Technologies\Windx Plugin 2018\pxplus.exe"
to start WindX, connection type SSH, port 22

I think I've done everything you've said to do (see below).  The IT guy at the client says he has opened port 20000 fully, and when I do the test program you suggested, he can see traffic on port 20000, followed by a 'random' port opening.

I have done what you suggested, and the test program you suggested now works as you said it would.  (It waits until my browser (on the WindX PC) asks for a connection, and then displays

GET / HTTP/1.1
Accept: application/x-ms-application, image/jpeg, application/xaml+xml, image/gi
f, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd
.ms-powerpoint, application/msword, */*
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/7.
0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C;
Accept-Encoding: gzip, deflate
Host: nn.nn.nn.nn:20000
Connection: Keep-Alive

and stops.

Any further suggestions?)
- Ned

Language / Re: *VIEWER* with SSH
« on: January 14, 2019, 10:53:17 AM »
Mike -
I am still having trouble.
Should the IP address in %PXPLUS_HOST$ be the address of the server, or the IP address of the Windows machine running Windx?  I've tried both, and the IT guy of my client has tried opening the firewall (for tcp) on both systems.

Restating the question:
Assume the the server is IP address and WindX is running on and an available port is 2000.
Should %PXPLUS_HOST$ be
or something else?

Also, if the value should be;2000 (which will be different on each user's WindX) what is an easy way for PxPlus sessions to determine their own IP address?

Thanks for your your help.
- Ned

Language / Re: *VIEWER* with SSH
« on: January 10, 2019, 02:46:25 PM »
Mike -
Thank you for your response!
But I need more guidance.
1) In your example, does 'open up port 20000' refer to specifying a port that the host firewall considers 'open'?  Or is it just 'any' port number?

2) My client has a 40 user license.  It is possible that more than one user will try to use *VIEWER* simultaneously. Can I use a hard-coded port number in the program (which would mean multiple users would use the same port number)?  If not, is there simple way for the PVX program to determine a separate port number for each user and set %PXPLUS_HOST$ appropriately?

Sorry if I'm being dense.   I really do appreciate your help.
- Ned

Language / *VIEWER* with SSH
« on: January 10, 2019, 12:55:54 PM »
I am helping a client move an existing Providex Plus application to a new server.
On the new server, when trying to execute:
   OPEN (7) "*VIEWER*"
they get the following error:

0134 LET ParametersSoftware=NEW("*viewer/parameters","*viewer/software.prm")
Error #99: Feature not supported
   Current program is /pxplus/lib/_dev/preview, line 134

I found a post on this forum "How can I spawn a process when using WindX and SSH" (July 12, 2018)
and based on it, I tried setting
   %PXPLUS_HOST$="*x.x.x.x;22" (where x.x.x.x is the IP address of the server)
but that didn't seem to make any difference.
That same post suggests running *plus/cs/host in the background.  How would I do that? 

They have been running Providex 9.1 On Red Hat Enterprise Linux 5.3
The new system runs Providex 15 on Red Hat Enterprise Linux 7.6

They have been connecting sessions using
"C:\PVX Plus Technologies\Windx Plugin V10\pxplus.exe" WindX
and *VIEWER* has been working with no problems.

Under the new system, they connect using
"C:\PVX Plus Technologies\Windx Plugin 2018\pxplus.exe", with connection type SSH

Is there a way to give them access to *VIEWER* using the SSH connection?
If not, is there a recommended alternate way to connect that WOULD give them access the *VIEWER* ?

Thanks in advance for any assistance.

Ned Lee
QA Solutions Division, AMS Software

Thin Client/WindX / Re: Printing from Application Server
« on: August 22, 2018, 02:16:54 PM »
Mike -
That solved it!
Thank you for your help and expertise. :D

Thin Client/WindX / Re: Printing from Application Server
« on: August 22, 2018, 01:24:41 PM »
New information:
My question has become:
"How do I use WindX with a remote App Server?"
See below for details.

Apparently I'm not running under WindX.  That would explain my problem.
As mentioned earlier, the icon on my local desktop has target

"C:\PVX Plus Technologies\Windx Plugin 2017\pxplus.exe" -mn "*client" -ARG "x.x.x.x" 10020 DMIAPP -ka -ssl

I thought that meant I was running WindX

But now I see that the App Server configuration has, on the Apps tab details:
Client Type: "Any Client Type"

If I change that to "WindX Clients only", then when I try to log in I get
"Your are attempting to connect and run an application which is not able to handle your Client Software.  The application is designed to work with WindX only."
So the above target isn't considered WindX.
I can understand that I need to be using WindX in order to access my local printer.
So my question becomes:
"How do I use WindX with a remote App Server".

Any help or advice would be greatly appreciated.

- Ned Lee

Thin Client/WindX / Re: Printing from Application Server
« on: August 22, 2018, 01:13:13 PM »
James -
Thanks for your time and willingness to help.
- Ned

Thin Client/WindX / Re: Printing from Application Server
« on: August 22, 2018, 12:48:47 PM »
James -
Sorry for the typo in my post.
When I tested your suggestion, I DID use
OPEN (1)"[lcl]*winprt*"
The typo occurred when I was writing my post.  Sorry for causing confusion.  I will be more careful in the future.
I still have the problem:
OPEN (1) "[lcl]*winprt*"
OPEN (1) "[wdx]*winprt*"
both generate
Error #61: Authorization failure
How can I get the system to print to the printer on my desk?

Thanks again for all your help!
- Ned

Pages: [1] 2