Another thought might be an automation solution. If the IEF message has FTP in the statement for this specific mount or there is a way to determine that this flavor is for FTP, then you could have automation (like OPS/MVS) trap the messages and automatically reply CANCEL.
Lizette > Fred Schmidt Wrote: routines > > Issued: Error! Unknown document property name. iii > > We are seeing... > > IEF244I ZZZ STEP1 - UNABLE TO ALLOCATE 1 UNIT(S) 969 > AT LEAST 1 OFFLINE UNIT(S) NEEDED. > IEF877E ZZZ NEEDS 1 UNIT(S) 970 > FOR STEP1 SYS00001 > FOR VOLUME PRIVAT- 1 > OFFLINE > 1004-1007 1011-1012 1027-1028 102E-1033 1035-1039 103B-103D 1042-1049 > IEF878I END OF IEF877E FOR ZZZ STEP1 SYS00001 > 05 IEF238D ZZZ - REPLY DEVICE NAME OR 'CANCEL'. > > ... when FTP'ing from userid=ZZZ a file to the mainframe named > ZZZ.TEST.DATA. It fails because the request is for a non-SMS allocation > with no VOLSER specified and we do not have any volumes mounted STORAGE. > > 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. > > I've tried setting a DFP segment for userid ZZZ, with STORCLAS= > FAILALOC and in the STORCLAS routine coding ... > > WHEN ((&DSOWNER = '') OR (&DEF_STORCLAS = 'FAILALOC')) > DO > SET &STORCLAS = '' > WRITE 'DATASET ALLOCATION FAILED' > WRITE 'HIGH LEVEL QUALIFIER (HLQ) IS NOT DEFINED' > WRITE 'PLEASE CONTACT YOUR SECURITY ADMINISTRATOR' > EXIT CODE(0) > END > > This works as intended for allocations via TSO/Batch. But it does not > prevent the WTOR for FTP's. > > Is there some way that I can prevent the WTOR for FTP using SMS? Or do > I have to use ALLOCxx to cancel all allocation requests? I would rather > not, as this has implications for all allocations and it is only FTP > that has the problem. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
