ADSM-L

Client Node Naming Conventions

2015-10-04 18:14:04
Subject: Client Node Naming Conventions
From: INTERNET.OWNERAD at SNADGATE
To: Jerry Lawson at TISDMAIL
Date: 8/15/96 9:11AM
Like you, we considered naming conventions involving descriptive entries.
However, when we actually went in to do it, we found that using the Host name
was sufficient, and more importantly, less confusing.

Jerry Lawson
jlawson AT itthartford DOT com


________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Client Node Naming Conventions
08-15-96 09:11 AM

   We are just starting to implement ADSM.  We will be having a minimum of
   four MVS ADSM servers (probably will expand to more on various
   platforms) and will be mananging many (hundreds) of clients (of the
   server variety, not workstations).

   We believe that a client node naming convention will be necessary in
   order to manage this environment.  Based on experience can anyone tell
   me if there are definite benefits to having this naming convention or if
   there were management problems encountered because one wasn't in place?
   We have had some resistance from our pilot clients in this area and want
   to make sure that there are good reasons for having one.

   The convention we are looking at denotes Business Unit, city, platform
   and target ADSM server.

   I appreciate any opinions in this area.

   Pat
<Prev in Thread] Current Thread [Next in Thread>