[Info-vax] DCL Integer Overflow

[Jan-Erik Soderholm]

Den 2017-07-03 kl. 02:15, skrev Arne Vajhøj:
> On 7/2/2017 5:58 PM, Jan-Erik Soderholm wrote:
>> Den 2017-07-02 kl. 23:41, skrev Simon Clubley:
>>> On 2017-07-02, Robert A. Brooks <FIRST.LAST at vmssoftware.com> wrote:
>>>> The thought is that DCL will always be the command parser, and some other
>>>> language (likely open source) would be used for scripting.
>>>
>>> Will you be running this scripting language as a normal user mode
>>> (not supervisor mode) image without any privileges other than those
>>> already granted to the user ?
>>>
>>
>> Isn't that how perl, Python and similar tools are run today?
>> And if so, why change anything?
> 
> The performance reason that may have been important in 1977
> is probably not relevant any longer.
> 
> But running it in P0 instead of P1 will change some
> things.
> 
> It will require external programs to be run in another
> process instead of same process.
> 
> And that has an impact on many things like
> symbols, logicals, default dir etc..
> 
> I am not saying that it is a bad change.
> 
> I am just saying that it is a major change.
> 
> Arne
> 
> 
> 

I do not think that any new scripting language should be viewed
as a replacement for DCL, but as a complement to DCL. Something
in between DCL and fully compiled programs.

But for the usual batch/job-flow control tool, DCL will probably
not be replaced as such. Like JCL on the MVS systems.