LLACROIX@carleton.EDU (Les LaCroix) (01/21/88)
Back in some recent VAX SIG Symposium tape, someone submitted a utility named LOCK, and claimed that they had registered the command with DEC. They further claimed that such registration would prevent name conflicts with other registered commands (including all DCL commands created by DEC). I have been unable to reach the author (whose name I forget just right now-- sorry). Has anyone out there heard of such a thing as registering DCL commands? Do you know what department at DEC would be in charge of this kind of thing, and how to contact them? Please reply directly to me, since I doubt this is a burning issue to most of the readership. (If anyone wants to receive this info, send me a note and I will forward to you whatever I find out.) Les LaCroix SPSS Inc., 402 Washington, Northfield MN USA 55057-2027 507/663-1205 llacroix@carleton.edu (CSnet) - or - llacroix@carleton.csnet (BITNET)
mhg@MITRE-BEDFORD.ARPA (Mark H. Granoff) (01/22/88)
>Back in some recent VAX SIG Symposium tape, someone submitted a utility >named LOCK, and claimed that they had registered the command with DEC. >They further claimed that such registration would prevent name conflicts >with other registered commands (including all DCL commands created by DEC). > >I have been unable to reach the author (whose name I forget just right now-- >sorry). Has anyone out there heard of such a thing as registering DCL >commands? Do you know what department at DEC would be in charge of this >kind of thing, and how to contact them? > >Please reply directly to me, since I doubt this is a burning issue to most >of the readership. (If anyone wants to receive this info, send me a note >and I will forward to you whatever I find out.) The only thing I have ever read regarding registering anything with Digital was in the "VAX/VMS Developer's Guide to VMSINSTAL" (Order number AA-HB12A-TE, $85.00 US, about 50 pages). The regsitration information deals with registering *facility codes*: "To avoid image name conflicts, you *must* register the facility code for each product with the DIGITAL VMS Product Registrar." (p. 2-1) I think the intent here is so that if you are planning on developing a (third-party) layered product, you would want to register your facitlity code with DEC so they don't develop a product with the same facility code. +---------------------------------------------------------------------+ | Mark H. Granoff Member of the Technical Staff | +---------------------------------------------------------------------+ | USMAIL: The MITRE Corporation | ARPAnet: mhg @ mitre-bedford.ARPA | | Burlington Rd. | UUCP : linus!mbunix!mhg | | M/S B015 |-----------------------------------| | Bedford, MA 01730 | A T & T: (617) 271 - 7030 | +--------------------------- Disclaimer ------------------------------+ |The views expressed herein are my own and do not necessarily reflect | | those of my employer. | +---------------------------------------------------------------------+
NED@YMIR.BITNET (Ned Freed) (01/26/88)
Digital maintains a registry for VMS products. This registry can be used
by third party developers as well as developers within Digital. When you
register a product, you specify five things:
(1) The facility code you use, if any. Digital will assign you a unique
facility number to go with your facility code. For example, PMDF uses
the code PMDF, so error symbols have the form PMDF$_blah, and PMDF's
facility number is 668.
(2) The prefix used for your system logical names. Continuing the example,
the preffix for PMDF is PMDF, so all PMDF logicals have the form PMDF_blah.
(3) System process names.
(4) System mailbox names.
(5) Shareable images.
I wish the registry included things like DCL command names, names of
images on SYS$SYSTEM (like print symbionts), and perhaps even lock IDs.
Anyway, last I heard the person to contact to register a product is:
Pamela R. Axtell
VMS Product Registrar
SSG/SQM Software Quality Group
110 Spit Brook Road
Nashua, NH 03062-2698
(603) 881-1362
I encourage all developers, even those who develop public domain software,
to register their products in this fashion. It sure helps eliminate conflicts.
To date I have registered three products -- DELIVER, MATHLIB, and PMDF, and
all has gone smoothly with them.
Ned Freed (ned@ymir.bitnet)
-------