I can agree that OMVS segments should usually have their own directory. It would be possible to have them share a common directory, but in that case you would usually want to make it ready only, which would prevent some z/OS Unix stuff from working but not, AFAIK, FTP.
But in order to have complete control over FTP access, you may want to implement a FTCHKCMD exit. See the z/OS Comm Server documentation for details; a sample is provided by IBM. Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Mar 20, 2012 at 1:01 PM, Bruce Wheatley <bwheat...@cds.ca> wrote: > We have numerous external clients and on occasion have found that > depending on what product they use for FTP, their file transfer may in some > fashion refer to our root directory or potentially the file transfer client > being used defaults to a root directory. > > In order to prevent such access we’re planning to change each userid’s > OMVS segment to have a HOME directory of: /u/userid. (Currently we just use > ‘ / ’.) > > Anyone know of any gotchas with this plan? > > TIA > > (Posted on both RACF & IBM-Main lists) > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
