|
I haven't run into this. Then again, our computer names are generally 6--
characters or less.
On Mon, Feb 16, 2026 at 2:10 PM Sizer, Joseph via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Has anyone experienced issues with ACS 5250 workstation naming collisionACS
avoidance algorithm reaching limits? My scenario is that we have a large
number of customer service reps using virtual desktops with similar
computer names. The configuration in ACS (currently at 1.1.9.11 - O/S at
V7R4) has the system generate a workstation ID based on computer name.
is set to truncate the end of the workstation name. The two check boxesid
for avoid duplicate names on this workstation and avoid duplicate names
with other workstations are both selected. This generates a workstation
variable of &COMPN*=would
Assuming the computer names are COMPUTER0001 through COMPUTER9999, as
users start their first session, the first user to connect would get
workstation ID COMPUTERA1, followed by COMPUTERA2, A3 and so on. It
then start moving on to COMPUTERAA, COMPUTERAB, etc. The issue we aresolution, I
running into is that at some point, ACS stops trying to find an available
unique name and simply attempts to use #COMPN##. Since this name is not
associated with any interactive sub-system, the end user simply gets a
blank screen and cannot log in.
The messages we receive in the ACS status bar include
Response code: 8902 Device not available.
Unable to automatically increment the Device Name
I have attempted to use different features available within ACS but have
not found a method that will guarantee the end user an available
workstation ID. If anyone has experienced this issue and has a
would be thankful.list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://urldefense.com/v3/__https://lists.midrange.com/mailman/listinfo/midrange-l__;!!FgubhKw!cbWyjMZG36zCA3pORxK3VfqAi02SJI17QKCKZyZiraV1WN_FBXOgNz3B8bGQpdoK8CnwzRorQWvSGkA2$
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://urldefense.com/v3/__https://archive.midrange.com/midrange-l__;!!FgubhKw!cbWyjMZG36zCA3pORxK3VfqAi02SJI17QKCKZyZiraV1WN_FBXOgNz3B8bGQpdoK8CnwzRorQaybFU8Q$ .
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://urldefense.com/v3/__https://lists.midrange.com/mailman/listinfo/midrange-l__;!!FgubhKw!cbWyjMZG36zCA3pORxK3VfqAi02SJI17QKCKZyZiraV1WN_FBXOgNz3B8bGQpdoK8CnwzRorQWvSGkA2$
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://urldefense.com/v3/__https://archive.midrange.com/midrange-l__;!!FgubhKw!cbWyjMZG36zCA3pORxK3VfqAi02SJI17QKCKZyZiraV1WN_FBXOgNz3B8bGQpdoK8CnwzRorQaybFU8Q$ .
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
