PxPlus User Forum

Twitter Twitter Twitter

Recent Posts

Pages: [1] 2 3 ... 10
Programming / Re: client time
« Last post by David Reynolds on Today at 10:23:45 AM »
I'm not sure if there's a Windows equivalent, but on Linux we use something like this...

Each user is assigned a location, and each location is assigned a time zone (matching those in /usr/share/zoneinfo)
So for local time we just issue:

Code: [Select]
READ RECORD("| TZ="+TZ$+" date +%Y%m%d%H%M%S")USERTIME$

Code: [Select]
TZ$="Canada/Pacific" ! or Canada/Mountain or Canada/Central or America/Toronto or Greenwich etc
Programming / Re: client time
« Last post by Devon Austen on Today at 09:32:30 AM »
I missed that you were not using Windx but RDP. What I suggested would only work if you are using WindX.

Mike is right that there is no easy way to get the client time when everything is running on the server except the RDP client.
Programming / Re: client time
« Last post by Mike King on Today at 09:18:59 AM »
Since you are using RDP and not WindX I don't know of anyway to find the users true workstation time zone.  When you connect using RDP the processes all run on your server and all the workstation does is handle display/input.  There is no real way to run anything locally to determine the time zone.

Now there may be an Windows API you could call in the windows WTS library ( https://docs.microsoft.com/en-us/windows/desktop/api/Wtsapi32/ ) but I did a quick look and couldn't see anything that would provide you what you are looking for.
Programming / Re: *web/email is very slow
« Last post by Mike King on Today at 09:09:35 AM »
What I might suggest is try passing an smtp server an invalid userid/password and time how long it takes for the error to be returned. This will allow you to get a feel as to if the system is taking a long time generate your email for sending or if the smtp server is taking a long to process it.

Generally a bad userid/password should disconnect quickly so if this time is fast but with a valid userid/password it likely the mail server itself is slow.

Also if you have a different mail server (perhaps a gmail account or your own in-house server) I would try that as a test to see if that is faster so you determine where the issue may be.
Programming / Re: Windx cannot find Server
« Last post by Mike King on Today at 09:03:30 AM »
How is the user connecting to the Linux server (Simple CS, SSH, Telnet, App Server, NtSlave)?

This error indicates the user started WindX but did not successfully run PxPlus within the first few minutes in order to obtain the license.  If they are using Telnet or SSH this can happen if once they connect they take their time starting PxPlus.  It can also happen also when using SSH or Telnet on very slow machines or connections if once the terminal type is set to ANSI. 

Generally for WindX you should set the terminal type to "winterm" however we do have logic in the Ansi terminal driver to try and detect if the workstation really is WindX.  This is done by sending a message to the terminal to which only WindX will respond.  If the expected response is not received then we assume the terminal is truly and ANSI terminal.
Programming / Re: Windx cannot find Server
« Last post by Devon Austen on Today at 08:54:27 AM »
I would check the Windows firewall on that machine.

I would also look into the antivirus/internet security software that machine is running.

I hope that helps.
Programming / Re: client time
« Last post by Devon Austen on Today at 08:51:10 AM »
Have you tried:

Code: [Select]
EXECUTE "[WDX]dte(0:"%hz:%mz %P")"
or if the code also needs to run not on windx

Code: [Select]
EXECUTE "[LCL]dte(0:"%hz:%mz %P")"
Programming / Windx cannot find Server
« Last post by Lawrence_Leavell on Today at 12:30:03 AM »
I have a Windx operator on Windows 10, cable connected to the Linux server using two monitors. Occasionally, the Windx side stops "Unable to acquire license from server in time allowed." In an office with 30+ users, this is the ONLY operator and workstation to experience this issue. We have restrung the cable, changed switches and routers, can find nothing to correct this error.
Can anyone offer a suggestion how to fix this, where to look?
Programming / Re: *web/email is very slow
« Last post by Mike Hatfield on September 19, 2018, 11:08:13 PM »
I put a TRM() round the call email form program in our invoice print program.
It averages 5-6 seconds from calling the email format program which in turn calls *web/email until it returns to the invoice rpint program.
We use smtp2go for a lot of email both for ourselves and end users.
Their servers are quite fast. Perhaps as you say it is the sender/recipient verification that is taking the time.
I can send you the email formatting send program and attachments if you think it would cast some light.
This also might help diagnose why *web/email is not receiving the sent status so it can remove the .eml file from the outlook/new folder.
Programming / client time
« Last post by John DeStefano on September 19, 2018, 05:13:52 PM »
Hi all,

We are using the function dte(0) to print the time on some forms and reports.  We also use it to capture and record events in data files.

e.g.  dte(0:"%hz:%mz %P")

We have a customer that has locations in multiple time zones.  The dte(0) function uses the server time.  We have users logged into the server with their client in a different time zone.

Is there a function that will return the client time and not the server time?

We are using PXPlus 13.10 running on a Windows Server 2012 and we are not using WINDX. Users connect to the server using an RDP connection.

Pages: [1] 2 3 ... 10