We get a console message every time StopX37 does a recovery for us. I'd expect to see some of them in the joblog for your allocating job. They all start with SVM. Although cryptic, if you understand StopX, they'll tell you what actions it performed and/or attempted.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of esmie moo Sent: Wednesday, June 23, 2010 11:22 AM To: IBM-MAIN@bama.ua.edu Subject: QUESTION ABOUT STOPX-37 - MAINVIEW SRM Good Morning Gentle Readers, I am trying to trouble shoot a problem which may be related to StopX37. The user is creating a VSAM file and is specifying the VOLSER. For some reason the dsn is being allocated on another volume. The environment does NOT have SMS or CA-ALLOCATE or any other software except for StopX37 which raises my suspicion. If somebody is familiar with StopX37 could you point me to look at the specific parm in the StopX37 Parmlib. Thanks in advance. ---------------------------------------------------------------------- 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 Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any system and destroy any copies. (GWCC) ---------------------------------------------------------------------- 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
