Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: jeffrey_dsi <jeffrey@digitalsynergyinc.com>
Newsgroups: comp.os.vms
Subject: Re: SSL3 on OpenVMS V8.4-2L3
Date: Tue, 20 Aug 2024 13:30:45 -0700
Organization: A noiseless patient Spider
Lines: 39
Message-ID: <va2udl$3gmfh$1@dont-email.me>
References: <va2kk5$3fh8u$1@dont-email.me> <va2lil$3f8oq$4@dont-email.me>
 <va2lqk$3f8oq$5@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 20 Aug 2024 22:30:45 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="a60ea131ec680b75d43854fff2ac29b5";
	logging-data="3693041"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+QUpvLtMjT3Xjq0uUiKKqtqyNnCiVRLcs="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:juyzIcvt3vHzysuZOH77XHdOytk=
Content-Language: en-US
In-Reply-To: <va2lqk$3f8oq$5@dont-email.me>
Bytes: 2711



On 8/20/24 11:04, Simon Clubley wrote:
> On 2024-08-20, Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
>> On 2024-08-20, jeffrey_dsi <jeffrey@digitalsynergyinc.com> wrote:
>>> We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
>>> after many conversations with VSI as to which version of SSL to run.
>>>
>>> We have a cron job that produces an xml file and uses sftp to push it to
>>> the VMS system. In the script it did a "cd pipeline_data" which was a
>>> system logical for where the file needs to go. This doesn't work as SSL
>>> doesn't appear to understand logicals. I had to change it to "cd
>>> /lda105/pipeline_data" to get it to work.
>>>
>>> This breaks my rule that no script/com file should have a real device
>>> name except for sys$manager:logicals.com. I put a remark in the
>>> logicals.com to remind me of the new dependency if that logical changes.
>>>
>>
>> Can you create a command procedure that looks up the logical and
>> writes out a temporary sftp command procedure containing the hardcoded
>> current definition ?
>>
>> That way, there's no permanent file containing the hardcoded definition.
>>
> 
> Oops, sorry, ignore that. I missed the bit where you were pushing it
> _onto_ the VMS system.
> 
> However, have you tried playing with the cd parameter to try and
> force a lookup (for example by trying a leading "/" or something
> that looks VMS-like such as "cd PIPELINE_DATA:" ?
> 
> Simon.
> 
cd PIPELINE_DATA: fails the same as without the colon. I started an 
issue with VSI so we'll see what they say.

Jeff