Lizette, I checked there were no IGD messages. I did a double check, none of the volumes in that group are SMS or CA-ALLOCATE managed.
--- On Thu, 6/24/10, Lizette Koehler <[email protected]> wrote: From: Lizette Koehler <[email protected]> Subject: Re: QUESTION ABOUT STOPX-37 - MAINVIEW SRM To: [email protected] Received: Thursday, June 24, 2010, 5:53 AM Is DFSMS doing this? Do you use an ACS code that might change the location of the volume? Look for IGD messages in the job messages section after the JCL. Lizette > >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 <[email protected]> wrote: > > >From: Spencer, Mike <[email protected]> >Subject: Re: QUESTION ABOUT STOPX-37 - MAINVIEW SRM >To: [email protected] >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:[email protected]] On Behalf Of >Mark Steely >Sent: Wednesday, June 23, 2010 12:34 PM >To: [email protected] >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:[email protected]] On Behalf Of >esmie moo >Sent: Wednesday, June 23, 2010 11:22 AM >To: [email protected] >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 [email protected] 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 [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
