[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::digital

Title:The Digital way of working
Moderator:QUARK::LIONELON
Created:Fri Feb 14 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5321
Total number of notes:139771

742.0. "HW Naming Conventions?" by KYOA::SACHS (Isn't M.O.R.F. related to ALF?) Mon Mar 06 1989 16:30

    I've been with DEC over 10 years and still can't figure out most
    of the conventions (if any) used for hardware product ids.
    
    I thought I had some of them, ie- VT: Video Terminal, LP: Line Printer.
    Does anyone know of a list which defines ALL of these?  Know where
    it can be obtained?
                                                          
    Thanks,
      Mark
T.RTitleUserPersonal
Name
DateLines
742.1Chief EngineerMSCSSE::LENNARDMon Mar 06 1989 16:523
    Try the office of the Chief Engineer.  The first function listed
    is "Consulting on New Product Nomenclature."  The manager is June
    Payne at 223-2912..........Hope this helps.
742.2Will give her a tryKYOA::SACHSIsn't M.O.R.F. related to ALF?Mon Mar 06 1989 18:084
    Thanks for the hint.  I'll give her a try.  Success or failure will
    be posted here.
    
    Mark
742.3BMT::SAPIENZAKnowledge applied is wisdom gained.Mon Mar 06 1989 21:0410
    
       Is there really a naming standard in use?
    
       I can see where VT = Video Terminal, and LP = Line Printer, but
    what about LA100, or TU80, TS11, etcetera? Some don't seem to make
    much sense at all.
    
    
    Frank
    
742.4Et tu, Brute!KYOA::SACHSBlack, with extra Caffeine, please!Mon Mar 06 1989 21:402
    That's why I asked!  As a field person, like yourself, I wondered
    if there was any method to this madness.
742.5Try LDP::DEC_HISTORYCOOKIE::WITHERSYou know you can't memorize ZenMon Mar 06 1989 21:445
If memory serves correctly, this is expalined in grusome detail in 
LDP::DEC_HISTORY (KP7 and all that...).

Regards,
BobW
742.6EAGLE1::EGGERSTom, VAX & MIPS architectureMon Mar 06 1989 22:363
    The history of the HW lettering noemclature may be in DEC_History, but
    I just looked at all the topic titles there, and it certainly isn't
    obvious just where it might be!
742.7Product names, and suchHSSWS1::GREGThe Texas ChainsawMon Mar 06 1989 22:5738
    
    	   Actually, I enjoy the diversity of naming conventions that
    	come into play, and make a game out of understanding how to 
    	translate them.  To draw upon previously mentioned examples,
    
    	   TU80 = Tape Unit 80
    	   TS11 = Tape Subsystem 11
    
    	   Whether or not these are valid remains to be seen, but this
    	is how I remember them.  I never did figure out why adding an
    	HSC interface to a TU made it a TA... that one still bugs me.
    	I figure it means Tape Access, but that's just a guess.  The 
    	storage media group has to be the worst when it comes to naming
    	conventions.  
    
    	   Except for the cables group... what on eart could be meant 
    	by the name "BNE3K"?  "BC16E" seems deceptively simple, until
    	you try to figure some significance for the 16... is it the
    	resistance of the line?  Perhaps the bandwidth?  Maximum
    	voltage?  Wire guage?  What the heck does the 16 mean?
    
    	   Networking products are a lot easier to understand.  Their
    	names are acronyms, almost always starting with DE (Digital
    	Ethernet).  The notable exception is the terminal server line,
    	which are DS's... I suppose DETS was not considered an appealing
    	product name.
    
    	   Are you looking for a real mental challenge?  Try finding any
    	five pieces of software in the price books... it's absolute
    	insanity!  Q-numbers out the wazzoo, split across two books, in
    	no obvious logical order.  
    
    	   Try using AQS!
    
    	   What a company... I love the challenges (excuse me,
    	opportunities).
    
    	- Greg
742.8Dontcha love the 2-5-2 SW Q numbers?FSADMN::REESEMon Mar 06 1989 23:067
    Re: l7
    
    Pogo *also* said "we are surrounded by insurmountable 
    opportunities"  :-)
    
    Karen
    
742.9standardsWR2FOR::BOUCHARD_KEKen Bouchard WRO3-2/T7Mon Mar 06 1989 23:2511
    There *are* conventions:
    Anything beginning with "K" pertains to a cpu.
    Anything beginning with "M" pertains to memory.(core or mos)
    Anything beginning with "D" pertains to data comm.
    Anything beginning with "T" pertains to tapes.
    Anything beginning with "R" pertains to disks.
    
    Anyway,these are the conventions that prevailed 15 years ago...there
    are exceptions now.
    BTW: The second letter of an option designation used to mean something
    but now it is arbitrary.(or so it seems)
742.10What about device driver names?DPDMAI::AINSLEYLess than 150 kts. is TOO slow!Tue Mar 07 1989 01:3913
    Given the explosion in our product line in the past few years, it
    is next to impossible to have meaningful 2 character letter
    combinations.
    
    I must admit, our Ethernet folks seem to have to most fun naming
    things.  I'm waiting for our news Unibus Ethernet controller to
    come out:
    
    	The DUMPER
    
    it also gets rid of excess Ethernet traffic :-)
    
    Bob
742.12Who needs vacuum columns?WHYVAX::DELBALSOI (spade) my (dog face)Tue Mar 07 1989 11:099
re: < Note 742.7 by HSSWS1::GREG "The Texas Chainsaw" >
 >                          -< Product names, and such >-
 >    	   TS11 = Tape Subsystem 11
 >

Well, that could be, Greg, but in all the years that I was with the RSTS/E
Engineering group we SWORE that it actually stood for "Tape Stretcher 11"!

-Jack
742.13Please don't post a lengthy answer hereDR::BLINNRule #5: There is no Rule 5.Tue Mar 07 1989 12:5214
        Like Bob Withers, I'm sure this topic has been raised, and beaten
        to death, several times in several conferences in the past.
        
        However, other than here (I haven't checked, but I wouldn't be
        surprised to find it here already), I believe it has been asked
        and answered (without, of course, a definitive answer) in one of
        the issues of ASKENET. 
        
        If you *do* find a definitive answer, and the information can be
        found on-line, please DO NOT POST IT HERE.  Post a pointer to
        where you found the information.  (Unless, of course, it's a page
        or less.  I'll be amazed if it's that little.) 
        
        Tom
742.14Marching on...KYOA::SACHSBlack, with extra Caffeine, please!Tue Mar 07 1989 20:4113
    RE: .12
    	I *was* referring to the *REAL* names.  If we added all the
    DECrynisms, we could probably fill up an RA90.
    
    RE: .13
    	'Twas exactly my intent, Tom.  If a pointer exists, I would
    have provided same (so far, my discovery process hasn't come up
    with anything).
    	If it is "large" and unwieldy for this conference, I'll keep
    it locally, and recommend that anyone wanting a copy send me mail,
    and I'll FWD the list back.
    
    Mark
742.15The Oatmeal StandardDPDMAI::DAVISGBLet's get Relational!Tue Mar 07 1989 21:3015
    While I was working in Corporate Product Operations, I attended
    one of the strategy meetings that produced the 62XX series of VAX'es.
    
    The chairman (Don't think he'd appreciate his name being published
    here...),  got up and explained the process, which 
    he likened to mixing up a bowl of oatmeal, throwing some around, and 
    going with whatever stuck to the walls.

    Discussion ensued, oatmeal flew and the 6210 stuck.
    
    Cheers,
    
    Gil
    
    
742.16EAGLE1::EGGERSTom, VAX &amp; MIPS architectureWed Mar 08 1989 01:401
    What makes you think it was oatmeal?
742.17Be nice, now!KYOA::SACHSBlack, with extra Caffeine, please!Wed Mar 08 1989 02:214
    Only because one can't get vulgar in these conferences.
    
    Remember, big brother (in this case Tom Blinn) is watching over
    us!
742.18Clear as mudMPGS::MCCLUREWhy Me???Wed Mar 08 1989 11:2025
    Other than the first letter naming convention, things get pretty
    mixed up. There are 'guidelines' in the product family groups,
    but some things occur only because the marketing and engineering
    folks want to DIS-associate the product from a dud predecessor.
    
    The tapes family is fairly traditional, but some of the old style
    units persist as the 'exceptions'.
    
    	T=tapes (general family)
    	TA= tape assembly and is the general family for reel-to-reel
    	TB= one that's coming, but I'm not clear about the 'B=' what yet
    	TC= tape control and is a TCU if a seperate piece
    	TU= tape drive(transport), couldn't use TT since thats a teletype
    Therefore, a TA90 consists of a TC90 and at least one TU90. Simple huh?
    
    	TK is for the cartridge tape units.
    	Initially, the number referred to the form factor EG TK50= 1/2 rack
    and 'full' height while the TK30 would have been '1/2' height but then
    came higher density in the TK70 that was the same size as the 50 8-).
    
    Then we get into the controllers, TUK for Ubus, TQK for Qbus but then
    came the SCSI controller and TSK was out of the question for several
    reasons, so it became the TZK.
    
    Bob Mc
