PxPlus User Forum

Twitter Twitter Twitter

Author Topic: Client-side FID(0)  (Read 428 times)

James Zukowski

  • Diamond Member
  • *****
  • Posts: 178
    • View Profile
Client-side FID(0)
« on: January 12, 2021, 03:55:56 PM »
Is there a way, other than AUTOEXEC.BAT or PxPlus.ini, to set the value of FID(0) on the client before establishing a WindX connection through SimpleCS using .windx files?

Thanks in advance!
James Zukowski
Programmer / ERP Analyst
Beauty Enterprises, Inc.
150 Meadow St.
Hartford, CT 06114
860.296.9303  Ext 231

Mike Hatfield

  • Gold Member
  • ****
  • Posts: 58
    • View Profile
Re: Client-side FID(0)
« Reply #1 on: January 12, 2021, 04:59:17 PM »
If the user starts multiple sessions on the PC do you expect each session to have a different FID or the same FID?
Mike H

James Zukowski

  • Diamond Member
  • *****
  • Posts: 178
    • View Profile
Re: Client-side FID(0)
« Reply #2 on: January 12, 2021, 05:02:48 PM »
We're looking at this being the same FID. We're using it more as a PC ID. Each process will get a unique FID once logged onto the server side.
James Zukowski
Programmer / ERP Analyst
Beauty Enterprises, Inc.
150 Meadow St.
Hartford, CT 06114
860.296.9303  Ext 231

Mike King

  • Administrator
  • Diamond Member
  • *****
  • Posts: 3416
  • Mike King
    • View Profile
    • PVX Plus Technologies
Re: Client-side FID(0)
« Reply #3 on: January 12, 2021, 05:22:59 PM »
Since you mentioned Simple CS -- have you considered using %pxplus_nid$ which will have the workstations computer name.  Generally these will be unique on the same network.

You could also consider %pxplus_client$ which has the workstation IP address port and name.


James Zukowski

  • Diamond Member
  • *****
  • Posts: 178
    • View Profile
Re: Client-side FID(0)
« Reply #4 on: January 12, 2021, 05:40:42 PM »
Most -- probably all -- of these would work fine, if keeping all of the information internal to the process. However, we have a couple of monitoring programs that provide us with information about other PxPlus processes. When we were using nthost/ntslave, we were able to provide a unique machine ID on the command line that we could parse out. With SimpleCS, all of the ID's come through as T0, and that's how they show up on the server side, even when we change the process's FID(0) once we start up. By changing the FID(0) before the WindX connection is established, the id=T0 is overridden.
Just looking for a clean way to establish that without having to touch 100+ machines around the country.

Thanks!
James Zukowski
Programmer / ERP Analyst
Beauty Enterprises, Inc.
150 Meadow St.
Hartford, CT 06114
860.296.9303  Ext 231

Mike Hatfield

  • Gold Member
  • ****
  • Posts: 58
    • View Profile
Re: Client-side FID(0)
« Reply #5 on: January 12, 2021, 05:47:05 PM »
in the past we had a requirement that a specific computer be assigned a specific fid so that a user could print to a specific printer but in the long run we found that to be cumbersome and restrictive.
We now have multiple methods of assigning fid.
A 'next' available from a fid pool
A range of fids dependant on a subnet
A specific fid based on computer id
A specific fid based on the user login - either from the local computer login name or domain login name or the application login name.
All this is controlled and assigned at the STARTUP or Application login.
Ultimately we don't really care what the fid actually is so long as it is unique.
Mike H

Mike King

  • Administrator
  • Diamond Member
  • *****
  • Posts: 3416
  • Mike King
    • View Profile
    • PVX Plus Technologies
Re: Client-side FID(0)
« Reply #6 on: January 13, 2021, 09:33:15 AM »
Actually if you want to control FID(0) based on the workstation shortcut simply add -ID=XXX to the command line.


James Zukowski

  • Diamond Member
  • *****
  • Posts: 178
    • View Profile
Re: Client-side FID(0)
« Reply #7 on: January 13, 2021, 10:00:56 AM »
If we were using a command-line shortcut, that would work fine. We're using .windx files, and it doesn't seem to fit in anywhere.  :(
James Zukowski
Programmer / ERP Analyst
Beauty Enterprises, Inc.
150 Meadow St.
Hartford, CT 06114
860.296.9303  Ext 231

James Zukowski

  • Diamond Member
  • *****
  • Posts: 178
    • View Profile
Re: Client-side FID(0)
« Reply #8 on: January 13, 2021, 11:08:29 AM »
It turns out this discussion may be moot. I've been trying to get the id from the task process list to change according to the fid(0) of the workstation connecting with SimpleCS. It finally 'clicked' that that's the id for the host, not the client.

Other options now under consideration. Thanks to all for the different insights.
James Zukowski
Programmer / ERP Analyst
Beauty Enterprises, Inc.
150 Meadow St.
Hartford, CT 06114
860.296.9303  Ext 231