Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!ukma!psuvm.bitnet!cunyvm!unknown
From: rrk@byuvax.bitnet
Newsgroups: comp.os.vms
Subject: Re: ALLIN1 NBS text format identifier.
Message-ID: <119rrk@byuvax.bitnet>
Date: 8 May 88 18:01:32 GMT
Lines: 18

I have my own DSAB that works much better for this application than the
foreign DSAB.  As a matter of fact the only problem I am having is the NBS
identifier.  I can even use the same NBS identifier that the foreign DSAB
uses on nodes that don't have the foreign DSAB.  The problem is that we
have the foreign DSAB and ALLIN1 gets confused when two DSABs are assigned
to the same number.  There are also open slots that I have been able to
successfully use which are left open for products not shipped as
a standard part of ALLIN1 such as DECTEXT (an old DEC WordProcessor) and
DECPAGE (DEC's desk top publishing), unfortunately some sites have these
products, so the mail fails to correctly type the messages on these systems.
The NBS number must be the same everywhere.  If I use a number
out of the range of those used by DEC, ALLIN1's fetcher fails.
If I use a number within the range used by DEC, it fails on sites with the
products for whom the slots were left open.  We cannot live without our
own DSAB.  It implements a text type and editor as known text format and
editing styles.

                                        AMMON::RAY