The following additional general conditions must be observed for Node-Files:
Only files of the type *NODE-FILE, the so-called node files, are permitted for interoperability with open systems.
Files of the type *BS2000 must not be changed by open systems!
Access to PAM node files requires BS2000 OSD/BC V10.0 or higher.
Access to SAM node files requires BS2000 OSD/BC V11.0 or higher.
Node files are structureless. The end at byte boundary.
As seen from BS2000, only the following files can become node files:
PAM files without a PAM key (BLKCTRL=NO)
SAM files with block control information and variable record length
(BLKCTRL=DATA, RECFORM=V)
Node files are created in user-specific directories. These are generated automatically by BS2000 the first time a node file is created and supplied with the necessary POSIX ACLs. Subsequently authorized users can access the directory and the node files it contains from both BS2000 and from open systems.
Access rights and protection attributes in BS2000 can also be set for node files as usual (access right (ACCESS), shareability (USER-ACCESS), access control, passwords), see, for example, the MODIFY-FILE-ATTRIBUTES command in the "Commands" manual [27]. They apply for BS2000, but not for open systems.
Node files which are created by open systems must be imported before they are used in BS2000.
The BS2000 command LIST-NODE-FILES informs a user of the node files in his/her user-specific directory.
In UFS, node files have the access rights
rw- --- ---.
These are the minimum access rights which BS2000 requires for a user of this type. A user of the open system may change these access rights. A BS2000 user may not do this.Users from open systems obtain access to node files through their user and group numbers (uid, gid).