742.19H/W NomenclatureGIAMEM::GOLDMANFri Mar 10 1989 19:164
    LA as in LA120, 180 etc. stands for  "Line Asynchronous"
    There is logic to all of this; simply not known to us.
    I suspect the logic is a product of Dick Best.
    
742.20MU::PORTERwhat's in a name?Sat Mar 11 1989 02:0018
    Here in NaC, where we build boxes that sit on the Ethernet,
    the defacto rule seems to be:
    
    	5 letters starting with DE.
    
    Thus the DECnet/SNA Gateway-CT hardware is the DESNA, because "SNA" 
    seemed vaguely appropriate, although maybe GCT would have fitted in
    better with the software name, but we didn't have it at the time.
    If we ever build a follow-on, we'd probably call it a DESNB, using
    the old increment rule.  If we ever built a follow-on to that, though,
    we'd be out of luck since someone else has claimed DESNC for the
    eNCryption box.
    
    Algorithm: think of a name that fits in with other things you've
    seen.  Apply to the office of the chief engineer to claim it for
    your own.   Other people will then use your name as a de facto
    standard, and before you know it you're part of a convention.
    
742.21Pretty good description in the Engineering NewsletterTHEJUG::WHITEWillie WhiteMon Mar 13 1989 12:438
    There were articles in the Engineering Newsletter last June and September
    describing the numbering scheme for option level parts.  The articles
    were submitted by Marcia Russell of the Chief Engineer's Office. 
    Probably worth a look.  I can photocopy the articles for you if you
    can't get them elsewhere.
    
    -willie
    
