Thanks James - I've been trying to get a server license moved.  Sent the request in on Saturday, expected something yesterday (Tuesday), but no joy.

Regards

Dave Fullerton

Hi folks:

I am just wondering if the derecho storm that hit Ontario over the weekend has impacted Pvx+'s ability to reply to support ticket requests.  Does anyone know if they are operational?

Regards

Dave Fullerton

Hi Mike:

Thanks for the link - I will pass it on.  I had mentioned to their IT support that this might be a reason, but they didn't know anything about the setting.   I checked the status of the drives in File Explorer, and did not see the red X that usually indicates the disabled drive, and the drive was being used pretty regularly (or so I'm told), but hopefully this link will remove that issue from the equation.

Dave

Hi Devon:

The problem is, that the errors seem to happen in *winproc, where I don't have a lot of control, and one of them wasn't associated with a Read.  I could suggest moving to client/server, but they will be winding down use of our application in the next seven months, so that really isn't an option.  As far as retries are concerned, I have tried going back to the statement to re-execute it, without success. 

Before this server change, the application was running quite well for over a decade without issue.

Thanks for the input - I am hoping that their tweaks (which seem to take an inordinate amount of time) will work.  If not, I may need to get them to go to WindX.

Dave

Hi John:

We use this in our menu to spawn new sessions

4145 call "*windx.utl;spawn",quo+local_dir$+"parms"+fid(0)+".txt"+quo,"",fid(0)

The txt file is treated as a program.

Hope this helps.

Regards

Dave Fullerton

Hi folks:

We have a client that has just changed their servers and configuration.  The user workstations are UserVMs: Windows 10 1909, Servers are 2019 Standard, and they are using ESXI Hosts: 7.0.  Under this configuration, the client is running our application in a mapped drive configuration.  Intermittently, a user will get an error 261 - Invalid/output or error 278 Invalid argument, usually in *winproc.  The PxPlus level was 12.5 but I upgraded them to 16.2 with the same results.

I have gotten connected to the workstations that have experienced the issue, and can bash the software around and I won't get any error - things work as expected.  I get out, and shortly after, while doing something reasonably mundane, the system hangs, and the user sees the stack level and the console prompt running down the screen when they press the Enter key. 

The error 278 happened on this statement
0320 let _header_obj_type$=""; read (%scr_lib,key=scrn_k$+"0000",dom=8800)iol=8010; let _header_obj_type$=_obj_type$
but we can start a new session, and all works well.

The error 261 happened on this statement
14311 let %_wp_dir$=msg("_WP_DIR",lwd),%_wp_prefix$=msg("_WP_PREFIX",pfx)

I am sure that this is a network issue and I have not got the most confidence in our client's IT support - well intentioned as they are.  Does anyone have any suggestions as to what may be done to resolve these issues?

Regards

Dave Fullerton

Hi:

In our START_UP program we do the following:

00900 ! ^100,5 - Set F5 and Shift F5 keys
00905 defctl $000074$=5 ! F5=F5
00910 defctl $000174$=-1 ! Shift F5 calls utilities

Like you, we found that F5 calling the utilities got in the way, but we liked having access to the utilities when we are in command mode, so Shift-F5 was a good tradeoff.

Hope this is useful

Regards

Dave

Hi Mike:

They will only be using our application for a period of less than 12 months, so an upgrade of PxPlus isn't in the cards - especially when the upgrade is to allow them to get a fix to a version that will be two releases back when 18 if released.  It would appear that nobody else caught this issue in V16 or v17 which is surprising as the spell check is a nice feature. 

I take it then, that it is not something that could be updated by an adjustment to a PxPlus program - is that correct?

Hi Mike:

That doesn't do us much good as the client can only go to V16 based on their CCP setting - they're always a version behind.

Normally, we would be using a spell checker that we have had in place for a very long time (20 years), but due to the pandemic, and people working from home, panels associated with the third party spell check application are hidden behind a PxPlus panel.  People think they're hung up as they can't see where they are supposed to do something associated with spell checking.  The issue has something to do with screen displays on systems that have multiple people connecting (possibly Citrix Terminal Server) and differences in screen resolutions on the workstations at the user's home.

Is this patch something that can be added to a V16 *win/ program?

Regards

Dave Fullerton

Hi Mike:

I think it's a great idea.  The have been more times than I care to count where someone has pasted data from an alternate source, which causes fields in files to be moved down causing all sorts of undesirable results.  My vote would  be to have the data stripped of these characters by default. 

Regards

Dave Fullerton

Thanks to Mike's suggestion, I now know what is going on - MSG(-1) says "Unable to load/locate functions from PxPlus PDF Library (err/ret=13/127)

MSG(RET) returns Permission denied.

Do I re-install Windx?

Regards

Dave

Hi Mike:

I was printing MSG(RET) and was getting something like I would get for an error 12 - didn't think about trying a [wdx]print msg(-1).  Msg(-1) didn't give me anything, but of course, that was relative to the server.

I'll give the [wdx]msg(-1) routine a shot - thanks

DAve

Hi Folks:

Running into an error 15 attempting to write to [wdx]*PDF* when the WindX user is connected via a Citrix server to our application server.  All works as expected if the user does not go through the Citrix server (i.e. they are in their network).   It looks like a convoluted setup to me.

We can create a folder for the file to reside in, and a file name is displayed in the folder, but then the error 15 occurs and an invalid PDF file (adobe can't read it) that is 2K in size is left.

PxPlus on the server is V12, PxPlus on the WindX is V15 (we are getting ready for an update).

Unfortunately, we can't trace the PDF on the WindX station.  We suspect that the issue is permissions based, but the folder is set for Everyone with full access.

Does anyone have any suggestions what we might do for a solution?

Thanks

Dave Fullerton

Hi:

The error gets trapped, you're just sending it automatically to the next line:

0010 let outdt$="40129C0"
0020 let dt$=dte(mid(outdt$,1,2)+"/"+mid(outdt$,3,2)+"/"+mid(outdt$,5,2):"%Mz/%Dz/%Yl",err=BAD_DATE)
0030 print outdt$
0100 BAD_DATE:! ^100,5
0110 print err
0120 escape

I hope this helps

Regards

Dave

Hey Stephane:

It's nice to hear from you.  Congrats on your continuing education ;-).

I am pretty sure that Jim didn't use ERD's when he started Explorer Software.

When I took my first Computer Science - Data Processing course in the early 80's it was GW-Basic, RPG II, Assembler, and Cobol.  Flow charts were mandatory as was psuedo code for the cobol routines.  When I started at MAI, I asked about flow charts and psuedo code forms, and was practically laughed out of the office ;-).  A case of things important at the academic level that don't really translate to the business world.

Take care

Dave