<![CDATA[User "batch" displayed as "local"]]>From lib/vstlib.p:
if u_name = "batch" then u_name = "local".

Why?

I ask because we have applications where there are batch clients with user names like batch, batch2, batch3. PT displays them as local, batch2, batch3. It seems an arbitrary change and there is no code comment about it.

Was this added to deal with a past Progress behaviour? Or some vendor application?

]]>https://community.wss.com/topic/56/user-batch-displayed-as-localRSS for NodeSun, 12 Apr 2026 06:19:47 GMTWed, 28 Aug 2019 18:30:08 GMT60<![CDATA[Reply to User "batch" displayed as "local" on Mon, 02 Sep 2019 14:19:17 GMT]]>Should be fixed in pt3.141x. I decided to simply use the first part of the device name unless the device name is "batch" and only if the name is otherwise blank. If that fails then use the usr#.

]]>https://community.wss.com/post/256https://community.wss.com/post/256Mon, 02 Sep 2019 14:19:17 GMT<![CDATA[Reply to User "batch" displayed as "local" on Wed, 28 Aug 2019 20:30:30 GMT]]>I'll get right on it.

]]>https://community.wss.com/post/250https://community.wss.com/post/250Wed, 28 Aug 2019 20:30:30 GMT<![CDATA[Reply to User "batch" displayed as "local" on Wed, 28 Aug 2019 20:21:11 GMT]]>Ok...

Do something different. (Please.)

😎

]]>https://community.wss.com/post/249https://community.wss.com/post/249Wed, 28 Aug 2019 20:21:11 GMT<![CDATA[Reply to User "batch" displayed as "local" on Wed, 28 Aug 2019 20:15:26 GMT]]>As I recall it started off because _connect-device is "batch" is the device name for shared memory batch connections, which gets pulled into the u_name, but "batch" could also be a remote batch process and I didn't want to have a confusing default name.

But... now that you ask about it. I'm not sure it serves much of a useful purpose and it probably wouldn't be very hard to convince me to do something different.

(pt3.141 should be available real soon.)

]]>https://community.wss.com/post/248https://community.wss.com/post/248Wed, 28 Aug 2019 20:15:26 GMT