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

Stephen Hoffman seaohveh at hoffmanlabs.invalid
Tue Jan 20 00:12:20 EST 2015


On 2015-01-20 03:42:46 +0000, David Froble said:

> Simon Clubley wrote:
>> On 2015-01-19, David Froble <davef at tsoft-inc.com> wrote:
>> 
>>> I also don't understand retaining the history.
>> 
>> It acts as a cache of your commonly used commands which are available
>> for immediate recall across multiple sessions.
> 
> I know what it does, I don't understand the need for the history.

Perform a RECALL/OUT=sys$login:history.log just before LOGOUT, and then 
perform a RECALL/INPUT=sys$login:history.log when you next log in.  You 
now have your command recall buffer populated with what you did prior 
to your LOGOUT.   It's handy for various tasks, particularly given the 
easy access to some command or group of commands you were working with 
earlier.

> If the alignment is correct, you'll see that you even agree that it's a 
> "command language".

DCL is a programming language, and it is used — like BASIC can be used 
— to string commands together.  DCL can also be used for general 
programming tasks.

> Yes, there is command files for backups and some other things.  But we 
> do not solve problems in DCL.

Then you're unusual, in that regard.  Yours would be the first site 
I've encountered that didn't have a fair amount of DCL or other 
scripting language around.


-- 
Pure Personal Opinion | HoffmanLabs LLC




More information about the Info-vax mailing list