[Info-vax] What does VMS get used for, these days?
Arne Vajhøj
arne at vajhoej.dk
Sat Nov 12 08:46:37 EST 2022
On 11/11/2022 10:25 PM, Craig A. Berry wrote:
> On 11/11/22 6:37 PM, Arne Vajhøj wrote:
>> On 11/10/2022 7:19 PM, Phillip Helbig (undress to reply) wrote:
>>> In article <tkk3rr$em$1 at gioia.aioe.org>, =?UTF-8?Q?Arne_Vajh=c3=b8j?=
>>> <arne at vajhoej.dk> writes:
>>>>> Consider the fact that the user submitting the file might not have
>>>>> write
>>>>> permission to the current directory or to the directory where the
>>>>> procedure is located, but very probably does to SYS$LOGIN.
>>>>
>>>> Not having write access to the dir must be a special case.
>>>
>>> I don't know. Certainly there are environments where there is some
>>> official software or whatever where normal users are not allowed to
>>> write. Think SYS$SYSTEM. Should every user have access there? Think
>>> of a company's software package in some directory. Same thing.
>>
>> I am not saying that such cases does not exist - I am just saying that
>> they must be rare.
>
> Not at all. It's actually the most common use case in my experience.
>
>> I don't expect many users to SUBMIT COM files residing in
>> SYS$SYSTEM.
>
> More likely SYS$MANAGER or a site-specific common directory, but rarely
> a directory to which all users have write access.
>
>> And the two most common cases for software packages must be
>> system wide install with any batch job started by SYSTEM and
>> user installs in the users dir tree started by that user.
>> Leaving only the more unusual cases.
>
> What you consider unusual is actually all I've ever seen in a production
> environment. And I've seen lots of non-system users submitting batch
> jobs from system or site directories to which they do not have write
> access.
OK.
Based on a quick survey on c.o.v then I will conclude that
my assumptions about the usage of batch jobs was wrong.
And as consequence trying to put log file in same
dir as com file is not a good idea.
Arne
More information about the Info-vax
mailing list