For such file transfers, we do not allow access to anything but the HLQ that matches the ID. Later, a production process picks up the file and copies/renames/whatever. Works great.
You might try removing the alias from the master catalog or blocking access to specific user catalogs. Don't know if that will fail the allocation soon enough to prevent the WTOR, but it is easy enough to find out. That assumes, of course, that your master cat is suitably protected. -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Denis Gäbler Sent: Thursday, April 29, 2010 8:50 AM To: IBM-MAIN@bama.ua.edu Subject: Re: REPLY DEVICE NAME OR 'CANCEL' for FTP to mainframe and SMS ACS routines You are right, but quoting his initial post, I assumed that those FTP userids do not use USS. We want the allocation to fail, as we don't want these FTP userids to create datasets under their own HLQ, only transfer other files. But we don't want the WTOR. NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
