The choice of LINK mode depends on what you want to accomplish. Consider not only how the choice affects your program, but those running in other virtual machines that might have it linked.
It is funny to see a program that has a comment “get disk in RW mode” and then use MR and dealing with the aftermath. When you need it RW, getting it RO doesn’t help. Regards, Alan Alan Altmark Senior z/VM Engineer and Consultant IBM Infrastructure Endicott, NY USA > On Dec 31, 2024, at 8:24 PM, Berry van Sleeuwen <berry.vansleeu...@xs4all.nl> > wrote: > > Indeed I would say you use either W or R. Never use M unless you know what > you're doing. And do not to link in write mode unless you actually need to > write. For instance if you link the 190 disk in write mode it will invalidate > your CMS segment and you need to resave CMS to be able to use the segment. We > used to have an exec to link disks the easy way (GETDISK <user> <vdev>) and > theat used write mode by default. I have changed that to read mode and option > (WRITE if I actually want a write link. > > I prefer minidisks to have linkmode WR instead of MR to prevent multiple > write link except when Multiple is actually required and supported by the OS > (VSE for example, with MWV). This way you can never get a multiple link by > accident. The same goes for the passwords, only specify the Multiple password > if you actually expect to use Multiple. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
