Re: Workstation Names in ACS

[Evan Harris <auctionitis@xxxxxxxxx>]

Hi Joseph

not quite the same, but I have a colleague currently working through a
similar-sounding issue.
Background to their case is that they have uniquely named printer sessions.
The symptom being seen is that the QTVDEVICE jobslogs are full of
CPF9802 Virtual device ##COMPN## not available messages (and from memory
QTVTELNET consumes a bit more CPU than usual)



On Tue, Feb 17, 2026 at 8:10 AM Sizer, Joseph via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> Has anyone experienced issues with ACS 5250 workstation naming collision
> 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.  ACS
> is set to truncate the end of the workstation name.  The two check boxes
> for avoid duplicate names on this workstation and avoid duplicate names
> with other workstations are both selected.  This generates a workstation id
> variable of &COMPN*=
>
> 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 would
> then start moving on to COMPUTERAA, COMPUTERAB, etc.  The issue we are
> 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 solution, I
> would be thankful.
>
>
>
>
> --
> 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://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.