RE: Static/Dynamic TN5250 Device Names

["Mark Villa" <markvilla@xxxxxxxxxxx>]

~~~automatically. But you are able to configure a static name
~~~if you choose
~~~to.

The other problem
~~~is that the
~~~workstation to which the device name belongs is unable to acquire a
~~~session.
~~~
~~~Anyone have any experience with this problem using a
~~~combination of CA/400
~~~or Mocha TN5250 sessions?
~~~
~~~Ken Slaugh  (707) 795-1512 x118
~~~Chouinard & Myhre, Inc.
~~~AS/400 Professional Administrator/MSE
~~~Client Access Specialist
~~~http://www.cm-inc.com/



my 2cents....
Good qeustion... I see it as: how to carry over from the twinax days...

I have not done so but there may be a way out by changing device recovery
action, if you are in an uncontrolled environment.
Turning auto create off will stop that, then they have to call somebody.

About the "scheme".
Making sure 100% of your users have defined 5250 names or none at all should
work. I have seen both.
The printers of course we like our defined queues. 3rd party queues and
profiles are always a problem.
The printer "device cycle" is different than the 5250 session, hard to
articulate, but it does not seem to be a problem of they a defined.
signon CL's used in many shops.
I have also seen problems of devices hanging open, this seems to depend on
the network and what PTF's are in place.
I work remote and if I had a predefined session I would have to call support
more than once per day (if I was a clerk)


Mark Villa in Charleston SC