Main Board > Thin Client/WindX

Client-side FID(0)

(1/2) > >>

James Zukowski:
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!

Mike Hatfield:
If the user starts multiple sessions on the PC do you expect each session to have a different FID or the same FID?

James Zukowski:
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.

Mike King:
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:
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!

Navigation

[0] Message Index

[#] Next page