topic Re: PathWorks running on OpenVMS 7.3-2 in Operating System - OpenVMS

PathWorks running on OpenVMS 7.3-2

Jasper_15 — Tue, 01 Nov 2005 23:23:30 GMT

Hi,
I am new to this forum, so I hope I'm posting this question at the right place. Please do advise if I'm in the wrong location. My question is regarding to Pathworks running on my Alpha ES45 v.7.3-2 - My problem is that I created this scratch area for everyone to temporary writes to and delete at free will. However, I don't know what I did or can see why none of the users can write to this temporary scratch area. I am a newbie to this site and OpenVMS, so please be kind (-:

Thank you in advance.

Jasper

Re: PathWorks running on OpenVMS 7.3-2

Karl Rohwedder — Wed, 02 Nov 2005 00:57:58 GMT

Jasper,

this seems to be the right forum.
Some questions:
- which version of Pathworks (or is it AdvancedServer really)?
- which security model (LANmanager or (LANman and VMS))?
- pls. post a SHOW SHARE/FULL ... of the share you created

Normally a new share gets the EVERYONE:F protection, i.e. every user in the domain can access the share. But if you specify both LAnman and VMS security, the users a mapped to VMS accounts and these account must have also permission to access the share. The latter is often used, if users are accessing files both from VMS and from PC's.

You can check the security scheme using ADMIN/CONFIG and the selecting ADVANCED.

regards Kalle

Re: PathWorks running on OpenVMS 7.3-2

Andy Bustamante — Wed, 02 Nov 2005 13:40:09 GMT

If none of your users can see a new share then you probably have a protection issue as Karl states above.

If these are new users, you should also check that you have enough Pathworks License units available to allow these users to connect to a share.

$ admin/license

will display the current state of license allocations on a system.

Andy

Re: PathWorks running on OpenVMS 7.3-2

Jasper_15 — Wed, 02 Nov 2005 23:02:38 GMT

You guys are GOOD!! Yes, the main folder/dir was set to READ only and nothing else. I left it that way and created a G-ALPHA group and stuck those users in there and everything seems to work. By the way, I am using the Advance server version and I access via VMS & network.

Guys, thanks for your help!!

Jasper

Re: PathWorks running on OpenVMS 7.3-2

Jasper_15 — Thu, 03 Nov 2005 00:24:38 GMT

Hi, again.

How would you go about adding a group to a share folder? Please see example below.

OCS\\Raider> show share dsp /full

Shared resources on server "RAIDER":

Name Type Description
------------ --------- -------------------------------------------------------
DSP Directory DSP Homedir
Path: DISK31:[DSP]
Connections: Current: 0, Maximum: No limit
RMS file format: Stream
Directory Permissions: System: RWED, Owner: RWED, Group: RWED, World: RE
File Permissions: System: RWD, Owner: RWD, Group: RWD, World: R
Share Permissions:
Domain Admins Full Control
Everyone Read
G-Alpha Source Admin Full Control
G-Alpha Source Save Change

Total of 1 share
I would like to add this group of users
G-IS-DP Change

Please let me know on how to add & modify from read to read & change permission.

Many Thanks!!

Jasper

Re: PathWorks running on OpenVMS 7.3-2

Mike Reznak — Thu, 03 Nov 2005 02:05:14 GMT

Hi,
this is the help for modifying share permission.

MODIFY

SHARE

/PERMISSIONS

/PERMISSIONS=([domain-name\]name=access[,...])
/NOPERMISSIONS

Specifies the access permissions for the directory share. These
permissions control network access to the directory share, and
determine which users or groups can access the shared directory,
and the type of access they are allowed. When a directory is
shared, the default is to grant FULL access to everyone. This
permission allows anyone to do anything they wish to any of the
files or subdirectories in the directory tree.

Use the /PERMISSIONS qualifier to add permissions to a resource
for specified users or groups. Use the /NOPERMISSIONS qualifier
to remove all permissions for all or specified users or groups.
If you remove all permissions from a share, no one will be able
to access it, and only the owner will be able to change the
permissions.

The permissions list name=access is a list of users and
groups allowed to access the shared resource, and the type of
access granted to each user or group. It must be enclosed in
parentheses, and consists of one or more name=access pairs, where
name can be any valid user or group name from this or another
trusted domain.

To specify a user or group name in a trusted domain, enter the
domain-qualified name (domain-name\name), such as KANSAS\DOLE,
where KANSAS is the name of the trusted domain, and DOLE is the
user or group name defined in the trusted domain. If you omit the
domain name, the user account or group is assumed to be defined
in the domain of the server currently being administered.

Access depends on the type of share being modified.

If the share is a directory share, access can be any one of the
following:

Access Description

NONE Prevents any access to the shared directory, its
subdirectories, and their files
READ Allows viewing file names and subdirectory names,
traversing to subdirectories, viewing data in files,
and running applications
CHANGE Allows viewing file names and subdirectory names,
traversing to subdirectories, viewing data in files,
running applications, adding files and subdirectories,
changing data in files, and deleting subdirectories and
files
FULL Allows viewing file names and subdirectory names,
traversing to subdirectories, viewing data in files,
running applications, adding files and subdirectories,
changing data in files, deleting subdirectories and
files, changing file and directory permissions, and
taking ownership of files and directories

If the share is a print share, access can be any one of the
following:

Access Description

NONE Prevents any access to the printer
PRINT Allows printing of documents
MANAGE_DOCUMENTS
Allows holding, releasing, and deleting of print jobs,
and changing the order in which jobs print
FULL Allows printing of documents; holding, releasing, and
deleting of print jobs; changing the order in which
jobs print; aborting and restarting of jobs being
printed; pausing, continuing, and purging of the print
queue; changing of print queue settings; removal of the
print queue; and changing of print resource permissions.

Mike

Re: PathWorks running on OpenVMS 7.3-2

Jan van den Ende — Thu, 03 Nov 2005 02:20:26 GMT

Jasper,

your second question:

$ ADMIN MODI SHARE /PERM=<...>

Proost.

Have one on me.

jpe

Re: PathWorks running on OpenVMS 7.3-2

Edwin Gersbach_2 — Thu, 03 Nov 2005 07:05:12 GMT

Notice however that you need domain admin rights to add group permissions.

I'm in the situation that I have only user rights in the domain. I can add share permissions for a user and I can list all the groups in the domain, but when I try to add share permissions for a group, it complains 'no such user' or something to that extent.

Gone have the days when we had full control over our VMS systems :-)

Edwin