742.22One that didn't make it ;-)TELGAR::WAKEMANLAAnother Eye Crossing Question!Thu Mar 16 1989 20:209
    I remember hearing about an ill fated project to produce a DES
    encryption board that sat on the unibus.At the time the scheme for
    numbering things was AAA11, as opposed to the older AA11A schema.  The
    first two letters were "KG" indicating that it was an auxilliary
    processor.  Since there was already a KG11A, it was to be called the
    KGB11.  Fitting.  I heard the government didn't take too kindly to the
    name.
    
    Larry
742.23Too late?TLE::LIONELThe dream is aliveThu Mar 16 1989 21:137
    Re: .22
    
    Then the government can't be too pleased with VMS which has various
    symbols used to interface to the security features that have prefixes
    such as KGB$, NSA$ and CIA$....
    
    				Steve
742.24HSC... SKIWVA::MAYNARDThu Mar 16 1989 22:4210
    
    At an IS Symposium I attended awhile back, one of the presenters
    swore that the HSC of the HSCXX stood for Hot "doo-doo" Controller.
    
    They actually had to retrofit the name Hierarchical (sp) Storage
    Controller.  
    
    May be true, Maybe not...
    
    Brent
742.25remembrance of things pastEAGLE1::EGGERSAnybody can fly with an engine.Thu May 04 1989 14:1210
    It finally came to mind. The name of the person who created Digital's
    "option designation list" in 1964 was Authur Hall. He was not a "CPU
    engineer", so he relegated the CPU options to the letters he had left
    over after assigning reasonable letters to the things he was familiar
    with. CPUs, even today, have an option number beginning with the letter
    K; this isn't for processor "chip" names, but rather for the modules
    the chips go on.
    
    Dick Best, as Digital's official "chief engineer", still heads the
    office that assigns all the engineering option numbers. 
742.26DFLAT::DICKSONtwang and toot, not beep or thudThu May 04 1989 19:224
Anyone who has read Bell & Newell's classic text on computer architecture will
recall that in the Processor/Memory/Switch (PMS) notation, "K" was used for
CPUs.  If the K convention dates from 1964, then I suspect that Bell took that
with him.
742.27EAGLE1::EGGERSAnybody can fly with an engine.Thu May 04 1989 20:034
    Gordon Bell was well aware of the option-number convention in 1964.
    Somehow I doubt that was the source of the "K" in the PMS notation, but
    I don't have any good reason for the doubt. Next time I see Gordon,
    I'll ask him. 
742.28PMS notationTHEJUG::WHITEWillie WhiteSun May 14 1989 00:3010
    re: .26
    
> Anyone who has read Bell & Newell's classic text on computer architecture will
> recall that in the Processor/Memory/Switch (PMS) notation, "K" was used for
> CPUs.  

    If I'm not mistaken "P" was used for processor in PMS (hence the P in
    PMS) and "K" was used for link or link/switch (control) elements.
    
    -willie
742.29More on PMSSEEK::HUGHESThus thru Windows call on us(Donne)Thu May 18 1989 17:289
    re .28:
    
>   If I'm not mistaken "P" was used for processor in PMS (hence the P in
>   PMS) and "K" was used for link or link/switch (control) elements.
    
    You are indeed correct: the designers of the HSC50 followed that convention
    and hence the names "P.io" and "K.sdi".

    -Jim