Re: Device names and interactive subsystem descriptions

The subsystem does not need to be restarted for a workstation entry to take effect.

I am confused about the "C0". Workstation IDs cannot start with a number. Did you start them literally with "C0"

In any case the subsystem does not need to restart to enable a workstation entry. One thing that might be happening. If another subsystem grabs the device and allocates it, then it might hang onto it until the device is varied off and back on. I just tried that on our system at iDevCloud and was able to mimic what you are describing. Try varying the devices off and then back on with the new subsystem entry active.

I would also look into the other workstation entries to be sure there is not a similar entry out there.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 2/3/2012 5:11 PM, John McKee wrote:

For a long time, there were standards where I work as to naming
conventions for devices. But, since the system is on the way out in
maybe a year, other people are dictating things.

In the case of the above, the person who assists others establishing a
remote connection through the firewall has decided that it would be
easier if the device name was same as the user id.

We have two interactive subsystems. Each has a number of workstation
entries - composed of three characters followed by an asterisk.

I had forgotten about those entries when I created device descriptions
that start with C0 (a digit zero).

My day off today, and I received a call from work that the remote
users only got a blank screen. So, I added the C0* entry. I was told
later that it still did not work.

I am guessing that the subsystem needed to be restarted for the change
to take effect. Am I right, or is there something else that needs to
be done?

John McKee
--