[Info-vax] Marketing ideas for VSI ?

[Dave Froble]

On 12/16/2018 4:34 PM, Arne Vajhøj wrote:
> On 12/16/2018 10:56 AM, Phillip Helbig (undress to reply) wrote:
>> In article <pv5pvo$p84$1 at dont-email.me>, Dave Froble
>> <davef at tsoft-inc.com> writes:
>>> On 12/16/2018 3:55 AM, Phillip Helbig (undress to reply) wrote:
>>>>      generic and specific queues
>>>
>>> I'd guess there are methods for printing.  Don't know about batch, or,
>>> other purposes VMS's queue manager can be used for.
>>
>> I was thinking about batch queues here.
>
> Job schedulers are available.
>
>>>>      queues which will failover to another node
>>>>
>>>>      cluster-alias IP address
>>>
>>> I'd guess that other systems handle networking tasks.
>>
>> Again, sure they do, but with how much hassle?  How much
>> user-friendliness.
>
> Most network gear support VIP's. Not much hassle.
>
>>>>      cluster-wide logical names
>>>
>>> Does any other system have logical names?  Not that I know.  But, I
>>> don't get out much.
>>
>> Probably not.  But is there any equivalent functionality.
>
> Storing something somewhere that can easily be accessed by
> application: yes.
>
> Arne
>

Logicals can be very helpful.  They can also be abused.  The following 
is an example of what I consider a decent use of logical names, and it 
is very helpful with finding, accessing, building executables, and such.

   "APE" = "DISK1:[SOFTWARE.AP.EXECUTE]"
   "APL" = "DISK1:[SOFTWARE.AP.LIBRARY]"
   "APPLIB" = "DISK1:[SOFTWARE.APPLIB]"
   "APS" = "DISK1:[SOFTWARE.AP.SOURCE]"
   "ARE" = "DISK1:[SOFTWARE.AR.EXECUTE]"
   "ARL" = "DISK1:[SOFTWARE.AR.LIBRARY]"
   "ARS" = "DISK1:[SOFTWARE.AR.SOURCE]"
   "BKE" = "DISK1:[SOFTWARE.BK.EXECUTE]"
   "BKL" = "DISK1:[SOFTWARE.BK.LIBRARY]"
   "BKS" = "DISK1:[SOFTWARE.BK.SOURCE]"
   "CME" = "DISK1:[SOFTWARE.CM.EXECUTE]"
   "CML" = "DISK1:[SOFTWARE.CM.LIBRARY]"
   "CMS" = "DISK1:[SOFTWARE.CM.SOURCE]"
   "DPE" = "DISK1:[SOFTWARE.DP.EXECUTE]"
   "DPL" = "DISK1:[SOFTWARE.DP.LIBRARY]"
   "DPS" = "DISK1:[SOFTWARE.DP.SOURCE]"
   "GAMES" = "DISK0:[DFE.GAMES]"
   "GLE" = "DISK1:[SOFTWARE.GL.EXECUTE]"
   "GLL" = "DISK1:[SOFTWARE.GL.LIBRARY]"
   "GLS" = "DISK1:[SOFTWARE.GL.SOURCE]"
   "IME" = "DISK1:[SOFTWARE.IM.EXECUTE]"
   "IML" = "DISK1:[SOFTWARE.IM.LIBRARY]"
   "IMS" = "DISK1:[SOFTWARE.IM.SOURCE]"
   "LNK$LIBRARY" = "APPLIB:APPLIB.OLB"
   "LNK$LIBRARY_1" = "FL:SUPLIB.OLB"
   "LNK$LIBRARY_2" = "FL:COMLIB.OLB"
   "OEE" = "DISK1:[SOFTWARE.OE.EXECUTE]"
   "OEL" = "DISK1:[SOFTWARE.OE.LIBRARY]"
   "OES" = "DISK1:[SOFTWARE.OE.SOURCE]"
   "POE" = "DISK1:[SOFTWARE.PO.EXECUTE]"
   "POL" = "DISK1:[SOFTWARE.PO.LIBRARY]"
   "POS" = "DISK1:[SOFTWARE.PO.SOURCE]"
   "PPE" = "DISK1:[SOFTWARE.PP.EXECUTE]"
   "PPL" = "DISK1:[SOFTWARE.PP.LIBRARY]"
   "PPS" = "DISK1:[SOFTWARE.PP.SOURCE]"
   "RPTLIB" = "DISK1:[SOFTWARE.RPTLIB]"
   "SAE" = "DISK1:[SOFTWARE.SA.EXECUTE]"
   "SAL" = "DISK1:[SOFTWARE.SA.LIBRARY]"
   "SAS" = "DISK1:[SOFTWARE.SA.SOURCE]"

And a build of an executable can be as simple as

$ CP AR2101

With this command file

$ sho sym cp
   CP == "@DISK1:[SOFTWARE]CP.COM"

$ t disk1:[software]cp.com
$ M = F$EXTRACT(0,2,P1)
$ SPAWN/NOWAIT/NOTIFY/INPUT='M'L:'P1'.COM/OUTPUT='M'L:'P1'.LOG

$ t arl:ar2101.com
$ DBASIC/NOLIST/OBJECT=ARL: ARS:AR2101.BAS
$ DLINK ARL:AR2101/EXE=ARE:/NOMAP
$ PURGE ARS:AR2101.*
$ PURGE ARL:AR2101.*
$ PURGE ARE:AR2101.*
$ DELETE ARL:AR2101.OBJ;*

With a bit of thought, and preparation, drudgery becomes much less, and 
the whole would have been more complex without the logical names. 
People working on programs don't have to think about where to find the 
programs, they know, because logical names greatly simplifies things.

Logical names are a rather good thing.

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486