[Info-vax] DCL's flaws (both scripting and UI)

[David Froble]

mcleanjoh at gmail.com wrote:
> On Friday, January 23, 2015 at 9:11:00 AM UTC+11, John Reagan wrote:
>> On Thursday, January 22, 2015 at 4:40:49 PM UTC-5, mcle... at gmail.com wrote:
>>
>>> - Let the choice be a SYSGEN parameter (to set a default) and able to be defined on the fly by any process
>> No, there is already a field in the UAF record for the CLI.  Currently, you're only supported choice is DCL.  I think (I can't check at the moment), you can even do:
>>
>> login: REAGAN/CLI=SOMETHING-BESIDES-DCL
>> password: *******
> 
> But you might not want to be locked into using one particular CLI for the entire process.  You might have command procedures that will only run under the "old" CLI and others that take advantage of the "new" CLI.
> 

Look.  Leaving DCL alone, and the CLI, is easy.

What's wrong with invoking any new CLI type of thingy from DCL when you 
want to use it?  Sort of like those using BASH on VMS.

Maybe I'm missing something, but if not, why not take the path of least 
pain?