Conference clt::cms

2485.0. "Wish: Specify Library on Command/Elements" by DOTWRK::LITT (Tim Litt) Sun May 11 1997 13:22

    Since the recent /gen discussion revealed that there is still some
    life in CMS -- another long-standing wish:
    
    I usually work with a long library list, as I have about a dozen 
    facilities within my codebase.
    
    It would be nice if I could specify a particular library as the target
    of a command.  For example, CREATE ELEMENT NEW.FOO/LIBR=FOO$ROOT:[BAZ.CMS]
    (or CREATE ELEMENT NEW.FOO/LIB=FOO$LIB, where FOO$LIB is a logical.)
    
    Currently, CMS will always create in the first library in the list,
    which is rather a pain.  I generally end up spawing a subprocess, 
    setting library, creating the element, and logging out the subprocess
    in order to work around this.  
    
    There are some old notes which hinted that the element syntax was to be
    extended in this direction (I got the impression CREATE ELE
    FOO$LIB:NEW.FOO would become possible.)  This would be OK.
    
    I would argue that this extension should be permitted anywhere an
    element spec is used.  (E.G. replace, or diff, or (un)reserve or...)
    
    I don't have a strong opinion on which approach is taken.  COPY ELE
    started us down the /lib path.  Extending the element syntax would
    minimize typing.  
    
    T

    Hi Tim,
    
    Yes, CMS is still very much in active development, as is all of DECset.
    
    Thanks for requesting this; I think it's a great idea, and it wasn't
    already on our wish list. I've raised it as CMS wish #70.
    
    -- Daryl