You're welcome. If there are no SVM* messages on the original allocation, then StopX37/II is probably not involved. StopX37/II by itself does not determine the volume for allocation. This would be in the IBM OS SRM (System Resource Manager) algorithms. Part of the SVM message text will display the type of StopX37/II Function that is being invoked. Something similar to the following: SVM4855I SET SECONDARY SPACE USING 50% OF PRIMARY ( 2 CYLS) : 1 CYLS
When you increased the allocation amount from 1 cyl to 5000, StopX37/II would have been invoked to prevent the allocation from abending, either on the initial allocation request or as part of the EOV call when the allocation ran out of space. Your Eligible Device Table (EDT) is used for the esoteric definitions. The user can code a volser in the JCL, but the UNIT parameter in the JCL will first determine the volume(s) to be used during allocation based on the volumes defined to the esoteric. IBM SRM selects the volume for allocation. I would check the UNIT parameter being used, and determine the volumes that are eligible to be used for that esoteric. One last item is volume level security. I do not see it much anymore, but there are locations that still use it to prevent certain volumes from being used by unauthorized users. You can directly email me the information in the users joblog. Mike Spencer BMC Software -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of esmie moo Sent: Wednesday, June 23, 2010 1:44 PM To: IBM-MAIN@bama.ua.edu Subject: Re: QUESTION ABOUT STOPX-37 - MAINVIEW SRM Mike, Thanks for clearing this up. I looked at the job which created the dsns but there was no SVM* messages displayed. I ran a test and when I increased the size from 1 cyl to 5000, the SVM messages were displayed. My question is what rule is bypassing the allocation. I verified my jcl and I do not have any parms to bypass the volser. --- On Thu, 6/24/10, Spencer, Mike <mike_spen...@bmc.com> wrote: From: Spencer, Mike <mike_spen...@bmc.com> Subject: Re: QUESTION ABOUT STOPX-37 - MAINVIEW SRM To: IBM-MAIN@bama.ua.edu Received: Thursday, June 24, 2010, 5:11 AM StopX37 is NOT CA-Allocate. Two different vendors. Please post facts, not postulates. You can bypass StopX37 routines by coding a DD DUMMY statement in the users job to determine the outcome of the allocation without StopX37/II being involved. Unless you have changed the value in the StopX37/II Global Member, the statement to code would be //PROIGN DD DUMMY. The //NOPLD DD DUMMY is a holdover from the original StopX37 and POOLDASD products back in the Empact Software days. Folks still use it by changing the Global Member parameter of IGNOREDD=PROIGN to IGNOREDD=NOPLD. In addition, unless messaging is turned off or the message prefix has been changed by the user, the joblog should display a message prefix of SVM* whenever StopX37 is invoked to take an action. Mike Spencer BMC Software -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Steely Sent: Wednesday, June 23, 2010 12:34 PM To: IBM-MAIN@bama.ua.edu Subject: Re: QUESTION ABOUT STOPX-37 - MAINVIEW SRM Stop X37 is now CA-Allocate which controls allocation of files. Look at the started task under SDSF and look for this message: CA Allocate ASR ROUTINE IS..... This will display the library with all the routines that are getting executed. The answer should be there. Thank You -----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 ******* CONFIDENTIALITY NOTICE ******* This e-mail message and all attachments transmitted with it may contain legally privileged and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message from your system. Thank you. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
