RE: V3R2 PTFs for CA/400 Win95/NT V3R1M3 new features

At 09:17 AM 7/2/98 -0400, Michal Guzak wrote:
>Since we now have this WONDERFUL ability to name our device sessions in
>V3R2, can somebody recommend a naming scheme that makes sense and
>provides some useful information.  Maybe some examples of the
>nomenclature being used at other sites - other than the old PC1, PC2,
>PC2, etc..

We've not had many PCs in use yet. In the past, those usually had a device
name based on their user name, like JOHNSONS1, JOHNSONS2, etc. That was
handled by PC Support. The named devices capability doesn't seem to include
this automatic extension to a name prefix—is this true, anyone?

For dumb terminals we use a short location/branch ID followed by a number.
We don't have that much to keep track of per location.

I think it's useful to know that someone is at a PWS versus a NWS, so I'd
lobby for 'PC' in the name somewhere.

Putting part of the IP address in is not very helpful, IMO, since it can
easily change. The protocols need it but no human agency does, usually. And
with DHCP & DNS it can change on a daily basis anyway. This is the same
reasoning behind using URLs instead of IP addresses, since the former are
much more stable and the latter are very much subject to change.

I think—keep it simple. Location code, sequence number, PWS vs. NWS,
enough? More ends up requiring more education of help desk, users,
developers, etc.

JMHO

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN  55401-2499
(612) 371-1111 x480


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---