[Info-vax] Very simple DCL question

[Chris Townley]

On 28/12/2022 20:35, Arne Vajhøj wrote:
> On 12/28/2022 1:45 PM, Chris Townley wrote:
>> On 28/12/2022 18:38, Arne Vajhøj wrote:
>>> On 12/28/2022 1:29 PM, Chris Townley wrote:
>>>> On 28/12/2022 16:45, Arne Vajhøj wrote:
>>>>> $ type z.com
>>>>> $ write sys$output "''p1'"
>>>>> $ @z a
>>>>> A
>>>>> $ @z "a"
>>>>> a
>>>>>
>>>>> This is not really surprising.
>>>>>
>>>>> But are there any way to preserve pn case without
>>>>> double-quoting it?
>>>>>
>>>>> Like this hypothetical syntax:
>>>>>
>>>>> $ set proc/parse=(extended,pnkeepcase)
>>>>
>>>> There is of course
>>>>
>>>> $ SET PROCESS /CASE=CASE_LOOKUP=SENSITIVE /PARSE_STYLE=EXTENDED
>>>>
>>>> Does this not work?
>>>
>>> I did not know that. But no.
>>>
>>> $ SET PROCESS /CASE=CASE_LOOKUP=SENSITIVE /PARSE_STYLE=EXTENDED
>>> %DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
>>>   \CASE_LOOKUP\
>>> $ SET PROCESS /CASE_LOOKUP=SENSITIVE /PARSE_STYLE=EXTENDED
>>> $ @z a
>>> %DCL-E-OPENIN, error opening DISK2:[ARNE.gpcp]z.COM; as input
>>> -RMS-E-FNF, file not found
>>> $ @z.com a
>>> A
>>> $ @z.com "a"
>>> a
>>
>> Interesting. What version of VMS are you on?
> 
> $ write sys$output f$getsyi("version")
> V8.4-2L2
> 
>> My example was straight from the VSI DCL dictionary. I was vaguely 
>> aware of something like that.
>>
>> Presumably the command affects the current process - do you need to 
>> have it in z.com? Although you shouldn't as you are double quoting the 
>> symbol substitution.
> 
> I am pretty sure that the problem has already happened when the first
> line in z.com is executed.
> 
> Arne
> 

Interesting

$ SET PROCESS /CASE_LOOKUP=SENSITIVE /PARSE_STYLE=EXTENDED
$ aa = "a"
$ show sym aa
   AA = "a"

$ @z.com 'aa'
A
$ @z.com "''aa'"
a

Not sure what else to suggest...

-- 
Chris