On Monday, 04/06/2015 at 02:18 EDT, Rob van der Heij <[email protected]> wrote: > Minidisk passwords are in the directory and can be set when you issue the > amdisk or afterwards. If you have racf you use that. > But you may want to rethink that approach from a security point of view.
If the purpose is to allow anyone to read the disk, then use a minidisk READ password of ALL. If you want to restrict access, then Mike's recommendation to put a LINK in each student's directory entry is preferred instead of assigning a READ password. After all, how do you know who has the read password? If an ESM is being used to protect minidisks, passwords aren't used and placing a LINK in the directory is not sufficient. To assure data integrity: 1. Never place an MW LINK in a CMS user's directory, unless you (the sysprog) understand why such access is need and you concur. (PSF/VM was the last product I saw that understood how to manage MW CMS minidisks properly.) 2. Place an MW LINK in a Linux user's directory only for minidisks managed by gpfs or other concurrent-write filesystem. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems & Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 [email protected] IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
