Newsgroups: comp.lang.apl
Path: watmath!watserv1!70530.1226@compuserve.com
From: Mike Kent <70530.1226@CompuServe.COM>
Subject: Component files and access
Message-ID: <920322064044_70530.1226_CHC101-1@CompuServe.COM>
Sender: root@watserv1.waterloo.edu (Operator)
Organization: University of Waterloo
Date: Sun, 22 Mar 1992 06:40:45 GMT
Lines: 20

[Further comment on Steve Wu's problem accessing APL files]


In all the mainframe component file systems for varous APLs, changing
your userid to match a file's library number is _useless_.  The file
systems themselves keep a table matching _host system_ userid's to
enrolled filesystem userids, filesystem libraries, etc.  Changing the
userid by which you identify your session to the APL system has no effect
because as far as the filesystem  is concerned, you're still known by
your host system moniker.

The STSC mainframe fileserver for APL2 (ShareFile/AP) provides a
filesystem function FUSERNO which returns the user/[default] library
number for the active session.  It is different for each VM userid, _but_
if you are user APL1234 enrolled in the filesystem as user 1234, starting
up APL2 with userid 5678 changes only the first item of []AI; FUSERNO will
still return 1234, and you will _not_ be able to access files in library
5678 unless these files' access matrices have been set to allow you (or
the general public) to use them.

