Has anybody using STOPX37 seen a problem where it gets in a loop fighting with SMS over an insufficient space condition? Anybody have suggestions on how to avoid it?
Details: A process is submitted via CONNECT:Direct (aka NDM) specifying SMS STORCLAS, MGMTCLAS, and DATACLAS that result in selection of volumes with too little space for the dataset being transfered. 1. SMS says IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE FOR DATASET ... 2. STOPX37 says SVM4000I ... ATTEMPTING SPACPRIM FOR ... 3. SMS repeats indefinitely IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE FOR DATASET ... Is there some way to cause a hard failure in situations like this? I don't think CONNECT:Direct is significant in this except that this request is coming from an outside business partner. We have absolutely no control over the size of the dataset or SMS parms specified. BTW, SMS and STOPX37 are way out of my areas of responsibility and expertise. I'm going to have to convey any suggestions to others that don't read IBM-Main. Don't assume comprehension on my part. Pat O'Keefe ---------------------------------------------------------------------- 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
