You surely can work with multiple systems programmers on z/VM, even without SFS. Just don't use MAINT all the time, use your own userid and use LINK & ACCESS to get access to the minidisks you need at a given time. Give you own userids the same CP classes as MAINT has. We worked like this at my former customer's installation for 20 years. Examples - at the time we didn't have DIRMAINT yet, we wrote the DRMAC EXEC It LINKs to the place of USER DIRECT, R/W if possible, ACCESS the disk start DRM USER DIRECT, at the end DETACH the linked to minidisk - We had our own VMLINK like exec: LNK to LINK and ACCESS, examples LNK MAINT (FD --> links to MAINT 191, starts FILELIST and DETACH at end LNK MAINT (MFD --> Same, but we links with mode MR LNK MAINT 193 --> Links and accesses MAINT 193 and keep it LNK MAINT 293 555 M pw Z --> just like CP LINK, but it ACCESSes as Z
You just need to make sure you don't keep MDISKS linked R/W when not needing them. 2009/5/21, Fred Schmidt <fred.schm...@nt.gov.au>: > > > > Hi Listers, > > What do you recommend as a solution to allow more than one person to fulfil > the role of making changes to z/VM system configuration files such as SYSTEM > CONFIG and USER DIRECT? > > Up until now, it has been just me making changes to z/VM. But now I have an > offsider and we would both like to work on a z/VM system at the same time. > > I have tried defining a second user and LINK’ing to MAINT’s minidisks. That > only allows read access if MAINT is already logged on. > > SFS sounded like a possible alternative, to share at the file level instead > of at the minidisk level. However, a quick trawl of the Listserver seems to > say that this is a lot of work to setup and administer. And I am loath to > make major changes to MAINT’s minidisks without understanding the > implications, especially if I will have to re-do this work at each new > install of z/VM. > > Regards, > > Fred Schmidt > > NT Government, Australia > > > > -- Kris Buelens, IBM Belgium, VM customer support
